Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.5
edited by Helena
on 2025/05/14 13:36
Change comment: There is no comment for this version
To version 8.1
edited by Helena
on 2025/05/14 13:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -88,8 +88,6 @@
88 88  
89 89  == //2.2 Transmission Formats// ==
90 90  
91 -:
92 -
93 93  (((
94 94  (% style="width:952.039px" %)
95 95  |(% style="width:130px" %)**SDMX-ML**|(% style="width:820px" %)(((
... ... @@ -117,20 +117,15 @@
117 117  The JSON structure message is not backwardly compatible primarily due to:
118 118  
119 119  * Changes to the information model
120 -* Changes to the way the structures are organised into
121 -
122 -‘collections’ within the message
123 -
118 +* Changes to the way the structures are organised into ‘collections’ within the message
124 124  * Deprecation of the Agency, ID, Version option for referencing of structures in messages
125 125  )))
126 126  |(% style="width:130px" %)**SDMX-EDI**|(% style="width:820px" %)The EDI format for both structures and data has been deprecated.
127 -|(% 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.
128 128  )))
129 129  
130 130  == //2.3 Information Model// ==
131 131  
132 -:
133 -
134 134  (((
135 135  (% style="width:955.039px" %)
136 136  |(% style="width:132px" %)**Data Structure Definition**|(% style="width:819px" %)(((
... ... @@ -158,10 +158,7 @@
158 158  
159 159  //Conversion guidance for implementors//
160 160  
161 -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
162 -)))
163 -|(% style="width:132px" %) |(% style="width:819px" %)(((
164 -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.
165 165  
166 166  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.
167 167  )))
... ... @@ -225,7 +225,8 @@
225 225  Removed Maintainable Artefacts
226 226  
227 227  * Structure Set – replaced by Structure Map and the four item scheme maps
228 -* 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
229 229  
230 230  Changed Maintainable Artefacts
231 231