Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 3.8
edited by Helena
on 2025/05/19 15:18
Change comment: There is no comment for this version
To version 3.5
edited by Helena
on 2025/05/19 15:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,7 +24,7 @@
24 24  1. SDMX-ML - the XML format for the exchange of SDMX-structured data and metadata. This document has normative sections describing the use of the XML syntax in SDMX messages, and is accompanied by a set of normative XML schemas and non-normative sample XML document instances.
25 25  1. The SDMX Registry Specification provides for a central registry of information about available data and reference metadata, and for a repository containing structural metadata and provisioning information. This specification defines the basic services offered by the SDMX Registry: registration of data and metadata; querying for data and metadata; and subscription/notification regarding updates to the registry. This document has normative sections.
26 26  1. The SDMX Technical Notes – this is a guide to help those who wish to use the SDMX specifications. It includes notes on the expressive differences of the various messages and syntaxes; versioning; maintenance agencies; the SDMX Registry. This document is not normative.
27 -1. Web Services Guidelines – this is a guide for those who wish to implement SDMX using web-services technologies. It places an emphasis on those aspects of web-services technologies (including, but not requiring, an SDMXconformant registry) which will work regardless of the development environment or platform used to create the web services. This document contains normative sections.{{footnote}}SOAP and REST specifications are not maintained any more in this section, see the SDMX website.{{/footnote}}
27 +1. Web Services Guidelines – this is a guide for those who wish to implement SDMX using web-services technologies. It places an emphasis on those aspects of web-services technologies (including, but not requiring, an SDMXconformant registry) which will work regardless of the development environment or platform used to create the web services. This document contains normative sections.^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^
28 28  
29 29  In July 2020 it was released an important improvement of the SDMX 2.1 specifications for the SDMX implementation of the Validation and Transformation Language (VTL). This implied a revision of some of the SDMX 2.1 sections. The relevant changes are not described in the next section but in the section 10 below.
30 30  
... ... @@ -42,22 +42,38 @@
42 42  
43 43  * **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.
44 44  * **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.
45 -* **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 98 lists are supported; relationships between data structures can be expressed, 99 providing support for extensibility of data structures; and the description of functional dependencies within cubes are supported.
45 +* **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 98 lists are supported; relationships between data structures can be expressed, 99 providing support for extensibility of data structures; and the description of 100 functional dependencies within cubes are supported.
46 46  
47 47  The major changes from 2.0 to 2.1 can be briefly summarized:
48 48  
49 -* **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using SDMX, and these 106 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.
50 -* **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.
51 -* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
52 -* **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.
53 -* **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.
54 -* **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.
55 -* **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
56 -* **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.
57 -* **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.
58 -* **Simplification and better support for the metadata structure: **New use 140 cases have been reported and these are now supported by a re-modelled metadata structure definition.
59 -* **Support for partial item schemes such as a code list: **The concept of a 143 partial (sub-set) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
49 +**Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using SDMX, and these 106 implementations have resulted in several changes to the specifications.
60 60  
51 +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.
52 +
53 +**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.** **
54 +
55 +**Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
56 +
57 +**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.** **
58 +
59 +**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.** **
60 +
61 +**Consistency between the SDMX-ML and the SDMX Information Model:**
62 +
63 +Certain aspects of the XML schemas and UML model have been more closely aligned, to allow for easier comprehension of the SDMX model.
64 +
65 +**Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
66 +
67 +**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.** **
68 +
69 +**Simplification of the data structure definition - specific message types:**
70 +
71 +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.
72 +
73 +**Simplification and better support for the metadata structure: **New use 140 cases have been reported and these are now supported by a re-modelled metadata structure definition.
74 +
75 +**Support for partial item schemes such as a code list: **The concept of a 143 partial (sub-set) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
76 +
61 61  = {{id name="_Toc38910"/}}3. Processes and Business Scope =
62 62  
63 63  == {{id name="_Toc38911"/}}3.1 Process Patterns ==
... ... @@ -302,6 +302,4 @@
302 302  
303 303  Finally, new REST interfaces for VTL have been added. These are not maintained any more in the section 7; the link to these specifications can be found on the SDMX website.
304 304  
305 -----
306 -
307 -{{putFootnotes/}}
321 +[[1>>path:#sdfootnote1anc||name="sdfootnote1sym"]] SOAP and REST specifications are not maintained any more in this section, see the SDMX website.