Wiki source code of 5 Data Structure Definition and Dataset

Version 9.1 by Helena on 2025/05/22 10:44

version	line-number	content
6.1	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
2.1	4
	5	== {{id name="_Toc371009"/}}5.1 Introduction ==
	6
	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
	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.
	10
	11	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).
	12
	13	The actual SDMX Base construct from which the concrete classes inherit depends upon the requirements of the class for:
	14
	15	* Annotation - //AnnotableArtefact//
	16	* Identification - //IdentifiableArtefact//
	17	* Naming - //NameableArtefact//
	18	* Versioning – //VersionableArtefact//
	19	* Maintenance - //MaintainableArtefact//
	20
	21	== {{id name="_Toc371010"/}}5.2 Inheritance View ==
	22
	23	=== {{id name="_Toc371011"/}}5.2.1 Class Diagram ===
	24
	25	[[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_aa1923f1.png\|\|height="628" width="556"]]
	26
	27	Figure 22 Class inheritance in the Data Structure Definition and Data Set Packages
	28
	29	=== {{id name="_Toc371012"/}}5.2.2 Explanation of the Diagram ===
	30
	31	==== 5.2.2.1 Narrative ====
	32
	33	Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact// . These are:
	34
	35	* //IdentifiableArtefact//
	36	* DataSet (and therefore StructureSpecificDataSet, GenericDataSet, GenericTimeSeriesDataSet StructureSpecificTimeSeriesDataSet)
3.3	37	* //Key //(and therefore SeriesKey and GroupKey)
2.1	38
	39	Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact// . These are:
	40
	41	* //NameableArtefact//
	42	* //ComponentList//
	43	* //Component//
	44
	45	Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact// . These are:
	46
	47	* //VersionableArtefact//
	48	* //Item//
	49
	50	The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact// . These are:
	51
	52	* //MaintainableArtefact//
	53
	54	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:
	55
	56	* //StructureUsage//
	57	* //Structure//
	58	* //ItemScheme//
	59
	60	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.
	61
	62	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:
	63
3.3	64	* DataflowDefinition
	65	* DataStructureDefinition
2.1	66
	67	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:
	68
3.3	69	* DataStructureDefinition
2.1	70
	71	A DataStructureDefinition contains a list of dimensions, a list of measures and a list of attributes.
	72
	73	The concrete classes which inherit from //ComponentList// and are sub components of the DataStructureDefinition are:
	74
	75	* DimensionDescriptor – content is Dimension, MeasureDimension and Time Dimension
	76	* DimensionGroupDescriptor – content is an association to Dimension, MeasureDimension, TimeDimension
	77	* MeasureDescriptor – content is PrimaryMeasure
	78	* AttributeDescriptor – content is DataAttribute
	79
	80	The classes that inherit from //Component// are:
	81
	82	* PrimaryMeasure
	83	* DimensionComponent and thereby its sub classes of Dimension, MeasureDimension, and TimeDimension
	84	* DataAttribute
	85
	86	The class that inherit from DataAttribute is:
	87
	88	* ReportingYearStartDay
	89
	90	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.
	91
	92	== {{id name="_Toc371013"/}}5.3 Data Structure Definition – Relationship View ==
	93
	94	=== {{id name="_Toc371014"/}}5.3.1 Class Diagram ===
	95
7.1	96	(% class="wikigeneratedid" %)
	97	[[image:1747897165713-725.png]]
2.1	98
7.1	99	(% class="wikigeneratedid" id="HFigure23RelationshipclassdiagramoftheDataStructureDefinitionexcludingrepresentation" %)
	100	Figure 23 Relationship class diagram of the Data Structure Definition excluding representation
	101
