Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.7
edited by Helena
on 2025/05/14 13:37
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
... ... @@ -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" %)(((
... ... @@ -153,10 +153,7 @@
153 153  
154 154  //Conversion guidance for implementors//
155 155  
156 -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
157 -)))
158 -|(% style="width:132px" %) |(% style="width:819px" %)(((
159 -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.
160 160  
161 161  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.
162 162  )))
... ... @@ -220,7 +220,8 @@
220 220  Removed Maintainable Artefacts
221 221  
222 222  * Structure Set – replaced by Structure Map and the four item scheme maps
223 -* 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
224 224  
225 225  Changed Maintainable Artefacts
226 226