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.6
edited by Helena
on 2025/05/16 13:51
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.
... ... @@ -170,10 +170,8 @@
170 170  
171 171  **Figure 30: Representation of DSD Components**
172 172  
173 -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.
174 174  
175 -(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.
176 -
177 177  A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
178 178  
179 179  ==== 5.3.2.2 Definitions ====
... ... @@ -186,7 +186,6 @@
186 186  |StructureUsage|(% style="width:194px" %) |(% style="width:454px" %)See “SDMX Base”.
187 187  |Dataflow|(% style="width:194px" %)(((
188 188  Inherits from
189 -
190 190  //StructureUsage//
191 191  )))|(% 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.
192 192  | |(% style="width:194px" %)/structure|(% style="width:454px" %)Associates a Dataflow to the Data Structure Definition.
... ... @@ -194,13 +194,11 @@
194 194  | |(% 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.
195 195  |GroupDimensionDescrip tor|(% style="width:194px" %)(((
196 196  Inherits from
197 -
198 198  //ComponentList//
199 199  )))|(% style="width:454px" %)A set of metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition.
200 200  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to the Dimension components that comprise the group.
201 201  |DimensionDescriptor|(% style="width:194px" %)(((
202 202  Inherits from
203 -
204 204  //ComponentList//
205 205  )))|(% 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.
206 206  | |(% style="width:194px" %)/components|(% style="width:454px" %)(((
... ... @@ -208,29 +208,24 @@
208 208  )))
209 209  |AttributeDescriptor|(% style="width:194px" %)(((
210 210  Inherits from
211 -
212 212  //ComponentList//
213 213  )))|(% style="width:454px" %)A set metadata concepts that define the Attributes of a Data Structure Definition.
214 214  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Data Attribute component.
215 215  |MeasureDescriptor|(% style="width:194px" %)(((
216 216  Inherits from
217 -
218 218  //ComponentList//
219 219  )))|(% style="width:454px" %)A metadata concept that defines the Measures of a Data Structure Definition.
220 220  | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Measure component.
221 221  |//DimensionComponent//|(% style="width:194px" %)(((
222 222  Inherits from
223 -
224 224  //Component//
225 225  
226 226  Sub class Dimension
227 -
228 228  TimeDimension
229 229  )))|(% style="width:454px" %)An abstract class representing any Component that can be used for identifying observations.
230 230  | |(% 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.
231 231  |Dimension|(% style="width:194px" %)(((
232 232  Inherits from
233 -
234 234  //DimensionComponent//
235 235  )))|(% 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.
236 236  | |(% 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.
... ... @@ -237,7 +237,6 @@
237 237  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the metadata concept which defines the semantic of the Dimension.
238 238  |TimeDimension|(% style="width:194px" %)(((
239 239  Inherits from
240 -
241 241  //DimensionComponent//
242 242  )))|(% style="width:454px" %)A metadata concept that identifies the component in the key structure that has the role of “time”.
243 243  |DataAttribute|(% style="width:194px" %)(((
... ... @@ -253,7 +253,6 @@
253 253  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which defines the semantic of the component.
254 254  |Measure|(% style="width:194px" %)(((
255 255  Inherits from
256 -
257 257  //Component//
258 258  )))|(% 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.
259 259  | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which carries the values of the measures.
... ... @@ -262,11 +262,8 @@
262 262  | |(% style="width:194px" %)usage|(% style="width:454px" %)Defines whether a Measure must be reported or not.
263 263  |//AttributeRelationship//|(% style="width:194px" %)(((
264 264  Abstract Class
265 -
266 266  Sub classes
267 -
268 268  ObservationRelationship
269 -
270 270  GroupRelationship DimensionRelationshi p
271 271  )))|(% style="width:454px" %)Specifies the type of artefact to which a Data Attribute can be attached in a Data Set.
272 272  |ObservationRelationsh ip|(% style="width:194px" %) |(% style="width:454px" %)The Data Attribute is related to the observations of the Data Set.
... ... @@ -307,10 +307,8 @@
307 307  
308 308  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.
309 309  
310 -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
311 311  
312 -DimensionDescriptor of the DataStructureDefinition, together with associated
313 -
314 314  //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.
315 315  
316 316  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//).
... ... @@ -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