Skip to Content
Last modified by Artur on 2025/09/30 12:30
From version 4.4
edited by Helena
on 2025/06/06 16:55
Change comment: There is no comment for this version
To version 4.1
edited by Helena
on 2025/06/06 16:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  |DRAFT 1.0|December 2024|Draft release updated for SDMX 3.1 for public consultation
9 9  |1.0|May 2025|Public release for SDMX 3.1
10 10  
11 -= 1 Introduction =
11 += {{id name="_Toc56630"/}}1 Introduction =
12 12  
13 13  The Statistical Data and Metadata Exchange (SDMX) initiative (https:~/~/www.sdmx.org) sets standards that can facilitate the exchange of statistical data and metadata using modern information technology.
14 14  
... ... @@ -50,7 +50,7 @@
50 50  
51 51  In July 2020 the SDMX 2.1 specifications were revised to add support for the Validation and Transformation Language (VTL). For 3.0, the VTL specification has been updated to align with changes to the information model and other modifications to the Standard such as the introduction of Semantic Versioning for the versioning of structural metadata artefacts. Section 2 (Information Model) sets out details of the ‘Transformation and Expressions’ package for defining and managing VTL 2.0 programs and Section 6 (Technical Notes) provides detailed guidance on implementing and using VTL with SDMX.
52 52  
53 -= 2 Change History =
53 += {{id name="_Toc56631"/}}2 Change History =
54 54  
55 55  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.
56 56  
... ... @@ -60,27 +60,27 @@
60 60  
61 61  The 3.1 version provides supports for data models to increase dimensionality over time without impacting existing data collections. The Data Constraint model was adjusted to separate concerns of data reporting and data dissemination.
62 62  
63 -== 2.1 Major Changes from 1.0 to 2.0 ==
63 +== {{id name="_Toc56632"/}}2.1 Major Changes from 1.0 to 2.0 ==
64 64  
65 65  * **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.
66 66  * **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/notification.
67 67  * **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; and the description of functional dependencies within cubes are supported.
68 68  
69 -== 2.2 Major Changes from 2.0 to 2.1 ==
69 +== {{id name="_Toc56633"/}}2.2 Major Changes from 2.0 to 2.1 ==
70 70  
71 71  * **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.
72 -* **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.
73 -* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
74 -* **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.
75 -* **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 objectoriented features of W3C XML Schema to allow for easier processing of SDMX data and metadata.
76 -* **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.
77 -* **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
78 -* **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.
79 -* **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 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.
72 +* **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.** **
73 +* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.**  **
74 +* **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.**  **
75 +* **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 objectoriented features of W3C XML Schema to allow for easier processing of SDMX data and metadata.** **
76 +* **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.**  **
77 +* **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.** **
78 +* **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.** **
79 +* **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 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.** **
81 81  * **Support for partial item schemes such as a code list: **The concept of a partial (subset) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
82 82  
83 -== 2.3 Major Changes from 2.1 to 3.0 ==
83 +== {{id name="_Toc56634"/}}2.3 Major Changes from 2.1 to 3.0 ==
84 84  
85 85  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
86 86  
... ... @@ -96,7 +96,7 @@
96 96  
97 97  ==== Versioning of Structural Metadata Artefacts ====
98 98  
99 -• Adoption of the three-number semantic versioning standard for structural metadata artefacts ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
99 +• Adoption of the three-number semantic versioning standard for structural metadata artefacts [[(>>url:https://semver.org/]][[__https:~~/~~/semver.org__>>url:https://semver.org/]][[)>>url:https://semver.org/]]
100 100  
101 101  ==== REST Web Services Application Programming Interface (API) ====
102 102  
... ... @@ -107,7 +107,7 @@
107 107  
108 108  ==== SOAP Web Services API ====
109 109  
110 -• The SOAP web services API has been deprecated with version 3.0 standardising on REST
110 +• The SOAP web services API has been deprecated with version 3.0 standardising on REST** **
111 111  
112 112  ==== XML, JSON, CSV and EDI Transmission formats ====
113 113  
... ... @@ -131,10 +131,9 @@
131 131  
132 132  The SDMX 3.0 Major Changes document provides more information including an analysis of the breaking changes.
133 133  
134 -== 2.4 Major Changes from 3.0 to 3.1 ==
134 +== {{id name="_Toc56635"/}}2.4 Major Changes from 3.0 to 3.1 ==
135 135  
136 -(% class="wikigeneratedid" id="HInformationModel-1" %)
137 -**Information Model**
136 +==== Information Model ====
138 138  
139 139  * Addition of Dimension Constraint property to a Dataflow//  //
140 140  * Addition of evolving structure property to a Data Structure Definition//  //
... ... @@ -143,8 +143,7 @@
143 143  
144 144  o Removal of Role, Data Constraints only restrict data that can be reported// //o Restrict constraint targets to Identifiable structures (not URLs) o Addition of Availability Constraint to define actual data
145 145  
146 -(% class="wikigeneratedid" id="HDocumentation" %)
147 -**Documentation**
145 +==== Documentation ====
148 148  
149 149  • Registering Reference Metadata removed from documentation, to align with XML Registration object which is unable to reference a Metadata Provision, and REST API which is unable to query for registered reference metadata sources.
150 150