Changes for page 5 Data Structure Definition and Dataset
Last modified by Elena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,9 @@ 1 -=== 5.1 Introduction === 1 +{{box title="**Contents**"}} 2 +{{toc/}} 3 +{{/box}} 2 2 5 +== 5.1 Introduction == 6 + 3 3 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. 4 4 5 5 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. ... ... @@ -9,51 +9,41 @@ 9 9 The actual SDMX Base construct from which the concrete classes inherit depends upon the requirements of the class for: 10 10 11 11 Annotation – //AnnotableArtefact// 12 - 13 13 Identification – //IdentifiableArtefact// 14 - 15 15 Naming – //NameableArtefact// 16 - 17 17 Versioning – //VersionableArtefact// 18 - 19 19 Maintenance – //MaintainableArtefact// 20 20 21 -== =5.2 Inheritance View ===21 +== 5.2 Inheritance View == 22 22 23 -=== =5.2.1 Class Diagram ====23 +=== 5.2.1 Class Diagram === 24 24 25 25 [[image:1749246368774-202.jpeg]] 26 26 27 27 **Figure 27 Class inheritance in the Data Structure Definition and Data Set Packages** 28 28 29 -=== ==5.2.2 Explanation of the Diagram =====29 +=== 5.2.2 Explanation of the Diagram === 30 30 31 -==== ==5.2.2.1 Narrative ======31 +==== 5.2.2.1 Narrative ==== 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,22 +60,17 @@ 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 - 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: 78 - 79 79 DataStructureDefinition 80 80 81 81 A DataStructureDefinition contains a list of dimensions, a list of measures and a list of attributes. ... ... @@ -83,34 +83,29 @@ 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: 94 94 95 95 Measure 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. 102 102 103 -== ==//5.3 Data Structure Definition – Relationship View//====87 +== 5.3 Data Structure Definition – Relationship View == 104 104 105 -=== ==5.3.1 Class Diagram =====89 +=== 5.3.1 Class Diagram === 106 106 107 107 [[image:1749246368782-690.jpeg]] 108 108 109 109 **Figure 28 Relationship class diagram of the Data Structure Definition excluding representation** 110 110 111 -=== ==5.3.2 Explanation of the Diagrams =====95 +=== 5.3.2 Explanation of the Diagrams === 112 112 113 -==== ==5.3.2.1 Narrative ======97 +==== 5.3.2.1 Narrative ==== 114 114 115 115 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. 116 116 ... ... @@ -155,11 +155,12 @@ 155 155 156 156 The following table details the possible relationships a DataAttribute may specify. Note that these relationships are mutually exclusive, and therefore only one of the following is possible. 157 157 158 -|**Relationship**|**Meaning**|**Location in Data Set at which the Attribute is reported** 159 -|DataflowRelationship|The value of the attribute is fixed for all data contained in the dataset. The Attribute value applies to all data defined by the underlying Dataflow.|The attribute is reported at the Dataset level. 160 -|Dimension (1..n)|The value of the attribute will vary with the value(s) of the referenced Dimension(s). In this case, Group(s) to which the attribute should be attached may optionally be specified.|The attribute is reported at the lowest level of the Dimension to which the Attribute is related, otherwise at the level of the Group if Attachment Group(s) is specified. 161 -|Group|The value of the Attribute varies with combination of values for all of the Dimensions contained in the Group. This is added as a convenience to listing all Dimensions and the attachment Group, but should only be used when the Attribute value varies based on all Group Dimension values.|The attribute is reported at the level of Group. 162 -|Observation|The value of the Attribute varies with the observed value.|The attribute is reported at the level of Observation. 142 +(% style="width:1142.83px" %) 143 +|**Relationship**|(% style="width:537px" %)**Meaning**|(% style="width:434px" %)**Location in Data Set at which the Attribute is reported** 144 +|DataflowRelationship|(% style="width:537px" %)The value of the attribute is fixed for all data contained in the dataset. The Attribute value applies to all data defined by the underlying Dataflow.|(% style="width:434px" %)The attribute is reported at the Dataset level. 145 +|Dimension (1..n)|(% style="width:537px" %)The value of the attribute will vary with the value(s) of the referenced Dimension(s). In this case, Group(s) to which the attribute should be attached may optionally be specified.|(% style="width:434px" %)The attribute is reported at the lowest level of the Dimension to which the Attribute is related, otherwise at the level of the Group if Attachment Group(s) is specified. 146 +|Group|(% style="width:537px" %)The value of the Attribute varies with combination of values for all of the Dimensions contained in the Group. This is added as a convenience to listing all Dimensions and the attachment Group, but should only be used when the Attribute value varies based on all Group Dimension values.|(% style="width:434px" %)The attribute is reported at the level of Group. 147 +|Observation|(% style="width:537px" %)The value of the Attribute varies with the observed value.|(% style="width:434px" %)The attribute is reported at the level of Observation. 163 163 164 164 [[image:1749246368790-555.jpeg]] 165 165 ... ... @@ -169,7 +169,7 @@ 169 169 170 170 A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap. 171 171 172 - **5.3.2.2 Definitions**157 +==== 5.3.2.2 Definitions ==== 173 173 174 174 |**Class**|**Feature**|**Description** 175 175 |StructureUsage| |See “SDMX Base”. ... ... @@ -179,7 +179,7 @@ 179 179 //StructureUsage// 180 180 )))|Abstract concept (i.e., the structure without any data) of a flow of data that providers will provide for different reference periods. 181 181 | |/structure|Associates a Dataflow to the Data Structure Definition. 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]].167 +| |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}}. 183 183 |DataStructureDefiniti on| |A collection of metadata concepts, their structure and usage when used to collect or disseminate data. 184 184 | |/grouping|An association to a set of metadata concepts that have an identified structural role in a Data Structure Definition. 185 185 | |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. ... ... @@ -200,7 +200,7 @@ 200 200 201 201 //ComponentList// 202 202 )))|A set metadata concepts that define the Attributes of a Data Structure Definition. 203 -| |/ ////components|An association to a Data Attribute component.188 +| |/components|An association to a Data Attribute component. 204 204 |MeasureDescriptor|((( 205 205 Inherits from 206 206 ... ... @@ -219,9 +219,6 @@ 219 219 TimeDimension 220 220 )))|An abstract class representing any Component that can be used for identifying observations. 221 221 222 - 223 - 224 - 225 225 |**Class**|**Feature**|**Description** 226 226 | |Order|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|((( ... ... @@ -284,19 +284,19 @@ 284 284 285 285 ==== //5.4 Data Set – Relationship View// ==== 286 286 287 -=== ==5.4.1 Context =====269 +=== 5.4.1 Context === 288 288 289 289 A data set comprises the collection of data values and associated metadata that are collected or disseminated according to a known DataStructureDefinition. 290 290 291 -=== ==5.4.2 Class Diagram =====273 +=== 5.4.2 Class Diagram === 292 292 293 293 [[image:1749246368794-672.jpeg]] 294 294 295 295 **Figure 31: Class Diagram of the Data Set** 296 296 297 -=== ===5.4.3 Explanation of the Diagram ======279 +=== 5.4.3 Explanation of the Diagram === 298 298 299 -5.4.3.1 Narrative – Data Set 281 +==== 5.4.3.1 Narrative – Data Set ==== 300 300 301 301 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. 302 302 ... ... @@ -314,11 +314,11 @@ 314 314 315 315 The GroupKey is a subunit of the //Key// that has the same dimensionality as the SeriesKey but defines a subset of the KeyValues of the SeriesKey. Its sub dimension structure is defined in the GroupDimensionDescriptor of the DataStructureDefinition identified by the same id as the GroupKey. The id identifies a “type” of group and the purpose of the GroupKey is to report one or more //AttributeValue// that are contained at this group level. The GroupKey is present when the GroupDimensionDescriptor is related to the GroupRelationship in the DataStructureDefinition. There can be many types of groups in a //DataSet//. If the Group is related to the DimensionRelationship in the DataStructureDefinition then the //AttributeValue// will be reported with the appropriate dimension in the SeriesKey or Observation. 316 316 317 -In this way each of SeriesKey, GroupKey, and Observation can have zero or more //AttributeValue//s that define some metadata about the object to which it is associated. The //AttributeValue// may be either a //DataAttributeValue// or a //MetadataAttributeValue//, representing values of DataAttributes defined in the DSD or MetadataAttributes of the linked MSD, respectively. The allowable Concepts and the objects to which these metadata can be associated (attached) are defined in the DataStructureDefinition and the linked MetadataStructureDefinition.299 +In this way each of SeriesKey, GroupKey, and Observation can have zero or more //AttributeValue//s that define some metadata about the object to which it is associated. The //AttributeValue// may be either a //DataAttributeValue// or a //MetadataAttributeValue//, representing values of DataAttributes defined in the DSD or MetadataAttributes of the linked MSD, respectively. The allowable Concepts and the objects to which these metadata can be associated (attached) are defined in the DataStructureDefinition and the linked MetadataStructureDefinition. 318 318 319 319 The //AttributeValue// links to the object type (SeriesKey, GroupKey, Observation) to which it is associated. 320 320 321 -5.4.3.2 Definitions 303 +==== 5.4.3.2 Definitions ==== 322 322 323 323 |**Class**|**Feature**|**Description** 324 324 |//DataSet//|((( ... ... @@ -421,61 +421,46 @@ 421 421 422 422 Sub classes 423 423 424 -//UncodedObservationVal ue//406 +//UncodedObservationValue// 425 425 426 426 CodedObservation 427 427 )))| 428 428 |//UncodedObservatio nValue//|((( 429 429 Abstract class 430 - 431 431 Inherits from 432 - 433 433 //ObservationValue// 434 - 435 435 Sub classes 436 - 437 -OtherUncodedMeasureVa lue 438 - 415 +OtherUncodedMeasureValue 439 439 TextMeasureValue 440 440 )))| 441 441 |OtherUncodedMeasu reValue|((( 442 442 Inherits from 443 - 444 -//UncodedObservationVal ue// 420 +//UncodedObservationValue// 445 445 )))|An observation that has a text value. 446 446 | |value|The value of the Uncoded Observation. 447 447 | |startTime|This attribute is only used if the textFormat of the Measure is of the Timespan type in the Data Structure Definition (in which case the value field takes a duration). 448 448 |TextMeasureValue|((( 449 449 Inherits from 450 - 451 -//UncodedObservationVal ue// 426 +//UncodedObservationValue// 452 452 )))|An observation that has a localised text value 453 453 | |text|The localised text values. 454 454 |CodedObservation|((( 455 455 Inherits from 456 - 457 457 //ObservationValue// 458 458 )))|An Observation that takes its value from a code in a Code list. 459 459 | |+valueOf|Association to the Code that is the value of the Observation. Note that this is a conceptual association showing that the Code must exist in the Codelist(s) associated with the Measure(s) in the Data Structure Definition. In the actual Data Set the value of the Code is placed in the Observation. 460 460 |//AttributeValue//|((( 461 461 Abstract class 462 - 463 463 Sub classes 464 - 465 465 //DataAttributeValue// //MetadataAttributeValu e// 466 466 )))|Represents the value for any Attribute reported in the Dataset, i.e., Data or Metadata Attribute. 467 467 |//DataAttributeValu e//|((( 468 468 Abstract class 469 - 470 470 Inherits from 471 - 472 472 //AttributeValue// 473 - 474 474 Sub classes 475 - 476 -//UncodedAttributeValue// 477 - 478 -//CodedAttributeValue// 444 +//UncodedAttributeValue 445 +CodedAttributeValue// 479 479 )))|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. 480 480 | |+valueFor|((( 481 481 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. ... ... @@ -489,20 +489,14 @@ 489 489 )))|The value of a Metadata Attribute, as specified in the Metadata Structure Definition, which is linked in the Data Structure Definition 490 490 |//UncodedAttributeV alue//|((( 491 491 Inherits from 492 - 493 493 //AttributeValue// 494 - 495 495 Sub classes 496 - 497 497 OtherUncodedAttribute 498 - 499 499 Value 500 - 501 501 TextAttributeValue 502 502 )))| 503 503 |OtherUncodedAttri buteValue|((( 504 504 Inherits from 505 - 506 506 //UncodedObservationVal ue// 507 507 )))|An attribute value that has a text value 508 508 | |value|The value of the Uncoded attribute. ... ... @@ -509,19 +509,15 @@ 509 509 | |startTime|This attribute is only used if the textFormat of the attribute is of the Timespan type in the Data Structure Definition (in which case the value field takes a duration). 510 510 |TextAttributeValu e|((( 511 511 Inherits from 512 - 513 513 //UncodedAttributeValue// 514 514 )))|An attribute that has a localised text value 515 515 | |text|The localised text values. 516 516 |CodedAttributeVal ue|((( 517 517 Inherits from 518 - 519 519 //AttributeValue// 520 520 )))|An attribute that takes it value from a Code in Code list. 521 521 | |+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. 522 522 523 - 524 - 525 525 ---- 526 526 527 - [[~[1~]>>path:#_ftnref1]] Referencing the latest minor version of the Data Structure is achieved by the reference including the plusoperator onthe minor versionto indicateit linksto the latest stable version, for example 2.0+.0 will resolve to the highest version 2.x.y.484 +{{putFootnotes/}}
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,1 +1,1 @@ 1 - 131 +6