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

Summary

Details

Page properties
Content
... ... @@ -25,25 +25,21 @@
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 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-rest2013RESTAPI" %)
31 -**sdmx-twg/sdmx-rest – REST API**
30 +=== sdmx-twg/sdmx-rest – REST API ===
32 32  
33 33  Technical specifications for the SDMX RESTful web services application programming interfaces (API).
34 34  
35 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-ml2013SDMX-ML" %)
36 -**sdmx-twg/sdmx-ml – SDMX-ML**
34 +=== sdmx-twg/sdmx-ml – SDMX-ML ===
37 37  
38 38  Technical specifications for the XML transmission format including XSD schemas, documentation and samples for data, structure and reference metadata messages.
39 39  
40 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-json2013SDMX-JSON" %)
41 -**sdmx-twg/sdmx-json – SDMX-JSON**
38 +=== sdmx-twg/sdmx-json – SDMX-JSON ===
42 42  
43 43  Technical specifications for the JSON transmission format including documentation, schemas and samples for data, structure and reference metadata messages.
44 44  
45 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-csv2013SDMX-CSV" %)
46 -**sdmx-twg/sdmx-csv – SDMX-CSV**
42 +=== sdmx-twg/sdmx-csv – SDMX-CSV ===
47 47  
48 48  Technical specifications for the SDMX-CSV transmission format for ‘comma-separated values’ (CSV) data and reference metadata.
49 49  
... ... @@ -89,7 +89,7 @@
89 89  
90 90  SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
91 91  
92 -=== Information Model ===
88 +===== Information Model =====
93 93  
94 94  * Simplification and improvement of the reference metadata model
95 95  * Support for microdata
... ... @@ -99,11 +99,11 @@
99 99  * Improvements to code hierarchies for data discovery
100 100  * Improvements to constraints
101 101  
102 -=== Versioning of Structural Metadata Artefacts ===
98 +===== Versioning of Structural Metadata Artefacts =====
103 103  
104 104  * Adoption of the three-number semantic versioning standard for structural metadata artefacts (__[[https:~~/~~/semver.org>>url:https://semver.org/]])__
105 105  
106 -=== REST Web Services Application Programming Interface (API) ===
102 +===== REST Web Services Application Programming Interface (API) =====
107 107  
108 108  * Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five
109 109  * Improvements to data queries
... ... @@ -110,11 +110,11 @@
110 110  * Improvements to reference metadata queries
111 111  * Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs
112 112  
113 -=== SOAP Web Services API ===
109 +===== SOAP Web Services API =====
114 114  
115 115  * The SOAP web services API has been deprecated with version 3.0 standardising on REST
116 116  
117 -=== XML, JSON, CSV and EDI Transmission formats ===
113 +===== XML, JSON, CSV and EDI Transmission formats =====
118 118  
119 119  * 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
120 120  * 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
... ... @@ -226,7 +226,7 @@
226 226  * //**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.
227 227  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
228 228  * //**Data Provider: **//An organization which produces data is termed a data provider.
229 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.
225 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
230 230  * //**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.
231 231  * //**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.
232 232  * //**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.
SUZ.Methodology.Code.MethodologyClass[0]