Changes for page SDMX 3.1 Standards. Section 1. Framework

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

From 4.5 to 4.4 From 10.1 to 9.1

From version 9.1

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

Change comment: There is no comment for this version

To version 4.5

edited by Helena
on 2025/06/06 16:55

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 0 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

@@ -14,7 +14,7 @@
  The SDMX Technical Specifications are organised into several discrete sections.
--The following are published on the SDMX website ([[__https:~~/~~/www.sdmx.org__>>https://https:www.sdmx.org]]):
++The following are published on the SDMX website ([[__https:~~/~~/www.sdmx.org__>>url:https://www.sdmx.org/]][[)>>url:https://www.sdmx.org/]]:
  **Section 1** **Framework for SDMX Technical Standards** – this document providing an introduction to the technical standards.
@@ -84,8 +84,7 @@
  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
--(% class="wikigeneratedid" id="HInformationModel" %)
--**Information Model**
++==== Information Model ====
  * Simplification and improvement of the reference metadata model
  * Support for microdata
@@ -95,13 +95,11 @@
  * Improvements to code hierarchies for data discovery
  * Improvements to constraints
--(% class="wikigeneratedid" id="HVersioningofStructuralMetadataArtefacts" %)
--**Versioning of Structural Metadata Artefacts**
++==== Versioning of Structural Metadata Artefacts ====
  • Adoption of the three-number semantic versioning standard for structural metadata artefacts ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
--(% class="wikigeneratedid" id="HRESTWebServicesApplicationProgrammingInterface28API29" %)
--**REST Web Services Application Programming Interface (API)**
++==== REST Web Services Application Programming Interface (API) ====
  * Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five
  * Improvements to data queries
@@ -108,13 +108,11 @@
  * Improvements to reference metadata queries
  * Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs
--(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
--**SOAP Web Services API**
++==== SOAP Web Services API ====
  • The SOAP web services API has been deprecated with version 3.0 standardising on REST
--(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
--**XML, JSON, CSV and EDI Transmission formats**
++==== XML, JSON, CSV and EDI Transmission formats ====
  * The SDMX-ML, SDMX-JSON and SDMX-CSV specifications have been extended and modified where needed to support the new features and changes such as reference metadata and microdata
  * Obsolete SDMX-ML 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
@@ -141,10 +141,10 @@
  (% class="wikigeneratedid" id="HInformationModel-1" %)
  **Information Model**
--* Addition of Dimension Constraint property to a Dataflow
--* Addition of evolving structure property to a Data Structure Definition
--* Remove version property on Categorisation
--* Simplification of Constraints o Removal of Advanced Release Calendar
++* Addition of Dimension Constraint property to a Dataflow// &nbsp;//
++* Addition of evolving structure property to a Data Structure Definition// &nbsp;//
++* Remove version property on Categorisation// &nbsp;//
++* Simplification of Constraints o Removal of Advanced Release Calendar// &nbsp;//
  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
@@ -206,10 +206,11 @@
  The formal objects in the information model are presented schematically in Figure 1, and are discussed in more detail elsewhere in this document.
++[[image:SDMX_3-1-0_SECTION_1_FINAL_6728d8d4.png||height="829" width="606"]]
  **Figure 1: High Level Schematic of Major Artefacts in the SDMX 3.0 Information Model**
--== 3.4 The SDMX View of Statistical Exchange ==
++== {{id name="_Toc56640"/}}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.
@@ -239,7 +239,7 @@
  * //**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.
++* //**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.
  * //**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
  * //**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
@@ -262,7 +262,7 @@
  • //**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 597 any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a VTL ‘program’.
--== 3.5 SDMX Registry Services ==
++== {{id name="_Toc56641"/}}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.
@@ -277,7 +277,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.
--== 3.6 RESTful Web services ==
++== {{id name="_Toc56642"/}}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.
@@ -292,7 +292,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
--= 4 The SDMX Information Model =
++= {{id name="_Toc56643"/}}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.
@@ -308,9 +308,9 @@
  A full UML conceptual design of the information model is set out in Section 2 of the Technical Specifications.
--= 5 The SDMX Transmission Formats =
++= {{id name="_Toc56644"/}}5 The SDMX Transmission Formats =
--== 5.1 SDMX-ML ==
++== {{id name="_Toc56645"/}}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.
@@ -338,7 +338,7 @@
 . //Data: //For the exchange of data. Unlike SDMX-ML, the structure of a SDMX-JSON data message is not specific to the DSDs of the data sets so schema validation will not check for compliance of the data with the DSDs.
 . //Metadata//: For the exchange of reference metadata sets.
--== 5.3 SDMX-CSV ==
++== {{id name="_Toc56647"/}}5.3 SDMX-CSV ==
  SDMX-CSV is the CSV transmission format specification for exchanging data and reference metadata only.
@@ -349,7 +349,7 @@
 . //Data//: For the exchange of data. Like SDMX-JSON, SDMX-CSV can include both code IDs and labels which is helpful when using the data to create human readable charts and dashboards.
 . //Metadata//: For the exchange of reference metadata sets.
--== 5.4 Formats and Messages Deprecated in Version 3.0 ==
++== {{id name="_Toc56648"/}}5.4 Formats and Messages Deprecated in Version 3.0 ==
  The following formats and messages have been deprecated in version 3.0 to simplify, modernise and rationalise the standard.
@@ -366,17 +366,17 @@
  * SDMX-ML Query messages
  * SDMX-ML Submit Structure Request messages
--= 6 Dependencies on SDMX content-oriented guidelines =
++= {{id name="_Toc56649"/}}6 Dependencies on SDMX content-oriented guidelines =
  The technical standards proposed here are designed so that they can be used in conjunction with other SDMX guidelines which are more closely tied to the content and semantics of statistical data exchange. The SDMX Information Model works equally well with any statistical concept, but to encourage interoperability, it is also necessary to standardize and harmonize the use of specific concepts and terminology. To achieve this goal, SDMX creates and maintains guidelines for cross-domain concepts, terminology, and structural definitions. There are three major parts to this effort.
--== 6.1 Cross-Domain Concepts ==
++== {{id name="_Toc56650"/}}6.1 Cross-Domain Concepts ==
  The SDMX Cross-Domain Concepts is a content guideline concerning concepts which are used across statistical domains. This list is expected to grow and to be subject to revision as SDMX is used in a growing number of domains. The use of the SDMX Cross-Domain Concepts, where appropriate, provides a framework to further promote interoperability among organisations using the technical standards presented here. The harmonization of statistical concepts includes not only the definitions of the concepts, and their names, but also, where appropriate, their representation with standard code lists, and the role they play within data structure definitions and metadata structure definitions.
  The intent of this guideline is two-fold: to provide a core set of concepts which can be used to structure statistical data and metadata, to promote interoperability between systems (“structural metadata”, as described above); and to promote the exchange of metadata more widely, with a set of harmonized concept names and definitions for other types of metadata (“reference metadata”, as defined above.)
--== 6.2 Metadata Common Vocabulary ==
++== {{id name="_Toc56651"/}}6.2 Metadata Common Vocabulary ==
  The Metadata Common Vocabulary is an SDMX guideline which provides definition of terms to be used for the comparison and mapping of terminology found in data structure definitions 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 mapped. This set of terms is inclusive of the terminology used within the SDMX Technical Standards.
@@ -384,17 +384,17 @@
  Concepts work is built.
--== 6.3 Statistical Subject-Matter Domains ==
++== {{id name="_Toc56652"/}}6.3 Statistical Subject-Matter Domains ==
  The Statistical Subject-Matter Domains 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 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, concepts, etc. within their domains. Such groups already exist within the international community. SDMX would use the Statistical Subject-Matter Domains list to facilitate the efforts of these groups to develop the kinds of content standards which could support the interoperation of SDMX-conformant technical systems within and across statistical domains. The organisation of the content of such schemes is supported in SDMX as a Category Scheme.
  SDMX Statistical Subject-Matter Domains will be listed and maintained by the SDMX Initiative and will be subject to adjustment.
--== 6.4 SDMX Concept Roles ==
++== {{id name="_Toc56653"/}}6.4 SDMX Concept Roles ==
  These guidelines define the standard set of SDMX Concept Roles and their use. This set of standard SDMX Concepts are implemented as a cross-domain Concept Scheme that defines the set of concept roles and gives examples on concept role implementation in SDMX 2.0, 2.1 and 3.0. A concept role gives a particular context to a concept for easy and systematic interpretation by machine processing and visualization tools. For example, the concepts REPORTING_AREA and COUNTERPART_AREA are different concepts but they are both geographical characteristics, therefore they can be associated with the same concept role ID: "GEO". This allows visualization systems to interpret these concepts as geographical data in order to generate maps. The implementation of concept roles is different in versions 2.0 and 2.1/3.0 of the SDMX technical standard. Specifically for SDMX 3.0, this set of roles is considered a normative list that must be interpreted in the same way by all organisations. Additional roles may be provided via the standard roles’ mechanism in SDMX 3.0, i.e., via Concept Schemes; the semantics of these roles have to be agreed bilateraly in data exchanges. The Concept Roles are available as an SDMX Concept Scheme on the SDMX Global Registry.
--= 7 Validation and Transformation Language =
++= {{id name="_Toc56654"/}}7 Validation and Transformation Language =
  For many years the SDMX initiative has been fostering and supporting the development of a standard calculation language, called Validation and Transformation Language (VTL). A blueprint for defining calculations was already described in the original SDMX 2.1 specifications (package 13 of the Information Model - “Transformations and Expressions”). It was just a basic framework that required further developments to became operational in order to achieve a calculation language able to manipulate SDMX artefacts.

SUZ.Methodology.Code.MethodologyClass[0]