Skip to Content
Last modified by Artur on 2025/09/30 12:30
From version 2.2
edited by Helena
on 2025/06/06 16:50
Change comment: Changed document title to [1 Introduction].
To version 4.3
edited by Helena
on 2025/06/06 16:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -1 Introduction
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**
... ... @@ -4,7 +4,7 @@
4 4  |DRAFT 1.0|December 2024|Draft release updated for SDMX 3.1 for public consultation
5 5  |1.0|May 2025|Public release for SDMX 3.1
6 6  
7 -= {{id name="_Toc56630"/}}1 Introduction =
11 += 1 Introduction =
8 8  
9 9  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.
10 10  
... ... @@ -20,20 +20,20 @@
20 20  
21 21  **Section 6** **SDMX Technical Notes** – detailed technical guidance for implementors of the SDMX standard.
22 22  
23 -The following are published on the GitHub repository of the SDMX Standards Technical Working Group (__[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg]][[->>url:https://github.com/sdmx-twg]][[twg>>url:https://github.com/sdmx-twg]]__[[)>>url:https://github.com/sdmx-twg]]: sdmx-twg/sdmx-rest – REST API
27 +The following are published on the GitHub repository of the SDMX Standards Technical Working Group ([[__https:~~/~~/github.com/sdmx-twg__>>https://https:github.comsdmx-twg]]): sdmx-twg/sdmx-rest – REST API
24 24  
25 25  Technical specifications for the SDMX RESTful web services application programming interfaces (API).
26 26  
27 -=== sdmx-twg/sdmx-ml – SDMX-ML ===
28 -
31 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-ml2013SDMX-ML" %)
32 +**sdmx-twg/sdmx-ml – SDMX-ML**
29 29  Technical specifications for the XML transmission format including XSD schemas, documentation and samples for data, structure and reference metadata messages.
30 30  
31 -=== sdmx-twg/sdmx-json – SDMX-JSON ===
32 -
35 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-json2013SDMX-JSON" %)
36 +**sdmx-twg/sdmx-json – SDMX-JSON**
33 33  Technical specifications for the JSON transmission format including documentation, schemas and samples for data, structure and reference metadata messages.
34 34  
35 -=== sdmx-twg/sdmx-csv – SDMX-CSV ===
36 -
39 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-csv2013SDMX-CSV" %)
40 +**sdmx-twg/sdmx-csv – SDMX-CSV**
37 37  Technical specifications for the SDMX-CSV transmission format for ‘comma-separated values’ (CSV) data and reference metadata.
38 38  
39 39  The following sections are obsolete:
... ... @@ -46,7 +46,7 @@
46 46  
47 47  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.
48 48  
49 -= {{id name="_Toc56631"/}}2 Change History =
53 += 2 Change History =
50 50  
51 51  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.
52 52  
... ... @@ -56,27 +56,27 @@
56 56  
57 57  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.
58 58  
59 -== {{id name="_Toc56632"/}}2.1 Major Changes from 1.0 to 2.0 ==
63 +== 2.1 Major Changes from 1.0 to 2.0 ==
60 60  
61 61  * **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.
62 62  * **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.
63 63  * **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.
64 64  
65 -== {{id name="_Toc56633"/}}2.2 Major Changes from 2.0 to 2.1 ==
69 +== 2.2 Major Changes from 2.0 to 2.1 ==
66 66  
67 67  * **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.
68 -* **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.** **
69 -* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.**  **
70 -* **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.**  **
71 -* **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.** **
72 -* **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.**  **
73 -* **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.** **
74 -* **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.** **
75 -* **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.**  **
76 -* **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.
77 77  * **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**.**
78 78  
79 -== {{id name="_Toc56634"/}}2.3 Major Changes from 2.1 to 3.0 ==
83 +== 2.3 Major Changes from 2.1 to 3.0 ==
80 80  
81 81  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
82 82  
... ... @@ -92,7 +92,7 @@
92 92  
93 93  ==== Versioning of Structural Metadata Artefacts ====
94 94  
95 -• 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/]]
99 +• Adoption of the three-number semantic versioning standard for structural metadata artefacts ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
96 96  
97 97  ==== REST Web Services Application Programming Interface (API) ====
98 98  
... ... @@ -131,10 +131,10 @@
131 131  
132 132  ==== Information Model ====
133 133  
134 -* Addition of Dimension Constraint property to a Dataflow//  //
135 -* Addition of evolving structure property to a Data Structure Definition//  //
136 -* Remove version property on Categorisation//  //
137 -* Simplification of Constraints o Removal of Advanced Release Calendar//  //
138 +* Addition of Dimension Constraint property to a Dataflow//  //
139 +* Addition of evolving structure property to a Data Structure Definition//  //
140 +* Remove version property on Categorisation//  //
141 +* Simplification of Constraints o Removal of Advanced Release Calendar//  //
138 138  
139 139  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
140 140  
... ... @@ -232,7 +232,7 @@
232 232  * //**Dataflow Definition:**// In SDMX, data sets are reported or disseminated according to a data flow definition. The data flow definition identifies the data structure definition and may be associated with one or more subject matter domains via a Categorisation (this facilitates the search for data according to organised category schemes). Constraints, in terms of reporting periodicity or sub set of possible keys that are allowed in a data set, may be attached to the data flow definition.
233 233  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
234 234  * //**Data Provider: **//An organization which produces data is termed a data provider.
235 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
239 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
236 236  * //**Provision Agreement (Metadata Provision Agreement):**// The set of information which describes the way in which data sets and metadata sets are provided by a data/metadata provider. A provision agreement can be constrained in much the same way as a data or metadata flow definition. Thus, a data provider can express the fact that it provides a particular data flow covering a specific set of countries and topics, Importantly, the actual source of registered data or metadata is attached to the provision agreement (in terms of a URL). The term “agreement” is used because this information can be understood as the basis of a “service-level agreement”. In SDMX, however, this is informational metadata to support the technical systems, as opposed to any sort of contractual information (which is outside the scope of a technical specification). In version 3.0, metadata provision agreement and data provision agreement are two separate artefacts.
237 237  * //**Data Constraint:**// Used to restrict content (such as enumerations) and are used by provision agreements, data flows, data structure definitions in order to provide a set of reporting restrictions in the context of a collection
238 238  * //**Metadata Constraint:**// Used to restrict content (such as enumerations) and are used by metadata provision agreements, metadata flows, metadata structure definitions in order to provide a set of reporting restrictions in the context of a collection
SDMX_3-1-0_SECTION_1_FINAL_6728d8d4.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +403.7 KB
Content