Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 7.5
edited by Helena
on 2025/05/15 10:41
Change comment: There is no comment for this version
To version 8.3
edited by Helena
on 2025/05/16 13:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,13 +13,9 @@
13 13  The actual SDMX Base construct from which the concrete classes inherit depends upon the requirements of the class for:
14 14  
15 15  Annotation – //AnnotableArtefact//
16 -
17 17  Identification – //IdentifiableArtefact//
18 -
19 19  Naming – //NameableArtefact//
20 -
21 21  Versioning – //VersionableArtefact//
22 -
23 23  Maintenance – //MaintainableArtefact//
24 24  
25 25  == 5.2 Inheritance View ==
... ... @@ -36,28 +36,22 @@
36 36  
37 37  Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
38 38  
39 -//IdentifiableArtefact//
40 -
41 -//DataSet//
42 -
43 -//Key// (and therefore //SeriesKey// and //GroupKey//)
44 -
35 +//IdentifiableArtefact
36 +DataSet
37 +Key// (and therefore //SeriesKey// and //GroupKey//)
45 45  //Observation//
46 46  
47 47  Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are:
48 48  
49 -//NameableArtefact//
42 +//NameableArtefact
43 +ComponentList
44 +Component//
50 50  
51 -//ComponentList//
52 -
53 -//Component//
54 -
55 55  Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are:
56 56  
57 -//VersionableArtefact//
48 +//VersionableArtefact
49 +Item//
58 58  
59 -//Item//
60 -
61 61  The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are:
62 62  
63 63  //MaintainableArtefact//
... ... @@ -64,18 +64,15 @@
64 64  
65 65  Abstract classes which represent information that is maintained by Maintenance Agencies all inherit from //MaintainableArtefact//, they also inherit all the features of a //VersionableArtefact//, and are:
66 66  
67 -//StructureUsage//
57 +//StructureUsage
58 +Structure
59 +ItemScheme//
68 68  
69 -//Structure//
70 -
71 -//ItemScheme//
72 -
73 73  All the above classes are abstract. The key to understanding the class diagrams presented in this section are the concrete classes that inherit from these abstract classes.
74 74  
75 75  Those concrete classes in the SDMX Data Structure Definition and Dataset packages of the metamodel which require to be maintained by Agencies all inherit (via other abstract classes) from //MaintainableArtefact//, these are:
76 76  
77 77  Dataflow
78 -
79 79  DataStructureDefinition
80 80  
81 81  The component structures that are lists of lists, inherit directly from //Structure//. A //Structure// contains several lists of components. The concrete class that inherits from //Structure// is:
... ... @@ -87,11 +87,8 @@
87 87  The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are:
88 88  
89 89  DimensionDescriptor – content is Dimension and TimeDimension
90 -
91 91  DimensionGroupDescriptor – content is an association to Dimension, TimeDimension
92 -
93 93  MeasureDescriptor – content is Measure
94 -
95 95  AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute
96 96  
97 97  The classes that inherit from //Component// are:
... ... @@ -99,7 +99,6 @@
99 99  Measure
100 100  
101 101  //DimensionComponent// and thereby its sub classes of Dimension and TimeDimension
102 -
103 103  //Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute
104 104  
105 105  The concrete classes identified above are the majority of the classes required to define the metamodel for the DataStructureDefinition. The diagrams and explanations in the rest of this section show how these concrete classes are related in order to support the functionality required.
... ... @@ -371,7 +371,6 @@
371 371  )))|(% style="width:437px" %)The value of a component of a key such as the value of the instance a Dimension in a Dimension Descriptor of a Data Structure Definition.
372 372  |(% style="width:147px" %) |(% style="width:222px" %)+valueFor|(% style="width:437px" %)(((
373 373  Association to the key component in the Data Structure Definition for which this Key Value is a valid representation.
374 -
375 375  Note that this is conceptual association as the key component is identified explicitly in the data set.
376 376  )))
377 377  |(% style="width:147px" %)TimeKeyValue|(% style="width:222px" %)(((
... ... @@ -477,7 +477,6 @@
477 477  )))|(% style="width:437px" %)The value of a Data Attribute, such as the instance of a Coded Attribute or of an Uncoded Attribute in a structure such as a Data Structure Definition.
478 478  |(% style="width:147px" %) |(% style="width:222px" %)+valueFor|(% style="width:437px" %)(((
479 479  Association to the Data Attribute defined in the Data Structure Definition. Note that this is conceptual association as the Concept is identified explicitly in the data set.
480 -
481 481  The source multiplicity (1..*) indicates the possibility to provide more than one values for a Data Attribute, if the latter allows it.
482 482  )))
483 483  |(% style="width:147px" %)//MetadataAttribute Value//|(% style="width:222px" %)(((
... ... @@ -520,6 +520,4 @@
520 520  )))|(% style="width:437px" %)An attribute that takes it value from a Code in Code list.
521 521  |(% style="width:147px" %) |(% style="width:222px" %)+valueOf|(% style="width:437px" %)Association to the Code that is the value of the Attribute Value. Note that this is a conceptual association showing that the Code must exist in the Code list associated with the Data Attribute in the Data Structure Definition. In the actual Data Set the value of the Code is placed in the Attribute Value.
522 522  
523 -
524 -
525 525