Changes for page 5 Data Structure Definition and Dataset
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -32,22 +32,28 @@ 32 32 33 33 Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are: 34 34 35 -//IdentifiableArtefact 36 -DataSet 37 -Key// (and therefore //SeriesKey// and //GroupKey//) 35 +//IdentifiableArtefact// 36 + 37 +//DataSet// 38 + 39 +//Key// (and therefore //SeriesKey// and //GroupKey//) 40 + 38 38 //Observation// 39 39 40 40 Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are: 41 41 42 -//NameableArtefact 43 -ComponentList 44 -Component// 45 +//NameableArtefact// 45 45 47 +//ComponentList// 48 + 49 +//Component// 50 + 46 46 Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are: 47 47 48 -//VersionableArtefact 49 -Item// 53 +//VersionableArtefact// 50 50 55 +//Item// 56 + 51 51 The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are: 52 52 53 53 //MaintainableArtefact// ... ... @@ -54,15 +54,18 @@ 54 54 55 55 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: 56 56 57 -//StructureUsage 58 -Structure 59 -ItemScheme// 63 +//StructureUsage// 60 60 65 +//Structure// 66 + 67 +//ItemScheme// 68 + 61 61 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. 62 62 63 63 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: 64 64 65 65 Dataflow 74 + 66 66 DataStructureDefinition 67 67 68 68 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: ... ... @@ -74,8 +74,11 @@ 74 74 The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are: 75 75 76 76 DimensionDescriptor – content is Dimension and TimeDimension 86 + 77 77 DimensionGroupDescriptor – content is an association to Dimension, TimeDimension 88 + 78 78 MeasureDescriptor – content is Measure 90 + 79 79 AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute 80 80 81 81 The classes that inherit from //Component// are: ... ... @@ -83,6 +83,7 @@ 83 83 Measure 84 84 85 85 //DimensionComponent// and thereby its sub classes of Dimension and TimeDimension 98 + 86 86 //Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute 87 87 88 88 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. ... ... @@ -153,8 +153,10 @@ 153 153 154 154 **Figure 30: Representation of DSD Components** 155 155 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.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 157 157 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 + 158 158 A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap. 159 159 160 160 ==== 5.3.2.2 Definitions ==== ... ... @@ -167,6 +167,7 @@ 167 167 |StructureUsage|(% style="width:194px" %) |(% style="width:454px" %)See “SDMX Base”. 168 168 |Dataflow|(% style="width:194px" %)((( 169 169 Inherits from 185 + 170 170 //StructureUsage// 171 171 )))|(% 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. 172 172 | |(% style="width:194px" %)/structure|(% style="width:454px" %)Associates a Dataflow to the Data Structure Definition. ... ... @@ -174,11 +174,13 @@ 174 174 | |(% 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. 175 175 |GroupDimensionDescrip tor|(% style="width:194px" %)((( 176 176 Inherits from 193 + 177 177 //ComponentList// 178 178 )))|(% style="width:454px" %)A set of metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition. 179 179 | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to the Dimension components that comprise the group. 180 180 |DimensionDescriptor|(% style="width:194px" %)((( 181 181 Inherits from 199 + 182 182 //ComponentList// 183 183 )))|(% 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. 184 184 | |(% style="width:194px" %)/components|(% style="width:454px" %)((( ... ... @@ -186,24 +186,29 @@ 186 186 ))) 187 187 |AttributeDescriptor|(% style="width:194px" %)((( 188 188 Inherits from 207 + 189 189 //ComponentList// 190 190 )))|(% style="width:454px" %)A set metadata concepts that define the Attributes of a Data Structure Definition. 191 191 | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Data Attribute component. 192 192 |MeasureDescriptor|(% style="width:194px" %)((( 193 193 Inherits from 213 + 194 194 //ComponentList// 195 195 )))|(% style="width:454px" %)A metadata concept that defines the Measures of a Data Structure Definition. 196 196 | |(% style="width:194px" %)/components|(% style="width:454px" %)An association to a Measure component. 197 197 |//DimensionComponent//|(% style="width:194px" %)((( 198 198 Inherits from 219 + 199 199 //Component// 200 200 201 201 Sub class Dimension 223 + 202 202 TimeDimension 203 203 )))|(% style="width:454px" %)An abstract class representing any Component that can be used for identifying observations. 204 204 | |(% 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. 205 205 |Dimension|(% style="width:194px" %)((( 206 206 Inherits from 229 + 207 207 //DimensionComponent// 208 208 )))|(% 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. 209 209 | |(% 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. ... ... @@ -210,6 +210,7 @@ 210 210 | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the metadata concept which defines the semantic of the Dimension. 211 211 |TimeDimension|(% style="width:194px" %)((( 212 212 Inherits from 236 + 213 213 //DimensionComponent// 214 214 )))|(% style="width:454px" %)A metadata concept that identifies the component in the key structure that has the role of “time”. 215 215 |DataAttribute|(% style="width:194px" %)((( ... ... @@ -225,6 +225,7 @@ 225 225 | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which defines the semantic of the component. 226 226 |Measure|(% style="width:194px" %)((( 227 227 Inherits from 252 + 228 228 //Component// 229 229 )))|(% 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. 230 230 | |(% style="width:194px" %)/conceptIdentity|(% style="width:454px" %)An association to the Concept which carries the values of the measures. ... ... @@ -233,8 +233,11 @@ 233 233 | |(% style="width:194px" %)usage|(% style="width:454px" %)Defines whether a Measure must be reported or not. 234 234 |//AttributeRelationship//|(% style="width:194px" %)((( 235 235 Abstract Class 261 + 236 236 Sub classes 263 + 237 237 ObservationRelationship 265 + 238 238 GroupRelationship DimensionRelationshi p 239 239 )))|(% style="width:454px" %)Specifies the type of artefact to which a Data Attribute can be attached in a Data Set. 240 240 |ObservationRelationsh ip|(% style="width:194px" %) |(% style="width:454px" %)The Data Attribute is related to the observations of the Data Set.