Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 25.1
edited by Helena
on 2025/05/23 12:16
Change comment: There is no comment for this version
To version 28.1
edited by Artur
on 2025/07/14 10:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SDMX 3.0 Standards. Summary of major changes and new functionality
1 +SDMX 3.0 Standards. Summary of Major Changes and New Functionality
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -11,7 +11,7 @@
11 11  
12 12  = 1 Overview =
13 13  
14 -[[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%) 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
14 +[[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] version 3.0 introduces new features, improvements and changes to the Standard in the following key areas:
15 15  
16 16  **Information Model**
17 17  
... ... @@ -36,7 +36,7 @@
36 36  
37 37  **SOAP Web Services API**
38 38  
39 -* The SOAP web services API has been deprecated with (% style="color:#e74c3c" %)version(%%) 3.0 standardising on REST**;**
39 +* The SOAP web services API has been deprecated with version 3.0 standardising on REST**;**
40 40  
41 41  **XML, JSON, CSV and EDI Transmission formats**
42 42  
... ... @@ -44,11 +44,11 @@
44 44  * Obsolete [[SDMX-ML>>doc: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 45  * The [[SDMX-EDI>>doc:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated
46 46  * The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified
47 -* The option to reference structures in [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
47 +* The option to reference structures in [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and [[Version>>doc:Glossary.Version.WebHome]] has been deprecated with URN now exclusively used for all non-local referencing purpose
48 48  
49 49  **Breaking Changes**
50 50  
51 -Many of the changes made are ‘breaking’ meaning that, while conversion between (% style="color:#e74c3c" %)versions(%%) may be possible in certain circumstances, the 3.0 specification is not directly backwardly compatible with earlier (% style="color:#e74c3c" %)versions(%%) of the Standard.
51 +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.
52 52  
53 53  A summary of the main breaking changes is given in chapter 2.
54 54  
... ... @@ -63,7 +63,7 @@
63 63  
64 64  = 2 Summary of Breaking Changes in 3.0 =
65 65  
66 -(% style="color:#e74c3c" %)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 +Version 3.0 introduces breaking changes into the web services API, transmission formats and information model. A summary is given in the table below.
67 67  
68 68  == 2.1 Web Services API ==
69 69  
... ... @@ -79,8 +79,8 @@
79 79  Schema queries are backwardly compatible.
80 80  //Guidance for implementors//
81 81  
82 -REST API implementors may provide partial backward compatibility by using web server URL rewriting rules to translate (% style="color:#e74c3c" %)version(%%) 2.1 structure queries to the 3.0 equivalent.
83 -Implementors are also recommended to (% style="color:#e74c3c" %)version(%%) their API services providing users with an explicit choice of which (% style="color:#e74c3c" %)version(%%) to use.
82 +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 +Implementors are also recommended to version their API services providing users with an explicit choice of which version to use.
84 84  )))
85 85  |**SOAP API**|(% style="width:818px" %)The SOAP API has been deprecated.
86 86  
... ... @@ -95,20 +95,20 @@
95 95  [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Compact (time-series) data message
96 96  [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Utility (time-series) data message
97 97  [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Cross-Sectional data message [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 2.1 Generic data messages (for observations, time-series and cross-sectional data)
98 -Structure Specific is the only data message option in (% style="color:#e74c3c" %)version(%%) 3.0 but is not backwardly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 due to several changes including deprecation of the option to reference structures like the [[DSD>>doc:Glossary.Data structure definition.WebHome]], [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] using their Agency, ID and (% style="color:#e74c3c" %)Version(%%). The time series variant of the message has also been deprecated.
98 +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>>doc:Glossary.Data structure definition.WebHome]], [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] using their Agency, ID and [[Version>>doc:Glossary.Version.WebHome]]. The time series variant of the message has also been deprecated.
99 99  The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] structure message is not backwardly compatible primarily due to:
100 100  
101 101  * Changes to the information model
102 102  * Changes to the way the structures are organised into ‘collections’ within the message
103 -* Deprecation of the Agency, ID, (% style="color:#e74c3c" %)Version(%%) option for referencing of structures in messages
103 +* Deprecation of the Agency, ID, [[Version>>doc:Glossary.Version.WebHome]] option for referencing of structures in messages
104 104  )))
105 105  |(% style="width:130px" %)**SDMX-JSON**|(% style="width:820px" %)(((
106 -The JSON data message is not backwardly compatible with (% style="color:#e74c3c" %)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:Glossary.Data set.WebHome]] with potentially different Data Structure Definitions.
106 +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>>doc:Glossary.Data set.WebHome]] with potentially different Data Structure Definitions.
107 107  The JSON structure message is not backwardly compatible primarily due to:
108 108  
109 109  * Changes to the information model
110 110  * Changes to the way the structures are organised into ‘collections’ within the message
111 -* Deprecation of the Agency, ID, (% style="color:#e74c3c" %)Version(%%) option for referencing of structures in messages
111 +* Deprecation of the Agency, ID, [[Version>>doc:Glossary.Version.WebHome]] option for referencing of structures in messages
112 112  )))
113 113  |(% style="width:130px" %)**SDMX-EDI**|(% style="width:820px" %)The EDI format for both structures and data has been deprecated.
114 114  |(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)The CSV data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#e74c3c" %)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.
... ... @@ -119,46 +119,46 @@
119 119  (((
120 120  (% style="width:955.039px" %)
121 121  |(% style="width:132px" %)**Data Structure Definition**|(% style="width:819px" %)(((
122 -The (% style="color:#e74c3c" %)version(%%) 3.0 [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:Glossary.Data structure definition.WebHome]]) model is not directly backwardly compatible with 2.1 primarily due to the deprecation of the special MeasureDimension.
122 +The version 3.0 [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]) model is not directly backwardly compatible with 2.1 primarily due to the deprecation of the special MeasureDimension.
123 123  
124 124  //Conversion guidance for implementors//
125 125  
126 -(% style="color:#e74c3c" %)Version(%%) 2.1 DSDs can be converted to the 3.0 model by creating a [[measure>>doc:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:Glossary.Measure.WebHome]]” (% style="color:#e74c3c" %)concept(%%) role applied as described in paragraph 3.5.
127 -(% style="color:#e74c3c" %)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:Glossary.Measure.WebHome]] and value arrays for [[measures>>doc:Glossary.Measure.WebHome]] and [[attributes>>doc:Glossary.Attribute.WebHome]].
126 +Version 2.1 DSDs can be converted to the 3.0 model by creating a [[measure>>doc:sdmx:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:sdmx:Glossary.Measure.WebHome]]” [[concept>>doc:sdmx:Glossary.Concept.WebHome]] role applied as described in paragraph 3.5.
127 +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:sdmx:Glossary.Measure.WebHome]] and value arrays for [[measures>>doc:sdmx:Glossary.Measure.WebHome]] and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]].
128 128  )))
129 129  |(% style="width:132px" %)**Structure mapping model**|(% style="width:819px" %)(((
130 -The structure mapping model has changed significantly in (% style="color:#e74c3c" %)version(%%) 3.0 with deprecation of the [[Structure Set>>doc:Glossary.Structure set.WebHome]] [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] and introduction of five new ones: [[Representation>>doc:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) and four variants of [[item scheme>>doc:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%).
130 +The structure mapping model has changed significantly in version 3.0 with deprecation of the [[Structure Set>>doc:Glossary.Structure set.WebHome]] [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] and introduction of five new ones: [[Representation>>doc:Glossary.Representation.WebHome]] Map and four variants of [[item scheme>>doc:Glossary.Item scheme.WebHome]] map.
131 131  
132 132  //Conversion guidance for implementors//
133 133  
134 -(% style="color:#e74c3c" %)Version(%%) 2.1 [[structure sets>>doc:Glossary.Structure set.WebHome]] can be practically converted to the (% style="color:#e74c3c" %)version(%%) 3.0 structure mapping model.
135 -Conversion from the (% style="color:#e74c3c" %)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:Glossary.Structure set.WebHome]] will not be precisely the same as the original. In converting to (% style="color:#e74c3c" %)version(%%) 3.0, the system must generate IDs for each of the new [[maintainable artefacts>>doc:Glossary.Maintainable artefact.WebHome]], but details of the original [[Structure Set>>doc:Glossary.Structure set.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] are lost.
134 +Version 2.1 [[structure sets>>doc:Glossary.Structure set.WebHome]] can be practically converted to the version 3.0 structure mapping model.
135 +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>>doc:Glossary.Structure set.WebHome]] 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>>doc:Glossary.Maintainable artefact.WebHome]], but details of the original [[Structure Set>>doc:Glossary.Structure set.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] are lost.
136 136  )))
137 137  |(% style="width:132px" %)**Reference metadata model**|(% style="width:819px" %)(((
138 -The [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] model has changed in (% style="color:#e74c3c" %)version(%%) 3.0 with modifications to the role of the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]]. Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] and Metadata Provider Scheme have been added. Metadatasets are now identifiable.
138 +The [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] model has changed in version 3.0 with modifications to the role of the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]]. Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] and Metadata Provider Scheme have been added. Metadatasets are now identifiable.
139 139  
140 -(% style="color:#e74c3c" %)Version(%%) 2.1 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] models are not valid in (% style="color:#e74c3c" %)version(%%) 3.0.
140 +Version 2.1 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] models are not valid in version 3.0.
141 141  
142 142  //Conversion guidance for implementors//
143 143  
144 -A (% style="color:#e74c3c" %)version(%%) 2.1 [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] can be converted to the (% style="color:#e74c3c" %)version(%%) 3.0 model under some circumstances, but target information is either lost or has to be translated into a [[metadataflow>>doc:Glossary.Metadataflow.WebHome]]. Further, conversion of a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] for collecting [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] against a [[dataset>>doc:Glossary.Data set.WebHome]] would need to make changes to the [[dataset>>doc:Glossary.Data set.WebHome]]’s [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]. As the [[Data Structure Definition>>doc: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:Glossary.Data set.WebHome]]. A 2.1 metadata report could be converted to a (% style="color:#e74c3c" %)version(%%) 3.0 Metadataset if it is attached to a structure, but requires a Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] which would need to be created if not already in existence.
145 -Conversion from the (% style="color:#e74c3c" %)version(%%) 3.0 model to (% style="color:#e74c3c" %)version(%%) 2.1 cannot be performed reliably. The process would need target information to be derived from analysis of the [[Metadataflows>>doc:Glossary.Metadataflow.WebHome]] and Metadata [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]]. Depending on the complexity it may not be possible to express that information in a (% style="color:#e74c3c" %)version(%%) 2.1 [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
144 +A version 2.1 [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] 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>>doc:Glossary.Metadataflow.WebHome]]. Further, conversion of a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] for collecting [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] against a [[dataset>>doc:Glossary.Data set.WebHome]] would need to make changes to the [[dataset>>doc:Glossary.Data set.WebHome]]’s [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]. As the [[Data Structure Definition>>doc: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:Glossary.Data set.WebHome]]. 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>>doc:Glossary.Provision agreement.WebHome]] which would need to be created if not already in existence.
145 +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>>doc:Glossary.Metadataflow.WebHome]] and Metadata [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]]. Depending on the complexity it may not be possible to express that information in a version 2.1 [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
146 146  )))
147 147  |(% style="width:132px" %)**Constraint model**|(% style="width:819px" %)(((
148 -The (% style="color:#e74c3c" %)version(%%) 2.1 Content (% style="color:#e74c3c" %)Constraint(%%) [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated in (% style="color:#e74c3c" %)version(%%) 3.0 and replaced by the Data (% style="color:#e74c3c" %)Constraint(%%) for data, and the Metadata (% style="color:#e74c3c" %)Constraint(%%) for reference metadata.
148 +The version 2.1 Content [[Constraint>>doc:Glossary.Constraint.WebHome]] [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated in version 3.0 and replaced by the Data Constraint for data, and the Metadata [[Constraint>>doc:Glossary.Constraint.WebHome]] for reference metadata.
149 149  
150 150  //Conversion guidance for implementors//
151 151  
152 -2.1 Content (% style="color:#e74c3c" %)Constraints(%%) can be converted without loss to the equivalent (% style="color:#e74c3c" %)version(%%) 3.0 Data (% style="color:#e74c3c" %)Constraint(%%) model.
152 +2.1 Content [[Constraint>>doc:Glossary.Constraint.WebHome]] can be converted without loss to the equivalent version 3.0 Data Constraint model.
153 153  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.
154 154  )))
155 155  |(% style="width:132px" %)**Hierarchical codelist structures**|(% style="width:819px" %)(((
156 -The (% style="color:#e74c3c" %)version(%%) 2.1 Hierarchical Codelist [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated in (% style="color:#e74c3c" %)version(%%) 3.0 and replaced by two new [[artefacts>>doc:Glossary.Artefact.WebHome]], [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] and [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association.
156 +The version 2.1 Hierarchical Codelist [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated in version 3.0 and replaced by two new [[artefacts>>doc:Glossary.Artefact.WebHome]], [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] and [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association.
157 157  
158 158  //Conversion guidance for implementors//
159 159  
160 -(% style="color:#e74c3c" %)Version(%%) 2.1 Hierarchical Codelists can be successfully converted to the (% style="color:#e74c3c" %)version(%%) 3.0 [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] model. Information on which [[artefacts>>doc:Glossary.Artefact.WebHome]] to link the [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] to on what context would need to be added as a separate procedure.
161 -Conversion from the (% style="color:#e74c3c" %)version(%%) 3.0 model to (% style="color:#e74c3c" %)version(%%) 2.1 is possible, but with loss of the linking information
160 +Version 2.1 Hierarchical Codelists can be successfully converted to the version 3.0 [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] model. Information on which [[artefacts>>doc:Glossary.Artefact.WebHome]] to link the [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] to on what context would need to be added as a separate procedure.
161 +Conversion from the version 3.0 model to version 2.1 is possible, but with loss of the linking information
162 162  )))
163 163  )))
164 164  
... ... @@ -170,26 +170,26 @@
170 170  
171 171  //Figure 1 Version 3.0 simplified Information Model UML class diagram with ‘heat map’ illustrating the areas with most change//
172 172  
173 -The schematic above is a simplified UML class diagram of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 information model illustrating the major areas of change as a ‘heat map’. Darker colours indicate where new structures have been added in (% style="color:#e74c3c" %)version(%%) 3.0 or where structures have been significantly changed.
173 +The schematic above is a simplified UML class diagram of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 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.
174 174  
175 -A number of ancillary structures including organisation schemes, process and [[reporting taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] are unchanged and have not been shown. Similarly, Organisation Scheme (% style="color:#e74c3c" %)Map(%%) and [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)Map(%%) have been omitted for simplicity. A schematic of the 2.1 model is given in Appendix A for comparison purposes.
175 +A number of ancillary structures including organisation schemes, process and [[reporting taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] are unchanged and have not been shown. Similarly, Organisation Scheme Map and [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] Map have been omitted for simplicity. A schematic of the 2.1 model is given in Appendix A for comparison purposes.
176 176  
177 177  == 3.2 Key Changes from Version 2.1 ==
178 178  
179 179  New Maintainable Artefacts
180 180  
181 -* Structure (% style="color:#e74c3c" %)Map
182 -* [[Representation>>doc:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map
183 -* Organisation Scheme (% style="color:#e74c3c" %)Map
184 -* (% style="color:#e74c3c" %)Concept(%%) Scheme (% style="color:#e74c3c" %)Map
185 -* Category Scheme (% style="color:#e74c3c" %)Map
186 -* Reporting Taxonomy (% style="color:#e74c3c" %)Map
181 +* Structure Map
182 +* Representation Map
183 +* Organisation Scheme Map
184 +* [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] Scheme Map
185 +* Category Scheme Map
186 +* Reporting Taxonomy Map
187 187  * Value List
188 -* [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]]
189 -* [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association
190 -* Metadata (% style="color:#e74c3c" %)Constraint
191 -* Data (% style="color:#e74c3c" %)Constraint
192 -* Metadata Provision Agreement
188 +* [[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]
189 +* [[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association
190 +* Metadata [[Constraint>>doc:Glossary.Constraint.WebHome]]
191 +* Data [[Constraint>>doc:Glossary.Constraint.WebHome]]
192 +* Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
193 193  * Metadata Provider Scheme
194 194  * Metadataset
195 195  
... ... @@ -201,9 +201,9 @@
201 201  
202 202  Removed Maintainable Artefacts
203 203  
204 -* Structure Set – replaced by Structure (% style="color:#e74c3c" %)Map(%%) and the four [[item scheme>>doc:Glossary.Item scheme.WebHome]] maps
204 +* Structure Set – replaced by Structure Map and the four [[item scheme>>doc:Glossary.Item scheme.WebHome]] maps
205 205  * Hierarchical Codelist – replaced by [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] and [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association
206 -* (% style="color:#e74c3c" %)Constraint(%%) – replaced by Data (% style="color:#e74c3c" %)Constraint(%%) and Metadata (% style="color:#e74c3c" %)Constraint
206 +* [[Constraint>>doc:Glossary.Constraint.WebHome]] – replaced by Data [[Constraint>>doc:Glossary.Constraint.WebHome]] and Metadata [[Constraint>>doc:Glossary.Constraint.WebHome]]
207 207  
208 208  Changed Maintainable Artefacts
209 209  
... ... @@ -211,7 +211,7 @@
211 211  * Metadataflow – simplifies exchange of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]], in particular those linked to structures
212 212  * Metadata Structure Definition – simplified model for [[reference metadata>>doc:Glossary.Reference metadata.WebHome]]
213 213  * Codelist – support for codelist extension and geospatial specialised codelists (GeographicCodelist, GeoGridCodelist)
214 -* [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme – [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)Concept(%%) Mapping Scheme removed to align the [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] / [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] interface with the 3.0 model
214 +* [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme – [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] Concept Mapping Scheme removed to align the [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] / [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] interface with the 3.0 model
215 215  
216 216  New [[Component>>doc:Glossary.Component.WebHome]] [[Representation>>doc:Glossary.Representation.WebHome]] Types
217 217  
... ... @@ -219,11 +219,11 @@
219 219  
220 220  == 3.3 Areas Unchanged from Version 2.1 ==
221 221  
222 -The following areas of the information model are unchanged from (% style="color:#e74c3c" %)version(%%) 2.1:
222 +The following areas of the information model are unchanged from version 2.1:
223 223  
224 224  * Categories
225 -* Concepts
226 -* Data providers
225 +* [[Concepts>>doc:sdmx:Glossary.Concept.WebHome]]
226 +* [[Data providers>>doc:sdmx:Glossary.Data provider.WebHome]]
227 227  * Agencies
228 228  * Data consumers
229 229  * [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] transformation and expressions – with the exception of [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] mapping scheme as already noted
... ... @@ -232,7 +232,7 @@
232 232  
233 233  == 3.4 Reference Metadata ==
234 234  
235 -[[Reference metadata>>doc:Glossary.Reference metadata.WebHome]] has been substantially re-designed for (% style="color:#e74c3c" %)version(%%) 3.0 to simplify the model and better support practical use cases.
235 +[[Reference metadata>>doc:Glossary.Reference metadata.WebHome]] has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
236 236  
237 237  (% class="wikigeneratedid" id="HSimplifyMetadataStructureDefinition" %)
238 238  **Simplify Metadata Structure Definition**
... ... @@ -250,13 +250,13 @@
250 250  **Change to reference metadata reported against data**
251 251  
252 252  (% class="wikigeneratedid" id="HChangetoreferencemetadatareportedagainstdata" %)
253 -[[Reference metadata>>doc:Glossary.Reference metadata.WebHome]] associated with [[datasets>>doc:Glossary.Data set.WebHome]], data series or observations are now reported with the data. The [[dataset>>doc:Glossary.Data set.WebHome]]’s [[DSD>>doc:Glossary.Data structure definition.WebHome]] must reference an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] to define the structure of its [[reference metadata>>doc:Glossary.Reference metadata.WebHome]]. In practice [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] for data are transmitted as part of the data message. The metadata [[attributes>>doc:Glossary.Attribute.WebHome]] are treated in a similar way to the data [[attributes>>doc:Glossary.Attribute.WebHome]] appearing in the message at the [[dataset>>doc:Glossary.Data set.WebHome]], data series or individual observation (% style="color:#e74c3c" %)level(%%) as appropriate. In contrast to simple data [[attributes>>doc:Glossary.Attribute.WebHome]], metadata [[attributes>>doc:Glossary.Attribute.WebHome]] defined by an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata [[attributes>>doc:Glossary.Attribute.WebHome]] appear in data messages structured in the same way as metadata messages.
253 +[[Reference metadata>>doc:Glossary.Reference metadata.WebHome]] associated with [[datasets>>doc:Glossary.Data set.WebHome]], data series or observations are now reported with the data. The [[dataset>>doc:Glossary.Data set.WebHome]]’s [[DSD>>doc:Glossary.Data structure definition.WebHome]] must reference an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] to define the structure of its [[reference metadata>>doc:Glossary.Reference metadata.WebHome]]. In practice [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] for data are transmitted as part of the data message. The metadata [[attributes>>doc:Glossary.Attribute.WebHome]] are treated in a similar way to the data [[attributes>>doc:Glossary.Attribute.WebHome]] appearing in the message at the [[dataset>>doc:Glossary.Data set.WebHome]], data series or individual observation level as appropriate. In contrast to simple data [[attributes>>doc:Glossary.Attribute.WebHome]], metadata [[attributes>>doc:Glossary.Attribute.WebHome]] defined by an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata [[attributes>>doc:Glossary.Attribute.WebHome]] appear in data messages structured in the same way as metadata messages.
254 254  
255 -The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] example below is an excerpt from a structure specific data message illustrating reporting of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] with a hierarchical structure at the observation (% style="color:#e74c3c" %)level(%%).
255 +The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] example below is an excerpt from a structure specific data message illustrating reporting of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] with a hierarchical structure at the observation level.
256 256  
257 257  For completeness, the excerpt also shows:
258 258  
259 -* OBS_STATUS – a simple observation-(% style="color:#e74c3c" %)level(%%) data [[attribute>>doc:Glossary.Attribute.WebHome]]
259 +* OBS_STATUS – a simple observation-level data [[attribute>>doc:Glossary.Attribute.WebHome]]
260 260  * TITLE – a multi-lingual data [[attribute>>doc:Glossary.Attribute.WebHome]]
261 261  * SOURCE_AGENCY – a multi-value data [[attribute>>doc:Glossary.Attribute.WebHome]]
262 262  
... ... @@ -305,7 +305,7 @@
305 305  **New - Metadata Provision Agreement**
306 306  
307 307  (% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement" %)
308 -In (% style="color:#e74c3c" %)version(%%) 2.1 a [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] could be used to report information against a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]. From (% style="color:#e74c3c" %)version(%%) 3.0 this is managed by two separate structures, the Data [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] and the Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
308 +In version 2.1 a [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] could be used to report information against a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]. From version 3.0 this is managed by two separate structures, the Data [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] and the Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
309 309  
310 310  (% class="wikigeneratedid" id="HMovetargettoMetadataflowandMetadataProvisionAgreement" %)
311 311  **Move target to Metadataflow and Metadata Provision Agreement**
... ... @@ -313,7 +313,7 @@
313 313  
314 314  (% class="wikigeneratedid" id="HAddmaintainablepropertiestoreferencemetadata" %)
315 315  **Add maintainable properties to reference metadata**
316 -A Metadataset now has mandatory identification information, (owner id, id, (% style="color:#e74c3c" %)version(%%)) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
316 +A Metadataset now has mandatory identification information, (owner id, id, [[version>>doc:Glossary.Version.WebHome]]) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
317 317  
318 318  == 3.5 Microdata Exchange ==
319 319  
... ... @@ -320,7 +320,7 @@
320 320  Several changes have been made the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] to support microdata use cases in addition to aggregated time series.
321 321  
322 322  (% class="wikigeneratedid" id="HMultiplemeasures" %)
323 -**Multiple measures**Multiple [[measures>>doc: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:Glossary.Measure.WebHome]]. [[Measures>>doc:Glossary.Measure.WebHome]] now act like any other [[component>>doc:Glossary.Component.WebHome]] in that they use (% style="color:#e74c3c" %)concepts(%%), can have their own local coded or uncoded [[representation>>doc:Glossary.Representation.WebHome]] defined within the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], and can be either mandatory or conditional. Creating a [[measure>>doc:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:Glossary.Measure.WebHome]]” (% style="color:#e74c3c" %)concept(%%) role applied emulates the (% style="color:#e74c3c" %)version(%%) 2.1 MeasureDimension behaviour as illustrated in the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] example below:
323 +**Multiple [[measures>>doc:sdmx:Glossary.Measure.WebHome]]** [[measures>>doc:sdmx: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:sdmx:Glossary.Measure.WebHome]]. [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] now act like any other [[component>>doc:sdmx:Glossary.Component.WebHome]] in that they use (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), can have their own local coded or uncoded [[representation>>doc:sdmx:Glossary.Representation.WebHome]] defined within the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], and can be either mandatory or conditional. Creating a [[measure>>doc:sdmx:Glossary.Measure.WebHome]] with the “[[MEASURE>>doc:sdmx:Glossary.Measure.WebHome]]” (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) role applied emulates the (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)version(%%) 2.1 MeasureDimension behaviour as illustrated in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] example below:
324 324  
325 325  > <str:MeasureList id=”MeasureDescriptor”>
326 326  > <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
... ... @@ -343,7 +343,7 @@
343 343  
344 344  (% class="wikigeneratedid" id="HAttributesrelationshiptomeasures" %)
345 345  **Attributes relationship to measures**
346 -In addition to attaching [[attributes>>doc:Glossary.Attribute.WebHome]] to a specific (% style="color:#e74c3c" %)level(%%) within the [[dataset>>doc:Glossary.Data set.WebHome]], their relationship 202 to [[measures>>doc:Glossary.Measure.WebHome]] can also be defined.
346 +In addition to attaching [[attributes>>doc:Glossary.Attribute.WebHome]] to a specific level within the [[dataset>>doc:Glossary.Data set.WebHome]], their relationship 202 to [[measures>>doc:Glossary.Measure.WebHome]] can also be defined.
347 347  
348 348  (% class="wikigeneratedid" id="HValuelists" %)
349 349  **Value lists**
... ... @@ -351,11 +351,11 @@
351 351  
352 352  == 3.6 Geospatial Data Exchange ==
353 353  
354 -The (% style="color:#e74c3c" %)version(%%) 3.0 model has been extended to provide explicit support for geospatial data.
354 +The version 3.0 model has been extended to provide explicit support for geospatial data.
355 355  
356 356  (% class="wikigeneratedid" id="HGeospatialInformationtype" %)
357 357  **GeospatialInformation type**
358 -A new GeospatialInformation string type has been added which can be used as the [[representation>>doc:Glossary.Representation.WebHome]] for any [[dimension>>doc:Glossary.Dimension.WebHome]], [[attribute>>doc:Glossary.Attribute.WebHome]] or measure [[component>>doc: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:#e74c3c" %)concept(%%) role.
358 +A new GeospatialInformation string type has been added which can be used as the [[representation>>doc:Glossary.Representation.WebHome]] for any [[dimension>>doc:Glossary.Dimension.WebHome]], [[attribute>>doc:Glossary.Attribute.WebHome]] or measure [[component>>doc: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” concept role.
359 359  
360 360  (% class="wikigeneratedid" id="HGeospatialcodelists" %)
361 361  **Geospatial code lists**
... ... @@ -368,13 +368,13 @@
368 368  
369 369  == 3.7 Structure Mapping ==
370 370  
371 -The [[Structure Set>>doc:Glossary.Structure set.WebHome]] in (% style="color:#e74c3c" %)version(%%) 2.1 is a container for many mapping structures including Data Structure (% style="color:#e74c3c" %)Map(%%), Codelist (% style="color:#e74c3c" %)Map(%%) and (% style="color:#e74c3c" %)Concept(%%) (% style="color:#e74c3c" %)Map(%%). For (% style="color:#e74c3c" %)version(%%) 3.0 the [[Structure Set>>doc:Glossary.Structure set.WebHome]] [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated and replaced with a number of new maintainables giving better flexibility and reusability, specifically: Structure (% style="color:#e74c3c" %)Map(%%), [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%), [[Representation>>doc:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%), [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)Map(%%), [[Category Scheme>>doc:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%) and Organisation Scheme (% style="color:#e74c3c" %)Map(%%).
371 +The [[Structure Set>>doc:Glossary.Structure set.WebHome]] 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>>doc:Glossary.Structure set.WebHome]] [[artefact>>doc:Glossary.Artefact.WebHome]] has been deprecated and replaced with a number of new maintainables giving better flexibility and reusability, specifically: Structure Map, [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] Map, [[Representation>>doc:Glossary.Representation.WebHome]] Map, [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] Map, [[Category Scheme>>doc:Glossary.Category scheme.WebHome]] Map and Organisation Scheme Map.
372 372  
373 -The (% style="color:#e74c3c" %)version(%%) 2.1 Codelist (% style="color:#e74c3c" %)Map(%%) been replaced with [[Representation>>doc:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) which allows mappings to be defined between any combination of [[Code Lists>>doc:Glossary.Code list.WebHome]], Value Lists and noncoded [[representations>>doc:Glossary.Representation.WebHome]] such as text strings and numbers.
373 +The version 2.1 Codelist Map been replaced with [[Representation>>doc:Glossary.Representation.WebHome]] Map which allows mappings to be defined between any combination of [[Code Lists>>doc:Glossary.Code list.WebHome]], Value Lists and noncoded [[representations>>doc:Glossary.Representation.WebHome]] such as text strings and numbers.
374 374  
375 375  (% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
376 376  **Many-to-many source and target components**
377 -Structure mapping rules may be defined with both multiple source [[components>>doc:Glossary.Component.WebHome]] and multiple target [[components>>doc:Glossary.Component.WebHome]] in contrast to (% style="color:#e74c3c" %)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>>doc:Glossary.Component.WebHome]]. For instance:
377 +Structure mapping rules may be defined with both multiple source [[components>>doc:Glossary.Component.WebHome]] and multiple target [[components>>doc:Glossary.Component.WebHome]] 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>>doc:Glossary.Component.WebHome]]. For instance:
378 378  
379 379  Set the output [[component>>doc:Glossary.Component.WebHome]] INDICATOR=”DE_A” if the input [[components>>doc:Glossary.Component.WebHome]] are FREQ=”A” and REF_AREA=”DE”.
380 380  
... ... @@ -383,34 +383,34 @@
383 383  Set the output [[components>>doc:Glossary.Component.WebHome]] FREQ=”A”, REF_AREA=”DE” if the input [[component>>doc:Glossary.Component.WebHome]] INDICATOR=”DE_A”.
384 384  
385 385  **Fixed source and target**
386 -The Structure (% style="color:#e74c3c" %)Map(%%) may now define input or output [[components>>doc:Glossary.Component.WebHome]] which have a fixed value.
386 +The Structure Map may now define input or output [[components>>doc:Glossary.Component.WebHome]] which have a fixed value.
387 387  
388 388  (% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
389 389  **Time representations mapping**
390 -Non [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] time [[representations>>doc:Glossary.Representation.WebHome]] may now be described in a Structure (% style="color:#e74c3c" %)Map(%%), allowing them to be (% style="color:#e74c3c" %)mapped(%%) into [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[time formats>>doc:Glossary.Time format.WebHome]].
390 +Non [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] time [[representations>>doc:Glossary.Representation.WebHome]] may now be described in a Structure Map, allowing them to be mapped into [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[time formats>>doc:Glossary.Time format.WebHome]].
391 391  
392 392  (% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
393 393  **Regular expression and substring mappings**
394 -All item (% style="color:#e74c3c" %)maps(%%) allow the use of regular expressions and substrings to match source values, specifically: [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%), [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)Map(%%), [[Category Scheme>>doc:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%) and Organisation Scheme (% style="color:#e74c3c" %)Map(%%).
394 +All item maps allow the use of regular expressions and substrings to match source values, specifically: [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] Map, [[Reporting Taxonomy>>doc:Glossary.Reporting taxonomy.WebHome]] Map, [[Category Scheme>>doc:Glossary.Category scheme.WebHome]] Map and Organisation Scheme Map.
395 395  
396 396  (% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
397 397  **Item maps validity period**
398 -Item (% style="color:#e74c3c" %)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 (% style="color:#e74c3c" %)mapped(%%) is within the period.
398 +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.
399 399  
400 400  == 3.8 Constraints ==
401 401  
402 -(% style="color:#e74c3c" %)Constraints(%%) in (% style="color:#e74c3c" %)version(%%) 3.0 are modelled using two separate [[artefacts>>doc:Glossary.Artefact.WebHome]] which replace the (% style="color:#e74c3c" %)version(%%) 2.1 content (% style="color:#e74c3c" %)constraint(%%):
402 +[[Constraints>>doc:Glossary.Constraint.WebHome]] in version 3.0 are modelled using two separate [[artefacts>>doc:Glossary.Artefact.WebHome]] which replace the version 2.1 content [[сonstraint>>doc:Glossary.Constraint.WebHome]]:
403 403  
404 -* data (% style="color:#e74c3c" %)constraint(%%) for data; and
405 -* metadata (% style="color:#e74c3c" %)constraint(%%) for [[reference metadata>>doc:Glossary.Reference metadata.WebHome]].
404 +* data [[сonstraint>>doc:Glossary.Constraint.WebHome]] for data; and
405 +* metadata [[сonstraint>>doc:Glossary.Constraint.WebHome]] for [[reference metadata>>doc:Glossary.Reference metadata.WebHome]].
406 406  
407 -Metadata (% style="color:#e74c3c" %)constraint(%%) differs from its data counterpart in having a simplified cube region model better suited to [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] reporting use cases and not carrying details of the constrained targets – that information instead being defined directly within the [[metadataflow>>doc:Glossary.Metadataflow.WebHome]] and Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]. Thus, metadata related (% style="color:#e74c3c" %)constraints(%%) only specify (% style="color:#e74c3c" %)constraints(%%) to the values of metadata attributes.
407 +Metadata [[сonstraint>>doc:Glossary.Constraint.WebHome]] differs from its data counterpart in having a simplified cube region model better suited to [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] reporting use cases and not carrying details of the constrained targets – that information instead being defined directly within the [[metadataflow>>doc:Glossary.Metadataflow.WebHome]] and Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]. Thus, metadata related (% style="color:#e74c3c" %)constraints(%%) only specify [[сonstraints>>doc:Glossary.Constraint.WebHome]] to the values of metadata attributes.
408 408  
409 -The ‘%’ wildcard character can now be used when defining cube region (% style="color:#e74c3c" %)constraints(%%) to match multiple [[codes>>doc:Glossary.Code.WebHome]] with a single expression, for instance for [[economic activity>>doc:Glossary.Economic activity.WebHome]], ISIC4_% matches all [[codes>>doc:Glossary.Code.WebHome]] beginning with ‘ISIC4_’ avoiding the need to maintain an explicit list.
409 +The ‘%’ wildcard character can now be used when defining cube region [[сonstraints>>doc:Glossary.Constraint.WebHome]] to match multiple [[codes>>doc:Glossary.Code.WebHome]] with a single expression, for instance for [[economic activity>>doc:Glossary.Economic activity.WebHome]], ISIC4_% matches all [[codes>>doc:Glossary.Code.WebHome]] beginning with ‘ISIC4_’ avoiding the need to maintain an explicit list.
410 410  
411 -The validity period definition has been moved from the (% style="color:#e74c3c" %)constraint(%%) to the individual constraining terms, specifically CubeRegion, DataKeySet and MetadataTargetRegion providing more granular control.
411 +The validity period definition has been moved from the [[сonstraint>>doc:Glossary.Constraint.WebHome]] to the individual constraining terms, specifically CubeRegion, DataKeySet and MetadataTargetRegion providing more granular control.
412 412  
413 -Attachment (% style="color:#e74c3c" %)constraints(%%) have been deprecated due to a lack of use cases.
413 +Attachment [[сonstraints>>doc:Glossary.Constraint.WebHome]] have been deprecated due to a lack of use cases.
414 414  
415 415  == 3.9 Code List Extension ==
416 416  
... ... @@ -420,17 +420,17 @@
420 420  
421 421  == 3.10 Discriminated Union of Code Lists ==
422 422  
423 -Combining [[code list>>doc:Glossary.Code list.WebHome]] extension with wildcarded (% style="color:#e74c3c" %)constraints(%%) solves the discriminated union of [[code lists>>doc:Glossary.Code list.WebHome]] problem where a classification or breakdown has multiple “variants” which are all valid but mutually exclusive. A common example is [[economic activity>>doc:Glossary.Economic activity.WebHome]] where several alternative classification schemes are in use including ISIC revisions 1 to 4 and NACE as used in the European Community.
423 +Combining [[code list>>doc:Glossary.Code list.WebHome]] extension with wildcarded [[сonstraints>>doc:Glossary.Constraint.WebHome]] solves the discriminated union of [[code lists>>doc:Glossary.Code list.WebHome]] problem where a classification or breakdown has multiple “variants” which are all valid but mutually exclusive. A common example is [[economic activity>>doc:Glossary.Economic activity.WebHome]] where several alternative classification schemes are in use including ISIC revisions 1 to 4 and NACE as used in the European Community.
424 424  
425 425  == 3.11 Code Hierarchies ==
426 426  
427 -[[Code>>doc:Glossary.Code.WebHome]] [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] allow the definition of complex [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] of [[codes>>doc:Glossary.Code.WebHome]] from potentially multiple lists for data discovery purposes. Hierarchical Codelist has been deprecated and replaced by two new [[artefacts>>doc:Glossary.Artefact.WebHome]]: [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] – the actual [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] of [[codes>>doc:Glossary.Code.WebHome]], and [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association links [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] directly to any other identifiable object, a capability missing from the (% style="color:#e74c3c" %)version(%%) 2.1 model. Further, the linkage can be within a particular context, for instance linking a [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] to a [[dimension>>doc:Glossary.Dimension.WebHome]] within the context of a specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]] ([[dimension>>doc:Glossary.Dimension.WebHome]] REF_AREA in the context of the ECB:EXR [[Dataflow>>doc:Glossary.Dataflow.WebHome]]).
427 +[[Code>>doc:Glossary.Code.WebHome]] [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] allow the definition of complex [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] of [[codes>>doc:Glossary.Code.WebHome]] from potentially multiple lists for data discovery purposes. Hierarchical Codelist has been deprecated and replaced by two new [[artefacts>>doc:Glossary.Artefact.WebHome]]: [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] – the actual [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] of [[codes>>doc:Glossary.Code.WebHome]], and [[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association links [[hierarchies>>doc:Glossary.Hierarchy.WebHome]] directly to any other identifiable object, a capability missing from the version 2.1 model. Further, the linkage can be within a particular context, for instance linking a [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] to a [[dimension>>doc:Glossary.Dimension.WebHome]] within the context of a specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]] ([[dimension>>doc:Glossary.Dimension.WebHome]] REF_AREA in the context of the ECB:EXR [[Dataflow>>doc:Glossary.Dataflow.WebHome]]).
428 428  
429 429  = 4 Versioning of Structural Metadata Artefacts =
430 430  
431 -(% style="color:#e74c3c" %)Version(%%) 3.0 adopts semantic versioning principles for versioning of metadata [[artefacts>>doc:Glossary.Artefact.WebHome]] 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 (% style="color:#e74c3c" %)version(%%) [[artefacts>>doc:Glossary.Artefact.WebHome]] by omitting the (% style="color:#e74c3c" %)//version//(%%) property. The (% style="color:#e74c3c" %)version(%%) number no longer defaults to 1.0 if not explicitly set.
431 +Version 3.0 adopts semantic versioning principles for versioning of metadata [[artefacts>>doc:Glossary.Artefact.WebHome]] 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>>doc:Glossary.Artefact.WebHome]] by omitting the //version// property. The version number no longer defaults to 1.0 if not explicitly set.
432 432  
433 -Semantic (% style="color:#e74c3c" %)version(%%) numbers are three digits:
433 +Semantic version numbers are three digits:
434 434  
435 435  MAJOR.MINOR.PATCH
436 436  
... ... @@ -450,17 +450,17 @@
450 450  
451 451  Additional constructs are possible for dependency management when referencing structures. For instance:
452 452  
453 -2.3+.1  Means the currently latest available (% style="color:#e74c3c" %)version(%%) >= “2.3.1” and < “3.0.0” (all backwards compatible (% style="color:#e74c3c" %)versions(%%) >= “2.3.1”).
454 -2+.3.1  Means the currently latest available (% style="color:#e74c3c" %)version(%%) >= “2.3.1” (even if not backwards compatible).
453 +2.3+.1  Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
454 +2+.3.1  Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
455 455  
456 456  (% class="wikigeneratedid" id="HDraftstructures" %)
457 457  **Draft structures**
458 458  
459 -A key principle is that semantically versioned structures are immutable and must not be changed without a corresponding change to the (% style="color:#e74c3c" %)version(%%) number, except where explicitly marked as draft using extensions to the (% style="color:#e74c3c" %)version(%%) number.
459 +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.
460 460  
461 461  MAJOR.MINOR.PATCH-EXTENSION
462 462  
463 -1.10.0-draft  Means that (% style="color:#e74c3c" %)version(%%) 1.10.0 is still being modified and may change – equivalent to setting isFinal=false in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 2.1.
463 +1.10.0-draft  Means that version 1.10.0 is still being modified and may change – equivalent to setting isFinal=false in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 2.1.
464 464  1.10.0-unstable  Alternative to -draft.
465 465  1.10.0-notfinal  Alternative to -draft.
466 466  
... ... @@ -470,7 +470,7 @@
470 470  
471 471  == 5.1 Simplified list of resources ==
472 472  
473 -The (% style="color:#e74c3c" %)version(%%) 3.0 REST API has just five main resources:
473 +The version 3.0 REST API has just five main resources:
474 474  
475 475  * structure
476 476  * data
... ... @@ -478,9 +478,9 @@
478 478  * availability
479 479  * metadata
480 480  
481 -All structure and item queries have been organised under the structure resource in contrast to the (% style="color:#e74c3c" %)version(%%) 2.1 API which specified a separate resource for each structure.
481 +All structure and item queries have been organised under the structure resource in contrast to the version 2.1 API which specified a separate resource for each structure.
482 482  
483 -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 (% style="color:#e74c3c" %)version(%%) 3.0 API is not backwardly compatible.
483 +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.
484 484  
485 485  == 5.2 Improved data queries ==
486 486  
... ... @@ -488,7 +488,7 @@
488 488  
489 489  (% class="wikigeneratedid" id="HExtendthecontextofdataretrieval" %)
490 490  **Extend the context of data retrieval**
491 -(% style="color:#e74c3c" %)Version(%%) 2.1 data queries always retrieved data from a single specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]]. In (% style="color:#e74c3c" %)version(%%) 3.0, the query context may be specified as:
491 +Version 2.1 data queries always retrieved data from a single specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]]. In version 3.0, the query context may be specified as:
492 492  
493 493  * [[Dataflow>>doc:Glossary.Dataflow.WebHome]];
494 494  * Data Structure Definition – i.e., all [[Dataflows>>doc:Glossary.Dataflow.WebHome]] that use it; or
... ... @@ -550,11 +550,11 @@
550 550  
551 551  == 6.1 SDMX-ML ==
552 552  
553 -The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] XML messages have been modified and updated for (% style="color:#e74c3c" %)version(%%) 3.0. While they broadly follow the same principles, there have been significant changes which break backward compatibility.
553 +The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 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.
554 554  
555 555  (% class="wikigeneratedid" id="HStructuremessage" %)
556 556  **Structure message**
557 -The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] structure message is used for transmission of [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. It closely reflects the [[SDMX information model>>doc:Glossary.SDMX Information Model.WebHome]] and has therefore been significantly updated for (% style="color:#e74c3c" %)version(%%) 3.0 with the addition of new structures, modifications where structures have changed, and removal of deprecated structures like Structure Set.
557 +The [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] structure message is used for transmission of [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. It closely reflects the [[SDMX information model>>doc:Glossary.SDMX Information Model.WebHome]] 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.
558 558  
559 559  Additionally, the way the individual [[artefacts>>doc:Glossary.Artefact.WebHome]] are organised into ‘collections’ within the message has been significantly revised with a simpler flat structure adopted as set out in the following table:
560 560  
... ... @@ -602,15 +602,15 @@
602 602  |(% style="width:326px" %)Process|(% style="width:776px" %)Processes
603 603  |(% style="width:326px" %)ProvisionAgreement|(% style="width:776px" %)ProvisionAgreements
604 604  
605 -From (% style="color:#e74c3c" %)version(%%) 3.0, collections can appear in any order within a structure message.
605 +From version 3.0, collections can appear in any order within a structure message.
606 606  
607 607  (% class="wikigeneratedid" id="HDatamessages" %)
608 608  **Data messages**
609 609  
610 610  (% class="wikigeneratedid" id="HDatamessages" %)
611 -All legacy [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] data messages have been deprecated with the exception of Structure Specific Data which becomes the sole standard format for transmission of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] data in XML in (% style="color:#e74c3c" %)version(%%) 3.0.
611 +All legacy [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] data messages have been deprecated with the exception of Structure Specific Data which becomes the sole standard format for transmission of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] data in XML in version 3.0.
612 612  
613 -Specifically, the following data messages are not supported in (% style="color:#e74c3c" %)version(%%) 3.0:
613 +Specifically, the following data messages are not supported in version 3.0:
614 614  
615 615  * [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Generic (time-series) data message
616 616  * [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 1.0/2.0 Compact (time-series) data message
... ... @@ -620,41 +620,41 @@
620 620  
621 621  The Structure Specific Data message has been extended to support the transmission of microdata sets, in particular those with multiple [[measures>>doc:Glossary.Measure.WebHome]] and array values for [[measures>>doc:Glossary.Measure.WebHome]] and [[attributes>>doc:Glossary.Attribute.WebHome]].
622 622  
623 -As detailed in paragraph 3.4, the message now additionally allows data’s [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be reported as an integral part of the [[dataset>>doc:Glossary.Data set.WebHome]]. Like data [[attributes>>doc:Glossary.Attribute.WebHome]], these metadata [[attributes>>doc:Glossary.Attribute.WebHome]] are included in the data message at the [[dataset>>doc:Glossary.Data set.WebHome]], series or observation (% style="color:#e74c3c" %)level(%%) as appropriate.
623 +As detailed in paragraph 3.4, the message now additionally allows data’s [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be reported as an integral part of the [[dataset>>doc:Glossary.Data set.WebHome]]. Like data [[attributes>>doc:Glossary.Attribute.WebHome]], these metadata [[attributes>>doc:Glossary.Attribute.WebHome]] are included in the data message at the [[dataset>>doc:Glossary.Data set.WebHome]], series or observation level as appropriate.
624 624  
625 625  The time series variant of the Structure Specific Data message is no longer used.
626 626  
627 627  (% class="wikigeneratedid" id="HReferencemetadatamessage" %)
628 628  **Reference metadata message**
629 -The Generic Metadata message remains the standard format for transmission of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sets in XML but has been modified to support the revised (% style="color:#e74c3c" %)version(%%) 3.0 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] model.
629 +The Generic Metadata message remains the standard format for transmission of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sets in XML but has been modified to support the revised version 3.0 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] model.
630 630  
631 631  (% class="wikigeneratedid" id="HRegistrystructuralmetadata2018query2019messages" %)
632 632  **Registry structural metadata ‘query’ messages**
633 -As a consequence of the deprecation of the SOAP API and standardisation on REST, the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] ‘query’ messages have all been removed. In (% style="color:#e74c3c" %)version(%%) 3.0, querying an [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] is performed solely using REST GET.
633 +As a consequence of the deprecation of the SOAP API and standardisation on REST, the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] ‘query’ messages have all been removed. In version 3.0, querying an [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] is performed solely using REST GET.
634 634  
635 635  (% class="wikigeneratedid" id="HStructurereferencing" %)
636 636  **Structure referencing**
637 -The option to reference structures using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been removed. From [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%) 3.0 URN is used for all referencing purposes with the exception of local references such as where groups reference [[dimensions>>doc:Glossary.Dimension.WebHome]] within a [[DSD>>doc:Glossary.Data structure definition.WebHome]].
637 +The option to reference structures using Agency, ID and Version has been removed. From [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] version 3.0 URN is used for all referencing purposes with the exception of local references such as where groups reference [[dimensions>>doc:Glossary.Dimension.WebHome]] within a [[DSD>>doc:Glossary.Data structure definition.WebHome]].
638 638  
639 639  == 6.2 SDMX-JSON ==
640 640  
641 -Like [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]], the [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] messages have been significantly modified and updated for (% style="color:#e74c3c" %)version(%%) 3.0. They are not backwardly compatible with (% style="color:#e74c3c" %)version(%%) 2.1.
641 +Like [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]], the [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] messages have been significantly modified and updated for version 3.0. They are not backwardly compatible with version 2.1.
642 642  
643 643  (% class="wikigeneratedid" id="HStructuremessage-1" %)
644 644  **Structure message**
645 -The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] structure message closely replicates the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] equivalent. Like that of [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] it has been updated to align it with the (% style="color:#e74c3c" %)version(%%) 3.0 information model with addition, deletion and modification of [[artefacts>>doc:Glossary.Artefact.WebHome]] as required. The organisation of the structure collections has also been revised as detailed in paragraph 6.1.
645 +The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] structure message closely replicates the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] equivalent. Like that of [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] it has been updated to align it with the version 3.0 information model with addition, deletion and modification of [[artefacts>>doc:Glossary.Artefact.WebHome]] as required. The organisation of the structure collections has also been revised as detailed in paragraph 6.1.
646 646  
647 647  (% class="wikigeneratedid" id="HDatamessage" %)
648 648  **Data message**
649 -The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] data message has similarly be updated. Additional changes have been made to allow a single message to carry data from multiple [[datasets>>doc:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]] to support REST data queries of the form “retrieve all data about a country”. For this reason, the (% style="color:#e74c3c" %)version(%%) 3.0 [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] is not backwardly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 data messages. Support has been added for the transmission of microdata and reporting of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] on data as an integral part of the dataset.
649 +The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] data message has similarly be updated. Additional changes have been made to allow a single message to carry data from multiple [[datasets>>doc:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]] to support REST data queries of the form “retrieve all data about a country”. For this reason, the version 3.0 [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] is not backwardly compatible with version 2.1 data messages. Support has been added for the transmission of microdata and reporting of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] on data as an integral part of the dataset.
650 650  
651 651  (% class="wikigeneratedid" id="HReferencemetadatamessage-1" %)
652 652  **Reference metadata message**
653 -The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] metadata message has also been updated to support the (% style="color:#e74c3c" %)version(%%) 3.0 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and Metadataset specifications.
653 +The [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] metadata message has also been updated to support the version 3.0 [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and Metadataset specifications.
654 654  
655 655  (% class="wikigeneratedid" id="HStructurereferencing-1" %)
656 656  **Structure referencing**
657 -As for [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]], the option to reference structures using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been removed with URN used for all non-local referencing purposes.
657 +As for [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]], the option to reference structures using Agency, ID and Version has been removed with URN used for all non-local referencing purposes.
658 658  
659 659  == 6.3 SDMX-CSV ==
660 660  
... ... @@ -662,22 +662,22 @@
662 662  
663 663  (% class="wikigeneratedid" id="HDatamessage-1" %)
664 664  **Data message**
665 -The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-CSV data message has been modified to align with the (% style="color:#e74c3c" %)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:
665 +The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-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:
666 666  
667 667  * An additional column identifying the type if the [[artefact>>doc:Glossary.Artefact.WebHome]] defining the structure of the data: “[[dataflow>>doc:Glossary.Dataflow.WebHome]]”, “datastructure” or “dataprovision”;
668 668  * A column for the structure [[artefact>>doc:Glossary.Artefact.WebHome]]’s identification of the form
669 669  
670 -ESTAT:NA_MAIN(1.6.0) which replaces the [[dataflow>>doc:Glossary.Dataflow.WebHome]] identifier in (% style="color:#e74c3c" %)version(%%) 2.1; and
670 +ESTAT:NA_MAIN(1.6.0) which replaces the [[dataflow>>doc:Glossary.Dataflow.WebHome]] identifier in version 2.1; and
671 671  
672 672  * A column for the [[dataset>>doc:Glossary.Data set.WebHome]] action: information, append, replace or delete, which is consistent with both the the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] data messages.
673 673  
674 674  (% class="wikigeneratedid" id="HReferencemetadatamessage-2" %)
675 675  **Reference metadata message**
676 -The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-CSV metadata message is new for (% style="color:#e74c3c" %)version(%%) 3.0 and, like the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] equivalents, is used for the transmission [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sets.
676 +The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-CSV metadata message is new for version 3.0 and, like the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] equivalents, is used for the transmission [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sets.
677 677  
678 678  == 6.4 EDI deprecation ==
679 679  
680 -The EDI format for transmission of both structures and data has been deprecated. (% style="color:#e74c3c" %)Version(%%) 3.0 is therefore not backwardly compatible with legacy EDI messages.
680 +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.
681 681  
682 682  = Appendix A – Version 2.1 Information Model =
683 683  
1750172098914-610.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.elenasemanticproorg
Size
... ... @@ -1,0 +1,1 @@
1 +310.2 KB
Content
SKMS.Methodology.Code.MethodologyClass[0]