Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -25,7 +25,7 @@ 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 ( ) :__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 30 (% class="wikigeneratedid" id="Hsdmx-twg2Fsdmx-rest2013RESTAPI" %) 31 31 **sdmx-twg/sdmx-rest – REST API** ... ... @@ -89,7 +89,8 @@ 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 === 92 +(% class="wikigeneratedid" id="HInformationModel" %) 93 +**Information Model** 93 93 94 94 * Simplification and improvement of the reference metadata model 95 95 * Support for microdata ... ... @@ -99,11 +99,13 @@ 99 99 * Improvements to code hierarchies for data discovery 100 100 * Improvements to constraints 101 101 102 -=== Versioning of Structural Metadata Artefacts === 103 +(% class="wikigeneratedid" id="HVersioningofStructuralMetadataArtefacts" %) 104 +**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) === 108 +(% class="wikigeneratedid" id="HRESTWebServicesApplicationProgrammingInterface28API29" %) 109 +**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,13 @@ 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 === 116 +(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %) 117 +**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 === 121 +(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %) 122 +**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 ... ... @@ -271,10 +271,8 @@ 271 271 272 272 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. 273 273 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 279 +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. 275 275 276 -"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. 277 - 278 278 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. 279 279 280 280 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]
-