Skip to Content
Last modified by Elena on 2025/09/10 11:19
From version 3.4
edited by Helena
on 2025/06/08 11:14
Change comment: There is no comment for this version
To version 2.1
edited by Helena
on 2025/06/07 00:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,5 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 +=== 5.1 Introduction ===
4 4  
5 -== 5.1 Introduction ==
6 -
7 7  The DataStructureDefiniton is the class name for a structure definition for data. Some organisations know this type of definition as a “Key Family” and so the two names are synonymous. The term Data Structure Definition (also referred to as DSD) is used in this specification.
8 8  
9 9  Many of the constructs in this layer of the model inherit from the SDMX Base Layer. Therefore, it is necessary to study both the inheritance and the relationship diagrams to understand the functionality of individual packages. In simple sub models these are shown in the same diagram but are omitted from the more complex sub models for the sake of clarity. In these cases, the inheritance diagram below shows the full inheritance tree for the classes concerned with data structure definitions.
... ... @@ -22,17 +22,17 @@
22 22  
23 23  Maintenance – //MaintainableArtefact//
24 24  
25 -== 5.2 Inheritance View ==
21 +=== 5.2 Inheritance View ===
26 26  
27 -=== 5.2.1 Class Diagram ===
23 +==== 5.2.1 Class Diagram ====
28 28  
29 29  [[image:1749246368774-202.jpeg]]
30 30  
31 31  **Figure 27 Class inheritance in the Data Structure Definition and Data Set Packages**
32 32  
33 -=== 5.2.2 Explanation of the Diagram ===
29 +===== 5.2.2 Explanation of the Diagram =====
34 34  
35 -==== 5.2.2.1 Narrative ====
31 +====== 5.2.2.1 Narrative ======
36 36  
37 37  Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
38 38  
... ... @@ -104,17 +104,17 @@
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.
106 106  
107 -== 5.3 Data Structure Definition – Relationship View ==
103 +==== //5.3 Data Structure Definition – Relationship View// ====
108 108  
109 -=== 5.3.1 Class Diagram ===
105 +===== 5.3.1 Class Diagram =====
110 110  
111 111  [[image:1749246368782-690.jpeg]]
112 112  
113 113  **Figure 28 Relationship class diagram of the Data Structure Definition excluding representation**
114 114  
115 -=== 5.3.2 Explanation of the Diagrams ===
111 +===== 5.3.2 Explanation of the Diagrams =====
116 116  
117 -==== 5.3.2.1 Narrative ====
113 +====== 5.3.2.1 Narrative ======
118 118  
119 119  A DataStructureDefinition defines the Dimensions, TimeDimension, DataAttributes, and Measures, and associated Representations, that comprise the valid structure of data and related attributes that are contained in a DataSet, which is defined by a Dataflow. In addition, a DataStructureDefinition may be related to one MetadataStructureDefinition, in order to use the latter’s MetadataAttributes, by relating them to other //Components// within the DSD, as explained below.
120 120  
... ... @@ -173,7 +173,7 @@
173 173  
174 174  A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
175 175  
176 -==== 5.3.2.2 Definitions ====
172 +**5.3.2.2 Definitions**
177 177  
178 178  |**Class**|**Feature**|**Description**
179 179  |StructureUsage| |See “SDMX Base”.
... ... @@ -183,7 +183,7 @@
183 183  //StructureUsage//
184 184  )))|Abstract concept (i.e., the structure without any data) of a flow of data that providers will provide for different reference periods.
185 185  | |/structure|Associates a Dataflow to the Data Structure Definition.
186 -| |dimensionConstraint|A list of Dimensions which the Dataflow uses. This is only required when the referenced DataStructureDefinition has the evolvingStructure property set to true and when the association to the DataStructureDefinition in on the latest minor version{{footnote}}Referencing the latest minor version of the Data Structure is achieved by the reference including the plus operator on the minor version to indicate it links to the latest stable version, for example 2.0+.0 will resolve to the highest version 2.x.y.{{/footnote}}.
182 +| |dimensionConstraint|A list of Dimensions which the Dataflow uses. This is only required when the referenced DataStructureDefinition has the evolvingStructure property set to true and when the association to the DataStructureDefinition in on the latest minor version[[^^~[1~]^^>>path:#_ftn1]].
187 187  |DataStructureDefiniti on| |A collection of metadata concepts, their structure and usage when used to collect or disseminate data.
188 188  | |/grouping|An association to a set of metadata concepts that have an identified structural role in a Data Structure Definition.
189 189  | |evolvingStructure|An optional boolean property, defaulting to false. When true the DataStructureDefinition may have new Dimensions added without having to change its major version number.
... ... @@ -204,7 +204,7 @@
204 204  
205 205  //ComponentList//
206 206  )))|A set metadata concepts that define the Attributes of a Data Structure Definition.
207 -| |/components|An association to a Data Attribute component.
203 +| |/////components|An association to a Data Attribute component.
208 208  |MeasureDescriptor|(((
209 209  Inherits from
210 210  
... ... @@ -298,9 +298,9 @@
298 298  
299 299  **Figure 31: Class Diagram of the Data Set**
300 300  
301 -=== 5.4.3 Explanation of the Diagram ===
297 +====== 5.4.3 Explanation of the Diagram ======
302 302  
303 -==== 5.4.3.1 Narrative – Data Set ====
299 +5.4.3.1 Narrative – Data Set
304 304  
305 305  Note that the //DataSet// must conform to the DataStructureDefinition associated to the Dataflow for which this DataSet is an “instance of data”. Whilst the model shows the association to the classes of the DataStructureDefinition, this is for conceptual purposes to show the link to the DataStructureDefinition. In the actual //DataSet// as exchanged there must, of course, be a reference to the DataStructureDefinition and optionally a Dataflow or a ProvisionAgreement, but the DataStructureDefinition is not necessarily exchanged with the data. Therefore, the DataStructureDefinition classes are shown in the grey areas, as these are not a part of the //DataSet// when the //DataSet// is exchanged. However, the structural metadata in the DataStructureDefinition can be used by an application to validate the contents of the //DataSet// in terms of the valid content of a //KeyValue// as defined by the Representation in the DataStructureDefinition.
306 306  
... ... @@ -322,7 +322,7 @@
322 322  
323 323  The //AttributeValue// links to the object type (SeriesKey, GroupKey, Observation) to which it is associated.
324 324  
325 -==== 5.4.3.2 Definitions ====
321 +5.4.3.2 Definitions
326 326  
327 327  |**Class**|**Feature**|**Description**
328 328  |//DataSet//|(((
... ... @@ -524,6 +524,8 @@
524 524  )))|An attribute that takes it value from a Code in Code list.
525 525  | |+valueOf|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.
526 526  
523 +
524 +
527 527  ----
528 528  
529 -{{putFootnotes/}}
527 +[[~[1~]>>path:#_ftnref1]] Referencing the latest minor version of the Data Structure is achieved by the reference including the plus operator on the minor version to indicate it links to the latest stable version, for example 2.0+.0 will resolve to the highest version 2.x.y.
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,1 @@
1 -6
1 +13