Changes for page 11 Transforming between versions of SDMX
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,0 +1,1 @@ 1 +11 Transforming between versions of SDMX - Content
-
... ... @@ -1,4 +1,6 @@ 1 -= 11 Transforming between versions of SDMX = 1 +{{box title="**Contents**"}} 2 +{{toc/}} 3 +{{/box}} 2 2 3 3 == 11.1 Scope == 4 4 ... ... @@ -15,11 +15,11 @@ 15 15 Model Measures as Attributes 16 16 )))|For a Measure Dimensions, all Concepts must reside in the same Concept Scheme 17 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| 20 +|Measure Relationship|Can be ignored, as it does not affect dataset format| 19 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| 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| 23 23 |Sentinel values|Cannot be supported in the DSD|Rules may be supported outside the DSD, in bilateral agreements 24 24 25 25 The following table illustrates forward compatibility issues from SDMX 2.1 to 3.0. ... ... @@ -36,4 +36,4 @@ 36 36 Create one Measure with role 37 37 38 38 ‘PRIMARY’; use id=”OBS_VALUE” 39 -)))| 41 +)))|