Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 1.1
edited by Helena
on 2025/05/15 15:48
Change comment: Changed document syntax from [XWiki 2.1] to [xwiki/2.1].
To version 2.3
edited by Helena
on 2025/05/16 12:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +11 Transforming between versions of SDMX
Content
... ... @@ -1,0 +1,41 @@
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
4 +
5 +== 11.1 Scope ==
6 +
7 +The scope of this section is to define both best practices and mandatory behaviour for specific aspects of transformation between different versions of SDMX.
8 +
9 +== 11.2 Compatibility and new DSD features ==
10 +
11 +The following table provides an overview of the backwards compatibility between SDMX 3.0 and 2.1.
12 +
13 +|**SDMX 3.0 feature**|**SDMX 2.1 compatibility**|**Comments**
14 +|Multiple Measures|(((
15 +Create a Measure Dimension Or
16 +
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
26 +
27 +The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0.
28 +
29 +|**SDMX 2.1 feature**|**SDMX 3.0 compatibility**|**Comments**
30 +|Measure Dimension|(((
31 +Create a Dimension with role ‘MEASURE’
32 +
33 +Or
34 +
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|(((
38 +Create one Measure with role
39 +
40 +‘PRIMARY’; use id=”OBS_VALUE”
41 +)))|