2.1	102	=== {{id name="_Toc371015"/}}5.3.2 Explanation of the Diagrams ===
	103
	104	==== 5.3.2.1 Narrative ====
	105
	106	A DataStructureDefinition defines the Dimensions, MeasureDimension, TimeDimension, DataAttributes, and PrimaryMeasure, and associated Representation that comprise the valid structure of data and related attributes that are contained in a DataSet, which is defined by a DataflowDefinition.
	107
	108	The DataflowDefinition may also have additional metadata attached that defines qualitative information and Constraints on the use of the DataStructureDefinition such as the sub set of Codes used in a Dimension (this is covered later in this document – see “Data Constraints and Provisioning” section 9). Each DataflowDefinition has a maximum of one DataStructureDefinition specified which defines the structure of any DataSets to be reported/disseminated.
	109
	110	There are three types of dimension each having a common association to Concept:
	111
	112	* Dimension
4.2	113	* MeasureDimension
	114	* TimeDimension
2.1	115
	116	Note that In the description here //DimensionComponent// can be oany or all of its sub classes i.e. Dimension, MeasureDimension, TimeDimension., and the term “DataAttribute” refers to both DataAttribute and its sub class ReportingYearStartDate.
	117
	118	The //DimensionComponent//, DataAttribute, and PrimaryMeasure link to the Concept that defines its name and semantic (/conceptIdentity association to Concept). The DataAttribute, Dimension, and MeasureDimension (but not TimeDimension) can optionally have a +conceptRole association with a Concept that identifies its role in the DataStructureDefinition. Therefore, the allowable roles of a Concept are maintained in a ConceptScheme. Examples of roles are: geography, entity, count, unit of measure. 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 that communities (such as the official statistics community) will harmonise these roles with their community so that data can be exchanged and shared in a meaningful way in the community.
	119
4.2	120	The valid values for a //DimensionComponent//, PrimaryMeasure, or DataAttribute, 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 23. Note that for the MeasureDimension the Representation must be a ConceptScheme and this must always be referenced from the MeasureDimension and cannot therefore be defaulted to the Representation of the Concept associated by the/conceptIdentity. Note also that TimeDimension and ReportingYearStartDate are constrained to specific FacetValueTypes
2.1	121
	122	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.
	123
	124	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 are reported at this group level in the DataSet.
	125
	126	There may be a maximum of one MeasureDimension specified in the DimensionDescriptor. The purpose of a MeasureDimension is to specify formally the meaning of the measures (because the PrimaryMeasure typically has a generic meaning e.g. observation value) and to enable multiple measures to be defined and reported in a StructureSpecificDataSet. Note that the MeasureDimension references a ConceptScheme as its Representation (see later) whereas a Dimension can have either an enumerated (Codelist) or non-enumerated (Facet) representation. For a MeasureDimension the Concepts in the ConceptScheme comprise the list of allowable measures. This enables the representation for each individual measure (Concept) to be declared as the coreRepresentation of the Concept, thus overriding the Representation specified for the PrimaryMeasure for the observation value of this MeasureDimension Concept.
	127
	128	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
	129
	130	The PrimaryMeasure is the observable phenomenon, and, although there can be only one PrimaryMeasure, for consistency with the ComponentList/Component pattern it is grouped by a MeasureDescriptor.
	131
	132	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 specified as being mandatory, or conditional, as defined in usageStatus. 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.
	133
	134	A DataAttribute is specified as being +relatedTo an AttributeRelationship which defines the constructs to which the DataAttribute is to be reported present in a //DataSet//. The DataAttribute can be specified as being related to one of the following artefacts:
	135
	136	* DataSet (NoSpecifiedRelationship)
	137	* Dimension or set of Dimensions (DimensionRelationship)
	138	* Set of Dimensions specified by a GroupKey (GroupRelationship – this is retained for compatibility reasons – or +groupKey of the DimensionRelationship)
	139	* Observation (PrimaryMeasureRelationship)
	140
6.1	141	[[image:1747896950895-141.png]]
	142
