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

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +1 Introduction
Content
... ... @@ -1,7 +5,3 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
4 -
5 5  **Revision History**
6 6  
7 7  |**Revision**|**Date**|**Contents**
... ... @@ -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 =
7 += {{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  
... ... @@ -24,20 +24,20 @@
24 24  
25 25  **Section 6** **SDMX Technical Notes** – detailed technical guidance for implementors of the SDMX standard.
26 26  
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
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
28 28  
29 29  Technical specifications for the SDMX RESTful web services application programming interfaces (API).
30 30  
31 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-ml2013SDMX-ML" %)
32 -**sdmx-twg/sdmx-ml – SDMX-ML**
27 +=== sdmx-twg/sdmx-ml – SDMX-ML ===
28 +
33 33  Technical specifications for the XML transmission format including XSD schemas, documentation and samples for data, structure and reference metadata messages.
34 34  
35 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-json2013SDMX-JSON" %)
36 -**sdmx-twg/sdmx-json – SDMX-JSON**
31 +=== sdmx-twg/sdmx-json – SDMX-JSON ===
32 +
37 37  Technical specifications for the JSON transmission format including documentation, schemas and samples for data, structure and reference metadata messages.
38 38  
39 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-csv2013SDMX-CSV" %)
40 -**sdmx-twg/sdmx-csv – SDMX-CSV**
35 +=== sdmx-twg/sdmx-csv – SDMX-CSV ===
36 +
41 41  Technical specifications for the SDMX-CSV transmission format for ‘comma-separated values’ (CSV) data and reference metadata.
42 42  
43 43  The following sections are obsolete:
... ... @@ -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 =
49 += {{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 ==
59 +== {{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 ==
65 +== {{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.
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.** **
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 ==
79 +== {{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]])
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/]]
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
106 +• 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,26 +131,24 @@
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 ==
130 +== {{id name="_Toc56635"/}}2.4 Major Changes from 3.0 to 3.1 ==
135 135  
136 -(% class="wikigeneratedid" id="HInformationModel-1" %)
137 -**Information Model**
132 +==== Information Model ====
138 138  
139 -* Addition of Dimension Constraint property to a Dataflow//  //
140 -* Addition of evolving structure property to a Data Structure Definition//  //
141 -* Remove version property on Categorisation//  //
142 -* Simplification of Constraints o Removal of Advanced Release Calendar//  //
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//  //
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**
141 +==== 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  
151 -= 3 Processes and Business Scope =
145 += {{id name="_Toc56636"/}}3 Processes and Business Scope =
152 152  
153 -== 3.1 Process Patterns ==
147 +== {{id name="_Toc56637"/}}3.1 Process Patterns ==
154 154  
155 155  SDMX identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
156 156  
... ... @@ -170,7 +170,7 @@
170 170  
171 171  It is important to note that SDMX is primarily focused on the //exchange// and //dissemination// of statistical data and metadata. There may also be many uses for the standard model and formats specified here in the context of internal processing of data that are not concerned with the exchange between organizations and users, however. It is felt that a clear, standard formatting of data and metadata for the purposes of exchange and dissemination can also facilitate internal processing by organizations and users, but this is not the focus of the specification.
172 172  
173 -== 3.2 SDMX and Process Automation ==
167 +== {{id name="_Toc56638"/}}3.2 SDMX and Process Automation ==
174 174  
175 175  Statistical data and metadata exchanges employ many different automated processes, but some are of more general interest than others. There are some common information technologies that are nearly ubiquitous within information systems today. SDMX aims to provide standards that are most useful for these automated processes and technologies.
176 176  
... ... @@ -178,12 +178,15 @@
178 178  
179 179  1. //Batch Exchange of Data and Metadata~:// The transmission of whole or partial databases between counterparties, including incremental updating.
180 180  1. //Provision of Data and Metadata on the Internet~:// Internet technology - including its use in private or semi-private TCP/IP networks - is extremely common. This technology includes XML, JSON and REST web services as primary mechanisms for automating data and metadata provision, as well as the more traditional static HTML and database-driven publishing.
181 -1. //Generic Processes~:// While many applications and processes are specific to some set of data and metadata, other types of automated services and processes are designed to handle any type of statistical data and metadata whatsoever. This is particularly true in cases where portal sites and data feeds are made available on the Internet.
175 +1. //Generic Processes~:// While many applications and processes are specific to some set of data and metadata, other types of automated services and processes are designed
176 +
177 +to handle any type of statistical data and metadata whatsoever. This is particularly true in cases where portal sites and data feeds are made available on the Internet.
178 +
182 182  1. //Presentation and Transformation of Data~:// In order to make data and metadata useful to consumers, they must support automated processes that transform them into application-specific processing formats, other standard formats, and presentational formats. Although not strictly an aspect of exchange, this type of automated processing represents a set of requirements that must be supported if the information exchange between counterparties is itself to be supported.
183 183  
184 184  The SDMX standards specified here are designed to support the requirements of all of these automation processes and technologies.
185 185  
186 -== 3.3 Statistical Data and Metadata ==
183 +== {{id name="_Toc56639"/}}3.3 Statistical Data and Metadata ==
187 187  
188 188  To avoid confusion about which "data" and "metadata" are the intended content of the SDMX formats specified here, a statement of scope is offered. Statistical "data" are sets of often numeric observations which typically have time associated with them. They are associated with a set of metadata values, representing specific concepts, which act as identifiers and descriptors of the data. These metadata values and concepts can be understood as the named dimensions of a multi-dimensional co-ordinate system, describing what is often called a "cube" of data.
189 189  
... ... @@ -235,7 +235,7 @@
235 235  * //**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.
236 236  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
237 237  * //**Data Provider: **//An organization which produces data is termed a data provider.
238 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
235 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
239 239  * //**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.
240 240  * //**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
241 241  * //**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,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -403.7 KB
Content