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,33 +4,21 @@ 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 - 11 11 ConceptScheme 12 - 13 13 CategoryScheme 14 - 15 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, 16 - 17 -DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 18 - 12 +AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 19 19 ReportingTaxonomy 20 - 21 21 TransformationScheme 22 - 23 23 RulesetScheme 24 - 25 25 UserDefinedOperatorScheme 26 - 27 27 NamePersonalisationScheme 28 - 29 29 CustomTypeScheme 30 - 31 31 VtlMappingScheme 32 32 33 -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). 34 34 35 35 == 4.2 Inheritance View == 36 36 ... ... @@ -48,19 +48,30 @@ 48 48 49 49 ==== 4.3.2.1 Narrative ==== 50 50 51 -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]]: 52 52 53 -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 54 54 55 -id uriurn52 +The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 56 56 57 -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 58 58 59 - 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). 60 60 61 - 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. 62 62 63 -//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//. 64 64 65 65 ==== 4.3.2.2 Definitions ==== 66 66 ... ... @@ -87,14 +87,12 @@ 87 87 88 88 ==== 4.3.3.1 Narrative ==== 89 89 90 -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="wikiinternallinkwikiinternallinkwikiinternallink"%)^^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. 91 91 92 92 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. 93 93 94 94 ==== 4.3.3.2 Definitions ==== 95 95 96 -: 97 - 98 98 ((( 99 99 (% style="width:753.039px" %) 100 100 |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description** ... ... @@ -114,7 +114,7 @@ 114 114 115 115 === 4.3.4 Class Diagram – Geospatial Codelist === 116 116 117 -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. 118 118 119 119 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]] 120 120 ... ... @@ -129,7 +129,6 @@ 129 129 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: 130 130 131 131 GeographicCodelist 132 - 133 133 GeoGridCodelist 134 134 135 135 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. ... ... @@ -151,9 +151,7 @@ 151 151 ))) 152 152 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)((( 153 153 Abstract Class Sub Classes: 154 - 155 155 GeoFeatureSet 156 - 157 157 GeoGridCode 158 158 )))|The abstract class that represents a special type of Code, which includes geospatial information. 159 159 |(% 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. ... ... @@ -178,7 +178,16 @@ 178 178 179 179 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes: 180 180 181 -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 182 182 183 183 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former. 184 184 ... ... @@ -211,10 +211,26 @@ 211 211 212 212 === 4.5.2 Explanation of the Diagram === 213 213 214 -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: 215 215 216 -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 217 217 231 +Concept inherits from Item and has the following attributes: 232 + 233 +id 234 +uri 235 +urn 236 + 218 218 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). 219 219 220 220 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. ... ... @@ -245,12 +245,10 @@ 245 245 |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description** 246 246 |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)((( 247 247 Inherits from 248 - 249 249 //ItemScheme// 250 250 )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 251 251 |(% style="width:204px" %)Concept|(% style="width:222px" %)((( 252 252 Inherits from 253 - 254 254 //Item// 255 255 )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 256 256 |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept. ... ... @@ -279,11 +279,22 @@ 279 279 280 280 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 281 281 282 -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 283 283 284 284 Category inherits from //Item// and has the following attributes: 285 285 286 -id uri urn 312 +id 313 +uri 314 +urn 287 287 288 288 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). 289 289 ... ... @@ -305,19 +305,16 @@ 305 305 |**Class**|(% colspan="2" %)**Feature**|**Description** 306 306 |CategoryScheme|(% colspan="2" %)((( 307 307 Inherits from 308 - 309 309 //ItemScheme// 310 310 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 311 311 | |(% colspan="2" %)/items|Associates the categories. 312 312 |Category|((( 313 313 Inherits from 314 - 315 315 //Item// 316 316 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 317 317 | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category. 318 318 |Categorisation|((( 319 319 Inherits from 320 - 321 321 //MaintainableArtefact// 322 322 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category. 323 323 | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact. ... ... @@ -355,17 +355,12 @@ 355 355 |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description** 356 356 |//OrganisationScheme//|(% style="width:246px" %)((( 357 357 Abstract Class Inherits from 358 - 359 359 //ItemScheme// 360 360 361 361 Sub classes are: 362 - 363 363 AgencyScheme 364 - 365 365 DataProviderScheme 366 - 367 367 MetadataProviderScheme DataConsumerScheme 368 - 369 369 OrganisationUnitScheme 370 370 )))|(% style="width:336px" %)A maintained collection of Organisations. 371 371 | |(% style="width:246px" %)/items|(% style="width:336px" %)((( ... ... @@ -375,19 +375,12 @@ 375 375 ))) 376 376 |//Organisation//|(% style="width:246px" %)((( 377 377 Abstract Class 398 +Inherits from //Item// 378 378 379 -Inherits from 380 - 381 -//Item// 382 - 383 383 Sub classes are: 384 - 385 385 Agency 386 - 387 387 DataProvider 388 - 389 389 MetadataProvider DataConsumer 390 - 391 391 OrganisationUnit 392 392 )))|(% 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. 393 393 | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information. ... ... @@ -413,27 +413,22 @@ 413 413 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme. 414 414 |Agency|(% style="width:246px" %)((( 415 415 Inherits from 416 - 417 417 //Organisation// 418 418 )))|(% 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. 419 419 |DataProvider|(% style="width:246px" %)((( 420 420 Inherits from 421 - 422 422 //Organisation// 423 423 )))|(% style="width:336px" %)An organisation that produces data. 424 424 |MetadataProvider|(% style="width:246px" %)((( 425 425 Inherits from 426 - 427 427 //Organisation// 428 428 )))|(% style="width:336px" %)An organisation that produces reference metadata. 429 429 |DataConsumer|(% style="width:246px" %)((( 430 430 Inherits from 431 - 432 432 //Organisation// 433 433 )))|(% style="width:336px" %)An organisation using data as input for further processing. 434 434 |OrganisationUnit|(% style="width:246px" %)((( 435 435 Inherits from 436 - 437 437 //Organisation// 438 438 )))|(% style="width:336px" %)A designation in the organisational structure. 439 439 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units ... ... @@ -474,13 +474,11 @@ 474 474 |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description** 475 475 |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)((( 476 476 Inherits from 477 - 478 478 //ItemScheme// 479 479 )))|(% 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. 480 480 |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category 481 481 |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)((( 482 482 Inherits from 483 - 484 484 //Item// 485 485 )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata. 486 486 |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category. ... ... @@ -488,3 +488,5 @@ 488 488 |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)((( 489 489 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. 490 490 ))) 497 + 498 +{{putFootnotes/}}