Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 13.2
edited by Helena
on 2025/05/16 21:22
Change comment: There is no comment for this version
To version 13.4
edited by Helena
on 2025/05/16 21:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -63,51 +63,51 @@
63 63  
64 64  = 2 Change History =
65 65  
66 -The 2.0 version of this standard represented a significant increase in scope, and also provided more complete support in those areas covered in the version 1.0 specification. Version 2.0 of this standard is backward-compatible with version 1.0, so that existing implementations can be easily migrated to conformance with version 2.0.
66 +The 2.0 (% style="color:#2ecc71" %)version(%%) of this standard represented a significant increase in scope, and also provided more complete support in those areas covered in the (% style="color:#2ecc71" %)version(%%) 1.0 specification. (% style="color:#2ecc71" %)Version(%%) 2.0 of this standard is backward-compatible with (% style="color:#2ecc71" %)version(%%) 1.0, so that existing implementations can be easily migrated to conformance with (% style="color:#2ecc71" %)version(%%) 2.0.
67 67  
68 -The 2.1 version of this standard represents a set of changes resulting from several years of implementation experience with the 2.0 standard. The changes do not represent a major increase in scope or functionality, but do correct some bugs, and add functionalities in some cases. Major changes in SDMX-ML include a much stronger alignment of the XML Schemas with the Information Model, to emphasize inheritance and object-oriented features, and increased precision and flexibility in the attachment of metadata reports to specific objects in the SDMX Information Model.
68 +The 2.1 (% style="color:#2ecc71" %)version(%%) of this standard represents a set of changes resulting from several years of implementation experience with the 2.0 standard. The changes do not represent a major increase in scope or functionality, but do correct some bugs, and add functionalities in some cases. Major changes in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] include a much stronger alignment of the XML Schemas with the Information Model, to emphasize inheritance and object-oriented features, and increased precision and flexibility in the attachment of metadata reports to specific objects in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Information Model.
69 69  
70 -The 3.0 version incorporates new features, improvements and changes arising from the collective knowledge gained from a decade of operating experience with the 2.1 standard. In pursuit of modernisation and simplification, features considered obsolete have been deprecated – in particular the EDI transmission format, the lesser-used XML data messages and the SOAP web services API. Many areas remain backwardly compatible with 2.1, but there are some breaking changes where the information model has been redesigned to better support practical use case. Structure mapping and reference metadata are examples. The opportunity has been taken to revise the RESTful web services API which is also not backwardly compatible, but benefits from a rationalisation and better organisations of resources, and a much richer data query URL syntax.
70 +The 3.0 (% style="color:#2ecc71" %)version(%%) incorporates new features, improvements and changes arising from the collective knowledge gained from a decade of operating experience with the 2.1 standard. In pursuit of modernisation and simplification, features considered obsolete have been deprecated – in particular the EDI transmission format, the lesser-used XML data messages and the SOAP web services API. Many areas remain backwardly compatible with 2.1, but there are some breaking changes where the information model has been redesigned to better support practical use case. Structure mapping and [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] are examples. The opportunity has been taken to revise the RESTful web services API which is also not backwardly compatible, but benefits from a rationalisation and better organisations of resources, and a much richer data query URL syntax.
71 71  
72 72  == 2.1 Major Changes from 1.0 to 2.0 ==
73 73  
74 -* **Reference Metadata**: In addition to describing and specifying data structures and formats (along with related structural metadata), the version 2.0 specification also provides for the exchange of metadata which is distinct from the structural metadata in the 1.0 version. This category includes “reference” metadata (regarding data quality, methodology, and similar types – it can be configured by the user to include whatever concepts require reporting); metadata related to data provisioning (release calendar information, description of the data and metadata provided, etc.); and metadata relevant to the exchange of categorization schemes.
74 +* **[[Reference Metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]]**: In addition to describing and specifying data structures and formats (along with related [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]]), the (% style="color:#2ecc71" %)version(%%) 2.0 specification also provides for the exchange of metadata which is distinct from the [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] in the 1.0 (% style="color:#2ecc71" %)version(%%). This [[category>>doc:xwiki:Glossary.Category.WebHome]] includes “reference” metadata (regarding data quality, methodology, and similar types – it can be configured by the user to include whatever (% style="color:#2ecc71" %)concepts(%%) require reporting); metadata related to data provisioning ([[release calendar>>doc:xwiki:Glossary.Release policy - release calendar.WebHome]] information, description of the data and metadata provided, etc.); and metadata relevant to the exchange of categorization schemes.
75 75  * **SDMX Registry**: Provision is made in the 2.0 standard for standard communication with registry services, to support a data-sharing model of statistical exchange. These services include registration of data and metadata, querying of registered data and metadata, and subscription.
76 -* **Structural Metadata**: The support for exchange of statistical data and related structural metadata has been expanded. Some support is provided for qualitative data; data cube structures are described; hierarchical code lists are supported; relationships between data structures can be expressed, providing support for extensibility of data structures; 101 and the description of functional dependencies within cubes are supported.
76 +* **[[Structural Metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]]**: The support for exchange of statistical data and related [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] has been expanded. Some support is provided for qualitative data; data cube structures are described; [[hierarchical code lists>>doc:xwiki:Glossary.Hierarchical code list.WebHome]] are supported; relationships between data structures can be expressed, providing support for extensibility of data structures; 101 and the description of functional dependencies within cubes are supported.
77 77  
78 78  == 2.2 Major Changes from 2.0 to 2.1 ==
79 79  
80 -* **Simplification of the data structure definition - specific message types:** Both time series (version 2.0 Compact) and non-time series data sets (version 2.0 Cross Sectional) use the same underlying structure for a structure-specific formatted message, which is specific to the Data Structure Definition of the data set.
80 +* **Simplification of the [[data structure definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] - specific message types:** Both time series ((% style="color:#2ecc71" %)version(%%) 2.0 Compact) and non-time series [[data sets>>doc:xwiki:Glossary.Data set.WebHome]] ((% style="color:#2ecc71" %)version(%%) 2.0 Cross Sectional) use the same underlying structure for a structure-specific formatted message, which is specific to the [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] of the data set.
81 81  * **Simplification and better support for the metadata structure: **New use cases have been reported and these are now supported by a re-modelled metadata structure definition.
82 -* **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using SDMX, and these implementations have resulted in several changes to the specifications. Because the nature of SDMX web services could not be anticipated at the time of the original drafting of the specifications, the web services guidelines have been completely re-developed.
83 -* **Presentational Changes: **Much work has gone into using various technologies for the visualization of SDMX data and metadata, and some changes have been proposed as a result, to better leverage this graphical visualization. These changes are largely to leverage the Cross-domain Concepts of the Content Oriented Guidelines.
82 +* **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], and these implementations have resulted in several changes to the specifications. Because the nature of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] web services could not be anticipated at the time of the original drafting of the specifications, the web services guidelines have been completely re-developed.
83 +* **Presentational Changes: **Much work has gone into using various technologies for the visualization of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data and metadata, and some changes have been proposed as a result, to better leverage this graphical visualization. These changes are largely to leverage the [[Cross-domain Concepts>>doc:xwiki:Glossary.Cross-domain concept.WebHome]] of the Content Oriented Guidelines.
84 84  * **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
85 85  * **Clarifications in Documentation:** In some cases, it has been identified that the documentation of specific fields within the standard needed clarification and elaboration, and these issues have been addressed.
86 -* **Optimization for XML Technologies:** Implementation has shown that it is possible to better organize the XML schemas for use within common technology development tools which work with XML. These changes are primarily focused on leveraging the object oriented features of W3C XML Schema to allow for easier processing of SDMX data and metadata.
87 -* **Consistency between the SDMX-ML and the SDMX Information Model: **Certain aspects of the XML schemas and UML model have been more closely aligned, to allow for easier comprehension of the SDMX model.
86 +* **Optimization for XML Technologies:** Implementation has shown that it is possible to better organize the XML schemas for use within common technology development tools which work with XML. These changes are primarily focused on leveraging the object oriented features of W3C XML Schema to allow for easier processing of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data and metadata.
87 +* **Consistency between the [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] and the [[SDMX Information Model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]: **Certain aspects of the XML schemas and UML model have been more closely aligned, to allow for easier comprehension of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] model.
88 88  * **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
89 89  * **Support for Non-Time-Series Data in the Generic Format: **One area which has been extended is the ability to express non-time-series data as part of the generic data message.
90 -* **Support for partial item schemes such as a code list: **The concept of a partial (sub set) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
90 +* **Support for partial [[item schemes>>doc:xwiki:Glossary.Item scheme.WebHome]] such as a [[code list>>doc:xwiki:Glossary.Code list.WebHome]]: **The (% style="color:#2ecc71" %)concept(%%) of a partial (sub set) [[item scheme>>doc:xwiki:Glossary.Item scheme.WebHome]] such as a partial [[code list>>doc:xwiki:Glossary.Code list.WebHome]] for use in exchange scenarios has been introduced**.**
91 91  
92 92  == 2.3 Major Changes from 2.1 to 3.0 ==
93 93  
94 -SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
94 +[[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)version(%%) 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
95 95  
96 96  (% class="wikigeneratedid" id="HInformationModel" %)
97 97  **Information Model**
98 98  
99 -* Simplification and improvement of the reference metadata model
99 +* Simplification and improvement of the [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] model
100 100  * Support for microdata
101 101  * Support for geospatial data
102 -* Support for code list extension and discriminated union of code lists
102 +* Support for [[code list>>doc:xwiki:Glossary.Code list.WebHome]] extension and discriminated union of [[code>>doc:xwiki:Glossary.Code.WebHome]] lists
103 103  * Improvements to structure mapping
104 -* Improvements to code hierarchies for data discovery
104 +* Improvements to [[code>>doc:xwiki:Glossary.Code.WebHome]] [[hierarchies>>doc:xwiki:Glossary.Hierarchy.WebHome]] for data discovery
105 105  * Improvements to constraints
106 106  
107 107  (% class="wikigeneratedid" id="HVersioningofStructuralMetadataArtefacts" %)
108 108  **Versioning of Structural Metadata Artefacts**
109 109  
110 -* Adoption of the three-number semantic versioning standard for structural metadata artefacts (__[[https:~~/~~/semver.org>>url:https://semver.org/]])__
110 +* Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] (__[[https:~~/~~/semver.org>>url:https://semver.org/]])__
111 111  
112 112  (% class="wikigeneratedid" id="HRESTWebServicesApplicationProgrammingInterface28API29" %)
113 113  **REST Web Services Application Programming Interface (API)**
... ... @@ -114,36 +114,36 @@
114 114  
115 115  * Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five
116 116  * Improvements to data queries
117 -* Improvements to reference metadata queries
118 -* Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs
117 +* Improvements to [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] queries
118 +* Support for [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] maintenance using HTTP PUT, POST and DELETE verbs
119 119  
120 120  (% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
121 121  **SOAP Web Services API**
122 122  
123 -* The SOAP web services API has been deprecated with version 3.0 standardising on REST
123 +* The SOAP web services API has been deprecated with (% style="color:#2ecc71" %)version(%%) 3.0 standardising on REST
124 124  
125 125  (% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
126 126  **XML, JSON, CSV and EDI Transmission formats**
127 127  
128 -* The SDMX-ML, SDMX-JSON and SDMX-CSV specifications have been extended and modified where needed to support the new features and changes such as reference metadata and microdata
129 -* Obsolete SDMX-ML data message variants including Generic, Compact, Utility and Cross-sectional have been deprecated standardising on Structure Specific Data as the sole XML format for data exchange
130 -* The SDMX-EDI transmission format for structures and data has been deprecated
131 -* The organisation of structures into ‘collections’ in SDMX-ML and SDMX-JSON structure messages has been flattened and simplified
132 -* The option to reference structures in SDMX-ML and SDMX-JSON messages using Agency, ID and Version has been deprecated with URN now exclusively used for all non-local referencing purpose
128 +* The [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-CSV specifications have been extended and modified where needed to support the new features and changes such as [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] and microdata
129 +* Obsolete [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] data message variants including Generic, Compact, Utility and Cross-sectional have been deprecated standardising on Structure Specific Data as the sole XML format for data exchange
130 +* The [[SDMX-EDI>>doc:xwiki:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated
131 +* The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified
132 +* The option to reference structures in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#2ecc71" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
133 133  
134 -Several of the changes are ‘breaking’ meaning that, in specific cases, the version 3.0 specification is not backwardly compatible with earlier versions of the Standard.
134 +Several of the changes are ‘breaking’ meaning that, in specific cases, the (% style="color:#2ecc71" %)version(%%) 3.0 specification is not backwardly compatible with earlier (% style="color:#2ecc71" %)versions(%%) of the Standard.
135 135  
136 136  The principle breaking changes are:
137 137  
138 138  * REST API – The REST API is not backwardly compatible due to modifications to the URLs and query parameters resulting in breaking changes in four of the five main resources.
139 -* SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with version 3.0 registries.
140 -* SDMX-ML – SDMX 2.1 and earlier structure, data and metadata XML messages are not valid in version 3.0. Specifically: legacy data messages including Generic, Compact and Utility are no longer supported. The remaining Structure Specific data message has been changed to support new features such as reporting of reference metadata as part of the dataset, Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-version-id option for referencing artefacts and changes to the way the structures are organised into ‘collections’ within the message.
141 -* SDMX-JSON – SDMX 2.1 structure, data and metadata JSON messages are not valid in version 3.0. The data message has been changed to support the improved REST data queries, in particular the ability to retrieve in one operation data from multiple datasets with potentially different Data Structure Definitions. Breaking changes similar to those for the SDMX-ML transmission format have been made to the structure message.
142 -* 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.
143 -* SDMX-EDI – Deprecation of the EDI transmission format means that existing systems designed to send or receive structures or data in EDI will not work with version 3.0 registries.
144 -* Information Model – Several structures have been changed in the version 3.0 model and three removed. For these reasons the version 3.0 model is not directly compatible with version 2.1 or earlier, although conversion of specific artefacts is possible under some circumstances. Loss of information during the conversion process however means that in cases like structure mapping, the conversion is not reversible i.e. it is not possible to recreate the 2.1 structure once it has been converted to the 3.0 model.
139 +* SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with (% style="color:#2ecc71" %)version(%%) 3.0 registries.
140 +* [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] – [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 and earlier structure, data and metadata XML messages are not valid in (% style="color:#2ecc71" %)version(%%) 3.0. Specifically: legacy data messages including Generic, Compact and Utility are no longer supported. The remaining Structure Specific data message has been changed to support new features such as reporting of [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] as part of the [[dataset>>doc:xwiki:Glossary.Data set.WebHome]], Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-(% style="color:#2ecc71" %)version(%%)-id option for referencing [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] and changes to the way the structures are organised into ‘collections’ within the message.
141 +* [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] – [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 structure, data and metadata JSON messages are not valid in (% style="color:#2ecc71" %)version(%%) 3.0. The data message has been changed to support the improved REST data queries, in particular the ability to retrieve in one operation data from multiple [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:xwiki:Glossary.Data structure definition.WebHome]]. Breaking changes similar to those for the [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] transmission format have been made to the structure message.
142 +* [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-CSV - The CSV data and [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#2ecc71" %)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.
143 +* [[SDMX-EDI>>doc:xwiki:Glossary.SDMX-EDI.WebHome]] – Deprecation of the EDI transmission format means that existing systems designed to send or receive structures or data in EDI will not work with (% style="color:#2ecc71" %)version(%%) 3.0 registries.
144 +* Information Model – Several structures have been changed in the (% style="color:#2ecc71" %)version(%%) 3.0 model and three removed. For these reasons the (% style="color:#2ecc71" %)version(%%) 3.0 model is not directly compatible with (% style="color:#2ecc71" %)version(%%) 2.1 or earlier, although conversion of specific [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] is possible under some circumstances. Loss of information during the conversion process however means that in cases like structure mapping, the conversion is not reversible i.e. it is not possible to recreate the 2.1 structure once it has been converted to the 3.0 model.
145 145  
146 -The SDMX 3.0 Major Changes document provides more information including an analysis of the breaking changes.
146 +The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Major Changes document provides more information including an analysis of the breaking changes.
147 147  
148 148  = 3 Processes and Business Scope =
149 149