Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Helena
on 2025/05/14 13:26
Change comment: There is no comment for this version
To version 19.5
edited by Helena
on 2025/05/16 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -1 Overview
1 +SDMX STANDARDS
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.WebHome
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Code|Code list|Hierarchy|Reference metadata|SDMX-EDI|SDMX-JSON|SDMX-ML|Statistical data and metadata exchange|Structural metadata
Content
... ... @@ -1,68 +1,74 @@
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
4 +
1 1  **Revision History**
2 2  
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
7 +(% style="width:738.039px" %)
8 +|(% style="width:187px" %)Revision|(% style="width:157px" %)Date|(% style="width:390px" %)Contents
9 +|(% style="width:187px" %)DRAFT 1.0|(% style="width:157px" %)May 2021|(% style="width:390px" %)Draft release updated for SDMX 3.0 for public consultation
10 +|(% style="width:187px" %)1.0|(% style="width:157px" %)October 2021|(% style="width:390px" %)Public Release for SDMX 3.0
6 6  
7 7  = 1 Overview =
8 8  
9 -SDMX version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
14 +[[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)version(%%) 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
10 10  
11 11  **Information Model**
12 12  
13 -* Simplification and improvement of the reference metadata model
18 +* Simplification and improvement of the [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] model
14 14  * Support for microdata
15 15  * Support for geospatial data
16 -* Support for code list extension and discriminated union of code lists
21 +* Support for [[code list>>doc:xwiki:Glossary.Code list.WebHome]] extension and discriminated union of [[code>>doc:xwiki:Glossary.Code.WebHome]] lists
17 17  * Improvements to structure mapping
18 -* Improvements to code hierarchies for data discovery
23 +* Improvements to [[code>>doc:xwiki:Glossary.Code.WebHome]] [[hierarchies>>doc:xwiki:Glossary.Hierarchy.WebHome]] for data discovery
19 19  * Improvements to constraints
20 20  
21 21  **Versioning of Structural Metadata Artefacts**
22 22  
23 -• Adoption of the three-number semantic versioning standard for structural metadata artefacts [[(>>url:https://semver.org/]][[__https:~~/~~/semver.org__>>url:https://semver.org/]][[)>>url:https://semver.org/]]
28 +* Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] ([[https:~~/~~/semver.org/>>https://semver.org/||rel="noopener noreferrer" target="_blank"]])
24 24  
25 25  **REST Web Services Application Programming Interface (API)**
26 26  
27 27  * Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five
28 28  * Improvements to data queries
29 -* Improvements to reference metadata queries
30 -* Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs
34 +* Improvements to [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] queries
35 +* Support for [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]] maintenance using HTTP PUT, POST and DELETE verbs
31 31  
32 32  **SOAP Web Services API**
33 33  
34 -• The SOAP web services API has been deprecated with version 3.0 standardising on REST** **
39 +* The SOAP web services API has been deprecated with (% style="color:#2ecc71" %)version(%%) 3.0 standardising on REST**;**
35 35  
36 36  **XML, JSON, CSV and EDI Transmission formats**
37 37  
38 -* 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
39 -* 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
40 -* The SDMX-EDI transmission format for structures and data has been deprecated
41 -* The organisation of structures into ‘collections’ in SDMX-ML and SDMX-JSON structure messages has been flattened and simplified
42 -* The option to reference structures in SDMX-ML and SDMX-JSON messages using Agency, ID and Version has been deprecated with URN now exclusively used for all non-local referencing purpose
43 +* The [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-CSV specifications have been extended and modified where needed to support the new features and changes such as [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] and microdata
44 +* Obsolete [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 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
45 +* The [[SDMX-EDI>>doc:xwiki:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated
46 +* The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified
47 +* The option to reference structures in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#2ecc71" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
43 43  
44 44  **Breaking Changes**
45 45  
46 -Many of the changes made are ‘breaking’ meaning that, while conversion between versions may be possible in certain circumstances, the 3.0 specification is not directly backwardly compatible with earlier versions of the Standard.
51 +Many of the changes made are ‘breaking’ meaning that, while conversion between (% style="color:#2ecc71" %)versions(%%) may be possible in certain circumstances, the 3.0 specification is not directly backwardly compatible with earlier (% style="color:#2ecc71" %)versions(%%) of the Standard.
47 47  
48 48  A summary of the main breaking changes is given in chapter 2.
49 49  
50 50  **Content of the Document**
51 51  
52 -The remainder of the document provides a summary of the main changes. More detailed information can be found the SDMX 3.0 Technical Specifications, in particular:
57 +The remainder of the document provides a summary of the main changes. More detailed information can be found the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Technical Specifications, in particular:
53 53  
54 54  * Section 2 – Information Model
55 55  * Section 5 – Registry Specification
56 56  * Section 6 – Technical Notes
57 -* SDMX-TWG GitHub for the REST API and the XML, JSON and CSV formats
62 +* [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-TWG GitHub for the REST API and the XML, JSON and CSV formats
58 58  
59 59  = 2 Summary of Breaking Changes in 3.0 =
60 60  
61 -Version 3.0 introduces breaking changes into the web services API, transmission formats and information model. A summary is given in the table below.
66 +(% style="color:#2ecc71" %)Version(%%) 3.0 introduces breaking changes into the web services API, transmission formats and information model. A summary is given in the table below.
62 62  
63 -== //2.1 Web Services API// ==
68 +== 2.1 Web Services API ==
64 64  
65 -|**REST API**|(((
70 +(% style="width:948.039px" %)
71 +|**REST API**|(% style="width:818px" %)(((
66 66  The REST API is not backwardly compatible due to modifications to the URLs and query parameters resulting in breaking changes in four of the five main resources:
67 67  
68 68  * Structure queries
... ... @@ -74,139 +74,125 @@
74 74  
75 75  //Guidance for implementors//
76 76  
77 -REST API implementors may provide partial backward compatibility by using web server URL rewriting rules to translate version 2.1 structure queries to the 3.0 equivalent.
83 +REST API implementors may provide partial backward compatibility by using web server URL rewriting rules to translate (% style="color:#2ecc71" %)version(%%) 2.1 structure queries to the 3.0 equivalent.
78 78  
79 -Implementors are also recommended to version their API services providing users with an explicit choice of which version to use.
85 +Implementors are also recommended to (% style="color:#2ecc71" %)version(%%) their API services providing users with an explicit choice of which (% style="color:#2ecc71" %)version(%%) to use.
80 80  )))
81 -|**SOAP API**|The SOAP API has been deprecated.
87 +|**SOAP API**|(% style="width:818px" %)The SOAP API has been deprecated.
82 82  
83 -== //2.2 Transmission Formats// ==
89 +== 2.2 Transmission Formats ==
84 84  
85 -:
86 -
87 87  (((
88 -|**SDMX-ML**|(((
92 +(% style="width:952.039px" %)
93 +|(% style="width:130px" %)**SDMX-ML**|(% style="width:820px" %)(((
89 89  The following legacy XML data messages have been deprecated:
90 90  
91 -SDMX-ML 1.0/2.0 Generic (time-series) data message
96 +[[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Generic (time-series) data message
97 +[[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Compact (time-series) data message
98 +[[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Utility (time-series) data message
99 +[[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Cross-Sectional data message [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] 2.1 Generic data messages (for observations, time-series and cross-sectional data)
92 92  
93 -SDMX-ML 1.0/2.0 Compact (time-series) data message
101 +Structure Specific is the only data message option in (% style="color:#2ecc71" %)version(%%) 3.0 but is not backwardly compatible with (% style="color:#2ecc71" %)version(%%) 2.1 due to several changes including deprecation of the option to reference structures like the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]], [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] and [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] using their Agency, ID and (% style="color:#2ecc71" %)Version(%%). The time series variant of the message has also been deprecated.
94 94  
95 -SDMX-ML 1.0/2.0 Utility (time-series) data message
103 +The [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] structure message is not backwardly compatible primarily due to:
96 96  
97 -SDMX-ML 1.0/2.0 Cross-Sectional data message SDMX-ML 2.1 Generic data messages (for observations, time-series and cross-sectional data)
98 -
99 -Structure Specific is the only data message option in version 3.0 but is not backwardly compatible with version 2.1 due to several changes including deprecation of the option to reference structures like the DSD, Dataflow and Provision Agreement using their Agency, ID and Version. The time series variant of the message has also been deprecated.
100 -
101 -The SDMX-ML structure message is not backwardly compatible primarily due to:
102 -
103 103  * Changes to the information model
104 -* Changes to the way the structures are organised into
105 -
106 -‘collections’ within the message
107 -
108 -* Deprecation of the Agency, ID, Version option for referencing of structures in messages
106 +* Changes to the way the structures are organised into ‘collections’ within the message
107 +* Deprecation of the Agency, ID, (% style="color:#2ecc71" %)Version(%%) option for referencing of structures in messages
109 109  )))
110 -|**SDMX-JSON**|(((
111 -The JSON data message is not backwardly compatible with version 2.1 primarily due to changes needed to support the improved REST API data queries, in particular the ability to retrieve in one operation data from multiple datasets with potentially different Data Structure Definitions.
109 +|(% style="width:130px" %)**SDMX-JSON**|(% style="width:820px" %)(((
110 +The JSON data message is not backwardly compatible with (% style="color:#2ecc71" %)version(%%) 2.1 primarily due to changes needed to support the improved REST API data queries, in particular the ability to retrieve in one operation data from multiple [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] with potentially different Data Structure Definitions.
112 112  
113 113  The JSON structure message is not backwardly compatible primarily due to:
114 114  
115 115  * Changes to the information model
116 -* Changes to the way the structures are organised into
117 -
118 -‘collections’ within the message
119 -
120 -* Deprecation of the Agency, ID, Version option for referencing of structures in messages
115 +* Changes to the way the structures are organised into ‘collections’ within the message
116 +* Deprecation of the Agency, ID, (% style="color:#2ecc71" %)Version(%%) option for referencing of structures in messages
121 121  )))
122 -|**SDMX-EDI**|The EDI format for both structures and data has been deprecated.
123 -|**SDMX-CSV**|The CSV data and reference metadata messages are not backwardly compatible with those under version 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries.**     **
118 +|(% style="width:130px" %)**SDMX-EDI**|(% style="width:820px" %)The EDI format for both structures and data has been deprecated.
119 +|(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)The CSV data and [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#2ecc71" %)version(%%) 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries.
124 124  )))
125 125  
126 -== //2.3 Information Model// ==
122 +== 2.3 Information Model ==
127 127  
128 -:
129 -
130 130  (((
131 -|**Data Structure Definition**|(((
132 -The version 3.0 Data Structure Definition (DSD) model is not directly backwardly compatible with 2.1 primarily due to the deprecation of the special MeasureDimension.
125 +(% style="width:955.039px" %)
126 +|(% style="width:132px" %)**Data Structure Definition**|(% style="width:819px" %)(((
127 +The (% style="color:#2ecc71" %)version(%%) 3.0 [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]) model is not directly backwardly compatible with 2.1 primarily due to the deprecation of the special MeasureDimension.
133 133  
134 134  //Conversion guidance for implementors//
135 135  
136 -Version 2.1 DSDs can be converted to the 3.0 model by creating a measure with the “MEASURE” concept role applied as described in paragraph 3.5.
131 +(% style="color:#2ecc71" %)Version(%%) 2.1 DSDs can be converted to the 3.0 model by creating a [[measure>>doc:xwiki:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:xwiki:Glossary.Measure.WebHome]]” (% style="color:#2ecc71" %)concept(%%) role applied as described in paragraph 3.5.
137 137  
138 -Version 3.0 DSDs cannot be reliably converted to the 2.1 model due to the introduction of new features such as multiple measures and value arrays for measures and attributes.
133 +(% style="color:#2ecc71" %)Version(%%) 3.0 DSDs cannot be reliably converted to the 2.1 model due to the introduction of new features such as multiple [[measures>>doc:xwiki:Glossary.Measure.WebHome]] and value arrays for [[measures>>doc:xwiki:Glossary.Measure.WebHome]] and [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]].
139 139  )))
140 -|**Structure mapping model**|(((
141 -The structure mapping model has changed significantly in version 3.0 with deprecation of the Structure Set maintainable artefact and introduction of five new ones: Representation Map and four variants of item scheme map.
135 +|(% style="width:132px" %)**Structure mapping model**|(% style="width:819px" %)(((
136 +The structure mapping model has changed significantly in (% style="color:#2ecc71" %)version(%%) 3.0 with deprecation of the [[Structure Set>>doc:xwiki:Glossary.Structure set.WebHome]] [[maintainable artefact>>doc:xwiki:Glossary.Maintainable artefact.WebHome]] and introduction of five new ones: [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] (% style="color:#2ecc71" %)Map(%%) and four variants of [[item scheme>>doc:xwiki:Glossary.Item scheme.WebHome]] (% style="color:#2ecc71" %)map(%%).
142 142  
143 143  //Conversion guidance for implementors//
144 144  
145 -Version 2.1 structure sets can be practically converted to the version 3.0 structure mapping model.
140 +(% style="color:#2ecc71" %)Version(%%) 2.1 [[structure sets>>doc:xwiki:Glossary.Structure set.WebHome]] can be practically converted to the (% style="color:#2ecc71" %)version(%%) 3.0 structure mapping model.
146 146  
147 -Conversion from the version 3.0 structure mapping model to 2.1 is generally possible. However, when attempting to convert mapping rules from 2.1 to 3.0 and back to 2.1, the resulting Structure Set will not be precisely the same as the original. In converting to version 3.0, the system must generate IDs for each of the new maintainable artefacts, but details of the original Structure Set artefacts are lost.
142 +Conversion from the (% style="color:#2ecc71" %)version(%%) 3.0 structure mapping model to 2.1 is generally possible. However, when attempting to convert mapping rules from 2.1 to 3.0 and back to 2.1, the resulting [[Structure Set>>doc:xwiki:Glossary.Structure set.WebHome]] will not be precisely the same as the original. In converting to (% style="color:#2ecc71" %)version(%%) 3.0, the system must generate IDs for each of the new [[maintainable artefacts>>doc:xwiki:Glossary.Maintainable artefact.WebHome]], but details of the original [[Structure Set>>doc:xwiki:Glossary.Structure set.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] are lost.
148 148  )))
149 -|**Reference metadata model**|(((
150 -The reference metadata model has changed in version 3.0 with modifications to the role of the Data Structure Definition, Metadata Structure Definition and Metadataflow artefacts. Metadata Provision Agreement and Metadata Provider Scheme have been added. Metadatasets are now identifiable.
144 +|(% style="width:132px" %)**Reference metadata model**|(% style="width:819px" %)(((
145 +The [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] model has changed in (% style="color:#2ecc71" %)version(%%) 3.0 with modifications to the role of the [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] and [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]]. Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] and Metadata Provider Scheme have been added. Metadatasets are now identifiable.
151 151  
152 -Version 2.1 reference metadata models are not valid in version 3.0.
147 +(% style="color:#2ecc71" %)Version(%%) 2.1 [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] models are not valid in (% style="color:#2ecc71" %)version(%%) 3.0.
153 153  
154 154  //Conversion guidance for implementors//
155 155  
156 -A version 2.1 Metadata Structure Definition can be converted to the version 3.0 model under some circumstances, but target information is either lost or has to be translated into a metadataflow. Further, conversion of a Data Structure Definition for collecting reference metadata against a dataset would need to make changes to the dataset’s Data Structure Definition. As the Data Structure Definition may not actually be specified, judgement would need to be taken, perhaps determining the most likely candidate by examining which
157 -)))
158 -||(((
159 -already have metadata reported against their datasets. A 2.1 metadata report could be converted to a version 3.0 Metadataset if it is attached to a structure, but requires a Metadata Provision Agreement which would need to be created if not already in existence.
151 +A (% style="color:#2ecc71" %)version(%%) 2.1 [[Metadata Structure Definition>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] can be converted to the (% style="color:#2ecc71" %)version(%%) 3.0 model under some circumstances, but target information is either lost or has to be translated into a [[metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]]. Further, conversion of a [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] for collecting [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] against a [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] would need to make changes to the [[dataset>>doc:xwiki:Glossary.Data set.WebHome]]’s [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]]. As the [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] may not actually be specified, judgement would need to be taken, perhaps determining the most likely candidate by examining which already have metadata reported against their [[datasets>>doc:xwiki:Glossary.Data set.WebHome]]. A 2.1 metadata report could be converted to a (% style="color:#2ecc71" %)version(%%) 3.0 Metadataset if it is attached to a structure, but requires a Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] which would need to be created if not already in existence.
160 160  
161 -Conversion from the version 3.0 model to version 2.1 cannot be performed reliably. The process would need target information to be derived from analysis of the Metadataflows and Metadata Provision Agreements. Depending on the complexity it may not be possible to express that information in a version 2.1 Data Structure Definition.
153 +Conversion from the (% style="color:#2ecc71" %)version(%%) 3.0 model to (% style="color:#2ecc71" %)version(%%) 2.1 cannot be performed reliably. The process would need target information to be derived from analysis of the [[Metadataflows>>doc:xwiki:Glossary.Metadataflow.WebHome]] and Metadata [[Provision Agreements>>doc:xwiki:Glossary.Provision agreement.WebHome]]. Depending on the complexity it may not be possible to express that information in a (% style="color:#2ecc71" %)version(%%) 2.1 [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]].
162 162  )))
163 -|**Constraint model**|(((
164 -The version 2.1 Content Constraint artefact has been deprecated in version 3.0 and replaced by the Data Constraint for data, and the Metadata Constraint for reference metadata.
155 +|(% style="width:132px" %)**Constraint model**|(% style="width:819px" %)(((
156 +The (% style="color:#2ecc71" %)version(%%) 2.1 Content (% style="color:#2ecc71" %)Constraint(%%) [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] has been deprecated in (% style="color:#2ecc71" %)version(%%) 3.0 and replaced by the Data (% style="color:#2ecc71" %)Constraint(%%) for data, and the Metadata (% style="color:#2ecc71" %)Constraint(%%) for reference metadata.
165 165  
166 166  //Conversion guidance for implementors//
167 167  
168 -2.1 Content Constraints can be converted without loss to the equivalent version 3.0 Data Constraint model.
160 +2.1 Content (% style="color:#2ecc71" %)Constraints(%%) can be converted without loss to the equivalent (% style="color:#2ecc71" %)version(%%) 3.0 Data (% style="color:#2ecc71" %)Constraint(%%) model.
169 169  
170 170  Conversion from 3.0 to 2.1 presents challenges where wildcards have been used, in those cases requiring expansion of the wildcard into explicit values.
171 171  )))
172 -|**Hierarchical codelist structures**|(((
173 -The version 2.1 Hierarchical Codelist artefact has been deprecated in version 3.0 and replaced by two new artefacts, Hierarchy and Hierarchy Association.
164 +|(% style="width:132px" %)**Hierarchical codelist structures**|(% style="width:819px" %)(((
165 +The (% style="color:#2ecc71" %)version(%%) 2.1 Hierarchical Codelist [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] has been deprecated in (% style="color:#2ecc71" %)version(%%) 3.0 and replaced by two new [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]], [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] and [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] Association.
174 174  
175 175  //Conversion guidance for implementors//
176 176  
177 -Version 2.1 Hierarchical Codelists can be successfully converted to the version 3.0 hierarchy model. Information on which artefacts to link the hierarchies to on what context would need to be added as a separate procedure.
169 +(% style="color:#2ecc71" %)Version(%%) 2.1 Hierarchical Codelists can be successfully converted to the (% style="color:#2ecc71" %)version(%%) 3.0 [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] model. Information on which [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] to link the [[hierarchies>>doc:xwiki:Glossary.Hierarchy.WebHome]] to on what context would need to be added as a separate procedure.
178 178  
179 -Conversion from the version 3.0 model to version 2.1 is possible, but with loss of the linking information
171 +Conversion from the (% style="color:#2ecc71" %)version(%%) 3.0 model to (% style="color:#2ecc71" %)version(%%) 2.1 is possible, but with loss of the linking information
180 180  )))
181 181  )))
182 182  
183 183  = 3 Information Model =
184 184  
185 -== //3.1 Version 3.0 Information Model// ==
177 +== 3.1 Version 3.0 Information Model ==
186 186  
187 187  [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png||height="404" width="718"]]
188 188  
189 189  //Figure 1 Version 3.0 simplified Information Model UML class diagram with ‘heat map’ illustrating the areas with most change//
190 190  
191 -The schematic above is a simplified UML class diagram of the SDMX 3.0 information model illustrating the major areas of change as a ‘heat map’. Darker colours indicate where new structures have been added in version 3.0 or where structures have been significantly changed.
183 +The schematic above is a simplified UML class diagram of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 information model illustrating the major areas of change as a ‘heat (% style="color:#2ecc71" %)map(%%)’. Darker colours indicate where new structures have been added in (% style="color:#2ecc71" %)version(%%) 3.0 or where structures have been significantly changed.
192 192  
193 -A number of ancillary structures including organisation schemes, process and reporting taxonomy are unchanged and have not been shown. Similarly, Organisation Scheme Map and Reporting Taxonomy Map have been omitted for simplicity. A schematic of the 2.1 model is given in Appendix A for comparison purposes.
185 +A number of ancillary structures including organisation schemes, process and [[reporting taxonomy>>doc:xwiki:Glossary.Reporting taxonomy.WebHome]] are unchanged and have not been shown. Similarly, Organisation Scheme (% style="color:#2ecc71" %)Map(%%) and [[Reporting Taxonomy>>doc:xwiki:Glossary.Reporting taxonomy.WebHome]] (% style="color:#2ecc71" %)Map(%%) have been omitted for simplicity. A schematic of the 2.1 model is given in Appendix A for comparison purposes.
194 194  
195 -== //3.2 Key Changes from Version 2.1// ==
187 +== 3.2 Key Changes from Version 2.1 ==
196 196  
197 197  New Maintainable Artefacts
198 198  
199 -* Structure Map
200 -* Representation Map
201 -* Organisation Scheme Map
202 -* Concept Scheme Map
203 -* Category Scheme Map
204 -* Reporting Taxonomy Map
191 +* Structure (% style="color:#2ecc71" %)Map
192 +* [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] (% style="color:#2ecc71" %)Map
193 +* Organisation Scheme (% style="color:#2ecc71" %)Map
194 +* (% style="color:#2ecc71" %)Concept(%%) Scheme (% style="color:#2ecc71" %)Map
195 +* Category Scheme (% style="color:#2ecc71" %)Map
196 +* Reporting Taxonomy (% style="color:#2ecc71" %)Map
205 205  * Value List
206 -* Hierarchy
207 -* Hierarchy Association
208 -* Metadata Constraint
209 -* Data Constraint
198 +* [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]]
199 +* [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] Association
200 +* Metadata (% style="color:#2ecc71" %)Constraint
201 +* Data (% style="color:#2ecc71" %)Constraint
210 210  * Metadata Provision Agreement
211 211  * Metadata Provider Scheme
212 212  * Metadataset
... ... @@ -219,24 +219,25 @@
219 219  
220 220  Removed Maintainable Artefacts
221 221  
222 -* Structure Set – replaced by Structure Map and the four item scheme maps
223 -* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association • Constraint – replaced by Data Constraint and Metadata Constraint
214 +* Structure Set – replaced by Structure (% style="color:#2ecc71" %)Map(%%) and the four [[item scheme>>doc:xwiki:Glossary.Item scheme.WebHome]] maps
215 +* Hierarchical Codelist – replaced by [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] and [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] Association
216 +* (% style="color:#2ecc71" %)Constraint(%%) – replaced by Data (% style="color:#2ecc71" %)Constraint(%%) and Metadata (% style="color:#2ecc71" %)Constraint
224 224  
225 225  Changed Maintainable Artefacts
226 226  
227 -* Data Structure Definition – support for microdatasets and reference metadata linked to data
228 -* Metadataflow – simplifies exchange of reference metadata, in particular those linked to structures
229 -* Metadata Structure Definition – simplified model for reference metadata
220 +* Data Structure Definition – support for microdatasets and [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] linked to data
221 +* Metadataflow – simplifies exchange of [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]], in particular those linked to structures
222 +* Metadata Structure Definition – simplified model for [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]]
230 230  * Codelist – support for codelist extension and geospatial specialised codelists (GeographicCodelist, GeoGridCodelist)
231 -* VTL Mapping Scheme – VTL Concept Mapping Scheme removed to align the VTL / SDMX interface with the 3.0 model
224 +* [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Mapping Scheme – [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (% style="color:#2ecc71" %)Concept(%%) Mapping Scheme removed to align the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] / [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] interface with the 3.0 model
232 232  
233 -New Component Representation Types
226 +New [[Component>>doc:xwiki:Glossary.Component.WebHome]] [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] Types
234 234  
235 235  * GeospatialInformation – a string type where the value is an expression defining a set of geographical features using a purpose-designed syntax
236 236  
237 -== //3.3 Areas Unchanged from Version 2.1// ==
230 +== 3.3 Areas Unchanged from Version 2.1 ==
238 238  
239 -The following areas of the information model are unchanged from version 2.1:
232 +The following areas of the information model are unchanged from (% style="color:#2ecc71" %)version(%%) 2.1:
240 240  
241 241  * Categories
242 242  * Concepts
... ... @@ -243,18 +243,18 @@
243 243  * Data providers
244 244  * Agencies
245 245  * Data consumers
246 -* VTL transformation and expressions – with the exception of VTL mapping scheme as already noted
239 +* [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] transformation and expressions – with the exception of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] mapping scheme as already noted
247 247  * Reporting taxonomy
248 248  * Process
249 249  
250 -== //3.4 Reference Metadata// ==
243 +== 3.4 Reference Metadata ==
251 251  
252 -Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
245 +[[Reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] has been substantially re-designed for (% style="color:#2ecc71" %)version(%%) 3.0 to simplify the model and better support practical use cases.
253 253  
254 -=== Simplify Metadata Structure Definition ===
247 +(% class="wikigeneratedid" id="HSimplifyMetadataStructureDefinition" %)
248 +**Simplify Metadata Structure Definition**
249 +The [[Metadata Structure Definition>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] ([[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]]) has been simplified to remove target information, and the support of multiple report structures. The [[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] now only contains Metadata [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] which are used to define the structure of a report.
255 255  
256 -The Metadata Structure Definition (MSD) has been simplified to remove target information, and the support of multiple report structures. The MSD now only contains Metadata Attributes which are used to define the structure of a report.
257 -
258 258  [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png||height="346" width="494"]]
259 259  
260 260  //Figure 2 version 2.1 Metadata Structure Definition (MSD)//
... ... @@ -263,191 +263,136 @@
263 263  
264 264  //Figure 3 the simplified version 3.0 MSD//
265 265  
266 -=== Change to reference metadata reported against data ===
259 +(% class="wikigeneratedid" id="HChangetoreferencemetadatareportedagainstdata" %)
260 +**Change to reference metadata reported against data**
267 267  
268 -Reference metadata associated with datasets, data series or observations are now reported with the data. The dataset’s DSD must reference an MSD to define the structure of its reference metadata. In practice reference metadata for data are transmitted as part of the data message. The metadata attributes are treated in a similar way to the data attributes appearing in the message at the dataset, data series or individual observation level as appropriate. In contrast to simple data attributes, metadata attributes defined by an MSD can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata attributes appear in data messages structured in the same way as metadata messages.
262 +(% class="wikigeneratedid" id="HChangetoreferencemetadatareportedagainstdata" %)
263 +[[Reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] associated with [[datasets>>doc:xwiki:Glossary.Data set.WebHome]], data series or observations are now reported with the data. The [[dataset>>doc:xwiki:Glossary.Data set.WebHome]]’s [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] must reference an [[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] to define the structure of its [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]]. In practice [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] for data are transmitted as part of the data message. The metadata [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] are treated in a similar way to the data [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] appearing in the message at the [[dataset>>doc:xwiki:Glossary.Data set.WebHome]], data series or individual observation (% style="color:#2ecc71" %)level(%%) as appropriate. In contrast to simple data [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]], metadata [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] defined by an [[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] appear in data messages structured in the same way as metadata messages.
269 269  
270 -The SDMX-ML example below is an excerpt from a structure specific data message illustrating reporting of reference metadata with a hierarchical structure at the observation level.
265 +The [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] example below is an excerpt from a structure specific data message illustrating reporting of [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] with a hierarchical structure at the observation (% style="color:#2ecc71" %)level(%%).
271 271  
272 272  For completeness, the excerpt also shows:
273 273  
274 -* OBS_STATUS – a simple observation-level data attribute
275 -* TITLE – a multi-lingual data attribute
276 -* SOURCE_AGENCY – a multi-value data attribute
269 +* OBS_STATUS – a simple observation-(% style="color:#2ecc71" %)level(%%) data [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
270 +* TITLE – a multi-lingual data [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
271 +* SOURCE_AGENCY – a multi-value data [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
277 277  
278 -<Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
273 +> <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
274 +> <!—- complex multi-value and multi-lingual data attributes ~-~->
275 +> <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
276 +> <Value>
277 +> <common:Text xml:lang="en">Some English Text</common:Text>
278 +> <common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
279 +> </Value>
280 +> </Comp>
281 +> <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
282 +> <Value>4F0</Value>
283 +> <Value>4D0</Value>
284 +> <Value>CZ2</Value>
285 +> </Comp>
286 +> <!—- metadata attributes are reported like in metadata messages ~-~->
287 +> <Metadata>
288 +> <Attribute id="COLLECTION">
289 +> <Attribute id="METHOD">
290 +> <Text lang="en">AAA</Text>
291 +> </Attribute>
292 +> </Attribute>
293 +> <Attribute id="CONTACT">
294 +> <Value>CONTACT 1</Value>
295 +> <Attribute id="NAME">
296 +> <Value>Contact 1 Name 1</Value>
297 +> </Attribute>
298 +> <Attribute id="NAME">
299 +> <Value>Contact 1 Name 2</Value>
300 +> </Attribute>
301 +> </Attribute>
302 +> <Attribute id="CONTACT">
303 +> <Value>CONTACT 2</Value>
304 +> <Attribute id="NAME">
305 +> <Value>Contact 2 Name 1</Value>
306 +> </Attribute>
307 +> <Attribute id="NAME">
308 +> <Value>Contact 2 Name 2</Value>
309 +> </Attribute>
310 +> </Attribute>
311 +> </Metadata>
312 +> </Obs>
279 279  
280 -<!—- complex multi-value and multi-lingual data attributes ~-~->
314 +(% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement" %)
315 +**New - Metadata Provision Agreement**
281 281  
282 -<Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
317 +(% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement" %)
318 +In (% style="color:#2ecc71" %)version(%%) 2.1 a [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] could be used to report information against a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]]. From (% style="color:#2ecc71" %)version(%%) 3.0 this is managed by two separate structures, the Data [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] and the Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]].
283 283  
284 -<Value>
320 +(% class="wikigeneratedid" id="HMovetargettoMetadataflowandMetadataProvisionAgreement" %)
321 +**Move target to Metadataflow and Metadata Provision Agreement**
322 +For [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] that is reported against structures, the allowable targets information which is used to specify what structures the [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] can be reported against, has moved to the [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] and can be further refined in the Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]].
285 285  
286 -<common:Text xml:lang="en">Some English Text</common:Text>
324 +(% class="wikigeneratedid" id="HAddmaintainablepropertiestoreferencemetadata" %)
325 +**Add maintainable properties to reference metadata**
326 +A Metadataset now has mandatory identification information, (owner id, id, (% style="color:#2ecc71" %)version(%%)) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
287 287  
288 -<common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
328 +== 3.5 Microdata Exchange ==
289 289  
290 -</Value>
330 +Several changes have been made the [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]] to support microdata use cases in addition to aggregated time series.
291 291  
292 -</Comp>
332 +(% class="wikigeneratedid" id="HMultiplemeasures" %)
333 +**Multiple measures**Multiple [[measures>>doc:xwiki:Glossary.Measure.WebHome]] are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more [[measures>>doc:xwiki:Glossary.Measure.WebHome]]. [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] now act like any other [[component>>doc:xwiki:Glossary.Component.WebHome]] in that they use (% style="color:#2ecc71" %)concepts(%%), can have their own local coded or uncoded [[representation>>doc:xwiki:Glossary.Representation.WebHome]] defined within the [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]], and can be either mandatory or conditional. Creating a [[measure>>doc:xwiki:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:xwiki:Glossary.Measure.WebHome]]” (% style="color:#2ecc71" %)concept(%%) role applied emulates the (% style="color:#2ecc71" %)version(%%) 2.1 MeasureDimension behaviour as illustrated in the [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] example below:
293 293  
294 -<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
335 +> <str:MeasureList id=”MeasureDescriptor”>
336 +> <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
337 +> <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
338 +> </str:ConceptIdentity>
339 +> <str:LocalRepresentation>
340 +> <str:TextFormat textType=”String” isMultiLingual=”true” />
341 +> </str:LocalRepresentation>
342 +> <str:ConceptRole>
343 +> <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
344 +> </str:ConceptRole>
345 +> </str:Measure>
346 +> ...
347 +> <str:Measure>
348 +> </str:MeasureList>
295 295  
296 -<Value>4F0</Value>
350 +(% class="wikigeneratedid" id="HMulti-valuemeasuresandattributes" %)
351 +**Multi-value measures and attributes**
297 297  
298 -<Value>4D0</Value>
353 +(% class="wikigeneratedid" id="HMulti-valuemeasuresandattributes" %)
354 +Both [[measures>>doc:xwiki:Glossary.Measure.WebHome]] and [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] have been extended with the option to take ‘arrays’ of 193 multiple coded or uncoded values. This supports use cases like multiple observation 194 status flags. New //minOccurs// and //maxOccurs// properties define the valid number of 195 values. The //usage// property separately defines whether the [[measure>>doc:xwiki:Glossary.Measure.WebHome]] or [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] is //mandatory// or optional. In the [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] [[measure>>doc:xwiki:Glossary.Measure.WebHome]] example above, the properties //minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.
299 299  
300 -<Value>CZ2</Value>
356 +(% class="wikigeneratedid" id="HAttributesrelationshiptomeasures" %)
357 +**Attributes relationship to measures**
358 +In addition to attaching [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] to a specific (% style="color:#2ecc71" %)level(%%) within the [[dataset>>doc:xwiki:Glossary.Data set.WebHome]], their relationship 202 to [[measures>>doc:xwiki:Glossary.Measure.WebHome]] can also be defined.
301 301  
302 -</Comp>
360 +(% class="wikigeneratedid" id="HValuelists" %)
361 +**Value lists**
362 +Value lists help in modelling microdata by providing an enumeration similar to [[code lists>>doc:xwiki:Glossary.Code list.WebHome]] 206 but allowing any string values without being restricted to the rules of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] identifiers. That allows ValueItems (the equivalent to [[Code>>doc:xwiki:Glossary.Code.WebHome]]) to contain symbols like ‘¥’ and ‘€’, but also means they are not identifiable.
303 303  
304 -<!—- metadata attributes are reported like in metadata messages ~-~->
364 +== 3.6 Geospatial Data Exchange ==
305 305  
306 -<Metadata>
366 +The (% style="color:#2ecc71" %)version(%%) 3.0 model has been extended to provide explicit support for geospatial data.
307 307  
308 -<Attribute id="COLLECTION">
368 +(% class="wikigeneratedid" id="HGeospatialInformationtype" %)
369 +**GeospatialInformation type**
370 +A new GeospatialInformation string type has been added which can be used as the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] for any [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]], [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] or measure [[component>>doc:xwiki:Glossary.Component.WebHome]]. The value which is a string expression conforming to the syntax defined in Section 6 of the technical specifications precisely defines a ‘Geo Feature Set’ – a collection of geographical features like points, lines or polygons. Its use is recommended in conjunction with the “GEO_FEATURE_SET” (% style="color:#2ecc71" %)concept(%%) role.
309 309  
310 -<Attribute id="METHOD">
372 +(% class="wikigeneratedid" id="HGeospatialcodelists" %)
373 +**Geospatial code lists**
311 311  
312 -<Text lang="en">AAA</Text>
375 +(% class="wikigeneratedid" id="HGeospatialcodelists" %)
376 +Two new specialised types of [[code list>>doc:xwiki:Glossary.Code list.WebHome]] have been added where the definition of each [[code>>doc:xwiki:Glossary.Code.WebHome]] includes additional geospatial information in addition to the standard ID, name and description:
313 313  
314 -</Attribute>
315 -
316 -</Attribute>
317 -
318 -<Attribute id="CONTACT">
319 -
320 -<Value>CONTACT 1</Value>
321 -
322 -<Attribute id="NAME">
323 -
324 -<Value>Contact 1 Name 1</Value>
325 -
326 -</Attribute>
327 -
328 -<Attribute id="NAME">
329 -
330 -<Value>Contact 1 Name 2</Value>
331 -
332 -</Attribute>
333 -
334 -</Attribute>
335 -
336 -<Attribute id="CONTACT">
337 -
338 -<Value>CONTACT 2</Value>
339 -
340 -<Attribute id="NAME">
341 -
342 -<Value>Contact 2 Name 1</Value>
343 -
344 -</Attribute>
345 -
346 -<Attribute id="NAME">
347 -
348 -<Value>Contact 2 Name 2</Value>
349 -
350 -</Attribute>
351 -
352 -</Attribute>
353 -
354 -</Metadata>
355 -
356 -</Obs>
357 -
358 -=== New - Metadata Provision Agreement ===
359 -
360 -In version 2.1 a Provision Agreement could be used to report information against a Dataflow or Metadataflow. From version 3.0 this is managed by two separate structures, the Data Provision Agreement and the Metadata Provision Agreement.
361 -
362 -=== Move target to Metadataflow and Metadata Provision Agreement ===
363 -
364 -For reference metadata that is reported against structures, the allowable targets information which is used to specify what structures the reference metadata can be reported against, has moved to the Metadataflow and can be further refined in the Metadata Provision Agreement.
365 -
366 -=== Add maintainable properties to reference metadata ===
367 -
368 -A Metadataset now has mandatory identification information, (owner id, id, version) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
369 -
370 -== //3.5 Microdata Exchange// ==
371 -
372 -Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series.
373 -
374 -=== Multiple measures ===
375 -
376 -Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the
377 -
378 -Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1
379 -
380 -MeasureDimension behaviour as illustrated in the SDMX-ML example below:
381 -
382 -<str:MeasureList id=”MeasureDescriptor”>
383 -
384 -<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
385 -
386 -<Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
387 -
388 -</str:ConceptIdentity>
389 -
390 -<str:LocalRepresentation>
391 -
392 -<str:TextFormat textType=”String” isMultiLingual=”true” />
393 -
394 -</str:LocalRepresentation>
395 -
396 -<str:ConceptRole>
397 -
398 -<Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
399 -
400 -</str:ConceptRole>
401 -
402 -</str:Measure>
403 -
404 -...
405 -
406 -<str:Measure>
407 -
408 -</str:MeasureList>
409 -
410 -=== Multi-value measures and attributes ===
411 -
412 -Both measures and attributes have been extended with the option to take ‘arrays’ of 193 multiple coded or uncoded values. This supports use cases like multiple observation 194 status flags. New //minOccurs// and //maxOccurs// properties define the valid number of 195 values. The //usage// property separately defines whether the measure or attribute is
413 -
414 -//mandatory// or optional. In the SDMX-ML measure example above, the properties
415 -
416 -//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.
417 -
418 -=== Attributes relationship to measures ===
419 -
420 -In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.
421 -
422 -=== Value lists ===
423 -
424 -Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers.
425 -
426 -That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.
427 -
428 -== //3.6 Geospatial Data Exchange// ==
429 -
430 -The version 3.0 model has been extended to provide explicit support for geospatial data.
431 -
432 -=== GeospatialInformation type ===
433 -
434 -A new GeospatialInformation string type has been added which can be used as the 214 representation for any dimension, attribute or measure component. The value which is a 215 string expression conforming to the syntax defined in Section 6 of the technical 216 specifications precisely defines a ‘Geo Feature Set’ – a collection of geographical 217 features like points, lines or polygons. Its use is recommended in conjunction with the “GEO_FEATURE_SET” concept role.
435 -
436 -=== Geospatial code lists ===
437 -
438 -Two new specialised types of code list have been added where the definition of each code includes additional geospatial information in addition to the standard ID, name and description:
439 -
440 440  * GeographicCodelist – each item includes an element to represent a specific Geo Feature Set which is described using the same expression syntax as for GeospatialInformation type.
441 -* GeoGridCodelist – A code list defining a geographical grid composed of cells representing regular squared portions of the Earth. Each item references a cell within the grid.
379 +* GeoGridCodelist – A [[code list>>doc:xwiki:Glossary.Code list.WebHome]] defining a geographical grid composed of cells representing regular squared portions of the Earth. Each item references a cell within the grid.
442 442  
443 -=== //3.7 Structure Mapping// ===
381 +== 3.7 Structure Mapping ==
444 444  
445 445  The Structure Set in version 2.1 is a container for many mapping structures including Data Structure Map, Codelist Map and Concept Map. For version 3.0 the Structure Set artefact has been deprecated and replaced with a number of new maintainables giving better flexibility and reusability, specifically: Structure Map, Concept Scheme Map, Representation Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
446 446  
447 447  The version 2.1 Codelist Map been replaced with Representation Map which allows mappings to be defined between any combination of Code Lists, Value Lists and noncoded representations such as text strings and numbers.
448 448  
449 -==== Many-to-many source and target components ====
450 -
387 +(% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
388 +**Many-to-many source and target components**
451 451  Structure mapping rules may be defined with both multiple source components and multiple target components in contrast to version 2.1 where only one source and target was allowed. That supports many-to-many (n-n) mapping use cases where the output of a mapping rule may be dependent on the combination of a number of input components. For instance:
452 452  
453 453  Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.
... ... @@ -457,22 +457,21 @@
457 457  Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.
458 458  
459 459  **Fixed source and target**
460 -
461 461  The Structure Map may now define input or output components which have a fixed value.
462 462  
463 -==== Time representations mapping ====
464 -
400 +(% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
401 +**Time representations mapping**
465 465  Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.
466 466  
467 -==== Regular expression and substring mappings ====
468 -
404 +(% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
405 +**Regular expression and substring mappings**
469 469  All item maps allow the use of regular expressions and substrings to match source values, specifically: Concept Scheme Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
470 470  
471 -==== Item maps validity period ====
472 -
408 +(% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
409 +**Item maps validity period**
473 473  Item maps may further define the period for which the mapping is valid, meaning the mapping rule will only be applied if the row of information being mapped is within the period.
474 474  
475 -=== //3.8 Constraints// ===
412 +== 3.8 Constraints ==
476 476  
477 477  Constraints in version 3.0 are modelled using two separate artefacts which replace the version 2.1 content constraint:
478 478  
... ... @@ -487,23 +487,23 @@
487 487  
488 488  Attachment constraints have been deprecated due to a lack of use cases.
489 489  
490 -=== //3.9 Code List Extension// ===
427 +== 3.9 Code List Extension ==
491 491  
492 492  In addition to the two new specialised geospatial forms, the option has been added to define a code list as an extension of, or by inheriting codes from, other lists. An optional prefix can be added to inherited codes to disambiguate duplicates.
493 493  
494 494  This feature allows new code lists to be easily derived from existing lists without the need to make and manually maintain copies. When querying for extended code list structures using the REST API, the option has been added to retrieve either the definition or the materialised list. Traditional literal lists of codes continue to be supported.
495 495  
496 -=== //3.10 Discriminated Union of Code Lists// ===
433 +== 3.10 Discriminated Union of Code Lists ==
497 497  
498 498  Combining code list extension with wildcarded constraints solves the discriminated union of code lists problem where a classification or breakdown has multiple “variants” which are all valid but mutually exclusive. A common example is economic activity where several alternative classification schemes are in use including ISIC revisions 1 to 4 and NACE as used in the European Community.
499 499  
500 -=== //3.11 Code Hierarchies// ===
437 +== 3.11 Code Hierarchies ==
501 501  
502 502  Code hierarchies allow the definition of complex hierarchies of codes from potentially multiple lists for data discovery purposes. Hierarchical Codelist has been deprecated and replaced by two new artefacts: Hierarchy – the actual hierarchy of codes, and Hierarchy Association links hierarchies directly to any other identifiable object, a capability missing 312 from the version 2.1 model. Further, the linkage can be within a particular context, for instance linking a hierarchy to a dimension within the context of a specific Dataflow (dimension REF_AREA in the context of the ECB:EXR Dataflow).
503 503  
504 504  = 4 Versioning of Structural Metadata Artefacts =
505 505  
506 -Version 3.0 adopts semantic versioning principles for versioning of metadata artefacts following the rules set out at [[__https:~~/~~/semver.org__>>url:https://semver.org/]][[.>>url:https://semver.org/]] However, this is not mandatory, and organisations may continue to use the pre-existing two-digit versioning strategy, or not to version artefacts by omitting the //version// property. The version number no longer defaults to 1.0 if not explicitly set.
443 +Version 3.0 adopts semantic versioning principles for versioning of metadata artefacts following the rules set out at __[[https:~~/~~/semver.org>>https://semver.org]] __However, this is not mandatory, and organisations may continue to use the pre-existing two-digit versioning strategy, or not to version artefacts by omitting the //version// property. The version number no longer defaults to 1.0 if not explicitly set.
507 507  
508 508  Semantic version numbers are three digits:
509 509  
... ... @@ -518,7 +518,6 @@
518 518  Examples:
519 519  
520 520  SDMX:CL_AREA(1.0.0)
521 -
522 522  SDMX:CL_AREA(2.3.2)
523 523  
524 524  == Dependency management ==
... ... @@ -525,10 +525,9 @@
525 525  
526 526  Additional constructs are possible for dependency management when referencing structures. For instance:
527 527  
528 -2.3+.1 Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
464 +2.3+.1  Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
465 +2+.3.1  Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
529 529  
530 -2+.3.1 Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
531 -
532 532  == Draft structures ==
533 533  
534 534  A key principle is that semantically versioned structures are immutable and must not be changed without a corresponding change to the version number, except where explicitly marked as draft using extensions to the version number.
... ... @@ -535,17 +535,15 @@
535 535  
536 536  MAJOR.MINOR.PATCH-EXTENSION
537 537  
538 -1.10.0-draft Means that version 1.10.0 is still being modified and may change – equivalent to setting isFinal=false in SDMX 2.1.
473 +1.10.0-draft  Means that version 1.10.0 is still being modified and may change – equivalent to setting isFinal=false in SDMX 2.1.
474 +1.10.0-unstable  Alternative to -draft.
475 +1.10.0-notfinal  Alternative to -draft.
539 539  
540 -1.10.0-unstable Alternative to -draft.
541 -
542 -1.10.0-notfinal Alternative to -draft.
543 -
544 544  The SDMX 2.1 isFinal property is deprecated in 3.0.
545 545  
546 546  = 5 REST Web Services API =
547 547  
548 -== //5.1 Simplified list of resources// ==
481 +== 5.1 Simplified list of resources ==
549 549  
550 550  The version 3.0 REST API has just five main resources:
551 551  
... ... @@ -559,12 +559,12 @@
559 559  
560 560  This and changes in the URLs and query parameters on the data, availability and metadata resources means that, with the exception of schema queries, the version 3.0 API is not backwardly compatible.
561 561  
562 -== //5.2 Improved data queries// ==
495 +== 5.2 Improved data queries ==
563 563  
564 564  Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow.
565 565  
566 -=== Extend the context of data retrieval ===
567 -
499 +(% class="wikigeneratedid" id="HExtendthecontextofdataretrieval" %)
500 +**Extend the context of data retrieval**
568 568  Version 2.1 data queries always retrieved data from a single specific Dataflow. In version 3.0, the query context may be specified as:
569 569  
570 570  * Dataflow;
... ... @@ -573,31 +573,35 @@
573 573  
574 574  Data queries may also search across datasets, for instance “retrieve all data about a country”.
575 575  
576 -=== Component-based filters ===
577 -
509 +(% class="wikigeneratedid" id="HComponent-basedfilters" %)
510 +**Component-based filters**
578 578  Expressions filtering on individual components can now be included as part of the data query URL.
579 579  
580 580  /data/dataflow/ESTAT/ICP?c[REF_AREA]=CH&c[CONF_STATUS]=F
581 581  
582 -=== Support for operators ===
583 -
515 +(% class="wikigeneratedid" id="HSupportforoperators" %)
516 +**Support for operators**
584 584  Filter expressions can also include operators.
585 585  
586 -/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 Operators include:
519 +/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015
587 587  
588 -|eq|Equals
589 -|ne|Not equal to
590 -|le|Less than
591 -|ge|Greater than or equal to
592 -|sw|Starts with
521 +Operators include:
593 593  
594 -=== Support for multiple keys ===
523 +(% style="width:531.039px" %)
524 +|(% style="width:151px" %)eq|(% style="width:378px" %)Equals
525 +|(% style="width:151px" %)ne|(% style="width:378px" %)Not equal to
526 +|(% style="width:151px" %)le|(% style="width:378px" %)Less than
527 +|(% style="width:151px" %)ge|(% style="width:378px" %)Greater than or equal to
528 +|(% style="width:151px" %)sw|(% style="width:378px" %)Starts with
595 595  
530 +(% class="wikigeneratedid" id="HSupportformultiplekeys" %)
531 +**Support for multiple keys**
596 596  Queries can now specify multiple series keys.
597 597  
534 +(% class="wikigeneratedid" %)
598 598  /data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG
599 599  
600 -== //5.3 Improved reference metadata queries// ==
537 +== 5.3 Improved reference metadata queries ==
601 601  
602 602  Reference metadata queries have been improved with a number of new options to retrieve metadata reports.
603 603  
... ... @@ -613,7 +613,7 @@
613 613  
614 614  /metadata/structure/datastructure/BIS/BIS_CBS/1.0
615 615  
616 -== //5.4 Structural metadata maintenance// ==
553 +== 5.4 Structural metadata maintenance ==
617 617  
618 618  Support has been added for maintenance of structural metadata.
619 619  
... ... @@ -621,62 +621,64 @@
621 621  
622 622  = 6 XML, JSON, CSV and EDI Transmission formats =
623 623  
624 -== //6.1 SDMX-ML// ==
561 +== 6.1 SDMX-ML ==
625 625  
626 626  The SDMX-ML XML messages have been modified and updated for version 3.0. While they broadly follow the same principles, there have been significant changes which break backward compatibility.
627 627  
628 -=== Structure message ===
629 -
565 +(% class="wikigeneratedid" id="HStructuremessage" %)
566 +**Structure message**
630 630  The SDMX-ML structure message is used for transmission of structural metadata. It closely reflects the SDMX information model and has therefore been significantly updated for version 3.0 with the addition of new structures, modifications where structures have changed, and removal of deprecated structures like Structure Set.
631 631  
632 632  Additionally, the way the individual artefacts are organised into ‘collections’ within the message has been significantly revised with a simpler flat structure adopted as set out in the following table:
633 633  
634 -|**Artefact type**|**Version 2.1 Collection**|**Version 3.0 Collection**
635 -|AgencyScheme|OrganisationSchemes|AgencySchemes
636 -|DataConsumerScheme|OrganisationSchemes|DataConsumerSchemes
637 -|DataProviderScheme|OrganisationSchemes|DataProviderSchemes
638 -|MetadataProviderScheme|OrganisationSchemes|MetadataProviderSchemes
639 -|OrganisationUnitScheme|OrganisationSchemes|OrganisationUnitSchemes
640 -|GeographicCodelist|Codelists|GeographicCodelists
641 -|GeoGridCodelist|Codelists|GeoGridCodelists
642 -|ConceptScheme|Concepts|ConceptSchemes
643 -|ValueList|Codelists|ValueLists
644 -|StructureMap|StructureMappings|StructureMaps
645 -|RepresentationMap|StructureMappings|RepresentationMaps
646 -|ConceptSchemeMap|StructureMappings|ConceptSchemeMaps
647 -|CategorySchemeMap|StructureMappings|CategorySchemeMaps
648 -|OrganisationSchemeMap|StructureMappings|OrganisationSchemeMaps
649 -|ReportingTaxonomyMap|StructureMappings|ReportingTaxonomyMaps
650 -|DataConstraint|Constraints|DataConstraints
651 -|MetadataConstraint|Constraints|MetadataConstraints
652 -|MetadataProvisionAgreement|ProvisionAgreement|MetadataProvisionAgreements
653 -|CustomTypeScheme|CustomTypes|CustomTypeSchemes
654 -|VtlMappingScheme|VtlMappings|VtlMappingSchemes
655 -|NamePersonalisationScheme|NamePersonalisations|NamePersonalisationSchemes
656 -|RulesetScheme|Rulesets|RulesetSchemes
657 -|TransformationScheme|Transformations|TransformationSchemes
658 -|UserDefinedOperatorScheme|UserDefinedOperators|UserDefinedOperatorSchemes
571 +(% style="width:1102.04px" %)
572 +|(% style="width:321px" %)**Artefact type**|(% style="width:351px" %)**Version 2.1 Collection**|(% style="width:426px" %)**Version 3.0 Collection**
573 +|(% style="width:321px" %)AgencyScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)AgencySchemes
574 +|(% style="width:321px" %)DataConsumerScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)DataConsumerSchemes
575 +|(% style="width:321px" %)DataProviderScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)DataProviderSchemes
576 +|(% style="width:321px" %)MetadataProviderScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)MetadataProviderSchemes
577 +|(% style="width:321px" %)OrganisationUnitScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)OrganisationUnitSchemes
578 +|(% style="width:321px" %)GeographicCodelist|(% style="width:351px" %)Codelists|(% style="width:426px" %)GeographicCodelists
579 +|(% style="width:321px" %)GeoGridCodelist|(% style="width:351px" %)Codelists|(% style="width:426px" %)GeoGridCodelists
580 +|(% style="width:321px" %)ConceptScheme|(% style="width:351px" %)Concepts|(% style="width:426px" %)ConceptSchemes
581 +|(% style="width:321px" %)ValueList|(% style="width:351px" %)Codelists|(% style="width:426px" %)ValueLists
582 +|(% style="width:321px" %)StructureMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)StructureMaps
583 +|(% style="width:321px" %)RepresentationMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)RepresentationMaps
584 +|(% style="width:321px" %)ConceptSchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)ConceptSchemeMaps
585 +|(% style="width:321px" %)CategorySchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)CategorySchemeMaps
586 +|(% style="width:321px" %)OrganisationSchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)OrganisationSchemeMaps
587 +|(% style="width:321px" %)ReportingTaxonomyMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)ReportingTaxonomyMaps
588 +|(% style="width:321px" %)DataConstraint|(% style="width:351px" %)Constraints|(% style="width:426px" %)DataConstraints
589 +|(% style="width:321px" %)MetadataConstraint|(% style="width:351px" %)Constraints|(% style="width:426px" %)MetadataConstraints
590 +|(% style="width:321px" %)MetadataProvisionAgreement|(% style="width:351px" %)ProvisionAgreement|(% style="width:426px" %)MetadataProvisionAgreements
591 +|(% style="width:321px" %)CustomTypeScheme|(% style="width:351px" %)CustomTypes|(% style="width:426px" %)CustomTypeSchemes
592 +|(% style="width:321px" %)VtlMappingScheme|(% style="width:351px" %)VtlMappings|(% style="width:426px" %)VtlMappingSchemes
593 +|(% style="width:321px" %)NamePersonalisationScheme|(% style="width:351px" %)NamePersonalisations|(% style="width:426px" %)NamePersonalisationSchemes
594 +|(% style="width:321px" %)RulesetScheme|(% style="width:351px" %)Rulesets|(% style="width:426px" %)RulesetSchemes
595 +|(% style="width:321px" %)TransformationScheme|(% style="width:351px" %)Transformations|(% style="width:426px" %)TransformationSchemes
596 +|(% style="width:321px" %)UserDefinedOperatorScheme|(% style="width:351px" %)UserDefinedOperators|(% style="width:426px" %)UserDefinedOperatorSchemes
659 659  
660 660  No changes have been made to the way the following artefacts are organised in the structure message:
661 661  
662 -|**Artefact type**|**Collection**
663 -|Dataflow|Dataflows
664 -|Metadataflow|Metadataflows
665 -|CategoryScheme|CategorySchemes
666 -|Categorisation|Categorisations
667 -|Codelist|Codelists
668 -|Hierarchy|Hierarchies
669 -|HierarchyAssociation|HierarchyAssociations
670 -|MetadataStructure|MetadataStructures
671 -|DataStructure|DataStructures
672 -|ReportingTaxonomy|ReportingTaxonomies
673 -|Process|Processes
674 -|ProvisionAgreement|ProvisionAgreements
600 +(% style="width:1106.04px" %)
601 +|(% style="width:326px" %)**Artefact type**|(% style="width:776px" %)**Collection**
602 +|(% style="width:326px" %)Dataflow|(% style="width:776px" %)Dataflows
603 +|(% style="width:326px" %)Metadataflow|(% style="width:776px" %)Metadataflows
604 +|(% style="width:326px" %)CategoryScheme|(% style="width:776px" %)CategorySchemes
605 +|(% style="width:326px" %)Categorisation|(% style="width:776px" %)Categorisations
606 +|(% style="width:326px" %)Codelist|(% style="width:776px" %)Codelists
607 +|(% style="width:326px" %)Hierarchy|(% style="width:776px" %)Hierarchies
608 +|(% style="width:326px" %)HierarchyAssociation|(% style="width:776px" %)HierarchyAssociations
609 +|(% style="width:326px" %)MetadataStructure|(% style="width:776px" %)MetadataStructures
610 +|(% style="width:326px" %)DataStructure|(% style="width:776px" %)DataStructures
611 +|(% style="width:326px" %)ReportingTaxonomy|(% style="width:776px" %)ReportingTaxonomies
612 +|(% style="width:326px" %)Process|(% style="width:776px" %)Processes
613 +|(% style="width:326px" %)ProvisionAgreement|(% style="width:776px" %)ProvisionAgreements
675 675  
676 676  From version 3.0, collections can appear in any order within a structure message.
677 677  
678 -=== Data messages ===
679 -
617 +(% class="wikigeneratedid" id="HDatamessages" %)
618 +**Data messages**
680 680  All legacy SDMX-ML data messages have been deprecated with the exception of Structure Specific Data which becomes the sole standard format for transmission of SDMX data in XML in version 3.0.
681 681  
682 682  Specifically, the following data messages are not supported in version 3.0:
... ... @@ -693,44 +693,44 @@
693 693  
694 694  The time series variant of the Structure Specific Data message is no longer used.
695 695  
696 -=== Reference metadata message ===
697 -
635 +(% class="wikigeneratedid" id="HReferencemetadatamessage" %)
636 +**Reference metadata message**
698 698  The Generic Metadata message remains the standard format for transmission of reference metadata sets in XML but has been modified to support the revised version 3.0 reference metadata model.
699 699  
700 -=== Registry structural metadata ‘query’ messages ===
701 -
639 +(% class="wikigeneratedid" id="HRegistrystructuralmetadata2018query2019messages" %)
640 +**Registry structural metadata ‘query’ messages**
702 702  As a consequence of the deprecation of the SOAP API and standardisation on REST, the structural metadata ‘query’ messages have all been removed. In version 3.0, querying an SDMX Registry for structural metadata is performed solely using REST GET.
703 703  
704 -=== Structure referencing ===
705 -
643 +(% class="wikigeneratedid" id="HStructurereferencing" %)
644 +**Structure referencing**
706 706  The option to reference structures using Agency, ID and Version has been removed. From SDMX version 3.0 URN is used for all referencing purposes with the exception of local references such as where groups reference dimensions within a DSD.
707 707  
708 -== //6.2 SDMX-JSON// ==
647 +== 6.2 SDMX-JSON ==
709 709  
710 710  Like SDMX-ML, the SDMX-JSON messages have been significantly modified and updated for version 3.0. They are not backwardly compatible with version 2.1.
711 711  
712 -=== Structure message ===
713 -
651 +(% class="wikigeneratedid" id="HStructuremessage-1" %)
652 +**Structure message**
714 714  The SDMX-JSON structure message closely replicates the SDMX-ML equivalent. Like that of SDMX-ML it has been updated to align it with the version 3.0 information model with addition, deletion and modification of artefacts as required. The organisation of the structure collections has also been revised as detailed in paragraph 6.1.
715 715  
716 -=== Data message ===
717 -
655 +(% class="wikigeneratedid" id="HDatamessage" %)
656 +**Data message**
718 718  The SDMX-JSON data message has similarly be updated. Additional changes have been made to allow a single message to carry data from multiple datasets with potentially different Data Structure Definitions to support REST data queries of the form “retrieve all data about a country”. For this reason, the version 3.0 SDMX-JSON is not backwardly compatible with version 2.1 data messages. Support has been added for the transmission of microdata and reporting of reference metadata on data as an integral part of the dataset.
719 719  
720 -=== Reference metadata message ===
721 -
659 +(% class="wikigeneratedid" id="HReferencemetadatamessage-1" %)
660 +**Reference metadata message**
722 722  The SDMX-JSON metadata message has also been updated to support the version 3.0 reference metadata and Metadataset specifications.
723 723  
724 -=== Structure referencing ===
725 -
663 +(% class="wikigeneratedid" id="HStructurereferencing-1" %)
664 +**Structure referencing**
726 726  As for SDMX-ML, the option to reference structures using Agency, ID and Version has been removed with URN used for all non-local referencing purposes.
727 727  
728 -== //6.3 SDMX-CSV// ==
667 +== 6.3 SDMX-CSV ==
729 729  
730 730  CSV in SDMX is used transmission of data and reference metadata only.
731 731  
732 -=== Data message ===
733 -
671 +(% class="wikigeneratedid" id="HDatamessage-1" %)
672 +**Data message**
734 734  The SDMX-CSV data message has been modified to align with the version 3.0 information model, support the enhanced REST API and ensure that data can be freely converted to and from the XML and JSON formats without loss. These changes include:
735 735  
736 736  * An additional column identifying the type if the artefact defining the structure of the data: “dataflow”, “datastructure” or “dataprovision”; • A column for the structure artefact’s identification of the form
... ... @@ -739,11 +739,11 @@
739 739  
740 740  * A column for the dataset action: information, append, replace or delete, which is consistent with both the the SDMX-ML and SDMX-JSON data messages.
741 741  
742 -=== Reference metadata message ===
743 -
681 +(% class="wikigeneratedid" id="HReferencemetadatamessage-2" %)
682 +**Reference metadata message**
744 744  The SDMX-CSV metadata message is new for version 3.0 and, like the SDMX-ML and SDMX-JSON equivalents, is used for the transmission reference metadata sets.
745 745  
746 -=== //6.4 EDI deprecation// ===
685 +== 6.4 EDI deprecation ==
747 747  
748 748  The EDI format for transmission of both structures and data has been deprecated. Version 3.0 is therefore not backwardly compatible with legacy EDI messages.
749 749  
SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +22.0 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]