Wiki source code of 11 Transforming between versions of SDMX
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.3 | 1 | {{box title="**Contents**"}} |
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| |
2.1 | 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 | |||
| |
2.4 | 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" %)((( | ||
| |
2.1 | 16 | Create a Measure Dimension Or |
| 17 | Model Measures as Attributes | ||
| |
2.4 | 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 | ||
| |
2.1 | 26 | |
| 27 | The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0. | ||
| 28 | |||
| |
2.4 | 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" %)((( | ||
| |
2.1 | 32 | Create a Dimension with role ‘MEASURE’ |
| 33 | Or | ||
| 34 | Create multiple Measures from the Measure Dimension Concept Scheme | ||
| |
2.4 | 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" %)((( | ||
| |
2.1 | 37 | Create one Measure with role |
| 38 | ‘PRIMARY’; use id=”OBS_VALUE” | ||
| |
2.4 | 39 | )))|(% style="width:634px" %) |