Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.4
edited by Helena
on 2025/05/14 13:35
Change comment: There is no comment for this version
To version 8.3
edited by Helena
on 2025/05/14 13:40
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -1 Overview
1 +SDMX STANDARDS
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.WebHome
Content
... ... @@ -4,9 +4,10 @@
4 4  
5 5  **Revision History**
6 6  
7 -|Revision|Date|Contents
8 -|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
9 -|1.0|October 2021|Public Release for SDMX 3.0
7 +(% style="width:738.039px" %)
8 +|(% style="width:187px" %)Revision|(% style="width:157px" %)Date|(% style="width:390px" %)Contents
9 +|(% style="width:187px" %)DRAFT 1.0|(% style="width:157px" %)May 2021|(% style="width:390px" %)Draft release updated for SDMX 3.0 for public consultation
10 +|(% style="width:187px" %)1.0|(% style="width:157px" %)October 2021|(% style="width:390px" %)Public Release for SDMX 3.0
10 10  
11 11  = 1 Overview =
12 12  
... ... @@ -87,8 +87,6 @@
87 87  
88 88  == //2.2 Transmission Formats// ==
89 89  
90 -:
91 -
92 92  (((
93 93  (% style="width:952.039px" %)
94 94  |(% style="width:130px" %)**SDMX-ML**|(% style="width:820px" %)(((
... ... @@ -107,10 +107,7 @@
107 107  The SDMX-ML structure message is not backwardly compatible primarily due to:
108 108  
109 109  * Changes to the information model
110 -* Changes to the way the structures are organised into
111 -
112 -‘collections’ within the message
113 -
109 +* Changes to the way the structures are organised into ‘collections’ within the message
114 114  * Deprecation of the Agency, ID, Version option for referencing of structures in messages
115 115  )))
116 116  |(% style="width:130px" %)**SDMX-JSON**|(% style="width:820px" %)(((
... ... @@ -119,20 +119,15 @@
119 119  The JSON structure message is not backwardly compatible primarily due to:
120 120  
121 121  * Changes to the information model
122 -* Changes to the way the structures are organised into
123 -
124 -‘collections’ within the message
125 -
118 +* Changes to the way the structures are organised into ‘collections’ within the message
126 126  * Deprecation of the Agency, ID, Version option for referencing of structures in messages
127 127  )))
128 128  |(% style="width:130px" %)**SDMX-EDI**|(% style="width:820px" %)The EDI format for both structures and data has been deprecated.
129 -|(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)The CSV data and reference metadata messages are not backwardly compatible with those under version 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries.**     **
122 +|(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)The CSV data and reference metadata messages are not backwardly compatible with those under version 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries.
130 130  )))
131 131  
132 132  == //2.3 Information Model// ==
133 133  
134 -:
135 -
136 136  (((
137 137  (% style="width:955.039px" %)
138 138  |(% style="width:132px" %)**Data Structure Definition**|(% style="width:819px" %)(((
... ... @@ -160,10 +160,7 @@
160 160  
161 161  //Conversion guidance for implementors//
162 162  
163 -A version 2.1 Metadata Structure Definition can be converted to the version 3.0 model under some circumstances, but target information is either lost or has to be translated into a metadataflow. Further, conversion of a Data Structure Definition for collecting reference metadata against a dataset would need to make changes to the dataset’s Data Structure Definition. As the Data Structure Definition may not actually be specified, judgement would need to be taken, perhaps determining the most likely candidate by examining which
164 -)))
165 -|(% style="width:132px" %) |(% style="width:819px" %)(((
166 -already have metadata reported against their datasets. A 2.1 metadata report could be converted to a version 3.0 Metadataset if it is attached to a structure, but requires a Metadata Provision Agreement which would need to be created if not already in existence.
154 +A version 2.1 Metadata Structure Definition can be converted to the version 3.0 model under some circumstances, but target information is either lost or has to be translated into a metadataflow. Further, conversion of a Data Structure Definition for collecting reference metadata against a dataset would need to make changes to the dataset’s Data Structure Definition. As the Data Structure Definition may not actually be specified, judgement would need to be taken, perhaps determining the most likely candidate by examining which already have metadata reported against their datasets. A 2.1 metadata report could be converted to a version 3.0 Metadataset if it is attached to a structure, but requires a Metadata Provision Agreement which would need to be created if not already in existence.
167 167  
168 168  Conversion from the version 3.0 model to version 2.1 cannot be performed reliably. The process would need target information to be derived from analysis of the Metadataflows and Metadata Provision Agreements. Depending on the complexity it may not be possible to express that information in a version 2.1 Data Structure Definition.
169 169  )))
... ... @@ -227,7 +227,8 @@
227 227  Removed Maintainable Artefacts
228 228  
229 229  * Structure Set – replaced by Structure Map and the four item scheme maps
230 -* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association • Constraint – replaced by Data Constraint and Metadata Constraint
218 +* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association
219 +* Constraint – replaced by Data Constraint and Metadata Constraint
231 231  
232 232  Changed Maintainable Artefacts
233 233