2.1	143	Figure 24: Attribute Attachment Defined in the Data Structure Definition
	144
	145	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.
	146
	147	(((
4.2	148	(% style="width:1104.83px" %)
5.1	149	\|Relationship\|(% style="width:415px" %)Meaning\|(% style="width:556px" %)Location in Data Set at which the Attribute is reported
	150	\|None\|(% style="width:415px" %)The value of the attribute does not vary with the values of any other Component.\|(% style="width:556px" %)The attribute is reported at the level of the Dataset Attribute.
2.1	151	\|(((
	152	Dimension
	153
	154	(1..n)
5.1	155	)))\|(% style="width:415px" %)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:556px" %)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.
	156	\|Relationship\|(% style="width:415px" %)Meaning\|(% style="width:556px" %)Location in Data Set at which the Attribute is reported
	157	\|Group\|(% style="width:415px" %)(((
4.2	158	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.
5.1	159	)))\|(% style="width:556px" %)The attribute is reported at the level of Group.
	160	\|Primary Measure\|(% style="width:415px" %)The value of the Attribute varies with the observed value.\|(% style="width:556px" %)The attribute is reported at the level of Observation.
2.1	161	)))
	162
	163	Figure 25: Representation of DSD Components
	164
	165	Each of Dimension, MeasureDimension, TimeDimension, PrimaryMeasure, and DataAttribute 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. For the MeasureDimension the representation for the individual measures is specified for the Concept in the ConceptScheme referenced by the MeasureDimension.
	166
	167	A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
	168
	169	==== 5.3.2.2 Definitions ====
	170
5.1	171	(% style="width:1060.83px" %)
	172	\|Class\|Feature\|(% style="width:695px" %)Description
	173	\|StructureUsage\| \|(% style="width:695px" %)See “SDMX Base”.
2.1	174	\|DataflowDefinition\|(((
	175	Inherits from
	176	//StructureUsage//
5.1	177	)))\|(% style="width:695px" %)Abstract concept (i.e. the structure without any data) of a flow of data that providers will provide for different reference periods.
	178	\| \|/structure\|(% style="width:695px" %)Associates a Dataflow Definition to the Data Structure Definition.
	179	\|DataStructureDefinition\| \|(% style="width:695px" %)A collection of metadata concepts, their structure and usage when used to collect or disseminate data.
	180	\| \|///grouping//\|(% style="width:695px" %)An association to a set of metadata concepts that have an identified structural role in a Data Structure Definition.
2.1	181	\|(((
	182	Group
	183
	184	DimensionDescriptor
	185	)))\|(((
	186	Inherits from
	187	//ComponentList//
5.1	188	)))\|(% style="width:695px" %)A set metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition.
	189	\| \|+constraint\|(% style="width:695px" %)Identifies an Attachment Constraint that specifies the sub set of Dimension, Measure, or Attribute values to which an Attribute can be attached.
	190	\| \|/components\|(% style="width:695px" %)An association to the Dimension and Measure Dimension components that comprise the group.
2.1	191	\|DimensionDescriptor\|(((
	192	Inherits from
	193	//ComponentList//
5.1	194	)))\|(% style="width:695px" %)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.
	195	\| \|/components\|(% style="width:695px" %)An association to the Dimension, Measure Dimension, and Time Dimension comprising the Key Descriptor.
2.1	196	\|AttributeDescriptor\|(((
	197	Inherits from
	198	//ComponentList//
5.1	199	)))\|(% style="width:695px" %)A set metadata concepts that define the attributes of a Data Structure Definition.
	200	\| \|/components\|(% style="width:695px" %)An association to a Data Attribute component.
2.1	201	\|MeasureDescriptor\|(((
	202	Inherits from
	203
	204	//ComponentList//
5.1	205	)))\|(% style="width:695px" %)A metadata concept that defines the measure of a Data Structure Definition.
	206	\| \|/components\|(% style="width:695px" %)An association to a measure component.
