Skip to Content
Last modified by Artur on 2025/09/30 12:30
From version 4.1
edited by Helena
on 2025/06/06 16:53
Change comment: There is no comment for this version
To version 2.1
edited by Helena
on 2025/06/06 16:50
Change comment: Created by office importer.

Summary

Details

Page properties
Content
... ... @@ -1,7 +5,3 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
4 -
5 5  **Revision History**
6 6  
7 7  |**Revision**|**Date**|**Contents**
... ... @@ -24,20 +24,20 @@
24 24  
25 25  **Section 6** **SDMX Technical Notes** – detailed technical guidance for implementors of the SDMX standard.
26 26  
27 -The following are published on the GitHub repository of the SDMX Standards Technical Working Group ([[__https:~~/~~/github.com/sdmx-twg__>>https://https:github.comsdmx-twg]]): sdmx-twg/sdmx-rest – REST API
23 +The following are published on the GitHub repository of the SDMX Standards Technical Working Group (__[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg]][[->>url:https://github.com/sdmx-twg]][[twg>>url:https://github.com/sdmx-twg]]__[[)>>url:https://github.com/sdmx-twg]]: sdmx-twg/sdmx-rest – REST API
28 28  
29 29  Technical specifications for the SDMX RESTful web services application programming interfaces (API).
30 30  
31 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-ml2013SDMX-ML" %)
32 -**sdmx-twg/sdmx-ml – SDMX-ML**
27 +=== sdmx-twg/sdmx-ml – SDMX-ML ===
28 +
33 33  Technical specifications for the XML transmission format including XSD schemas, documentation and samples for data, structure and reference metadata messages.
34 34  
35 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-json2013SDMX-JSON" %)
36 -**sdmx-twg/sdmx-json – SDMX-JSON**
31 +=== sdmx-twg/sdmx-json – SDMX-JSON ===
32 +
37 37  Technical specifications for the JSON transmission format including documentation, schemas and samples for data, structure and reference metadata messages.
38 38  
39 -(% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-csv2013SDMX-CSV" %)
40 -**sdmx-twg/sdmx-csv – SDMX-CSV**
35 +=== sdmx-twg/sdmx-csv – SDMX-CSV ===
36 +
41 41  Technical specifications for the SDMX-CSV transmission format for ‘comma-separated values’ (CSV) data and reference metadata.
42 42  
43 43  The following sections are obsolete:
... ... @@ -70,13 +70,13 @@
70 70  
71 71  * **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using SDMX, and these 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.
72 72  * **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.** **
73 -* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.**  **
74 -* **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.**  **
69 +* **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.**  **
70 +* **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.**  **
75 75  * **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 objectoriented features of W3C XML Schema to allow for easier processing of SDMX data and metadata.** **
76 -* **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.**  **
72 +* **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.**  **
77 77  * **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.** **
78 78  * **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.** **
79 -* **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.**  **
75 +* **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.**  **
80 80  * **Simplification and better support for the metadata structure: **New use cases have been reported and these are now supported by a re-modelled metadata structure definition.** **
81 81  * **Support for partial item schemes such as a code list: **The concept of a partial (subset) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
82 82  
... ... @@ -135,10 +135,10 @@
135 135  
136 136  ==== Information Model ====
137 137  
138 -* Addition of Dimension Constraint property to a Dataflow//  //
139 -* Addition of evolving structure property to a Data Structure Definition//  //
140 -* Remove version property on Categorisation//  //
141 -* Simplification of Constraints o Removal of Advanced Release Calendar//  //
134 +* Addition of Dimension Constraint property to a Dataflow//  //
135 +* Addition of evolving structure property to a Data Structure Definition//  //
136 +* Remove version property on Categorisation//  //
137 +* Simplification of Constraints o Removal of Advanced Release Calendar//  //
142 142  
143 143  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
144 144  
... ... @@ -236,7 +236,7 @@
236 236  * //**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.
237 237  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
238 238  * //**Data Provider: **//An organization which produces data is termed a data provider.
239 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
235 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
240 240  * //**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.
241 241  * //**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
242 242  * //**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
SDMX_3-1-0_SECTION_1_FINAL_6728d8d4.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -403.7 KB
Content