Skip to Content
Version 3.1 by Helena on 2025/05/15 09:59
Hide last authors
Helena 2.1 1 = 5 Data Structure Definition and Dataset =
2
3 == 5.1 Introduction ==
4
5 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.
6
7 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.
8
9 There are very few additional classes in this sub model other than those shown in the inheritance diagram below. In other words, the SDMX Base gives most of the structure of this sub model both in terms of associations and in terms of attributes. The relationship diagrams shown in this section show clearly when these associations are inherited from the SDMX Base (see the Appendix “A Short Guide to UML in the SDMX Information Model” to see the diagrammatic notation used to depict this).
10
11 The actual SDMX Base construct from which the concrete classes inherit depends upon the requirements of the class for:
12
13 Annotation – //AnnotableArtefact//
14
15 Identification – //IdentifiableArtefact//
16
17 Naming – //NameableArtefact//
18
19 Versioning – //VersionableArtefact//
20
21 Maintenance – //MaintainableArtefact//
22
23 == 5.2 Inheritance View ==
24
25 === 5.2.1 Class Diagram ===
26
27 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_91284c0b.jpg||height="762" width="598"]]
28
29 **Figure 27 Class inheritance in the Data Structure Definition and Data Set Packages**
30
31 === 5.2.2 Explanation of the Diagram ===
32
33 ==== 5.2.2.1 Narrative ====
34
35 Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
36
37 //IdentifiableArtefact//
38
39 //DataSet//
40
41 //Key// (and therefore //SeriesKey// and //GroupKey//)
42
43 //Observation//
44
45 Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are:
46
47 //NameableArtefact//
48
49 //ComponentList//
50
51 //Component//
52
53 Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are:
54
55 //VersionableArtefact//
56
57 //Item//
58
59 The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are:
60
61 //MaintainableArtefact//
62
63 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:
64
65 //StructureUsage//
66
67 //Structure//
68
69 //ItemScheme//
70
71 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.
72
73 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:
74
75 Dataflow
76
77 DataStructureDefinition
78
79 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:
80
81 DataStructureDefinition
82
83 A DataStructureDefinition contains a list of dimensions, a list of measures and a list of attributes.
84
85 The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are:
86
87 DimensionDescriptor – content is Dimension and TimeDimension
88
89 DimensionGroupDescriptor – content is an association to Dimension, TimeDimension
90
91 MeasureDescriptor – content is Measure
92
93 AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute
94
95 The classes that inherit from //Component// are:
96
97 Measure
98
99 //DimensionComponent// and thereby its sub classes of Dimension and TimeDimension
100
101 //Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute
102
103 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.
104
105 == 5.3 Data Structure Definition – Relationship View ==
106
107 === 5.3.1 Class Diagram ===
108
109 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_c415af49.jpg||height="478" width="583"]]
110
111 **Figure 28 Relationship class diagram of the Data Structure Definition excluding representation**
112
113 === 5.3.2 Explanation of the Diagrams ===
114
115 ==== 5.3.2.1 Narrative ====
116
117 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.
118
119 The Dataflow may also have additional metadata attached that define qualitative information and Constraints on the use of the DataStructureDefinition such as the subset of Codes used in a Dimension (this is covered later in this document – see sections “Constraints” and “Data Provisioning”). Each Dataflow has a maximum of one DataStructureDefinition specified which defines the structure of any DataSets to be reported/disseminated.
120
121 There are two types of dimensions each having a common association to Concept:
122
123 * Dimension
124 * TimeDimension
125
126 Note that DimensionComponent can be any or all its sub classes i.e., Dimension, TimeDimension.
127
128 The //DimensionComponent//, DataAttribute, MetadataAttribute and Measure link to the Concept that defines its name and semantic (/conceptIdentity association to Concept). The DataAttribute, Dimension (but not TimeDimension) and Measure can optionally have a +conceptRole association with a Concept that identifies its role in the DataStructureDefinition, or one of the standard pre-defined roles, i.e., those published in "GUIDELINES FOR SDMX CONCEPT ROLES" by the SDMX SWG. The use of these roles is to enable applications to process the data in a meaningful way (e.g., relating a dimension value to a mapping vector). It is expected, beyond the standard roles published by the SWG, that communities (such as the official statistics community) will harmonise such roles within their community so that data can be exchanged and shared in a meaningful way within that community.
129
130 The valid values for a //DimensionComponent//, Measure, DataAttribute or MetadataAttribute, when used in this DataStructureDefinition, are defined by the Representation. This Representation is taken from the Concept definition (coreRepresentation) unless it is overridden in this DataStructureDefinition (localRepresentation) – see Figure 28. Note also that TimeDimension is constrained to specific FacetValueTypes. Moreover, the Representations of MetadataAttributes are specified in the corresponding MetadataStructureDefinition, linked by the DataStructureDefinition.
131
132 There will always be a DimensionDescriptor grouping that identifies all of the Dimension comprising the full key. Together the Dimensions specify the key of an Observation.
133
134 The //DimensionComponent// can optionally be grouped by multiple GroupDimensionDescriptors each of which identifies the group of Dimensions that can form a partial key. The GroupDimensionDescriptor must be identified (GroupDimensionDescriptor.id) and this is used in the GroupKey of the DataSet to declare which DataAttributes or MetadataAttributes are reported at this group level in the DataSet.
135
136 There can be a maximum of one TimeDimension specified in the DimensionDescriptor. The TimeDimension is used to specify the Concept used to convey the time period of the observation in a data set. The TimeDimension must contain a valid representation of time and cannot be coded.
137
138 here can be one or more Measures under the MeasureDescriptor. Measures represent the observable phenomena. Each Measure may have a valid representation, a maxOccurs attribute limiting the maximum number of values per Measure (which may be set to 'unbounded' for unlimited occurrences), as well as a minOccurs attribute, indicating the minimum required number of values, when the Measure is reported. If minOccurs or maxOccurs are omitted (they both default to ‘1’), the Measure is considered to take a single value; otherwise, it is an array. Moreover, the usage attribute indicates whether a Measure must be reported or not, by the corresponding values: mandatory or optional.
139
140 The AttributeDescriptor may contain one or more //Attribute//s, i.e., at least one DataAttribute definition or one MetadataAttribute reference.
141
142 The DataAttribute defines a characteristic of data that are collected or disseminated and is grouped in the DataStructureDefinition by a single AttributeDescriptor. The DataAttribute can be indicated if it must be reported or not, by the corresponding value of the usage attribute: i.e., mandatory or optional. The property minOccurs specifies the minimum number of array values to be included when the DataAttribute is reported. Moreover, a maxOccurs attribute indicates whether the DataAttribute may need to report more than one values, i.e., an array of values. The DataAttribute may play a specific role in the structure and this is specified by the +role association to the Concept that identifies its role.
143
144 The MetadataAttribute defines reference metadata that may be collected or disseminated and is grouped together with DataAttribute under the AttributeDescriptor.
145
146 A DataAttribute or a MetadataAttribute (i.e., an //AttributeComponent//) is specified as being +relatedTo an AttributeRelationship, which defines the constructs to which the //AttributeComponent// is to be reported within a //DataSet//. An //AttributeComponent// can be specified as being related to one of the following artefacts:
147
148 * All data within the dataset (DataflowRelationship) – this is equivalent to attaching an Attribute to all data within the Dataflow.
149 * Dimension or set of Dimensions (DimensionRelationship)
150 * Set of Dimensions specified by a GroupKey (GroupRelationship – this is retained for compatibility reasons – or +groupKey of the DimensionRelationship)
151 * Observation (ObservationRelationship)
152 * In addition to the positioning of an //AttributeComponent// within a //DataSet//, another relationship indicates the Measure(s) for which the //AttributeComponent// is reported. Regardless of the position of the //AttributeComponent// within the //DataSet//, the //AttributeComponent// may concern one, more than one, or all Measures included in the DSD. This is expressed using the MeasureRelationship class, which relates a DataAttribute to one or more Measures. Lack of the MeasureRelationship defaults to a relationship to all Measures.
153
154 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_f235bfd4.jpg||height="542" width="604"]]
155
156 **Figure 29: Attribute Attachment Defined in the Data Structure Definition**
157
158 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.
159
160 |**Relationship**|**Meaning**|**Location in Data Set at which the Attribute is reported**
161 |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.
162 |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.
163 |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.
164 |Observation|The value of the Attribute varies with the observed value.|The attribute is reported at the level of Observation.
165
166 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_42ff01fb.jpg||height="380" width="590"]]
167
168 **Figure 30: Representation of DSD Components**
169
170 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
171
172 (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.
173
174 A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
175
176 ==== 5.3.2.2 Definitions ====
177
178 :
179
180 (((
181 |**Class**|**Feature**|**Description**
182 |StructureUsage||See “SDMX Base”.
183 |Dataflow|(((
184 Inherits from
185
186 //StructureUsage//
187 )))|Abstract concept (i.e., the structure without any data) of a flow of data that providers will provide for different reference periods.
188 ||/structure|Associates a Dataflow to the Data Structure Definition.
189 |DataStructureDefiniti on||A collection of metadata concepts, their structure and usage when used to collect or disseminate data.
190 ||/grouping|An association to a set of metadata concepts that have an identified structural role in a Data Structure Definition.
191 |GroupDimensionDescrip tor|(((
192 Inherits from
193
194 //ComponentList//
195 )))|A set of metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition.
196 ||/components|An association to the Dimension components that comprise the group.
197 |DimensionDescriptor|(((
198 Inherits from
199
200 //ComponentList//
201 )))|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.
202 ||/components|(((
203 An association to the Dimension and Time
204
205 Dimension comprising the Key Descriptor.
206 )))
207 |AttributeDescriptor|(((
208 Inherits from
209
210 //ComponentList//
211 )))|A set metadata concepts that define the Attributes of a Data Structure Definition.
212 ||/////components//     //|An association to a Data Attribute component.
213 |MeasureDescriptor|(((
214 Inherits from
215
216 //ComponentList//
217 )))|A metadata concept that defines the Measures of a Data Structure Definition.
218 ||/components|An association to a Measure component.
219 |//DimensionComponent//|(((
220 Inherits from
221
222 //Component//
223
224 Sub class Dimension
225
226 TimeDimension
227 )))|An abstract class representing any Component that can be used for identifying observations.
228 ||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.
229 |Dimension|(((
230 Inherits from
231
232 //DimensionComponent//
233 )))|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.
234 ||/role|Association to the Concept that specifies the role that that the Dimension plays in the Data Structure Definition.
235 ||/conceptIdentity|An association to the metadata concept which defines the semantic of the Dimension.
236 |TimeDimension|(((
237 Inherits from
238
239 //DimensionComponent//
240 )))|A metadata concept that identifies the component in the key structure that has the role of “time”.
241 |DataAttribute|(((
242 Inherits from
243
244 //Component//
245 )))|A characteristic of an object or entity.
246 ||/role|Association to the Concept that specifies the role that that the Data Attribute plays in the Data Structure Definition.
247 ||minOccurs|Defines the minimum required occurrences for the Attribute. When equals to zero, the Attribute is conditional.
248 ||maxOccurs|Defines the maximum allowed occurrences for the Attribute.
249 ||usage|Defines whether a Data Attribute must be reported or not.
250 ||+relatedTo|Association to an Attribute Relationship.
251 ||/conceptIdentity|An association to the Concept which defines the semantic of the component.
252 |Measure|(((
253 Inherits from
254
255 //Component//
256 )))|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.
257 ||/conceptIdentity|An association to the Concept which carries the values of the measures.
258 ||minOccurs|Defines the minimum required occurrences for the Measure. When equals to zero, the Measure is conditional.
259 ||maxOccurs|Defines the maximum allowed occurrences for the Measure.
260 ||usage|Defines whether a Measure must be reported or not.
261 |//AttributeRelationship//|(((
262 Abstract Class
263
264 Sub classes
265
266 ObservationRelationship
267
268 GroupRelationship DimensionRelationshi p
269 )))|Specifies the type of artefact to which a Data Attribute can be attached in a Data Set.
270 |ObservationRelationsh ip||The Data Attribute is related to the observations of the Data Set.
271 |GroupRelationship||The Data Attribute is related to a Group Dimension Descriptor construct.
272 ||+groupKey|An association to the Group Dimension Descriptor
273 |DimensionRelationship||The Data Attribute is related to a set of Dimensions.
274 ||+dimensions|Association to the set of Dimensions to which the Data Attribute is related.
275 ||+groupKey|Association to the Group Dimension Descriptor which specifies the set of Dimensions to which the Data Attribute is attached.
276 |MeasureRelationship||The Measures that a Data Attribute is reported for.
277 ||+measures|Association to the set of Measures to which a Data Attribute is related to.
278 |SentinelValuesType||This facet indicates that an Attribute or a Measure has sentinel values with special meaning within their data type. This is realised by providing such values within the TextFormat, in addition to any textType or other Facet.
279 |SentinelValue||A value that has a special meaning within the text format representation of the Component.
280 ||+name|An association of a Sentinel Value to a multilingual name.
281 ||+description|An association of a Sentinel Value to a multilingual description.
282 )))
283
284
285
286 The explanation of the classes, attributes, and associations comprising the Representation is described in the section on the SDMX Base.
287
288 == 5.4 Data Set – Relationship View ==
289
290 === 5.4.1 Context ===
291
292 A data set comprises the collection of data values and associated metadata that are collected or disseminated according to a known DataStructureDefinition.
293
294 === 5.4.2 Class Diagram ===
295
296 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_78f5c87f.jpg||height="822" width="535"]]
297
298 **Figure 31: Class Diagram of the Data Set**
299
300 === 5.4.3 Explanation of the Diagram ===
301
302 ==== 5.4.3.1 Narrative – Data Set ====
303
304 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.
305
306 An organisation playing the role of DataProvider can be responsible for one or more //DataSet//.
307
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
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
311
312 DimensionDescriptor of the DataStructureDefinition, together with associated
313
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
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//).
317
318 The //KeyValue// is a value for one of TimeDimension or Dimension specified in the DataStructureDefinition. If it is a Dimension, it can be coded (CodedKeyValue) or uncoded (UncodedKeyValue). If it is the TimeDimension then it is a TimeKeyValue. The actual value that the CodedDimensionValue can take must be one of the Codes in the Codelist specified as the Representation of the Dimension in the DataStructureDefinition.
319
320 An ObservationValue can be coded – this is the CodedObservation – or it can be uncoded – this is the UncodedObservation. In the case of uncoded observations, the values may be multilingual – expressed via the TextMeasureValue – or not (OtherUncodedMeasureValue).
321
322 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.
323
324 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.
325
326 The //AttributeValue// links to the object type (SeriesKey, GroupKey, Observation) to which it is associated.
327
328 ==== 5.4.3.2 Definitions ====
329
330 |**Class**|**Feature**|**Description**
331 |//DataSet//|(((
332 Abstract Class
333
334 Sub classes
335
336 StructureSpecificData
337
338 Set
339 )))|An organised collection of data.
340 ||reportingBegin|A specific time period in a known system of time periods that identifies the start period of a report.
341 ||reportingEnd|A specific time period in a known system of time periods that identifies the end period of a report.
342 ||dataExtractionDate|A specific time period that identifies the date and time that the data are extracted from a data source.
343 ||validFrom|Indicates the inclusive start time indicating the validity of the information in the data set.
344 ||validTo|Indicates the inclusive end time indicating the validity of the information in the data set.
345 ||publicationYear|Specifies the year of publication of the data or metadata in terms of whatever provisioning agreements might be in force.
346 ||publicationPeriod|Specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force.
347 ||setId|Provides an identification of the data set.
348 ||action|Defines the action to be taken by the recipient system (information, append, replace, delete)
349 ||describedBy|Associates a Dataflow and thereby a Data Structure Definition to the data set.
350 ||+structuredBy|Associates the Data Structure Definition that defines the structure of the Data Set. Note that the Data Structure Definition is the same as that associated (non-mandatory) to the Dataflow.
351 ||+publishedBy|Associates the Data Provider that reports/publishes the data.
352 |StructureSpecific DataSet||An XML specific data format structure that contains data corresponding to one specific Data Structure Definition.
353 |//Key//|(((
354 Abstract class Sub classes
355
356 SeriesKey
357
358 GroupKey
359 )))|Comprises the cross product of values of dimensions that identify uniquely an Observation.
360 ||keyValues|Association to the individual Key Values that comprise the Key.
361 ||+attachedAttribute|Association to the Attribute Values relating to the Series Key or Group Key.
362 |//KeyValue//|(((
363 Abstract class Sub classes
364
365 TimeKeyValue
366
367 CodedKeyValue
368
369 UncodedKeyValue
370 )))|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.
371 ||+valueFor|(((
372 Association to the key component in the Data Structure Definition for which this Key Value is a valid representation.
373
374 Note that this is conceptual association as the key component is identified explicitly in the data set.
375 )))
376 |TimeKeyValue|(((
377 Inherits from
378
379 //KeyValue//
380 )))|The value of the Time Dimension component of the key.
381 |CodedKeyValue|(((
382 Inherits from
383
384 //KeyValue//
385 )))|The value of a coded component of the key. The value is the Code to which this class is associated.
386 ||+valueOf|Association to the Code. Note that this is a conceptual association showing that the Code must exist in the Code list associated with the Dimension in the Data Structure Definition. In the actual Data Set the value of the Code is placed in the Key Value.
387 |UnCodedKeyValue|(((
388 Inherits from
389
390 //KeyValue//
391 )))|The value of an uncoded component of the key.
392 ||value|The value of the key component.
393 ||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).
394 |GroupKey|(((
395 Inherits from
396
397 //Key//
398 )))|A set of Key Values that comprise a partial key, of the same dimensionality as the Time Series Key for the purpose of attaching Data Attributes.
399 ||+describedBy|Associates the Group Dimension Descriptor defined in the Data Structure Definition.
400 |SeriesKey|(((
401 Inherits from
402
403 //Key//
404 )))|Comprises the cross product of values of all the Key Values that, together with the Key Value of the +observation Dimension identify uniquely an Observation.
405 ||+describedBy|Associates the Dimension Descriptor defined in the Data Structure Definition.
406 |Observation||The value(s) of the observed phenomenon in the context of the Key Values comprising the key.
407 ||+valueFor|(((
408 Associates the Measure(s) defined in the Data Structure Definition.
409
410 The source multiplicity (1..*) indicates that more than one values may be provided for a Measure, if the latter allows it.
411 )))
412 ||+attachedAttribute|Association to the Attribute Values relating to the Observation.
413 ||+observationDimension|Association to the Key Value that holds the value of the “Dimension at the Observation Level”.
414 |//ObservationValue//|(((
415 Abstract class
416
417 Sub classes
418
419 //UncodedObservationVal//
420
421 //ue//
422
423 CodedObservation
424 )))|
425 |//UncodedObservatio nValue//|(((
426 Abstract class
427
428 Inherits from
429
430 //ObservationValue//
431
432 Sub classes
433
434 OtherUncodedMeasureVa lue
435
436 TextMeasureValue
437 )))|
438 |OtherUncodedMeasu reValue|(((
439 Inherits from
440
441 //UncodedObservationVal ue//
442 )))|An observation that has a text value.
443 ||value|The value of the Uncoded Observation.
444 ||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).
445 |TextMeasureValue|(((
446 Inherits from
447
448 //UncodedObservationVal ue//
449 )))|An observation that has a localised text value
450 ||text|The localised text values.
451 |CodedObservation|(((
452 Inherits from
453
454 //ObservationValue//
455 )))|An Observation that takes its value from a code in a Code list.
456 ||+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.
457 |//AttributeValue//|(((
458 Abstract class
459
460 Sub classes
461
462 //DataAttributeValue// //MetadataAttributeValu e//
463 )))|Represents the value for any Attribute reported in the Dataset, i.e., Data or Metadata Attribute.
464 |//DataAttributeValu e//|(((
465 Abstract class
466
467 Inherits from
468
469 //AttributeValue//
470
471 Sub classes
472
473 //UncodedAttributeValue//
474
475 //CodedAttributeValue//
476 )))|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.
477 ||+valueFor|(((
478 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.
479
480 The source multiplicity (1..*) indicates the possibility to provide more than one values for a Data Attribute, if the latter allows it.
481 )))
482 |//MetadataAttribute Value//|(((
483 (explained further in section
484
485 “Metadata Set”)
486 )))|(((
487 The value of a Metadata Attribute, as specified in the Metadata Structure Definition, which is linked in the Data Structure
488
489 Definition
490 )))
491 |//UncodedAttributeV alue//|(((
492 Inherits from
493
494 //AttributeValue//
495
496 Sub classes
497
498 OtherUncodedAttribute Value
499
500 TextAttributeValue
501 )))|
502 |OtherUncodedAttri buteValue|(((
503 Inherits from
504
505 //UncodedObservationVal ue//
506 )))|An attribute value that has a text value
507 ||value|The value of the Uncoded attribute.
508 ||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).
509 |TextAttributeValu e|(((
510 Inherits from
511
512 //UncodedAttributeValue//
513 )))|An attribute that has a localised text value
514 ||text|The localised text values.
515 |CodedAttributeVal ue|(((
516 Inherits from
517
518 //AttributeValue//
519 )))|An attribute that takes it value from a Code in Code list.
520 ||+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.
521
522
523
524