Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,7 +4,7 @@ 4 4 5 5 == 4.1 Introduction == 6 6 7 -The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are: 7 +The structures that are an arrangement of objects into [[hierarchies>>doc:xwiki:Glossary.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are: 8 8 9 9 Codelist 10 10 ConceptScheme ... ... @@ -18,7 +18,7 @@ 18 18 CustomTypeScheme 19 19 VtlMappingScheme 20 20 21 -Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15). 21 +Note that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15). 22 22 23 23 == 4.2 Inheritance View == 24 24 ... ... @@ -36,19 +36,30 @@ 36 36 37 37 ==== 4.3.2.1 Narrative ==== 38 38 39 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: d uriurn version validFrom validTo isExternalReference serviceURL structureURLisPartial39 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 40 40 41 -The Code inherits from //Item// and has the following attributes: 41 +id 42 +uri 43 +urn 44 +version 45 +validFrom 46 +validTo 47 +isExternalReference 48 +serviceURL 49 +structureURL 50 +isPartial 42 42 43 -id uriurn52 +The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 44 44 45 -Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown). 54 +id 55 +uri 56 +urn 46 46 47 - Throughtheinheritance theCodelistcompriseoner moreCodes, and theCodeitself canhaveone or morechild Codesin the(inherited) hierarchy association.NotethatachildCodecanhaveonlyoneparent Codeinthisassociation.A morecomplex Hierarhcy,which allowsmultiple parentsis describedlater.58 +Both Codelist and [[Code>>doc:xwiki:Glossary.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:xwiki:Glossary.Annotation.WebHome]] to support notes (not shown). 48 48 49 - A partialCodelist(where isPartial issetto'true')isidenticaltolistand containstheCode and associatednamesand descriptions, justasin a normalCodelist.However,its contentis aubsetfthefull Codelist.Thewaythisworks is describedin section 3.5.3.1 on60 +Through the inheritance the Codelist comprise one or more [[Codes>>doc:xwiki:Glossary.Code.WebHome]], and the [[Code>>doc:xwiki:Glossary.Code.WebHome]] itself can have one or more child [[Codes>>doc:xwiki:Glossary.Code.WebHome]] in the (inherited) [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:xwiki:Glossary.Code.WebHome]] can have only one parent [[Code>>doc:xwiki:Glossary.Code.WebHome]] in this association. A more complex Hierarhcy, which allows multiple parents is described later. 50 50 51 -//ItemScheme//. 62 +A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the [[Code>>doc:xwiki:Glossary.Code.WebHome]] and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//. 52 52 53 53 ==== 4.3.2.2 Definitions ==== 54 54 ... ... @@ -75,14 +75,12 @@ 75 75 76 76 ==== 4.3.3.1 Narrative ==== 77 77 78 -A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending ^^[[(%class="wikiinternallinkwikiinternallinkwikiinternallinkwikiinternallink"%)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.89 +A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending{{footnote}}The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).{{/footnote}} Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists. 79 79 80 80 The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a ,,Code,,, including its children ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers. 81 81 82 82 ==== 4.3.3.2 Definitions ==== 83 83 84 -: 85 - 86 86 ((( 87 87 (% style="width:753.039px" %) 88 88 |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description** ... ... @@ -102,7 +102,7 @@ 102 102 103 103 === 4.3.4 Class Diagram – Geospatial Codelist === 104 104 105 -The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.114 +The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams. 106 106 107 107 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]] 108 108 ... ... @@ -117,7 +117,6 @@ 117 117 A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property: 118 118 119 119 GeographicCodelist 120 - 121 121 GeoGridCodelist 122 122 123 123 The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set. ... ... @@ -139,9 +139,7 @@ 139 139 ))) 140 140 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)((( 141 141 Abstract Class Sub Classes: 142 - 143 143 GeoFeatureSet 144 - 145 145 GeoGridCode 146 146 )))|The abstract class that represents a special type of Code, which includes geospatial information. 147 147 |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies. ... ... @@ -166,7 +166,16 @@ 166 166 167 167 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes: 168 168 169 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL 175 +id 176 +uri 177 +urn 178 +version 179 +validFrom 180 +validTo 181 +isExternalReference 182 +registryURL 183 +structureURL 184 +repositoryURL 170 170 171 171 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former. 172 172 ... ... @@ -199,10 +199,26 @@ 199 199 200 200 === 4.5.2 Explanation of the Diagram === 201 201 202 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:217 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 203 203 204 -id uri urn 219 +id 220 +uri 221 +urn 222 +version 223 +validFrom 224 +validTo 225 +isExternalReference 226 +registryURL 227 +structureURL 228 +repositoryURL 229 +isPartial 205 205 231 +Concept inherits from Item and has the following attributes: 232 + 233 +id 234 +uri 235 +urn 236 + 206 206 Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown). 207 207 208 208 Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association. ... ... @@ -233,12 +233,10 @@ 233 233 |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description** 234 234 |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)((( 235 235 Inherits from 236 - 237 237 //ItemScheme// 238 238 )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 239 239 |(% style="width:204px" %)Concept|(% style="width:222px" %)((( 240 240 Inherits from 241 - 242 242 //Item// 243 243 )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 244 244 |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept. ... ... @@ -267,11 +267,22 @@ 267 267 268 268 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 269 269 270 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial 299 +id 300 +uri 301 +urn 302 +version 303 +validFrom 304 +validTo 305 +isExternalReference 306 +structureURL 307 +serviceURL 308 +isPartial 271 271 272 272 Category inherits from //Item// and has the following attributes: 273 273 274 -id uri urn 312 +id 313 +uri 314 +urn 275 275 276 276 Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model). 277 277 ... ... @@ -293,19 +293,16 @@ 293 293 |**Class**|(% colspan="2" %)**Feature**|**Description** 294 294 |CategoryScheme|(% colspan="2" %)((( 295 295 Inherits from 296 - 297 297 //ItemScheme// 298 298 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 299 299 | |(% colspan="2" %)/items|Associates the categories. 300 300 |Category|((( 301 301 Inherits from 302 - 303 303 //Item// 304 304 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 305 305 | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category. 306 306 |Categorisation|((( 307 307 Inherits from 308 - 309 309 //MaintainableArtefact// 310 310 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category. 311 311 | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact. ... ... @@ -343,17 +343,12 @@ 343 343 |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description** 344 344 |//OrganisationScheme//|(% style="width:246px" %)((( 345 345 Abstract Class Inherits from 346 - 347 347 //ItemScheme// 348 348 349 349 Sub classes are: 350 - 351 351 AgencyScheme 352 - 353 353 DataProviderScheme 354 - 355 355 MetadataProviderScheme DataConsumerScheme 356 - 357 357 OrganisationUnitScheme 358 358 )))|(% style="width:336px" %)A maintained collection of Organisations. 359 359 | |(% style="width:246px" %)/items|(% style="width:336px" %)((( ... ... @@ -363,19 +363,12 @@ 363 363 ))) 364 364 |//Organisation//|(% style="width:246px" %)((( 365 365 Abstract Class 398 +Inherits from //Item// 366 366 367 -Inherits from 368 - 369 -//Item// 370 - 371 371 Sub classes are: 372 - 373 373 Agency 374 - 375 375 DataProvider 376 - 377 377 MetadataProvider DataConsumer 378 - 379 379 OrganisationUnit 380 380 )))|(% style="width:336px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 381 381 | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information. ... ... @@ -401,27 +401,22 @@ 401 401 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme. 402 402 |Agency|(% style="width:246px" %)((( 403 403 Inherits from 404 - 405 405 //Organisation// 406 406 )))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 407 407 |DataProvider|(% style="width:246px" %)((( 408 408 Inherits from 409 - 410 410 //Organisation// 411 411 )))|(% style="width:336px" %)An organisation that produces data. 412 412 |MetadataProvider|(% style="width:246px" %)((( 413 413 Inherits from 414 - 415 415 //Organisation// 416 416 )))|(% style="width:336px" %)An organisation that produces reference metadata. 417 417 |DataConsumer|(% style="width:246px" %)((( 418 418 Inherits from 419 - 420 420 //Organisation// 421 421 )))|(% style="width:336px" %)An organisation using data as input for further processing. 422 422 |OrganisationUnit|(% style="width:246px" %)((( 423 423 Inherits from 424 - 425 425 //Organisation// 426 426 )))|(% style="width:336px" %)A designation in the organisational structure. 427 427 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units ... ... @@ -462,13 +462,11 @@ 462 462 |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description** 463 463 |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)((( 464 464 Inherits from 465 - 466 466 //ItemScheme// 467 467 )))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow. 468 468 |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category 469 469 |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)((( 470 470 Inherits from 471 - 472 472 //Item// 473 473 )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata. 474 474 |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category. ... ... @@ -476,3 +476,5 @@ 476 476 |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)((( 477 477 Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 478 478 ))) 497 + 498 +{{putFootnotes/}}