2.1	207	\|Dimension\|(((
	208	Inherits from
	209	Component
5.1	210	)))\|(% style="width:695px" %)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.
	211	\| \|/role\|(% style="width:695px" %)Association to the Concept that specifies the role that that the Dimension plays in the Data Structure Definition.
	212	\| \|/conceptIdentity\|(% style="width:695px" %)An association to the metadata concept which defines the semantic of the Dimension.
2.1	213	\|MeasureDimension\|(((
	214	Inherits from
	215
3.4	216	Dimension
5.1	217	)))\|(% style="width:695px" %)A statistical concept that identifies the component in the key structure that has an enumerated list of measures. This dimension has, as its representation the Concept Scheme that enumerates the measure concepts.
2.1	218	\|DataAttribute\|(((
	219	Inherits from
	220	Component
	221	Sub class
	222	ReportingYear
	223	StartDay
5.1	224	)))\|(% style="width:695px" %)A characteristic of an object or entity.
	225	\| \|/role\|(% style="width:695px" %)Association to the Concept that specifies the role that that the Data Attribute plays in the Data Structure Definition.
	226	\| \|usageStatus\|(% style="width:695px" %)Defines the usage status which is constrained by the data type Usage Status.
	227	\| \|+relatedTo\|(% style="width:695px" %)Association to a Attribute Relationship.
	228	\| \|/conceptIdentity\|(% style="width:695px" %)An association to the Concept which defines the semantic of the component.
2.1	229	\|TimeDimension\|(((
	230	Inherits from
	231
3.4	232	Dimension
5.1	233	)))\|(% style="width:695px" %)A metadata concept that identifies the component in the key structure that has the role of “time”.
2.1	234	\|ReportingYearStartDay\|(((
	235	Inherits from
	236	DataAttribute
5.1	237	)))\|(% style="width:695px" %)A specialised Data Attribute whose value is used in conjunction with the predefined reporting periods in the Time Dimension. If this is not present, then by default all reporting period values for the Time Dimension will be assumed to be based on a reporting year start day of January 1.
2.1	238	\|PrimaryMeasure\|(((
	239	Inherits from
	240	//Component//
5.1	241	)))\|(% style="width:695px" %)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.
	242	\| \|/conceptIdentity\|(% style="width:695px" %)An association to the Concept which carries the values of the measures.
2.1	243	\|//AttributeRelationship//\|(((
	244	Abstract Class
	245	Sub classes
	246	NoSpecified
	247	Relationship
	248	PrimaryMeasure
	249	Relationship
	250	GroupRelationship
	251	Dimension
	252	Relationship
5.1	253	)))\|(% style="width:695px" %)Specifies the type of artefact to which a Data Attribute can be attached in a Data Set.
	254	\|NoSpecifiedRelationship\| \|(% style="width:695px" %)The Data Attribute is not related to any specific construct.
	255	\|PrimaryMeasure Relationship\| \|(% style="width:695px" %)The Data Attribute is related to the Primary Measure construct.
	256	\|GroupRelationship\| \|(% style="width:695px" %)The Data Attribute is related to a Group Dimension Descriptor construct.
	257	\| \|+groupKey\|(% style="width:695px" %)An association to the Group Dimension Descriptor
	258	\|DimensionRelationship\| \|(% style="width:695px" %)The Data Attribute is related to a set of Dimensions.
	259	\| \|+dimensions\|(% style="width:695px" %)Association to the set of Dimensions to which the Data Attribute is related.
	260	\| \|+groupKey\|(% style="width:695px" %)Association to the Group Dimension Descriptor which specifies the set of Dimensions to which the Data Attribute is attached.
2.1	261
	262	The explanation of the classes, attributes, and associations comprising the Representation is described in the section on the SDMX Base.
	263
	264	== {{id name="_Toc371016"/}}5.4 Data Set – Relationship View ==
	265
	266	=== {{id name="_Toc371017"/}}5.4.1 Context ===
	267
	268	A data set comprises the collection of data values and associated metadata that are collected or disseminated according to a known DataStructureDefinition.
	269
	270	=== {{id name="_Toc371018"/}}5.4.2 Class Diagram ===
	271
