Changes for page 4 Specific Item Schemes

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

From version 15.8
edited by Helena
on 2025/05/16 13:46
Change comment: There is no comment for this version
To version 13.3
edited by Helena
on 2025/05/15 10:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,15 +7,27 @@
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 +
10 10  ConceptScheme
12 +
11 11  CategoryScheme
12 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
14 +
15 +AgencyScheme, DataProviderScheme, MetadataProviderScheme,
16 +
17 +DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
18 +
13 13  ReportingTaxonomy
20 +
14 14  TransformationScheme
22 +
15 15  RulesetScheme
24 +
16 16  UserDefinedOperatorScheme
26 +
17 17  NamePersonalisationScheme
28 +
18 18  CustomTypeScheme
30 +
19 19  VtlMappingScheme
20 20  
21 21  Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
... ... @@ -36,24 +36,11 @@
36 36  
37 37  ==== 4.3.2.1 Narrative ====
38 38  
39 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
51 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
40 40  
41 -id
42 -uri
43 -urn
44 -version
45 -validFrom
46 -validTo
47 -isExternalReference
48 -serviceURL
49 -structureURL
50 -isPartial
51 -
52 52  The Code inherits from //Item// and has the following attributes:
53 53  
54 -id
55 -uri
56 -urn
55 +id uri urn
57 57  
58 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).
59 59  
... ... @@ -88,12 +88,14 @@
88 88  
89 89  ==== 4.3.3.1 Narrative ====
90 90  
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.
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.
92 92  
93 93  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.
94 94  
95 95  ==== 4.3.3.2 Definitions ====
96 96  
96 +:
97 +
97 97  (((
98 98  (% style="width:753.039px" %)
99 99  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
... ... @@ -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.
117 +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,6 +128,7 @@
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
132 +
131 131  GeoGridCodelist
132 132  
133 133  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.
... ... @@ -149,7 +149,9 @@
149 149  )))
150 150  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
151 151  Abstract Class Sub Classes:
154 +
152 152  GeoFeatureSet
156 +
153 153  GeoGridCode
154 154  )))|The abstract class that represents a special type of Code, which includes geospatial information.
155 155  |(% 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.
... ... @@ -174,16 +174,7 @@
174 174  
175 175  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176 176  
177 -id
178 -uri
179 -urn
180 -version
181 -validFrom
182 -validTo
183 -isExternalReference
184 -registryURL
185 -structureURL
186 -repositoryURL
181 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
187 187  
188 188  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
189 189  
... ... @@ -193,18 +193,17 @@
193 193  
194 194  ==== 4.4.2.2 Definitions ====
195 195  
196 -(% style="width:749.039px" %)
197 -|**Class**|**Feature**|(% style="width:421px" %)**Description**
191 +|**Class**|**Feature**|**Description**
198 198  |ValueList|(((
199 199  Inherits from
200 200  
201 201  //EnumeratedList//
202 -)))|(% style="width:421px" %)A list from which some statistical concepts (enumerated concepts) take their values.
196 +)))|A list from which some statistical concepts (enumerated concepts) take their values.
203 203  |ValueItem|(((
204 204  Inherits from
205 205  
206 206  //EnumeratedItem//
207 -)))|(% style="width:421px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
201 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
208 208  
209 209  == 4.5 Concept Scheme and Concepts ==
210 210  
... ... @@ -216,26 +216,10 @@
216 216  
217 217  === 4.5.2 Explanation of the Diagram ===
218 218  
219 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
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:
220 220  
221 -id
222 -uri
223 -urn
224 -version
225 -validFrom
226 -validTo
227 -isExternalReference
228 -registryURL
229 -structureURL
230 -repositoryURL
231 -isPartial
215 +id uri urn
232 232  
233 -Concept inherits from Item and has the following attributes:
234 -
235 -id
236 -uri
237 -urn
238 -
239 239  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).
240 240  
241 241  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.
... ... @@ -262,23 +262,24 @@
262 262  
263 263  ==== 4.5.4.2 Definitions ====
264 264  
265 -(% style="width:765.039px" %)
266 -|(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
267 -|(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
243 +|**Class**|**Feature**|**Description**
244 +|ConceptScheme|(((
268 268  Inherits from
246 +
269 269  //ItemScheme//
270 -)))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
271 -|(% style="width:204px" %)Concept|(% style="width:222px" %)(((
248 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
249 +|Concept|(((
272 272  Inherits from
251 +
273 273  //Item//
274 -)))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
275 -|(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
276 -|(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation.
277 -|(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference.
278 -|(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition.
279 -|(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept.
280 -|(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme.
281 -|(% style="width:204px" %) |(% style="width:222px" %)conceptID|(% style="width:337px" %)The identifier of the concept.
253 +)))|A concept is a unit of knowledge created by a unique combination of characteristics.
254 +| |/hierarchy|Associates the parent and the child concept.
255 +| |coreRepresentation|Associates a Representation.
256 +| |+ISOConcept|Association to an ISO concept reference.
257 +|ISOConceptReference| |The identity of an ISO concept definition.
258 +| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
259 +| |conceptSchemeID|The identifier of the concept scheme.
260 +| |conceptID|The identifier of the concept.
282 282  
283 283  == 4.6 Category Scheme ==
284 284  
... ... @@ -320,7 +320,6 @@
320 320  
321 321  ==== 4.6.4.1 Definitions ====
322 322  
323 -(% style="width:753.039px" %)
324 324  |**Class**|(% colspan="2" %)**Feature**|**Description**
325 325  |CategoryScheme|(% colspan="2" %)(((
326 326  Inherits from
... ... @@ -370,9 +370,8 @@
370 370  
371 371  ==== 4.7.2.2 Definitions ====
372 372  
373 -(% style="width:763.039px" %)
374 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
375 -|//OrganisationScheme//|(% style="width:246px" %)(((
351 +|**Class**|**Feature**|**Description**
352 +|//OrganisationScheme//|(((
376 376  Abstract Class Inherits from
377 377  
378 378  //ItemScheme//
... ... @@ -386,13 +386,13 @@
386 386  MetadataProviderScheme DataConsumerScheme
387 387  
388 388  OrganisationUnitScheme
389 -)))|(% style="width:336px" %)A maintained collection of Organisations.
390 -| |(% style="width:246px" %)/items|(% style="width:336px" %)(((
366 +)))|A maintained collection of Organisations.
367 +| |/items|(((
391 391  Association to the
392 392  
393 393  Organisations in the scheme.
394 394  )))
395 -|//Organisation//|(% style="width:246px" %)(((
372 +|//Organisation//|(((
396 396  Abstract Class
397 397  
398 398  Inherits from
... ... @@ -408,54 +408,54 @@
408 408  MetadataProvider DataConsumer
409 409  
410 410  OrganisationUnit
411 -)))|(% 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.
412 -| |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
413 -| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations.
414 -|Contact|(% style="width:246px" %) |(% style="width:336px" %)An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
415 -| |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression.
416 -| |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
417 -| |(% style="width:246px" %)responsibility|(% style="width:336px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
418 -| |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact.
419 -| |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact.
420 -| |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact.
421 -| |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact.
422 -| |(% style="width:246px" %)uri|(% style="width:336px" %)The URL address of the Contact.
423 -|AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies.
424 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme.
425 -|DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers.
426 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Providers in the scheme.
427 -|MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers.
428 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme.
429 -|DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers.
430 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Consumers in the scheme.
431 -|OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units.
432 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
433 -|Agency|(% style="width:246px" %)(((
388 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
389 +| |+contact|Association to the Contact information.
390 +| |/hierarchy|Association to child Organisations.
391 +|Contact| |An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
392 +| |name|The designation of the Contact person by a linguistic expression.
393 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
394 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
395 +| |telephone|The telephone number of the Contact.
396 +| |fax|The fax number of the Contact.
397 +| |email|The Internet e-mail address of the Contact.
398 +| |X400|The X400 address of the Contact.
399 +| |uri|The URL address of the Contact.
400 +|AgencyScheme| |A maintained collection of Maintenance Agencies.
401 +| |/items|Association to the Maintenance Agency in the scheme.
402 +|DataProviderScheme| |A maintained collection of Data Providers.
403 +| |/items|Association to the Data Providers in the scheme.
404 +|MetadataProviderScheme| |A maintained collection of Metadata Providers.
405 +| |/items|Association to the Metadata Providers in the scheme.
406 +|DataConsumerScheme| |A maintained collection of Data Consumers.
407 +| |/items|Association to the Data Consumers in the scheme.
408 +|OrganisationUnitScheme| |A maintained collection of Organisation Units.
409 +| |/items|Association to the Organisation Units in the scheme.
410 +|Agency|(((
434 434  Inherits from
435 435  
436 436  //Organisation//
437 -)))|(% 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.
438 -|DataProvider|(% style="width:246px" %)(((
414 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
415 +|DataProvider|(((
439 439  Inherits from
440 440  
441 441  //Organisation//
442 -)))|(% style="width:336px" %)An organisation that produces data.
443 -|MetadataProvider|(% style="width:246px" %)(((
419 +)))|An organisation that produces data.
420 +|MetadataProvider|(((
444 444  Inherits from
445 445  
446 446  //Organisation//
447 -)))|(% style="width:336px" %)An organisation that produces reference metadata.
448 -|DataConsumer|(% style="width:246px" %)(((
424 +)))|An organisation that produces reference metadata.
425 +|DataConsumer|(((
449 449  Inherits from
450 450  
451 451  //Organisation//
452 -)))|(% style="width:336px" %)An organisation using data as input for further processing.
453 -|OrganisationUnit|(% style="width:246px" %)(((
429 +)))|An organisation using data as input for further processing.
430 +|OrganisationUnit|(((
454 454  Inherits from
455 455  
456 456  //Organisation//
457 -)))|(% style="width:336px" %)A designation in the organisational structure.
458 -| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
434 +)))|A designation in the organisational structure.
435 +| |/hierarchy|Association to child Organisation Units
459 459  
460 460  == 4.8 Reporting Taxonomy ==
461 461  
... ... @@ -489,23 +489,22 @@
489 489  
490 490  ==== 4.8.2.2 Definitions ====
491 491  
492 -(% style="width:759.039px" %)
493 -|(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description**
494 -|(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
469 +|**Class**|**Feature**|**Description**
470 +|ReportingTaxonomy|(((
495 495  Inherits from
496 496  
497 497  //ItemScheme//
498 -)))|(% 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.
499 -|(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
500 -|(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
474 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
475 +| |/items|Associates the Reporting Category
476 +|ReportingCategory|(((
501 501  Inherits from
502 502  
503 503  //Item//
504 -)))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
505 -|(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
506 -|(% 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.
507 -|(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
508 -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.
509 -)))
480 +)))|A component that gives structure to the report and links to data and metadata.
481 +| |/hierarchy|Associates child Reporting Category.
482 +| |+flow|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.
483 +| |+structure|(((
484 +Association to the Data Structure
510 510  
511 -{{putFootnotes/}}
486 +Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
487 +)))