Changes for page SDMX 3.0 Standards. Summary of Major Changes and New Functionality

Last modified by Helena on 2025/09/10 11:19

From 11.1 to 10.2 From 16.3 to 16.2

From version 16.2

edited by Helena
on 2025/05/16 13:18

Change comment: There is no comment for this version

To version 11.1

edited by Helena
on 2025/05/14 14:45

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -247,8 +247,8 @@
  Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
--(% class="wikigeneratedid" id="HSimplifyMetadataStructureDefinition" %)
--**Simplify Metadata Structure Definition**
++=== Simplify Metadata Structure Definition ===
++
  The Metadata Structure Definition (MSD) has been simplified to remove target information, and the support of multiple report structures. The MSD now only contains Metadata Attributes which are used to define the structure of a report.
  [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png||height="346" width="494"]]
@@ -259,8 +259,8 @@
  //Figure 3 the simplified version 3.0 MSD//
--(% class="wikigeneratedid" id="HChangetoreferencemetadatareportedagainstdata" %)
--**Change to reference metadata reported against data**
++=== Change to reference metadata reported against data ===
++
  Reference metadata associated with datasets, data series or observations are now reported with the data. The dataset’s DSD must reference an MSD to define the structure of its reference metadata. In practice reference metadata for data are transmitted as part of the data message. The metadata attributes are treated in a similar way to the data attributes appearing in the message at the dataset, data series or individual observation level as appropriate. In contrast to simple data attributes, metadata attributes defined by an MSD can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata attributes appear in data messages structured in the same way as metadata messages.
  The SDMX-ML example below is an excerpt from a structure specific data message illustrating reporting of reference metadata with a hierarchical structure at the observation level.
@@ -271,57 +271,58 @@
  * TITLE – a multi-lingual data attribute
  * SOURCE_AGENCY – a multi-value data attribute
