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,7 +36,7 @@ 36 36 37 37 ==== 4.3.2.1 Narrative ==== 38 38 39 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: 39 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 40 40 41 41 id 42 42 uri ... ... @@ -49,20 +49,18 @@ 49 49 structureURL 50 50 isPartial 51 51 52 -The Code inherits from //Item// and has the following attributes: 52 +The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 53 53 54 54 id 55 55 uri 56 56 urn 57 57 58 -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). 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). 59 59 60 -Through the inheritance the Codelist comprise one or more Codes, and the Code itself can have one or more child Codes in the (inherited) hierarchy association. Note that a child Code can have only one parent Code in this association. A more complex Hierarhcy, which allows multiple parents is described later. 60 +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. 61 61 62 -A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the Code 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 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//. 63 63 64 -//ItemScheme//. 65 - 66 66 ==== 4.3.2.2 Definitions ==== 67 67 68 68 (% style="width:743.039px" %) ... ... @@ -113,7 +113,7 @@ 113 113 114 114 === 4.3.4 Class Diagram – Geospatial Codelist === 115 115 116 -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. 117 117 118 118 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]] 119 119 ... ... @@ -128,7 +128,6 @@ 128 128 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: 129 129 130 130 GeographicCodelist 131 - 132 132 GeoGridCodelist 133 133 134 134 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. ... ... @@ -150,9 +150,7 @@ 150 150 ))) 151 151 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)((( 152 152 Abstract Class Sub Classes: 153 - 154 154 GeoFeatureSet 155 - 156 156 GeoGridCode 157 157 )))|The abstract class that represents a special type of Code, which includes geospatial information. 158 158 |(% 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. ... ... @@ -177,7 +177,16 @@ 177 177 178 178 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes: 179 179 180 -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 181 181 182 182 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former. 183 183 ... ... @@ -210,10 +210,26 @@ 210 210 211 211 === 4.5.2 Explanation of the Diagram === 212 212 213 -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: 214 214 215 -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 216 216 231 +Concept inherits from Item and has the following attributes: 232 + 233 +id 234 +uri 235 +urn 236 + 217 217 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). 218 218 219 219 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. ... ... @@ -244,12 +244,10 @@ 244 244 |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description** 245 245 |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)((( 246 246 Inherits from 247 - 248 248 //ItemScheme// 249 249 )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 250 250 |(% style="width:204px" %)Concept|(% style="width:222px" %)((( 251 251 Inherits from 252 - 253 253 //Item// 254 254 )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 255 255 |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept. ... ... @@ -278,11 +278,22 @@ 278 278 279 279 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 280 280 281 -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 282 282 283 283 Category inherits from //Item// and has the following attributes: 284 284 285 -id uri urn 312 +id 313 +uri 314 +urn 286 286 287 287 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). 288 288 ... ... @@ -304,19 +304,16 @@ 304 304 |**Class**|(% colspan="2" %)**Feature**|**Description** 305 305 |CategoryScheme|(% colspan="2" %)((( 306 306 Inherits from 307 - 308 308 //ItemScheme// 309 309 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 310 310 | |(% colspan="2" %)/items|Associates the categories. 311 311 |Category|((( 312 312 Inherits from 313 - 314 314 //Item// 315 315 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 316 316 | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category. 317 317 |Categorisation|((( 318 318 Inherits from 319 - 320 320 //MaintainableArtefact// 321 321 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category. 322 322 | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact. ... ... @@ -354,17 +354,12 @@ 354 354 |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description** 355 355 |//OrganisationScheme//|(% style="width:246px" %)((( 356 356 Abstract Class Inherits from 357 - 358 358 //ItemScheme// 359 359 360 360 Sub classes are: 361 - 362 362 AgencyScheme 363 - 364 364 DataProviderScheme 365 - 366 366 MetadataProviderScheme DataConsumerScheme 367 - 368 368 OrganisationUnitScheme 369 369 )))|(% style="width:336px" %)A maintained collection of Organisations. 370 370 | |(% style="width:246px" %)/items|(% style="width:336px" %)((( ... ... @@ -374,19 +374,12 @@ 374 374 ))) 375 375 |//Organisation//|(% style="width:246px" %)((( 376 376 Abstract Class 398 +Inherits from //Item// 377 377 378 -Inherits from 379 - 380 -//Item// 381 - 382 382 Sub classes are: 383 - 384 384 Agency 385 - 386 386 DataProvider 387 - 388 388 MetadataProvider DataConsumer 389 - 390 390 OrganisationUnit 391 391 )))|(% 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. 392 392 | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information. ... ... @@ -412,27 +412,22 @@ 412 412 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme. 413 413 |Agency|(% style="width:246px" %)((( 414 414 Inherits from 415 - 416 416 //Organisation// 417 417 )))|(% 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. 418 418 |DataProvider|(% style="width:246px" %)((( 419 419 Inherits from 420 - 421 421 //Organisation// 422 422 )))|(% style="width:336px" %)An organisation that produces data. 423 423 |MetadataProvider|(% style="width:246px" %)((( 424 424 Inherits from 425 - 426 426 //Organisation// 427 427 )))|(% style="width:336px" %)An organisation that produces reference metadata. 428 428 |DataConsumer|(% style="width:246px" %)((( 429 429 Inherits from 430 - 431 431 //Organisation// 432 432 )))|(% style="width:336px" %)An organisation using data as input for further processing. 433 433 |OrganisationUnit|(% style="width:246px" %)((( 434 434 Inherits from 435 - 436 436 //Organisation// 437 437 )))|(% style="width:336px" %)A designation in the organisational structure. 438 438 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units ... ... @@ -473,13 +473,11 @@ 473 473 |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description** 474 474 |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)((( 475 475 Inherits from 476 - 477 477 //ItemScheme// 478 478 )))|(% 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. 479 479 |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category 480 480 |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)((( 481 481 Inherits from 482 - 483 483 //Item// 484 484 )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata. 485 485 |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.