Wiki source code of 11 Transforming between versions of SDMX
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{box title="**Contents**"}} |
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| 4 | |||
| 5 | == 11.1 Scope == | ||
| 6 | |||
| |
7.1 | 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. |
| |
1.1 | 8 | |
| 9 | == 11.2 Compatibility and new DSD features == | ||
| 10 | |||
| |
7.1 | 11 | The following table provides an overview of the backwards compatibility between SDMX 3.0 and 2.1. |
| |
1.1 | 12 | |
| 13 | (% style="width:1018.29px" %) | ||
| 14 | |(% style="width:195px" %)**SDMX 3.0 feature**|(% style="width:375px" %)**SDMX 2.1 compatibility**|(% style="width:445px" %)**Comments** | ||
| |
7.1 | 15 | |(% style="width:195px" %)Multiple Measures|(% style="width:375px" %)((( |
| 16 | Create a Measure Dimension | ||
| |
1.1 | 17 | Or |
| |
7.1 | 18 | Model Measures as Attributes |
| |
1.1 | 19 | )))|(% style="width:445px" %)((( |
| |
3.2 | 20 | For a Measure |
| |
7.1 | 21 | Dimensions, all Concepts must reside in the same Concept Scheme |
| |
1.1 | 22 | ))) |
| 23 | |(% style="width:195px" %)Arrays for values|(% style="width:375px" %)Cannot be supported|(% style="width:445px" %)Arrays are always reported in a verbose format, even if one value is reported | ||
| 24 | |(% style="width:195px" %)((( | ||
| |
7.1 | 25 | Measure |
| |
1.1 | 26 | |
| 27 | Relationship | ||
| |
7.1 | 28 | )))|(% style="width:375px" %)Can be ignored, as it does not affect dataset format|(% style="width:445px" %) |
| 29 | |(% style="width:195px" %)Metadata Attributes|(% style="width:375px" %)Can be created as Data Attributes|(% style="width:445px" %)Not for extended facets | ||
| 30 | |(% style="width:195px" %)Multilingual Components|(% style="width:375px" %)Cannot be supported|(% style="width:445px" %) | ||
| 31 | |(% style="width:195px" %)No Measure|(% style="width:375px" %)Can only be emulated by ignoring the Primary Measure value|(% style="width:445px" %) | ||
| 32 | |(% style="width:195px" %)Use extended Codelist|(% style="width:375px" %)A new Codelist with all Codes must be created|(% style="width:445px" %) | ||
| 33 | |(% style="width:195px" %)Sentinel values|(% style="width:375px" %)Cannot be supported in the DSD|(% style="width:445px" %)Rules may be supported outside the DSD, in bilateral agreements | ||
| |
1.1 | 34 | |
| |
7.1 | 35 | The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0. |
| |
1.1 | 36 | |
| 37 | (% style="width:1016.29px" %) | ||
| 38 | |(% style="width:197px" %)**SDMX 2.1 feature**|(% style="width:374px" %)**SDMX 3.0 compatibility**|(% style="width:441px" %)**Comments** | ||
| |
7.1 | 39 | |(% style="width:197px" %)Measure Dimension|(% style="width:374px" %)((( |
| 40 | Create a Dimension with role ‘MEASURE’ | ||
| |
1.1 | 41 | Or |
| |
7.1 | 42 | Create multiple Measures from the Measure Dimension Concept Scheme |
| |
1.1 | 43 | )))|(% style="width:441px" %)((( |
| |
7.1 | 44 | If the dataset has to resemble that of SDMX 2.1 |
| |
1.1 | 45 | Structure Specific, then the first option must be used |
| 46 | ))) | ||
| |
7.1 | 47 | |(% style="width:197px" %)Primary Measure|(% style="width:374px" %)((( |
| 48 | Create one Measure with role ‘PRIMARY’; use id=”OBS_VALUE” | ||
| 49 | ))) | ||
| 50 | |||
| 51 | (% style="width:1016.29px" %) | ||
| 52 | |(% style="width:441px" %) |