Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.10
edited by Helena
on 2025/05/14 15:28
Change comment: There is no comment for this version
To version 10.1
edited by Helena
on 2025/05/14 15:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,21 +25,25 @@
25 25  
26 26  **Section 6** **SDMX Technical Notes** – detailed technical guidance for implementors of the SDMX standard.
27 27  
28 -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]]) :__
28 +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]]__):
29 29  
30 -=== sdmx-twg/sdmx-rest – REST API ===
30 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-rest2013RESTAPI" %)
31 +**sdmx-twg/sdmx-rest – REST API**
31 31  
32 32  Technical specifications for the SDMX RESTful web services application programming interfaces (API).
33 33  
34 -=== sdmx-twg/sdmx-ml – SDMX-ML ===
35 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-ml2013SDMX-ML" %)
36 +**sdmx-twg/sdmx-ml – SDMX-ML**
35 35  
36 36  Technical specifications for the XML transmission format including XSD schemas, documentation and samples for data, structure and reference metadata messages.
37 37  
38 -=== sdmx-twg/sdmx-json – SDMX-JSON ===
40 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-json2013SDMX-JSON" %)
41 +**sdmx-twg/sdmx-json – SDMX-JSON**
39 39  
40 40  Technical specifications for the JSON transmission format including documentation, schemas and samples for data, structure and reference metadata messages.
41 41  
42 -=== sdmx-twg/sdmx-csv – SDMX-CSV ===
45 +(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-csv2013SDMX-CSV" %)
46 +**sdmx-twg/sdmx-csv – SDMX-CSV**
43 43  
44 44  Technical specifications for the SDMX-CSV transmission format for ‘comma-separated values’ (CSV) data and reference metadata.
45 45  
... ... @@ -85,7 +85,7 @@
85 85  
86 86  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
87 87  
88 -===== Information Model =====
92 +=== Information Model ===
89 89  
90 90  * Simplification and improvement of the reference metadata model
91 91  * Support for microdata
... ... @@ -95,11 +95,11 @@
95 95  * Improvements to code hierarchies for data discovery
96 96  * Improvements to constraints
97 97  
98 -===== Versioning of Structural Metadata Artefacts =====
102 +=== Versioning of Structural Metadata Artefacts ===
99 99  
100 100  * Adoption of the three-number semantic versioning standard for structural metadata artefacts (__[[https:~~/~~/semver.org>>url:https://semver.org/]])__
101 101  
102 -===== REST Web Services Application Programming Interface (API) =====
106 +=== REST Web Services Application Programming Interface (API) ===
103 103  
104 104  * Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five
105 105  * Improvements to data queries
... ... @@ -106,11 +106,11 @@
106 106  * Improvements to reference metadata queries
107 107  * Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs
108 108  
109 -===== SOAP Web Services API =====
113 +=== SOAP Web Services API ===
110 110  
111 111  * The SOAP web services API has been deprecated with version 3.0 standardising on REST
112 112  
113 -===== XML, JSON, CSV and EDI Transmission formats =====
117 +=== XML, JSON, CSV and EDI Transmission formats ===
114 114  
115 115  * 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
116 116  * 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
... ... @@ -222,7 +222,7 @@
222 222  * //**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.
223 223  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
224 224  * //**Data Provider: **//An organization which produces data is termed a data provider.
225 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
229 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.
226 226  * //**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.
227 227  * //**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.
228 228  * //**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.
... ... @@ -267,10 +267,8 @@
267 267  
268 268  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.
269 269  
270 -SDMX recognizes that statistical data is structured; in SDMX this structure is termed a Data Structure Definition. “Data sets” are made up of one or more lower-level “groups”, based on their degrees of similarity. Each group is in turn comprised of one or more “series” of data. Each series or section has a “key” - values for each of a cluster of concepts, also called
274 +SDMX recognizes that statistical data is structured; in SDMX this structure is termed a Data Structure Definition. “Data sets” are made up of one or more lower-level “groups”, based on their degrees of similarity. Each group is in turn comprised of one or more “series” of data. Each series or section has a “key” - values for each of a cluster of concepts, also called "dimensions" - which identifies it, and one or more “observations”, which typically combine the time of the observation, and the value of the observation (e.g., measurement). Additionally, metadata may be attached at any level of this structure as descriptive “attributes”. Code lists (enumerations) and other patterns for representation of data and metadata are also modelled.
271 271  
272 -"dimensions" - which identifies it, and one or more “observations”, which typically combine the time of the observation, and the value of the observation (e.g., measurement). Additionally, metadata may be attached at any level of this structure as descriptive “attributes”. Code lists (enumerations) and other patterns for representation of data and metadata are also modelled.
273 -
274 274  There is some similarity between “cube” structures commonly used to process statistical data, and the Data Structure Definition idea in the SDMX Information Model. It is important to note that the data as structured according to the SDMX Information Model is optimized for exchange, potentially with partners who may have no ability to process a “cube” of data coming from complex statistical systems. SDMX time series can be understood as “slices” of the cube. Such a slice is identified by its key. A "series" key consists of the values for all dimensions specified by the key family except time. Thus, it is possible to reconstruct and describe data cubes from SDMX-structured data, and to exchange such databases using the interfaces and formats provided for that purpose in the standard. Additional objects such as hierarchical code lists, constraints and structure maps make it possible to more fully model the structure of cubes.
275 275  
276 276  The information model also provides a view of reference metadata: a mechanism for referencing the meaningful “objects” within the SDMX view of statistical exchange processes (data providers, structures, provisioning agreements, dataflows, metadata flows, etc.) to which metadata is attached; a mechanism for describing a set of meaningful concepts, of organizing them into a presentational structure, and of indicating how their values are represented. This is based on a simple, hierarchical view of reference metadata which is common to many metadata systems and classification/categorization schemes. SDMX provides a model (and XML and JSON formats) for both describing reference metadata structures, and of reporting reference metadata according to those structures.
SUZ.Methodology.Code.MethodologyClass[0]