6.1	272	(% class="wikigeneratedid" id="H" %)
	273	[[image:1747897072125-219.png]]
2.1	274
6.1	275	(% class="wikigeneratedid" id="HFigure26ClassDiagramoftheDataSet" %)
	276	Figure 26 Class Diagram of the Data Set
3.6	277
2.1	278	=== {{id name="_Toc371019"/}}5.4.3 Explanation of the Diagram ===
	279
	280	==== 5.4.3.1 Narrative – Data Set ====
	281
	282	Note that the //DataSet// must conform to the DataStructureDefinition associated to the DataflowDefinition 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 DataflowDefinition, 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.
	283
	284	An organisation playing the role of DataProvider can be responsible for one or more //DataSet//.
	285
3.5	286	A //DataSet// can be formatted either as a generic data set (GenericDataSet, GenericTimeseriesDataSet) or a DataStructureDefinition specific data set (StructureSpecificDataSet, StructureSpecificTimeseriesDataSet). The generic data set is structured in exactly the same way no matter which DataStructureDefinition the DataSet expresses. The structured data set is structured according to one specific DataStructureDefinition. Depending on the syntax chosen for the implementation the structured data set should support better validation at the syntax level.
2.1	287
	288	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, MeasureDimension, TimeDimension) defined in the DimensionDescriptor of the DataStructureDefinition, together with associated //AttributeValue//s that define specific characteristics about the artefact to which it is attached. - DataSet, Observation, set of Dimensions. It is structured in terms of a SeriesKey to which //Observation//s are reported.
	289
	290	The Observation can be the value of the variable being measured for the Concept associated to the PrimaryMeasure in the MeasureDescriptor of the DataStructureDefinition. This is true when there is no MeasureDimension that specifies the precise meaning of each Observation. Each Observation associates an ObservationValue 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//).
	291
	292	If the “Dimension at the Observation Level” is the MeasureDimension it is possible (but not mandatory) that an Observation can be reported with an explicit identification of one or more Concept in the ConceptScheme referenced by the MeasureDimension as its Representation. In other words, the actual Concepts are explicitly stated in the Observation.
	293
	294	If it is required to specify explicitly that the DataSet is time series then one of GenericTimeSeriesDataSet or StructureSpecificTimeSeriesDataSet is used and the //KeyValue// for the +observationDimension must be a TimeKeyValue. In a GenericDataSet and a StructureSpecificDataSet it is permissible to have any dimension as the +observationDimension including the TimeDimension.
	295
	296	The //KeyValue// is a value for one of MeasureDimension, TimeDimension, or Dimension specified in the DataStructureDefinition. If it is a Dimension it can be coded (CodedKeyValue) or uncoded (UncodedKeyValue). If it is a MeasureDimension then it is MeasureKeyValue. If it is 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. The actual value that the MeasureDimensionValue can take must be a valid representation specified for the Concept in the ConceptScheme to which this MeasureDimensionValue is related (+valueFor).
	297
	298	The ObservationValue can be coded - this is the CodedObservation – or it can be uncoded – this is the UncodedObservation.
	299
	300	The GroupKey is a sub unit 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
	301
	302	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.
	303
	304	In this way each of //DataSet//, SeriesKey, GroupKey, and Observation can have zero or more AttributeValue that defines some metadata about the object to which it is associated. The allowable Concepts and the objects to which these metadata can be associated (attached) are defined in the DataStructureDefinition.
	305
	306	The //AttributeValue// links to the object type (DataSet, SeriesKey, GroupKey, Observation,) to which it is associated.
	307
	308	==== 5.4.3.2 Definitions ====
	309
3.5	310	(% style="width:1012.83px" %)
	311	\|(% style="width:182px" %)Class\|(% style="width:210px" %)Feature\|(% style="width:617px" %)Description
	312	\|(% style="width:182px" %)//DataSet//\|(% style="width:210px" %)(((
