Changes for page SDMX 3.0 Standards. Section 1. Framework for SDMX technical standards

Last modified by Helena on 2025/09/10 11:19

From 1.1 to 2.1 From 4.9 to 4.10

From version 2.1

edited by Helena
on 2025/05/14 15:17

Change comment: Created by office importer.

To version 4.9

edited by Helena
on 2025/05/14 15:27

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- SDMX 3-0-0 SECTION 1 FINAL-1.0_en_a3e7967f.png

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+SDMX STANDARDS: SECTION 1

Content

@@ -1,16 +1,21 @@
++{{box title="**Contents**"}}
++{{toc/}}
++{{/box}}
++
  **Revision History**
--|**Revision**|**Date**|**Contents**
--|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
--|1.0|October 2021|Public release for SDMX 3.0
++(% style="width:769.039px" %)
++|(% style="width:144px" %)**Revision**|(% style="width:195px" %)**Date**|(% style="width:426px" %)**Contents**
++|(% style="width:144px" %)DRAFT 1.0|(% style="width:195px" %)May 2021|(% style="width:426px" %)Draft release updated for SDMX 3.0 for public consultation
++|(% style="width:144px" %)1.0|(% style="width:195px" %)October 2021|(% style="width:426px" %)Public release for SDMX 3.0
--= {{id name="_Toc56226"/}}1 Introduction =
++= 1 Introduction =
  The Statistical Data and Metadata Exchange (SDMX) initiative (https:~/~/www.sdmx.org) sets 3 standards that can facilitate the exchange of statistical data and metadata using modern 4 information technology.
  The SDMX Technical Specifications are organised into several discrete sections.
