Skip to Content
Version 2.1 by Helena on 2025/05/15 15:48
Hide last authors
Helena 2.1 1 = 11 Transforming between versions of SDMX =
2
3 == 11.1 Scope ==
4
5 The scope of this section is to define both best practices and mandatory behaviour for specific aspects of transformation between different versions of SDMX.
6
7 == 11.2 Compatibility and new DSD features ==
8
9 The following table provides an overview of the backwards compatibility between SDMX 3.0 and 2.1.
10
11 |**SDMX 3.0 feature**|**SDMX 2.1 compatibility**|**Comments**
12 |Multiple Measures|(((
13 Create a Measure Dimension Or
14
15 Model Measures as Attributes
16 )))|For a Measure Dimensions, all Concepts must reside in the same Concept Scheme
17 |Arrays for values|Cannot be supported|Arrays are always reported in a verbose format, even if one value is reported
18 |Measure Relationship|Can be ignored, as it does not affect dataset format|
19 |Metadata Attributes|Can be created as Data Attributes|Not for extended facets
20 |Multilingual Components|Cannot be supported|
21 |No Measure|Can only be emulated by ignoring the Primary Measure value|
22 |Use extended Codelist|A new Codelist with all Codes must be created|
23 |Sentinel values|Cannot be supported in the DSD|Rules may be supported outside the DSD, in bilateral agreements
24
25 The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0.
26
27 |**SDMX 2.1 feature**|**SDMX 3.0 compatibility**|**Comments**
28 |Measure Dimension|(((
29 Create a Dimension with role ‘MEASURE’
30
31 Or
32
33 Create multiple Measures from the Measure Dimension Concept Scheme
34 )))|If the dataset has to resemble that of SDMX 2.1 Structure Specific, then the first option must be used
35 |Primary Measure|(((
36 Create one Measure with role
37
38 ‘PRIMARY’; use id=”OBS_VALUE”
39 )))|