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

Summary

Details

Page properties
Content
... ... @@ -32,28 +32,22 @@
32 32  
33 33  Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
34 34  
35 -//IdentifiableArtefact//
36 -
37 -//DataSet//
38 -
39 -//Key// (and therefore //SeriesKey// and //GroupKey//)
40 -
35 +//IdentifiableArtefact
36 +DataSet
37 +Key// (and therefore //SeriesKey// and //GroupKey//)
41 41  //Observation//
42 42  
43 43  Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are:
44 44  
45 -//NameableArtefact//
42 +//NameableArtefact
43 +ComponentList
44 +Component//
46 46  
47 -//ComponentList//
48 -
49 -//Component//
50 -
51 51  Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are:
52 52  
53 -//VersionableArtefact//
48 +//VersionableArtefact
49 +Item//
54 54  
55 -//Item//
56 -
57 57  The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are:
58 58  
59 59  //MaintainableArtefact//
... ... @@ -60,18 +60,15 @@
60 60  
61 61  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:
62 62  
63 -//StructureUsage//
57 +//StructureUsage
58 +Structure
59 +ItemScheme//
64 64  
65 -//Structure//
66 -
67 -//ItemScheme//
68 -
69 69  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.
70 70  
71 71  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:
72 72  
73 73  Dataflow
74 -
75 75  DataStructureDefinition
76 76  
77 77  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:
... ... @@ -83,11 +83,8 @@
83 83  The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are:
84 84  
85 85  DimensionDescriptor – content is Dimension and TimeDimension
86 -
87 87  DimensionGroupDescriptor – content is an association to Dimension, TimeDimension
88 -
89 89  MeasureDescriptor – content is Measure
90 -
91 91  AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute
92 92  
93 93  The classes that inherit from //Component// are:
... ... @@ -95,7 +95,6 @@
95 95  Measure
96 96  
97 97  //DimensionComponent// and thereby its sub classes of Dimension and TimeDimension
98 -
99 99  //Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute
100 100  
101 101  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.
... ... @@ -166,10 +166,8 @@
166 166  
167 167  **Figure 30: Representation of DSD Components**
168 168  
169 -Each of Dimension, TimeDimension, Measure, DataAttribute and MetadataAttribute can have a Representation specified (using the localRepresentation association). If this is not specified in the DataStructureDefinition then the representation specified for Concept
156 +Each of Dimension, TimeDimension, Measure, DataAttribute and MetadataAttribute can have a Representation specified (using the localRepresentation association). If this is not specified in the DataStructureDefinition then the representation specified for Concept (coreRepresentation) is used. Measure, and DataAttribute may be also represented by multilingual text (as seen in the DataSet diagram further down). An exception is the MetadataAttribute, where its Representation is specified in the MetadataStructureDefinition.
170 170  
171 -(coreRepresentation) is used. Measure, and DataAttribute may be also represented by multilingual text (as seen in the DataSet diagram further down). An exception is the MetadataAttribute, where its Representation is specified in the MetadataStructureDefinition.
172 -
173 173  A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
174 174  
175 175  ==== 5.3.2.2 Definitions ====