Changes for page SDMX 3.1 Standards. Section 1. Framework

Last modified by Artur on 2025/09/30 12:30

From 12.5 to 13.1 From 15.3 to 15.4

From version 13.1

edited by Helena
on 2025/06/06 17:15

Change comment: There is no comment for this version

To version 15.3

edited by Helena
on 2025/06/06 17:30

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- SDMX%203.1%20Section%201.png

Details

Page properties

Content

@@ -98,7 +98,7 @@
  (% class="wikigeneratedid" id="HVersioningofStructuralMetadataArtefacts" %)
  **Versioning of Structural Metadata Artefacts**
--• Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
++Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
  (% class="wikigeneratedid" id="HRESTWebServicesApplicationProgrammingInterface28API29" %)
  **REST Web Services Application Programming Interface (API)**
@@ -108,39 +108,60 @@
  * Improvements to [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] queries
  * Support for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] maintenance using HTTP PUT, POST and DELETE verbs
++(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
++**SOAP Web Services API**
++* The SOAP web services API has been deprecated with (% style="color:#e74c3c" %)version(%%) 3.0 standardising on REST
--The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards specified here are designed to support the requirements of all of these automation processes and technologies.
++(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
++**XML, JSON, CSV and EDI Transmission formats**
--== 3.3 Statistical Data and Metadata ==
++The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:sdmx: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:sdmx:Glossary.Reference metadata.WebHome]] and microdata Obsolete [[SDMX-ML>>doc:sdmx: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 The [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified The option to reference structures in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
--To avoid confusion about which "data" and "metadata" are the intended content of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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 (% style="color:#e74c3c" %)concepts(%%), which act as identifiers and descriptors of the data. These metadata values and (% style="color:#e74c3c" %)concepts(%%) can be understood as the named [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of a multi-dimensional co-ordinate system, describing what is often called a "cube" of data.
++Several of the changes are ‘breaking’ meaning that, in specific cases, the (% style="color:#e74c3c" %)version(%%) 3.0 specification is not backwardly compatible with earlier (% style="color:#e74c3c" %)versions(%%) of the Standard.
--[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies a standard technique for modelling, expressing, and understanding the structure of this multi-dimensional "cube", allowing automated processing of data from a variety of sources. This approach is widely applicable across types of data and attempts to provide the simplest and most easily comprehensible technique that will support the exchange of this broad set of data and related metadata.
++The principle breaking changes are:
--The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those (% style="color:#e74c3c" %)concepts(%%) used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of (% style="color:#e74c3c" %)concepts(%%) that describe and qualify statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and processing more generally, and which are often associated not with specific observations or series of data, but with entire collections of data or even the institutions which provide that data.
++* 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.
++* SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries.
++* [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 and earlier structure, data and metadata XML messages are not valid in (% style="color:#e74c3c" %)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:sdmx:Glossary.Reference metadata.WebHome]] as part of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]], Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-(% style="color:#e74c3c" %)version(%%)-id option for referencing [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] and changes to the way the structures are organised into ‘collections’ within the message.
++* [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 structure, data and metadata JSON messages are not valid in (% style="color:#e74c3c" %)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:sdmx:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Breaking changes similar to those for the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] transmission format have been made to the structure message.
++* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV - The CSV data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#e74c3c" %)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.
++* [[SDMX-EDI>>doc:sdmx: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:#e74c3c" %)version(%%) 3.0 registries.
++* Information Model – Several structures have been changed in the (% style="color:#e74c3c" %)version(%%) 3.0 model and three removed. For these reasons the (% style="color:#e74c3c" %)version(%%) 3.0 model is not directly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 or earlier, although conversion of specific [[artefacts>>doc:sdmx: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.
--The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the structuring not only of data, but also of “reference” metadata. While these [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures exist independent of the data and its [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], they are often linked. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the attachment of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to any part of the data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], as well as for the reporting and exchange of the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and its structural descriptions. This function of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards supports many aspects of data quality initiatives, allowing as it does for the exchange of metadata in its broadest sense, of which quality-related metadata is a major part.
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Major Changes document provides more information including an analysis of the breaking changes.
--Metadata are associated not only with data, but also with the process of providing and managing the flow of data. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for a set of metadata concerned with “data provisioning” – metadata which are useful to those who need to understand the content and form of a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]’s output. Each [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can describe in standard fashion the content of and dependencies within the data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] which they produce, and supply information about the scheduling and mechanism by which their data and metadata are provided. This allows for automation of some validation and control functions, as well as supporting management of data reporting.
++== 2.4 Major Changes from 3.0 to 3.1 ==
--[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] also recognizes the importance of classification schemes in organizing and managing the exchange and dissemination of data and metadata. It is possible to express information about classification schemes and domain [[categories>>doc:sdmx:Glossary.Category.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], along with their relationships to data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], as well as to categorize other objects in the model.
++(% class="wikigeneratedid" id="HInformationModel-1" %)
++**Information Model**
--The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards offer a common model, a choice of syntax and, for XML, a choice of data formats which support the exchange of any type of statistical data meeting the definition above; several optimized formats are specified based on the specific requirements of each implementation, as described below in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] section.
++* Addition of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) property to a Dataflow
++* Addition of evolving structure property to a Data Structure Definition
++* Remove (% style="color:#e74c3c" %)version(%%) property on Categorisation
++* Simplification of (% style="color:#e74c3c" %)Constraints
++** Removal of Advanced Release Calendar
++** Removal of Role, Data (% style="color:#e74c3c" %)Constraints(%%) only restrict data that can be reported
++** Restrict (% style="color:#e74c3c" %)constraint(%%) targets to Identifiable structures (not URLs)
++** Addition of Availability (% style="color:#e74c3c" %)Constraint(%%) to define actual data
--The formal objects in the information model are presented schematically in Figure 1, and are discussed in more detail elsewhere in this document.
++(% class="wikigeneratedid" id="HDocumentation" %)
++**Documentation**
--This document specifies the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards designed to facilitate exchanges based on any of these process patterns, and shows how [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] offers advantages in all cases. It is possible to agree bilaterally to use a standard format (such as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] or [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]]); it is possible for data senders in a gateway process to use a standard format for data exchange with each other, or with any [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] who agree to do so; it is possible to agree to use the full set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to support a common data-sharing process of exchange, whether based on an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant registry or some other architecture.
++* Registering [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] 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>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources.
--The standards specified here specifically support a data-sharing process based on the use of central registry services. Registry services provide visibility into the data and metadata existing within the community, and support the access and use of this data and metadata by providing a set of triggers for automated processing. The data or metadata itself is not stored in a central registry – these services merely provide a useful set of metadata about the data (and additional metadata) in a known location, so that users/applications can easily locate and obtain whatever data and/or metadata is registered. The use of standards for all data, metadata, and the registry services themselves is ubiquitous, permitting a high (% style="color:#e74c3c" %)level(%%) of automation within a data-sharing community.
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards specified here are designed to support the requirements of all of these automation processes and technologies.
--It should be pointed out that these different process models are not mutually exclusive – a single system capable of expressing data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant formats could support all three scenarios. Different standards may be applicable to different processes (for example, many registry services interfaces are used only in a data-sharing scenario) but all have a common basis in a shared information model.
++= 3 Processes and Business Scope =
--In addition to looking at collection and reporting, it is also important to consider the dissemination of data. Data and metadata – no matter how they are exchanged between counterparties in the process of their development and creation – are all eventually supplied to an end user of some type. Often, this is through specific applications inside of institutions. But more and more frequently, data and metadata are also published on websites in various formats. The dissemination of data and its accompanying metadata on the web is a focus of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards. Standards for statistical data and metadata allow improvements in the publication of data – it becomes more easily possible to process a standard format once the data is obtained, and the data and metadata are linked together, making the comprehension and further processing of the data easier.
++== 3.1 Process Patterns ==
--In discussions of statistical data, there are many aspects of its dissemination which impact data quality: data discovery, ease of use, and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]]. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards provide support for all of these aspects of data dissemination. Standard data formats promote ease of use, and provide links to relevant metadata. The (% style="color:#e74c3c" %)concept(%%) of registry services means that data and metadata can more easily be discovered. [[Timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] is improved throughout the data lifecycle by increases in efficiency, promoted through the availability of metadata and ease of use.
++[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
--It is important to note that [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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.
++1. //**Bilateral exchange**~:// All aspects of the exchange process are agreed between counterparties, including the mechanism for exchange of data and metadata, the formats, the frequency or schedule, and the mode used for communications regarding the exchange. This is perhaps the most common process pattern.
++1. //**Gateway exchange**~:// Gateway exchanges are an organized set of bilateral exchanges, in which several data and metadata collecting organizations or individuals agree to exchange the collected information with each other in a single, known format, and according to a single, known process. This pattern has the effect of reducing the burden of managing multiple bilateral exchanges (in data and metadata collection) across the sharing organizations/individuals. This is also a very common process pattern in the statistical area, where communities of institutions agree on ways to gain efficiencies within the scope of their collective responsibilities.
++1. //**Data-sharing exchange**~:// Open, freely available data formats and process patterns are known and standard. Thus, any organization or individual can use any counterparty’s data and metadata (assuming they are permitted access to it). This model requires no bilateral agreement, but only requires that data and metadata providers and consumers adhere to the standards.
  == 3.2 SDMX and Process Automation ==
@@ -148,50 +148,43 @@
  Briefly, these can be described as:
--//Batch Exchange of Data and Metadata~:// The transmission of whole or partial databases between counterparties, including incremental updating. //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. //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. //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.
++1. //**Batch Exchange of Data and Metadata**~:// The transmission of whole or partial databases between counterparties, including incremental updating.
++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.
++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.
++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.
--o Removal of Role, Data (% style="color:#e74c3c" %)Constraints(%%) only restrict data that can be reported// //o Restrict (% style="color:#e74c3c" %)constraint(%%) targets to Identifiable structures (not URLs) o Addition of Availability (% style="color:#e74c3c" %)Constraint(%%) to define actual data
++== 3.3 Statistical Data and Metadata ==
--(% class="wikigeneratedid" id="HDocumentation" %)
--**Documentation**
++To avoid confusion about which "data" and "metadata" are the intended content of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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 (% style="color:#e74c3c" %)concepts(%%), which act as identifiers and descriptors of the data. These metadata values and (% style="color:#e74c3c" %)concepts(%%) can be understood as the named [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of a multi-dimensional co-ordinate system, describing what is often called a "cube" of data.
--• Registering [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] 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>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources.
++[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies a standard technique for modelling, expressing, and understanding the structure of this multi-dimensional "cube", allowing automated processing of data from a variety of sources. This approach is widely applicable across types of data and attempts to provide the simplest and most easily comprehensible technique that will support the exchange of this broad set of data and related metadata.
--= 3 Processes and Business Scope =
++The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those (% style="color:#e74c3c" %)concepts(%%) used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of (% style="color:#e74c3c" %)concepts(%%) that describe and qualify statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and processing more generally, and which are often associated not with specific observations or series of data, but with entire collections of data or even the institutions which provide that data.
--== 3.1 Process Patterns ==
++The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the structuring not only of data, but also of “reference” metadata. While these [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures exist independent of the data and its [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], they are often linked. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the attachment of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to any part of the data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], as well as for the reporting and exchange of the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and its structural descriptions. This function of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards supports many aspects of data quality initiatives, allowing as it does for the exchange of metadata in its broadest sense, of which quality-related metadata is a major part.
--[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
++Metadata are associated not only with data, but also with the process of providing and managing the flow of data. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for a set of metadata concerned with “data provisioning” – metadata which are useful to those who need to understand the content and form of a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]’s output. Each [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can describe in standard fashion the content of and dependencies within the data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] which they produce, and supply information about the scheduling and mechanism by which their data and metadata are provided. This allows for automation of some validation and control functions, as well as supporting management of data reporting.
--//Bilateral exchange~:// All aspects of the exchange process are agreed between counterparties, including the mechanism for exchange of data and metadata, the formats, the frequency or schedule, and the mode used for communications regarding the exchange. This is perhaps the most common process pattern. //Gateway exchange~:// Gateway exchanges are an organized set of bilateral exchanges, in which several data and metadata collecting organizations or individuals agree to exchange the collected information with each other in a single, known format, and according to a single, known process. This pattern has the effect of reducing the burden of managing multiple bilateral exchanges (in data and metadata collection) across the sharing organizations/individuals. This is also a very common process pattern in the statistical area, where communities of institutions agree on ways to gain efficiencies within the scope of their collective responsibilities. //Data-sharing exchange~:// Open, freely available data formats and process patterns are known and standard. Thus, any organization or individual can use any counterparty’s data and metadata (assuming they are permitted access to it). This model requires no bilateral agreement, but only requires that data and metadata providers and consumers adhere to the standards.
++[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] also recognizes the importance of classification schemes in organizing and managing the exchange and dissemination of data and metadata. It is possible to express information about classification schemes and domain [[categories>>doc:sdmx:Glossary.Category.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], along with their relationships to data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], as well as to categorize other objects in the model.
--The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Major Changes document provides more information including an analysis of the breaking changes.
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards offer a common model, a choice of syntax and, for XML, a choice of data formats which support the exchange of any type of statistical data meeting the definition above; several optimized formats are specified based on the specific requirements of each implementation, as described below in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] section.
--== 2.4 Major Changes from 3.0 to 3.1 ==
++The formal objects in the information model are presented schematically in Figure 1, and are discussed in more detail elsewhere in this document.
--(% class="wikigeneratedid" id="HInformationModel-1" %)
--**Information Model**
++This document specifies the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards designed to facilitate exchanges based on any of these process patterns, and shows how [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] offers advantages in all cases. It is possible to agree bilaterally to use a standard format (such as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] or [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]]); it is possible for data senders in a gateway process to use a standard format for data exchange with each other, or with any [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] who agree to do so; it is possible to agree to use the full set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to support a common data-sharing process of exchange, whether based on an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant registry or some other architecture.
--Addition of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) property to a Dataflow Addition of evolving structure property to a Data Structure Definition Remove (% style="color:#e74c3c" %)version(%%) property on Categorisation Simplification of (% style="color:#e74c3c" %)Constraints(%%) o Removal of Advanced Release Calendar
++The standards specified here specifically support a data-sharing process based on the use of central registry services. Registry services provide visibility into the data and metadata existing within the community, and support the access and use of this data and metadata by providing a set of triggers for automated processing. The data or metadata itself is not stored in a central registry – these services merely provide a useful set of metadata about the data (and additional metadata) in a known location, so that users/applications can easily locate and obtain whatever data and/or metadata is registered. The use of standards for all data, metadata, and the registry services themselves is ubiquitous, permitting a high (% style="color:#e74c3c" %)level(%%) of automation within a data-sharing community.
--Several of the changes are ‘breaking’ meaning that, in specific cases, the (% style="color:#e74c3c" %)version(%%) 3.0 specification is not backwardly compatible with earlier (% style="color:#e74c3c" %)versions(%%) of the Standard.
++It should be pointed out that these different process models are not mutually exclusive – a single system capable of expressing data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant formats could support all three scenarios. Different standards may be applicable to different processes (for example, many registry services interfaces are used only in a data-sharing scenario) but all have a common basis in a shared information model.
--The principle breaking changes are:
++In addition to looking at collection and reporting, it is also important to consider the dissemination of data. Data and metadata – no matter how they are exchanged between counterparties in the process of their development and creation – are all eventually supplied to an end user of some type. Often, this is through specific applications inside of institutions. But more and more frequently, data and metadata are also published on websites in various formats. The dissemination of data and its accompanying metadata on the web is a focus of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards. Standards for statistical data and metadata allow improvements in the publication of data – it becomes more easily possible to process a standard format once the data is obtained, and the data and metadata are linked together, making the comprehension and further processing of the data easier.
--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. SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries. [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 and earlier structure, data and metadata XML messages are not valid in (% style="color:#e74c3c" %)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:sdmx:Glossary.Reference metadata.WebHome]] as part of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]], Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-(% style="color:#e74c3c" %)version(%%)-id option for referencing [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] and changes to the way the structures are organised into ‘collections’ within the message. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 structure, data and metadata JSON messages are not valid in (% style="color:#e74c3c" %)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:sdmx:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Breaking changes similar to those for the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] transmission format have been made to the structure message. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV - The CSV data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#e74c3c" %)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. [[SDMX-EDI>>doc:sdmx: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:#e74c3c" %)version(%%) 3.0 registries. Information Model – Several structures have been changed in the (% style="color:#e74c3c" %)version(%%) 3.0 model and three removed. For these reasons the (% style="color:#e74c3c" %)version(%%) 3.0 model is not directly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 or earlier, although conversion of specific [[artefacts>>doc:sdmx: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.
++In discussions of statistical data, there are many aspects of its dissemination which impact data quality: data discovery, ease of use, and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]]. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards provide support for all of these aspects of data dissemination. Standard data formats promote ease of use, and provide links to relevant metadata. The (% style="color:#e74c3c" %)concept(%%) of registry services means that data and metadata can more easily be discovered. [[Timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] is improved throughout the data lifecycle by increases in efficiency, promoted through the availability of metadata and ease of use.
--(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
--**SOAP Web Services API**
++It is important to note that [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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.
--• The SOAP web services API has been deprecated with (% style="color:#e74c3c" %)version(%%) 3.0 standardising on REST
++[[image:SDMX%203.1%20Section%201.png]]
--(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
--**XML, JSON, CSV and EDI Transmission formats**
--
--The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:sdmx: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:sdmx:Glossary.Reference metadata.WebHome]] and microdata Obsolete [[SDMX-ML>>doc:sdmx: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 The [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified The option to reference structures in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
--
--[[image:SDMX 3.1 Section 1.png]]
--
  **Figure 1: High Level Schematic of Major Artefacts in the SDMX 3.0 Information Model**
  == 3.4 The SDMX View of Statistical Exchange ==
@@ -299,10 +299,10 @@
  Many XML tools and technologies have expectations about the functions performed by an XML schema, one of which is a very direct relationship between the XML constructs described in the XML schema and the tagged data in the XML instance. Strong data typing is also considered normal, supporting full validation of the tagged data. These message types are designed to support validation and other expected XML schema functions.
--1. //Generic Metadata~:// For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets. ‘Generic’ means the XML elements and XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are the same regardless of the metadata set.
--1. //Registry~:// All of the possible interactions with the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services are supported using [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] interfaces and REST API calls. Submission of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] content, data registrations and [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] is performed by a synchronous exchange of documents – a “request” message answered by a “response” message.
++1. //**Generic Metadata**~:// For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets. ‘Generic’ means the XML elements and XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are the same regardless of the metadata set.
++1. //**Registry**~:// All of the possible interactions with the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services are supported using [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] interfaces and REST API calls. Submission of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] content, data registrations and [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] is performed by a synchronous exchange of documents – a “request” message answered by a “response” message.
--== 5.2 SDMX-JSON ==
++== 5.2 SDMX-JSON ==
  [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] is the JSON transmission format specification for exchanging [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. It provides an alternative to [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and is most suited to applications like web data dissemination.
@@ -312,8 +312,8 @@
  There are three distinct message types:
--1. //Structure~:// For the exchange [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages follow the same principles as for [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] in that a single message can transmit any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. While the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages are structured differently, it is possible to freely convert between them.
--1. //Data: //For the exchange of data. Unlike [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], the structure of a [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] data message is not specific to the DSDs of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] so schema validation will not check for compliance of the data with the DSDs.
++1. //**Structure**~:// For the exchange [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages follow the same principles as for [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] in that a single message can transmit any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. While the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages are structured differently, it is possible to freely convert between them.
++1. //**Data**: //For the exchange of data. Unlike [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], the structure of a [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] data message is not specific to the DSDs of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] so schema validation will not check for compliance of the data with the DSDs.
 . //Metadata//: For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets.
  == 5.3 SDMX-CSV ==
@@ -358,10 +358,8 @@
  The Metadata Common Vocabulary is an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] guideline which provides definition of terms to be used for the comparison and mapping of terminology found in [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and in other aspects of statistical metadata management. Essentially, it provides ISOcompliant definitions for a wide range of statistical terms, which may be used directly, or against which other terminology systems may be (% style="color:#e74c3c" %)mapped(%%). This set of terms is inclusive of the terminology used within the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Technical Standards.
--The MCV provides definitions for terms on which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Metadata
++The MCV provides definitions for terms on which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Metadata (% style="color:#e74c3c" %)Concepts(%%) work is built.
--(% style="color:#e74c3c" %)Concepts(%%) work is built.
--
  == 6.3 Statistical Subject-Matter Domains ==
  The [[Statistical Subject-Matter Domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] is a listing of the breadth of statistical information for the purposes of organizing widespread statistical exchange and categorization. It acts as a standard scheme against which the categorization schemes of various counterparties can be (% style="color:#e74c3c" %)mapped(%%), to facilitate interoperable data and metadata exchange. It serves another useful purpose, however, which is to allow an organization of corresponding “domain groups”, each of which could define standard [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], (% style="color:#e74c3c" %)concepts(%%), etc. within their domains. Such groups already exist within the international community. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] would use the [[Statistical Subject-Matter Domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] list to facilitate the efforts of these groups to develop the kinds of content standards which could support the interoperation of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant technical systems within and across [[statistical domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]]. The organisation of the content of such schemes is supported in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] as a [[Category>>doc:sdmx:Glossary.Category.WebHome]] Scheme.

SDMX%203.1%20Section%201.png

Author

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

Size

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

Content