Changes for page 11 Transforming between versions of SDMX
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,32 +10,30 @@ 10 10 11 11 The following table provides an overview of the backwards compatibility between SDMX 3.0 and 2.1. 12 12 13 -|**SDMX 3.0 feature**|**SDMX 2.1 compatibility**|**Comments** 14 -|Multiple Measures|((( 13 +(% style="width:1165.29px" %) 14 +|(% style="width:218px" %)**SDMX 3.0 feature**|(% style="width:417px" %)**SDMX 2.1 compatibility**|(% style="width:526px" %)**Comments** 15 +|(% style="width:218px" %)Multiple Measures|(% style="width:417px" %)((( 15 15 Create a Measure Dimension Or 16 - 17 17 Model Measures as Attributes 18 -)))|For a Measure Dimensions, all Concepts must reside in the same Concept Scheme 19 -|Arrays for values|Cannot be supported|Arrays are always reported in a verbose format, even if one value is reported 20 -|Measure Relationship|Can be ignored, as it does not affect dataset format| 21 -|Metadata Attributes|Can be created as Data Attributes|Not for extended facets 22 -|Multilingual Components|Cannot be supported| 23 -|No Measure|Can only be emulated by ignoring the Primary Measure value| 24 -|Use extended Codelist|A new Codelist with all Codes must be created| 25 -|Sentinel values|Cannot be supported in the DSD|Rules may be supported outside the DSD, in bilateral agreements 18 +)))|(% style="width:526px" %)For a Measure Dimensions, all Concepts must reside in the same Concept Scheme 19 +|(% style="width:218px" %)Arrays for values|(% style="width:417px" %)Cannot be supported|(% style="width:526px" %)Arrays are always reported in a verbose format, even if one value is reported 20 +|(% style="width:218px" %)Measure Relationship|(% style="width:417px" %)Can be ignored, as it does not affect dataset format|(% style="width:526px" %) 21 +|(% style="width:218px" %)Metadata Attributes|(% style="width:417px" %)Can be created as Data Attributes|(% style="width:526px" %)Not for extended facets 22 +|(% style="width:218px" %)Multilingual Components|(% style="width:417px" %)Cannot be supported|(% style="width:526px" %) 23 +|(% style="width:218px" %)No Measure|(% style="width:417px" %)Can only be emulated by ignoring the Primary Measure value|(% style="width:526px" %) 24 +|(% style="width:218px" %)Use extended Codelist|(% style="width:417px" %)A new Codelist with all Codes must be created|(% style="width:526px" %) 25 +|(% style="width:218px" %)Sentinel values|(% style="width:417px" %)Cannot be supported in the DSD|(% style="width:526px" %)Rules may be supported outside the DSD, in bilateral agreements 26 26 27 27 The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0. 28 28 29 -|**SDMX 2.1 feature**|**SDMX 3.0 compatibility**|**Comments** 30 -|Measure Dimension|((( 29 +(% style="width:1175.29px" %) 30 +|**SDMX 2.1 feature**|(% style="width:320px" %)**SDMX 3.0 compatibility**|(% style="width:634px" %)**Comments** 31 +|Measure Dimension|(% style="width:320px" %)((( 31 31 Create a Dimension with role ‘MEASURE’ 32 - 33 33 Or 34 - 35 35 Create multiple Measures from the Measure Dimension Concept Scheme 36 -)))|If the dataset has to resemble that of SDMX 2.1 Structure Specific, then the first option must be used 37 -|Primary Measure|((( 35 +)))|(% style="width:634px" %)If the dataset has to resemble that of SDMX 2.1 Structure Specific, then the first option must be used 36 +|Primary Measure|(% style="width:320px" %)((( 38 38 Create one Measure with role 39 - 40 40 ‘PRIMARY’; use id=”OBS_VALUE” 41 -)))| 39 +)))|(% style="width:634px" %)