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.6
edited by Helena
on 2025/05/16 13:51
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 ====
... ... @@ -182,7 +182,6 @@
182 182  |StructureUsage|(% style="width:194px" %) |(% style="width:454px" %)See “SDMX Base”.
183 183  |Dataflow|(% style="width:194px" %)(((
184 184  Inherits from
185 -
186 186  //StructureUsage//
187 187  )))|(% style="width:454px" %)Abstract concept (i.e., the structure without any data) of a flow of data that providers will provide for different reference periods.
188 188  | |(% style="width:194px" %)/structure|(% style="width:454px" %)Associates a Dataflow to the Data Structure Definition.
... ... @@ -190,13 +190,11 @@
190 190  | |(% style="width:194px" %)/grouping|(% style="width:454px" %)An association to a set of metadata concepts that have an identified structural role in a Data Structure Definition.
191 191  |GroupDimensionDescrip tor|(% style="width:194px" %)(((
192 192  Inherits from
193 -
194 194  //ComponentList//
195 195  )))|(% style="width:454px" %)A set of metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition.
196 196  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to the Dimension components that comprise the group.
197 197  |DimensionDescriptor|(% style="width:194px" %)(((
198 198  Inherits from
199 -
200 200  //ComponentList//
201 201  )))|(% style="width:454px" %)An ordered set of metadata concepts that, combined, classify a statistical series, and whose values, when combined (the key) in an instance such as a data set, uniquely identify a specific observation.
202 202  | |(% style="width:194px" %)/components|(% style="width:454px" %)(((
... ... @@ -204,29 +204,24 @@
204 204  )))
205 205  |AttributeDescriptor|(% style="width:194px" %)(((
206 206  Inherits from
207 -
208 208  //ComponentList//
209 209  )))|(% style="width:454px" %)A set metadata concepts that define the Attributes of a Data Structure Definition.
210 210  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Data Attribute component.
211 211  |MeasureDescriptor|(% style="width:194px" %)(((
212 212  Inherits from
213 -
214 214  //ComponentList//
215 215  )))|(% style="width:454px" %)A metadata concept that defines the Measures of a Data Structure Definition.
216 216  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Measure component.
217 217  |//DimensionComponent//|(% style="width:194px" %)(((
218 218  Inherits from
219 -
220 220  //Component//
221 221  
222 222  Sub class Dimension
223 -
224 224  TimeDimension
225 225  )))|(% style="width:454px" %)An abstract class representing any Component that can be used for identifying observations.
226 226  | |(% style="width:194px" %)order|(% style="width:454px" %)Specifies the order of the Dimension Components within the DSD. The property is used to indicate the position of the Dimension Component and determines the Key for identifying observations, or series. The Time Dimension, when specified, must be the last within the Dimension Descriptor.
227 227  |Dimension|(% style="width:194px" %)(((
228 228  Inherits from
229 -
230 230  //DimensionComponent//
231 231  )))|(% style="width:454px" %)A metadata concept used (most probably together with other metadata concepts) to classify a statistical series, e.g., a statistical concept indicating a certain economic activity or a geographical reference area.
232 232  | |(% style="width:194px" %)/role|(% style="width:454px" %)Association to the Concept that specifies the role that that the Dimension plays in the Data Structure Definition.
... ... @@ -233,7 +233,6 @@
233 233  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the metadata concept which defines the semantic of the Dimension.
234 234  |TimeDimension|(% style="width:194px" %)(((
235 235  Inherits from
236 -
237 237  //DimensionComponent//
238 238  )))|(% style="width:454px" %)A metadata concept that identifies the component in the key structure that has the role of “time”.
239 239  |DataAttribute|(% style="width:194px" %)(((
... ... @@ -249,7 +249,6 @@
249 249  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which defines the semantic of the component.
250 250  |Measure|(% style="width:194px" %)(((
251 251  Inherits from
252 -
253 253  //Component//
254 254  )))|(% style="width:454px" %)The metadata concept that is the phenomenon to be measured in a data set. In a data set the instance of the measure is often called the observation.
255 255  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which carries the values of the measures.
... ... @@ -258,11 +258,8 @@
258 258  | |(% style="width:194px" %)usage|(% style="width:454px" %)Defines whether a Measure must be reported or not.
259 259  |//AttributeRelationship//|(% style="width:194px" %)(((
260 260  Abstract Class
261 -
262 262  Sub classes
263 -
264 264  ObservationRelationship
265 -
266 266  GroupRelationship DimensionRelationshi p
267 267  )))|(% style="width:454px" %)Specifies the type of artefact to which a Data Attribute can be attached in a Data Set.
268 268  |ObservationRelationsh ip|(% style="width:194px" %) |(% style="width:454px" %)The Data Attribute is related to the observations of the Data Set.
... ... @@ -303,10 +303,8 @@
303 303  
304 304  A //DataSet// is formatted as a DataStructureDefinition specific data set (StructureSpecificDataSet). The structured data set is structured according to one specific DataStructureDefinition; hence the latter is required for validation at the syntax level.
305 305  
306 -A //DataSet// is a collection of a set of //Observation//s that share the same dimensionality, which is specified by a set of unique components (Dimension, TimeDimension) defined in the
278 +A //DataSet// is a collection of a set of //Observation//s that share the same dimensionality, which is specified by a set of unique components (Dimension, TimeDimension) defined in the DimensionDescriptor of the DataStructureDefinition, together with associated
307 307  
308 -DimensionDescriptor of the DataStructureDefinition, together with associated
309 -
310 310  //AttributeValue//s that define specific characteristics about the artefact to which it is attached – //Observation//s, set of Dimensions. It can be structured in terms of a SeriesKey to which //Observation//s are reported.
311 311  
312 312  The //Observation// can be the value(s) of the variable(s) being measured for the Concept associated to the Measure(s) in the MeasureDescriptor of the DataStructureDefinition. Each //Observation// associates one or more //ObservationValue//s with a KeyValue (+observationDimension) which is the value for the “Dimension at the Observation Level”. Any Dimension can be specified as being the “Dimension at the Observation Level”, and this specification is made at the level of the //DataSet// (i.e., it must be the same Dimension for the entire //DataSet//).