--> <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
-->     <!—- complex multi-value and multi-lingual data attributes ~-~->
-->     <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
-->         <Value>
-->         <common:Text xml:lang="en">Some English Text</common:Text>
-->         <common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
-->         </Value>
-->     </Comp>
-->     <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
-->         <Value>4F0</Value>
-->         <Value>4D0</Value>
-->         <Value>CZ2</Value>
-->     </Comp>
--> <!—- metadata attributes are reported like in metadata messages ~-~->
--> <Metadata>
-->     <Attribute id="COLLECTION">
-->         <Attribute id="METHOD">
-->             <Text lang="en">AAA</Text>
-->         </Attribute>
-->     </Attribute>
-->     <Attribute id="CONTACT">
-->          <Value>CONTACT 1</Value>
-->          <Attribute id="NAME">
-->             <Value>Contact 1 Name 1</Value>
-->      </Attribute>
-->      <Attribute id="NAME">
-->             <Value>Contact 1 Name 2</Value>
-->         </Attribute>
-->     </Attribute>
-->     <Attribute id="CONTACT">
-->           <Value>CONTACT 2</Value>
-->         <Attribute id="NAME">
-->             <Value>Contact 2 Name 1</Value>
-->       </Attribute>
-->       <Attribute id="NAME">
-->                 <Value>Contact 2 Name 2</Value>
-->                </Attribute>
-->           </Attribute>
-->       </Metadata>
--> </Obs>
++<Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
++<!—- complex multi-value and multi-lingual data attributes ~-~->
++<Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
++<Value>
++<common:Text xml:lang="en">Some English Text</common:Text>
++<common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
++</Value>
++</Comp>
--(% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement" %)
--**New - Metadata Provision Agreement**
++<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
++<Value>4F0</Value>
++<Value>4D0</Value>
++<Value>CZ2</Value>
++</Comp>
++<!—- metadata attributes are reported like in metadata messages ~-~->
++<Metadata>
++<Attribute id="COLLECTION">
++<Attribute id="METHOD">
++<Text lang="en">AAA</Text>
++</Attribute>
++</Attribute>
++<Attribute id="CONTACT">
++<Value>CONTACT 1</Value>
++<Attribute id="NAME">
++<Value>Contact 1 Name 1</Value>
++</Attribute>
++<Attribute id="NAME">
++<Value>Contact 1 Name 2</Value>
++</Attribute>
++</Attribute>
++<Attribute id="CONTACT">
++<Value>CONTACT 2</Value>
++<Attribute id="NAME">
++<Value>Contact 2 Name 1</Value>
++</Attribute>
++<Attribute id="NAME">
++<Value>Contact 2 Name 2</Value>
++</Attribute>
++</Attribute>
++</Metadata>
++</Obs>
++
++=== New - Metadata Provision Agreement ===
++
  In version 2.1 a Provision Agreement could be used to report information against a Dataflow or Metadataflow. From version 3.0 this is managed by two separate structures, the Data Provision Agreement and the Metadata Provision Agreement.
--(% class="wikigeneratedid" id="HMovetargettoMetadataflowandMetadataProvisionAgreement" %)
--**Move target to Metadataflow and Metadata Provision Agreement**
++=== Move target to Metadataflow and Metadata Provision Agreement ===
++
  For reference metadata that is reported against structures, the allowable targets information which is used to specify what structures the reference metadata can be reported against, has moved to the Metadataflow and can be further refined in the Metadata Provision Agreement.
--(% class="wikigeneratedid" id="HAddmaintainablepropertiestoreferencemetadata" %)
--**Add maintainable properties to reference metadata**
++=== Add maintainable properties to reference metadata ===
++
  A Metadataset now has mandatory identification information, (owner id, id, version) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
  == 3.5 Microdata Exchange ==
@@ -328,37 +328,47 @@
  Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series.
--(% class="wikigeneratedid" id="HMultiplemeasures" %)
--**Multiple measures**
--Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1 MeasureDimension behaviour as illustrated in the SDMX-ML example below:
++=== Multiple measures ===
--> <str:MeasureList id=”MeasureDescriptor”>
-->     <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
-->         <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
-->     </str:ConceptIdentity>
-->     <str:LocalRepresentation>
-->         <str:TextFormat textType=”String” isMultiLingual=”true” />
-->     </str:LocalRepresentation>
-->     <str:ConceptRole>
-->         <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
-->     </str:ConceptRole>
-->  </str:Measure>
-->         ...
-->     <str:Measure>
--> </str:MeasureList>
++Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the
--(% class="wikigeneratedid" id="HMulti-valuemeasuresandattributes" %)
--**Multi-value measures and attributes**
--Both measures and attributes have been extended with the option to take ‘arrays’ of 193 multiple coded or uncoded values. This supports use cases like multiple observation 194 status flags. New //minOccurs// and //maxOccurs// properties define the valid number of 195 values. The //usage// property separately defines whether the measure or attribute is //mandatory// or optional. In the SDMX-ML measure example above, the properties //minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.
++Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1
--(% class="wikigeneratedid" id="HAttributesrelationshiptomeasures" %)
--**Attributes relationship to measures**
++MeasureDimension behaviour as illustrated in the SDMX-ML example below:
++
++<str:MeasureList id=”MeasureDescriptor”>
++<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
++<Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
++</str:ConceptIdentity>
++<str:LocalRepresentation>
++<str:TextFormat textType=”String” isMultiLingual=”true” />
++</str:LocalRepresentation>
++<str:ConceptRole>
++<Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
++</str:ConceptRole>
++</str:Measure>
++...
++<str:Measure>
++</str:MeasureList>
++
++=== Multi-value measures and attributes ===
++
++Both measures and attributes have been extended with the option to take ‘arrays’ of 193 multiple coded or uncoded values. This supports use cases like multiple observation 194 status flags. New //minOccurs// and //maxOccurs// properties define the valid number of 195 values. The //usage// property separately defines whether the measure or attribute is
++
++//mandatory// or optional. In the SDMX-ML measure example above, the properties
++
++//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.
++
++=== Attributes relationship to measures ===
++
  In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.
--(% class="wikigeneratedid" id="HValuelists" %)
--**Value lists**
--Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers. That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but also means they are not identifiable.
++=== Value lists ===
++Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers.
++
++That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.
++
  == 3.6 Geospatial Data Exchange ==
  The version 3.0 model has been extended to provide explicit support for geospatial data.
@@ -374,14 +374,14 @@
  * GeographicCodelist – each item includes an element to represent a specific Geo Feature Set which is described using the same expression syntax as for GeospatialInformation type.
  * GeoGridCodelist – A code list defining a geographical grid composed of cells representing regular squared portions of the Earth. Each item references a cell within the grid.
--== 3.7 Structure Mapping ==
++=== 3.7 Structure Mapping ===
  The Structure Set in version 2.1 is a container for many mapping structures including Data Structure Map, Codelist Map and Concept Map. For version 3.0 the Structure Set artefact has been deprecated and replaced with a number of new maintainables giving better flexibility and reusability, specifically: Structure Map, Concept Scheme Map, Representation Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
  The version 2.1 Codelist Map been replaced with Representation Map which allows mappings to be defined between any combination of Code Lists, Value Lists and noncoded representations such as text strings and numbers.
--(% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
--**Many-to-many source and target components**
++==== Many-to-many source and target components ====
++
  Structure mapping rules may be defined with both multiple source components and multiple target components in contrast to version 2.1 where only one source and target was allowed. That supports many-to-many (n-n) mapping use cases where the output of a mapping rule may be dependent on the combination of a number of input components. For instance:
  Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.
@@ -391,21 +391,22 @@
  Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.
  **Fixed source and target**
++
  The Structure Map may now define input or output components which have a fixed value.
--(% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
--**Time representations mapping**
++==== Time representations mapping ====
++
  Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.
--(% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
--**Regular expression and substring mappings**
++==== Regular expression and substring mappings ====
++
  All item maps allow the use of regular expressions and substrings to match source values, specifically: Concept Scheme Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
--(% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
--**Item maps validity period**
++==== Item maps validity period ====
++
  Item maps may further define the period for which the mapping is valid, meaning the mapping rule will only be applied if the row of information being mapped is within the period.
--== 3.8 Constraints ==
++=== 3.8 Constraints ===
  Constraints in version 3.0 are modelled using two separate artefacts which replace the version 2.1 content constraint:
@@ -420,17 +420,17 @@
  Attachment constraints have been deprecated due to a lack of use cases.
--== 3.9 Code List Extension ==
++=== 3.9 Code List Extension ===
  In addition to the two new specialised geospatial forms, the option has been added to define a code list as an extension of, or by inheriting codes from, other lists. An optional prefix can be added to inherited codes to disambiguate duplicates.
  This feature allows new code lists to be easily derived from existing lists without the need to make and manually maintain copies. When querying for extended code list structures using the REST API, the option has been added to retrieve either the definition or the materialised list. Traditional literal lists of codes continue to be supported.
--== 3.10 Discriminated Union of Code Lists ==
++=== 3.10 Discriminated Union of Code Lists ===
  Combining code list extension with wildcarded constraints solves the discriminated union of code lists problem where a classification or breakdown has multiple “variants” which are all valid but mutually exclusive. A common example is economic activity where several alternative classification schemes are in use including ISIC revisions 1 to 4 and NACE as used in the European Community.
--== 3.11 Code Hierarchies ==
++=== 3.11 Code Hierarchies ===
  Code hierarchies allow the definition of complex hierarchies of codes from potentially multiple lists for data discovery purposes. Hierarchical Codelist has been deprecated and replaced by two new artefacts: Hierarchy – the actual hierarchy of codes, and Hierarchy Association links hierarchies directly to any other identifiable object, a capability missing 312 from the version 2.1 model. Further, the linkage can be within a particular context, for instance linking a hierarchy to a dimension within the context of a specific Dataflow (dimension REF_AREA in the context of the ECB:EXR Dataflow).