--The following are published on the SDMX website ( __[[https:~~/~~/www.sdmx.org>>url:https://www.sdmx.org/]]__ [[)>>url:https://www.sdmx.org/]]:
++The following are published on the SDMX website ([[__https:~~/~~/www.sdmx.org__>>https://https:www.sdmx.org]]).
  **Section 1** **Framework for SDMX Technical Standards** – this document providing an introduction to the technical standards.
@@ -20,7 +20,7 @@
  **Section 6** **SDMX Technical Notes** – detailed technical guidance for implementors of the SDMX standard.
--The following are published on the GitHub repository of the SDMX Standards Technical Working Group ( __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx]][[->>url:https://github.com/sdmx-twg]][[twg>>url:https://github.com/sdmx-twg]]__ [[)>>url:https://github.com/sdmx-twg]]:
++The following are published on the GitHub repository of the SDMX Standards Technical Working Group ( __[[https:~~/~~/github.com/sdmx-twg>>https://github.com/sdmx-twg]]) :__
  === sdmx-twg/sdmx-rest – REST API ===
@@ -48,7 +48,7 @@
  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.
--= {{id name="_Toc56227"/}}2 Change History =
++= 2 Change History =
  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,39 +56,28 @@
  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.
--== {{id name="_Toc56228"/}}2.1 Major Changes from 1.0 to 2.0 ==
++== 2.1 Major Changes from 1.0 to 2.0 ==
  * **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.
--* **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.
++* **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.
++* **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.
--• **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.
++== 2.2 Major Changes from 2.0 to 2.1 ==
--== {{id name="_Toc56229"/}}2.2 Major Changes from 2.0 to 2.1 ==
++* **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.
++* **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.
++* **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.
++* **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.
++* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
++* **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.
++* **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.
++* **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.
++* **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
++* **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.
++* **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**.**
--• **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.
++== 2.3 Major Changes from 2.1 to 3.0 ==
--• **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.
--
--• **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
--
--• **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.
--
--• **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.
--
--• **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.
--
--• **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
--
--• **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.
--
--==== • **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. ====
--
--• **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.
--
--• **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**.**
--
--== {{id name="_Toc56230"/}}2.3 Major Changes from 2.1 to 3.0 ==
--
  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
  ===== Information Model =====
@@ -103,7 +103,7 @@
  ===== Versioning of Structural Metadata Artefacts =====
--• 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/]]
++* Adoption of the three-number semantic versioning standard for structural metadata artefacts (__[[https:~~/~~/semver.org>>url:https://semver.org/]])__
  ===== REST Web Services Application Programming Interface (API) =====
@@ -114,7 +114,7 @@
  ===== SOAP Web Services API =====
--• The SOAP web services API has been deprecated with version 3.0 standardising on REST**&nbsp;**
++* The SOAP web services API has been deprecated with version 3.0 standardising on REST
  ===== XML, JSON, CSV and EDI Transmission formats =====
@@ -138,9 +138,9 @@
  The SDMX 3.0 Major Changes document provides more information including an analysis of the breaking changes.
--= {{id name="_Toc56231"/}}3 Processes and Business Scope =
++= 3 Processes and Business Scope =
--== {{id name="_Toc56232"/}}3.1 Process Patterns ==
++== 3.1 Process Patterns ==
  SDMX identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
@@ -160,7 +160,7 @@
  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.
--== {{id name="_Toc56233"/}}3.2 SDMX and Process Automation ==
++== 3.2 SDMX and Process Automation ==
  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,7 +176,7 @@
  The SDMX standards specified here are designed to support the requirements of all of these automation processes and technologies.
--== {{id name="_Toc56234"/}}3.3 Statistical Data and Metadata ==
++== 3.3 Statistical Data and Metadata ==
  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.
@@ -196,9 +196,9 @@
  [[image:SDMX 3-0-0 SECTION 1 FINAL-1.0_en_a3e7967f.png||height="921" width="629"]]
--**Figure 1: High Level Schematic of Major Artefacts in the SDMX 3.0 Information Model**
++Figure 1: High Level Schematic of Major Artefacts in the SDMX 3.0 Information Model
--== {{id name="_Toc56235"/}}3.4 The SDMX View of Statistical Exchange ==
++== 3.4 The SDMX View of Statistical Exchange ==
  Version 1.0 of ISO/TS 17369 SDMX covered statistical data sets and the metadata related to the structure of these data sets. This scope was useful in supporting the different models of statistical exchange (bilateral exchange, gateway exchange, and data-sharing) but was not by itself sufficient to support them completely. Versions 2.0 and 2.1 provide a much more complete view of statistical exchange, so that an open data-sharing model can be fully supported, and other models of exchange can be more completely automated. In order to produce technical standards that will support this increased scope, the SDMX Information Model provides a broader set of formal objects which describe the actors, processes, and resources within statistical exchanges.
@@ -228,27 +228,20 @@
  * //**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.
  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
  * //**Data Provider: **//An organization which produces data is termed a data provider.
--* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.// &nbsp;//
++* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.// &nbsp;//
  * //**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.
  * //**Constraint:**// Data and Metadata Constraints describe a subset of a data source or metadata source, and may also provide information about scheduled releases of data. They are associated with data / metadata providers, provision agreements, data flows, metadataflows, data structure definitions and metadata structure definitions.
  * //**Structure Map: **//Structure maps describes a mapping between data structure definitions or dataflows for the purpose of transforming a data set into a different structure. The mapping rules are defined using one or more component maps which each map in turn describes how one or more components from the source data 534 structure definition map to one or more components in that of the target. Represent maps act as lookup tables and specific provision is made for mapping dates and times.
++* //**Representation Map:**// Representation maps describe mappings between source value(s) and target value(s) where the values are restricted to those in a code list, value list or be of a certain type such as integer or string.
++* //**Item Scheme Map:**// An item scheme map describes mapping rules between any item scheme with the exception of code lists and value lists which use representation maps. The version 3.0 information model provides four item scheme maps: organisation scheme map, concept scheme map, category scheme map and reporting taxonomy map. Organisation scheme map and reporting scheme map have been omitted from the information model schematic in Figure 1.
++* //**Reporting Taxonomy: **//A reporting taxonomy allows an organisation to link (possibly in a hierarchical way) a number of cube or data flow definitions which together form a complete “report” of data or metadata. This supports primary reporting which often comprises multiple cubes of heterogeneous data, but may also support other collection and reporting functions. It also supports the specification of publications such as a yearbook, in terms of the data or metadata contained in the publication.
++* //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of reference 556 metadata sets which describe processes-related concepts.
++* //**Hierarchy**//: Describes complex code hierarchies principally for data discovery purposes. The codes themselves are referenced from the code lists in which they are maintained.
++* //**Hierarchy Association**//: A hierarchy association links a hierarchy to something that needs it like a dimension. Furthermore, the linking can be specified in the context of another object such as a dimension in the context of a dataflow. Thus, a dimension in a data structure definition could have different hierarchies depending on the dataflow.
++* //**Transformation Scheme:**// A transformation scheme is a set of Validation and Transformation Language (VTL) transformations aimed at obtaining some meaningful results for the user (e.g., the validation of one or more data sets). The set of transformations is meant to be executed together (in the same run) and may contain any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a VTL ‘program’.
--• //**Representation Map:**// Representation maps describe mappings between source value(s) and target value(s) where the values are restricted to those in a code list, value list or be of a certain type such as integer or string.
++== 3.5 SDMX Registry Services ==
--• //**Item Scheme Map:**// An item scheme map describes mapping rules between any item scheme with the exception of code lists and value lists which use representation maps. The version 3.0 information model provides four item scheme maps: organisation scheme map, concept scheme map, category scheme map and reporting taxonomy map. Organisation scheme map and reporting scheme map have been omitted from the information model schematic in Figure 1.
--
--• //**Reporting Taxonomy: **//A reporting taxonomy allows an organisation to link (possibly in a hierarchical way) a number of cube or data flow definitions which together form a complete “report” of data or metadata. This supports primary reporting which often comprises multiple cubes of heterogeneous data, but may also support other collection and reporting functions. It also supports the specification of publications such as a yearbook, in terms of the data or metadata contained in the publication.
--
--• //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of reference 556 metadata sets which describe processes-related concepts.
--
--• //**Hierarchy**//: Describes complex code hierarchies principally for data discovery purposes. The codes themselves are referenced from the code lists in which they are maintained.
--
--• //**Hierarchy Association**//: A hierarchy association links a hierarchy to something that needs it like a dimension. Furthermore, the linking can be specified in the context of another object such as a dimension in the context of a dataflow. Thus, a dimension in a data structure definition could have different hierarchies depending on the dataflow.
--
--• //**Transformation Scheme:**// A transformation scheme is a set of Validation and Transformation Language (VTL) transformations aimed at obtaining some meaningful results for the user (e.g., the validation of one or more data sets). The set of transformations is meant to be executed together (in the same run) and may contain any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a VTL ‘program’.
--
--== {{id name="_Toc56236"/}}3.5 SDMX Registry Services ==
--
  In order to provide visibility into the large amount of data and metadata which exists within the SDMX model of statistical exchange, it is felt that an architecture based on a set of registry services is potentially useful. A “registry” – as understood in webservices terminology – is an application which maintains and stores metadata for querying, and which can be used by any other application in the network with sufficient access privileges (though note that the mechanism of access control is outside of the scope of the SDMX standard). It can be understood as the index of a distributed database or metadata repository which is made up of all the data provider’s data sets and reference metadata sets within a statistical community, located across the Internet or similar network.
  Note that the SDMX registry services are not concerned with the storage of data or reference metadata. The assumption is that data and reference metadata lives on the sites of its data and metadata providers. The SDMX registry services concern themselves with providing visibility of the data and reference metadata, and information needed to access the data and reference metadata. Thus, a registered data set will have its URL available in the registry, but not the data itself. An application which wishes to access that data would query the registry, perhaps by drilling down via a Category Scheme and Dataflow, for the URL of a registered data source, and then retrieve the data directly from the data provider (using an SDMX REST API query message or other mechanism).
@@ -262,7 +262,7 @@
  * //**Querying: **//The registry services have interfaces for querying the metadata contained in a registry, so that applications and users can discover the existence of data sets and reference metadata sets, structural metadata, the providers/agencies associated with those objects, and the provider agreements which describe how the data and metadata are made available, and how they are categorized.
  * //**Subscription/Notification:**// It is possible to “subscribe” to specific objects in a registry, so that a notification will be sent to all subscribers whenever the registry objects are updated.
--== {{id name="_Toc56237"/}}3.6 RESTful Web services ==
++== 3.6 RESTful Web services ==
  Web services allow computer applications to exchange data directly over the Internet, essentially allowing modular or distributed computing in a more flexible fashion than ever before. In order to allow web services to function, however, many standards are required: for requesting and supplying data; for expressing the enveloping data which is used to package exchanged data; for describing web services to one another, to allow for easy integration into applications that use other web services as data resources.
@@ -276,7 +276,7 @@
  The following conceptual example uses the ‘data’ resource to query a data repository for a series identified by the key ‘M.USD.EUR.SP00.A’ in the EXR (ECB exchange rates) Dataflow: https:~/~/ws-entry-point/data/dataflow/ECB/EXR/1.0.0/M.USD.EUR.SP00.A
--= {{id name="_Toc56238"/}}4 The SDMX Information Model =
++= 4 The SDMX Information Model =
  SDMX provides a way of modelling statistical data, and defines the set of metadata constructs used for this purpose. Because SDMX specifies a number of transmission formats for expressing data and structural metadata, the model is used as a mechanism for guaranteeing that transformation between the different formats is lossless. In this sense, all of the formats are syntax-bound expressions of the common information model.
@@ -294,9 +294,9 @@
  A full UML conceptual design of the information model is set out in Section 2 of the Technical Specifications.
--= {{id name="_Toc56239"/}}5 The SDMX Transmission Formats =
++= 5 The SDMX Transmission Formats =
--== {{id name="_Toc56240"/}}5.1 SDMX-ML ==
++== 5.1 SDMX-ML ==
  SDMX-ML is the XML transmission format specification for exchanging structural metadata, data and reference metadata, and interacting with SDMX registry services. It is designed as a general-purpose format for all automation and data / metadata exchange tasks, and provides the most complete coverage.

SDMX 3-0-0 SECTION 1 FINAL-1.0_en_a3e7967f.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+102.2 KB

Content