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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SDMX STANDARDS: SECTION 1
1 +1 Introduction
Content
... ... @@ -1,13 +5,8 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
4 -
5 5  **Revision History**
6 6  
7 -(% style="width:769.039px" %)
8 -|(% style="width:144px" %)**Revision**|(% style="width:195px" %)**Date**|(% style="width:426px" %)**Contents**
9 -|(% style="width:144px" %)DRAFT 1.0|(% style="width:195px" %)May 2021|(% style="width:426px" %)Draft release updated for SDMX 3.0 for public consultation
10 -|(% style="width:144px" %)1.0|(% style="width:195px" %)October 2021|(% style="width:426px" %)Public release for SDMX 3.0
3 +|**Revision**|**Date**|**Contents**
4 +|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
5 +|1.0|October 2021|Public release for SDMX 3.0
11 11  
12 12  = {{id name="_Toc56226"/}}1 Introduction =
13 13  
... ... @@ -15,7 +15,7 @@
15 15  
16 16  The SDMX Technical Specifications are organised into several discrete sections.
17 17  
18 -The following are published on the SDMX website ([[__https:~~/~~/www.sdmx.org__>>https://https:www.sdmx.org]]).
13 +The following are published on the SDMX website ( __[[https:~~/~~/www.sdmx.org>>url:https://www.sdmx.org/]]__ [[)>>url:https://www.sdmx.org/]]:
19 19  
20 20  **Section 1** **Framework for SDMX Technical Standards** – this document providing an introduction to the technical standards.
21 21  
... ... @@ -233,7 +233,7 @@
233 233  * //**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.
234 234  * //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
235 235  * //**Data Provider: **//An organization which produces data is termed a data provider.
236 -* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
231 +* //**Metadata Provider: **//An organization which produces reference metadata is termed a metadata provider.//  //
237 237  * //**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.
238 238  * //**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.
239 239  * //**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.