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)
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,22 +64,17 @@ 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 - 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: 82 - 83 83 DataStructureDefinition 84 84 85 85 A DataStructureDefinition contains a list of dimensions, a list of measures and a list of attributes. ... ... @@ -87,19 +87,14 @@ 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: 98 98 99 99 Measure 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. ... ... @@ -159,11 +159,12 @@ 159 159 160 160 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. 161 161 162 -|**Relationship**|**Meaning**|**Location in Data Set at which the Attribute is reported** 163 -|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. 164 -|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. 165 -|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. 166 -|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. 167 167 168 168 [[image:1749246368790-555.jpeg]] 169 169 ... ... @@ -223,9 +223,6 @@ 223 223 TimeDimension 224 224 )))|An abstract class representing any Component that can be used for identifying observations. 225 225 226 - 227 - 228 - 229 229 |**Class**|**Feature**|**Description** 230 230 | |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. 231 231 |Dimension|((( ... ... @@ -288,11 +288,11 @@ 288 288 289 289 ==== //5.4 Data Set – Relationship View// ==== 290 290 291 -=== ==5.4.1 Context =====269 +=== 5.4.1 Context === 292 292 293 293 A data set comprises the collection of data values and associated metadata that are collected or disseminated according to a known DataStructureDefinition. 294 294 295 -=== ==5.4.2 Class Diagram =====273 +=== 5.4.2 Class Diagram === 296 296 297 297 [[image:1749246368794-672.jpeg]] 298 298 ... ... @@ -318,7 +318,7 @@ 318 318 319 319 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. 320 320 321 -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. 322 322 323 323 The //AttributeValue// links to the object type (SeriesKey, GroupKey, Observation) to which it is associated. 324 324