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

Summary

Details

Page properties
Content
... ... @@ -32,22 +32,28 @@
32 32  
33 33  Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
34 34  
35 -//IdentifiableArtefact
36 -DataSet
37 -Key// (and therefore //SeriesKey// and //GroupKey//)
35 +//IdentifiableArtefact//
36 +
37 +//DataSet//
38 +
39 +//Key// (and therefore //SeriesKey// and //GroupKey//)
40 +
38 38  //Observation//
39 39  
40 40  Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are:
41 41  
42 -//NameableArtefact
43 -ComponentList
44 -Component//
45 +//NameableArtefact//
45 45  
47 +//ComponentList//
48 +
49 +//Component//
50 +
46 46  Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are:
47 47  
48 -//VersionableArtefact
49 -Item//
53 +//VersionableArtefact//
50 50  
55 +//Item//
56 +
51 51  The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are:
52 52  
53 53  //MaintainableArtefact//
... ... @@ -54,15 +54,18 @@
54 54  
55 55  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:
56 56  
57 -//StructureUsage
58 -Structure
59 -ItemScheme//
63 +//StructureUsage//
60 60  
65 +//Structure//
66 +
67 +//ItemScheme//
68 +
61 61  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.
62 62  
63 63  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:
64 64  
65 65  Dataflow
74 +
66 66  DataStructureDefinition
67 67  
68 68  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:
... ... @@ -74,8 +74,11 @@
74 74  The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are:
75 75  
76 76  DimensionDescriptor – content is Dimension and TimeDimension
86 +
77 77  DimensionGroupDescriptor – content is an association to Dimension, TimeDimension
88 +
78 78  MeasureDescriptor – content is Measure
90 +
79 79  AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute
80 80  
81 81  The classes that inherit from //Component// are:
... ... @@ -83,6 +83,7 @@
83 83  Measure
84 84  
85 85  //DimensionComponent// and thereby its sub classes of Dimension and TimeDimension
98 +
86 86  //Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute
87 87  
88 88  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.
... ... @@ -153,8 +153,10 @@
153 153  
154 154  **Figure 30: Representation of DSD Components**
155 155  
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.
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
157 157  
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 +
158 158  A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
159 159  
160 160  ==== 5.3.2.2 Definitions ====