Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19

From version 14.1
edited by Helena
on 2025/05/15 10:36
Change comment: There is no comment for this version
To version 15.10
edited by Helena
on 2025/05/16 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,27 +7,15 @@
7 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:
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 33  Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
... ... @@ -48,11 +48,24 @@
48 48  
49 49  ==== 4.3.2.1 Narrative ====
50 50  
51 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
39 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
52 52  
41 +id
42 +uri
43 +urn
44 +version
45 +validFrom
46 +validTo
47 +isExternalReference
48 +serviceURL
49 +structureURL
50 +isPartial
51 +
53 53  The Code inherits from //Item// and has the following attributes:
54 54  
55 -id uri urn
54 +id
55 +uri
56 +urn
56 56  
57 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).
58 58  
... ... @@ -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="wikiinternallink wikiinternallink" %)^^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.
91 +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.
116 +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
177 +id
178 +uri
179 +urn
180 +version
181 +validFrom
182 +validTo
183 +isExternalReference
184 +registryURL
185 +structureURL
186 +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:
219 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
215 215  
216 -id uri urn
221 +id
222 +uri
223 +urn
224 +version
225 +validFrom
226 +validTo
227 +isExternalReference
228 +registryURL
229 +structureURL
230 +repositoryURL
231 +isPartial
217 217  
233 +Concept inherits from Item and has the following attributes:
234 +
235 +id
236 +uri
237 +urn
238 +
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
301 +id
302 +uri
303 +urn
304 +version
305 +validFrom
306 +validTo
307 +isExternalReference
308 +structureURL
309 +serviceURL
310 +isPartial
283 283  
284 284  Category inherits from //Item// and has the following attributes:
285 285  
286 -id uri urn
314 +id
315 +uri
316 +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
400 +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
... ... @@ -486,7 +486,7 @@
486 486  |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
487 487  |(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
488 488  |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
489 -Association to the Data Structure
490 -
491 -Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
499 +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.
492 492  )))
501 +
502 +{{putFootnotes/}}