2.1	313	Abstract Class
	314	Sub classes
	315	GenericDataSet
	316	StructureSpecificDataSet
	317	GenericTime
	318	SeriesDataSet
	319	StructureSpecificTime
	320	SeriesDataSet
3.5	321	)))\|(% style="width:617px" %)An organised collection of data.
	322	\|(% style="width:182px" %) \|(% style="width:210px" %)reportingBegin\|(% style="width:617px" %)A specific time period in a known system of time periods that identifies the start period of a report.
	323	\|(% style="width:182px" %) \|(% style="width:210px" %)reportingEnd\|(% style="width:617px" %)A specific time period in a known system of time periods that identifies the end period of a report.
	324	\|(% style="width:182px" %) \|(% style="width:210px" %)dataExtractionDate\|(% style="width:617px" %)A specific time period that identifies the date and time that the data are extracted from a data source.
	325	\|(% style="width:182px" %) \|(% style="width:210px" %)validFrom\|(% style="width:617px" %)Indicates the inclusive start time indicating the validity of the information in the data set.
	326	\|(% style="width:182px" %) \|(% style="width:210px" %)validTo\|(% style="width:617px" %)Indicates the inclusive end time indicating the validity of the information in the data set.
	327	\|(% style="width:182px" %) \|(% style="width:210px" %)publicationYear\|(% style="width:617px" %)Specifies the year of publication of the data or metadata in terms of whatever provisioning agreements might be in force.
	328	\|(% style="width:182px" %) \|(% style="width:210px" %)publicationPeriod\|(% style="width:617px" %)Specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force.
	329	\|(% style="width:182px" %) \|(% style="width:210px" %)setId\|(% style="width:617px" %)Provides an identification of the data set.
	330	\|(% style="width:182px" %) \|(% style="width:210px" %)action\|(% style="width:617px" %)Defines the action to be taken by the recipient system (update, append, delete)
	331	\|(% style="width:182px" %) \|(% style="width:210px" %)describedBy\|(% style="width:617px" %)Associates a data flow definition and thereby a Data Structure Definition to the data set.
	332	\|(% style="width:182px" %) \|(% style="width:210px" %)+structuredBy\|(% style="width:617px" %)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 (nonmandatory) to the Dataflow Definition.
	333	\|(% style="width:182px" %) \|(% style="width:210px" %)+publishedBy\|(% style="width:617px" %)Associates the Data Provider that reports/publishes the data.
	334	\|(% style="width:182px" %) \|(% style="width:210px" %)+attachedAttribute\|(% style="width:617px" %)Association to the Attribute Values relating to the Data Set
	335	\|(% style="width:182px" %)GenericDataSet\|(% style="width:210px" %) \|(% style="width:617px" %)A data format structure that is able to contain data corresponding to any Data Structure Definition.
	336	\|(% style="width:182px" %)StructureSpecific DataSet\|(% style="width:210px" %) \|(% style="width:617px" %)A data format structure that contains data corresponding to one specific Data Structure Definition.
	337	\|(% style="width:182px" %)GenericTimeseries DataSet\|(% style="width:210px" %) \|(% style="width:617px" %)A data format structure that is able to contain timeseries data corresponding to any Data Structure Definition.
	338	\|(% style="width:182px" %)(((
2.1	339	StructureSpecific
	340
	341	TimeseriesDataSet
3.5	342	)))\|(% style="width:210px" %) \|(% style="width:617px" %)A data format structure that contains timeseries data corresponding to one specific Data Structure Definition.
	343	\|(% style="width:182px" %)Key\|(% style="width:210px" %)(((
2.1	344	Abstract class Sub classes
	345	SeriesKey
	346	GroupKey
3.5	347	)))\|(% style="width:617px" %)Comprises the cross product of values of dimensions that identify uniquely an Observation.
	348	\|(% style="width:182px" %) \|(% style="width:210px" %)keyValues\|(% style="width:617px" %)Association to the individual Key Values that comprise the Key.
	349	\|(% style="width:182px" %) \|(% style="width:210px" %)+attachedAttribute\|(% style="width:617px" %)Association to the Attribute Values relating to the Series Key or Group Key.
	350	\|(% style="width:182px" %)//KeyValue//\|(% style="width:210px" %)(((
