Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.1
edited by Helena
on 2025/05/14 13:26
Change comment: Created by office importer.
To version 7.2
edited by Helena
on 2025/05/14 13:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +1 Overview
Content
... ... @@ -1,3 +1,7 @@
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
4 +
1 1  **Revision History**
2 2  
3 3  |Revision|Date|Contents
... ... @@ -82,7 +82,7 @@
82 82  
83 83  == //2.2 Transmission Formats// ==
84 84  
85 -:
89 +:
86 86  
87 87  (((
88 88  |**SDMX-ML**|(((
... ... @@ -120,12 +120,12 @@
120 120  * Deprecation of the Agency, ID, Version option for referencing of structures in messages
121 121  )))
122 122  |**SDMX-EDI**|The EDI format for both structures and data has been deprecated.
123 -|**SDMX-CSV**|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.**     **
127 +|**SDMX-CSV**|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.**     **
124 124  )))
125 125  
126 126  == //2.3 Information Model// ==
127 127  
128 -:
132 +:
129 129  
130 130  (((
131 131  |**Data Structure Definition**|(((
... ... @@ -155,7 +155,7 @@
155 155  
156 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 157  )))
158 -||(((
162 +| |(((
159 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.
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.
SDMX 3-0-0 Major Changes FINAL-1.0_en_5f21cdf9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +103.2 KB
Content
SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +148.8 KB
Content
SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +22.0 KB
Content
SDMX 3-0-0 Major Changes FINAL-1.0_en_f2695ed5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +5.7 KB
Content