2.1	351	Abstract class
	352	Sub classes
	353	MeasureKeyValue
	354	TimeKeyValue
	355	CodedKeyValue
	356	UncodedKeyValue
3.5	357	)))\|(% style="width:617px" %)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.
	358	\|(% style="width:182px" %) \|(% style="width:210px" %)+valueFor\|(% style="width:617px" %)(((
2.1	359	Association to the key component in the Data Structure Definition for which this Key Value is a valid representation.
	360	Note that this is conceptual association as the key component is identified explicitly in the data set.
	361	)))
3.5	362	\|(% style="width:182px" %)MeasureKeyValue\|(% style="width:210px" %)(((
2.1	363	Inherits from
	364	//KeyValue//
3.5	365	)))\|(% style="width:617px" %)The value of the Measure Dimension component of the key. The value is the Concept to which this class is associated.
	366	\|(% style="width:182px" %) \|(% style="width:210px" %)+value\|(% style="width:617px" %)(((
2.1	367	Association to the Concept.
3.5	368	Note that this is a conceptual association showing that the Concept must exist in the Concept Scheme associated with the Measure Dimension in the Data Structure Definition. In the actual Data Set the value of the Concept is placed in the Key Value.
2.1	369	)))
3.5	370	\|(% style="width:182px" %)TimeKeyValue\|(% style="width:210px" %)(((
2.1	371	Inherits from
	372	//KeyValue//
3.5	373	)))\|(% style="width:617px" %)The value of the Time Dimension component of the key.
	374	\|(% style="width:182px" %)CodedKeyValue\|(% style="width:210px" %)(((
2.1	375	Inherits from
	376	//KeyValue//
3.5	377	)))\|(% style="width:617px" %)The value of a coded component of the key. The value is the Code to which this class is associated.
	378	\|(% style="width:182px" %) \|(% style="width:210px" %)+value\|(% style="width:617px" %)(((
2.1	379	Association to the Code.
3.5	380	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.
2.1	381	)))
3.5	382	\|(% style="width:182px" %)UnCodedKeyValue\|(% style="width:210px" %)(((
2.1	383	Inherits from
	384	//KeyValue//
3.5	385	)))\|(% style="width:617px" %)The value of an uncoded component of the key.
	386	\|(% style="width:182px" %) \|(% style="width:210px" %)value\|(% style="width:617px" %)The value of the key component.
	387	\|(% style="width:182px" %) \|(% style="width:210px" %)startTime\|(% style="width:617px" %)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).
	388	\|(% style="width:182px" %) \|(% style="width:210px" %)+valueFor\|(% style="width:617px" %)Associates Dimension, Measure Dimension, or Time Dimension to the Key Value, and thereby to the Concept that is the semantic of the Dimension, or Time Dimension.
	389	\|(% style="width:182px" %)GroupKey\|(% style="width:210px" %)(((
2.1	390	Inherits from
	391
	392	Key
3.5	393	)))\|(% style="width:617px" %)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.
	394	\|(% style="width:182px" %) \|(% style="width:210px" %)+describedBy\|(% style="width:617px" %)Associates the Group Dimension Descriptor defined in the Data Structure Definition.
	395	\|(% style="width:182px" %)SeriesKey\|(% style="width:210px" %)(((
2.1	396	Inherits from
	397	Key
3.5	398	)))\|(% style="width:617px" %)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.
	399	\|(% style="width:182px" %) \|(% style="width:210px" %)+describedBy\|(% style="width:617px" %)Associates the Dimension Descriptor defined in the Data Structure Definition.
	400	\|(% style="width:182px" %)Observation\|(% style="width:210px" %) \|(% style="width:617px" %)The value of the observed phenomenon in the context of the Key Values comprising the key.
	401	\|(% style="width:182px" %) \|(% style="width:210px" %)+valueFor\|(% style="width:617px" %)Associates the Primary Measure defined in the Data Structure Definition.
	402	\|(% style="width:182px" %) \|(% style="width:210px" %)+attachedAttribute\|(% style="width:617px" %)Association to the Attribute Values relating to the Observation.
	403	\|(% style="width:182px" %) \|(% style="width:210px" %)+observationDimension\|(% style="width:617px" %)Association to the Key Value that holds the value of the “Dimension at the Observation Level”.
	404	\|(% style="width:182px" %)//ObservationValue//\|(% style="width:210px" %)(((
2.1	405	Abstract class
	406	Sub classes
	407	UncodedObservation
	408	CodedObservation
3.5	409	)))\|(% style="width:617px" %)
	410	\|(% style="width:182px" %)UncodedObservation\|(% style="width:210px" %)(((
2.1	411	Inherits from
	412	ObservationValue
3.5	413	)))\|(% style="width:617px" %)An observation that has a text value.
	414	\|(% style="width:182px" %) \|(% style="width:210px" %)value\|(% style="width:617px" %)The value of the Uncoded Observation.
	415	\|(% style="width:182px" %)CodedObservation\|(% style="width:210px" %)(((
2.1	416	Inherits from
	417	ObservationValue
3.5	418	)))\|(% style="width:617px" %)An Observation that takes its value from a code in a Code list.
	419	\|(% style="width:182px" %) \|(% style="width:210px" %)+value\|(% style="width:617px" %)(((
2.1	420	Association to the Code that is the value of the Observation.
3.5	421	Note that this is a conceptual association showing that the Code must exist in the Code list associated with the Primary Measure or the Concept of the Measure Dimension in the Data Structure Definition. In the actual Data Set the value of the Code is placed in the Observation.
2.1	422	)))
3.5	423	\|(% style="width:182px" %)//AttributeValue//\|(% style="width:210px" %)(((
2.1	424	Abstract class
	425	Sub classes
3.5	426	//UncodedAttributeValue
	427	CodedAttributeValue//
	428	)))\|(% style="width:617px" %)The value of an attribute, such as the instance of a Coded Attribute or of an Uncoded Attribute in a structure such as a Data Structure Definition.
	429	\|(% style="width:182px" %) \|(% style="width:210px" %)value\|(% style="width:617px" %)The value of the attribute.
	430	\|(% style="width:182px" %) \|(% style="width:210px" %)+valueFor\|(% style="width:617px" %)(((
2.1	431	Association to the Data Attribute defined in the Data Structure Definition.
	432	Note that this is conceptual association as the Concept is identified explicitly in the data set.
	433	)))
3.5	434	\|(% style="width:182px" %)//UncodedAttribute Value//\|(% style="width:210px" %)(((
2.1	435	Inherits from
	436	//AttributeValue//
3.5	437	)))\|(% style="width:617px" %)An attribute value that has a text value.
	438	\|(% style="width:182px" %) \|(% style="width:210px" %)startTime\|(% style="width:617px" %)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).
	439	\|(% style="width:182px" %)(((
2.1	440	CodedAttribute
	441
	442	Value
3.5	443	)))\|(% style="width:210px" %)(((
2.1	444	Inherits from
	445	//AttributeValue//
3.5	446	)))\|(% style="width:617px" %)An attribute that takes it value from a Code in Code list.
	447	\|(% style="width:182px" %) \|(% style="width:210px" %)+value\|(% style="width:617px" %)(((
2.1	448	Association to the Code that is the value of the Attribute Value.
	449	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.
	450	)))
	451
6.1	452