Changes for page SDMX 3.0 Standards. Summary of Major Changes and New Functionality

Summary

• Page properties (4 modified, 0 added, 0 removed)
• Attachments (0 modified, 4 added, 0 removed)
  • SDMX 3-0-0 Major Changes FINAL-1.0_en_5f21cdf9.png
  • SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png
  • SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png
  • SDMX 3-0-0 Major Changes FINAL-1.0_en_f2695ed5.png
• Objects (0 modified, 1 added, 0 removed)
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+SDMX STANDARDS

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Methodology.WebHome

Content

...	...	@@ -1,8 +1,13 @@
	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
...	...	@@ -20,7 +20,7 @@
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 artefacts ([[https:~~/~~/semver.org/>>https://semver.org/||rel="noopener noreferrer" target="_blank"]])
24	24
25	25	**REST Web Services Application Programming Interface (API)**
26	26
...	...	@@ -31,7 +31,7 @@
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 version 3.0 standardising on REST**;**
35	35
36	36	**XML, JSON, CSV and EDI Transmission formats**
37	37
...	...	@@ -60,9 +60,10 @@
60	60
61	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.
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
...	...	@@ -78,14 +78,13 @@
78	78
79	79	Implementors are also recommended to version their API services providing users with an explicit choice of which 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	91	SDMX-ML 1.0/2.0 Generic (time-series) data message
...	...	@@ -101,34 +101,27 @@
101	101	The SDMX-ML structure message is not backwardly compatible primarily due to:
102	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		-
	109	+* Changes to the way the structures are organised into ‘collections’ within the message
108	108	* Deprecation of the Agency, ID, Version option for referencing of structures in messages
109	109	)))
110		-|**SDMX-JSON**|(((
	112	+|(% style="width:130px" %)**SDMX-JSON**|(% style="width:820px" %)(((
111	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.
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		-
	118	+* Changes to the way the structures are organised into ‘collections’ within the message
120	120	* Deprecation of the Agency, ID, 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.**     **
	121	+|(% style="width:130px" %)**SDMX-EDI**|(% style="width:820px" %)The EDI format for both structures and data has been deprecated.
	122	+|(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)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.
124	124	)))
125	125
126		-== //2.3 Information Model// ==
	125	+== 2.3 Information Model ==
127	127
128		-:
129		-
130	130	(((
131		-|**Data Structure Definition**|(((
	128	+(% style="width:955.039px" %)
	129	+|(% style="width:132px" %)**Data Structure Definition**|(% style="width:819px" %)(((
132	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.
133	133
134	134	//Conversion guidance for implementors//
...	...	@@ -137,7 +137,7 @@
137	137
138	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.
139	139	)))
140		-|**Structure mapping model**|(((
	138	+|(% style="width:132px" %)**Structure mapping model**|(% style="width:819px" %)(((
141	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.
142	142
143	143	//Conversion guidance for implementors//
...	...	@@ -146,7 +146,7 @@
146	146
147	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.
148	148	)))
149		-|**Reference metadata model**|(((
	147	+|(% style="width:132px" %)**Reference metadata model**|(% style="width:819px" %)(((
150	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.
151	151
152	152	Version 2.1 reference metadata models are not valid in version 3.0.
...	...	@@ -153,14 +153,11 @@
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.
	154	+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 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.
160	160
161	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.
162	162	)))
163		-|**Constraint model**|(((
	158	+|(% style="width:132px" %)**Constraint model**|(% style="width:819px" %)(((
164	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.
165	165
166	166	//Conversion guidance for implementors//
...	...	@@ -169,7 +169,7 @@
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**|(((
	167	+|(% style="width:132px" %)**Hierarchical codelist structures**|(% style="width:819px" %)(((
173	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.
174	174
175	175	//Conversion guidance for implementors//
...	...	@@ -182,7 +182,7 @@
182	182
183	183	= 3 Information Model =
184	184
185		-== //3.1 Version 3.0 Information Model// ==
	180	+== 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
...	...	@@ -192,7 +192,7 @@
192	192
193	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.
194	194
195		-== //3.2 Key Changes from Version 2.1// ==
	190	+== 3.2 Key Changes from Version 2.1 ==
196	196
197	197	New Maintainable Artefacts
198	198
...	...	@@ -220,7 +220,8 @@
220	220	Removed Maintainable Artefacts
221	221
222	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
	218	+* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association
	219	+* Constraint – replaced by Data Constraint and Metadata Constraint
224	224
225	225	Changed Maintainable Artefacts
226	226
...	...	@@ -234,7 +234,7 @@
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// ==
	233	+== 3.3 Areas Unchanged from Version 2.1 ==
238	238
239	239	The following areas of the information model are unchanged from version 2.1:
240	240
...	...	@@ -247,7 +247,7 @@
247	247	* Reporting taxonomy
248	248	* Process
249	249
250		-== //3.4 Reference Metadata// ==
	246	+== 3.4 Reference Metadata ==
251	251
252	252	Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
253	253
...	...	@@ -275,86 +275,47 @@
275	275	* TITLE – a multi-lingual data attribute
276	276	* SOURCE_AGENCY – a multi-value data attribute
277	277
278		-<Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
	274	+> <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
	275	+> <!—- complex multi-value and multi-lingual data attributes ~-~->
	276	+> <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
	277	+> <Value>
	278	+> <common:Text xml:lang="en">Some English Text</common:Text>
	279	+> <common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
	280	+> </Value>
	281	+> </Comp>
	282	+> <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
	283	+> <Value>4F0</Value>
	284	+> <Value>4D0</Value>
	285	+> <Value>CZ2</Value>
	286	+> </Comp>
	287	+> <!—- metadata attributes are reported like in metadata messages ~-~->
	288	+> <Metadata>
	289	+> <Attribute id="COLLECTION">
	290	+> <Attribute id="METHOD">
	291	+> <Text lang="en">AAA</Text>
	292	+> </Attribute>
	293	+> </Attribute>
	294	+> <Attribute id="CONTACT">
	295	+> <Value>CONTACT 1</Value>
	296	+> <Attribute id="NAME">
	297	+> <Value>Contact 1 Name 1</Value>
	298	+> </Attribute>
	299	+> <Attribute id="NAME">
	300	+> <Value>Contact 1 Name 2</Value>
	301	+> </Attribute>
	302	+> </Attribute>
	303	+> <Attribute id="CONTACT">
	304	+> <Value>CONTACT 2</Value>
	305	+> <Attribute id="NAME">
	306	+> <Value>Contact 2 Name 1</Value>
	307	+> </Attribute>
	308	+> <Attribute id="NAME">
	309	+> <Value>Contact 2 Name 2</Value>
	310	+> </Attribute>
	311	+> </Attribute>
	312	+> </Metadata>
	313	+> </Obs>
279	279
280		-<!—- complex multi-value and multi-lingual data attributes ~-~->
281		-
282		-<Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
283		-
284		-<Value>
285		-
286		-<common:Text xml:lang="en">Some English Text</common:Text>
287		-
288		-<common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
289		-
290		-</Value>
291		-
292		-</Comp>
293		-
294		-<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
295		-
296		-<Value>4F0</Value>
297		-
298		-<Value>4D0</Value>
299		-
300		-<Value>CZ2</Value>
301		-
302		-</Comp>
303		-
304		-<!—- metadata attributes are reported like in metadata messages ~-~->
305		-
306		-<Metadata>
307		-
308		-<Attribute id="COLLECTION">
309		-
310		-<Attribute id="METHOD">
311		-
312		-<Text lang="en">AAA</Text>
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	358	=== New - Metadata Provision Agreement ===
359	359
360	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.
...	...	@@ -367,7 +367,7 @@
367	367
368	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	369
370		-== //3.5 Microdata Exchange// ==
	327	+== 3.5 Microdata Exchange ==
371	371
372	372	Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series.
373	373
...	...	@@ -379,34 +379,21 @@
379	379
380	380	MeasureDimension behaviour as illustrated in the SDMX-ML example below:
381	381
382		-<str:MeasureList id=”MeasureDescriptor”>
	339	+> <str:MeasureList id=”MeasureDescriptor”>
	340	+> <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
	341	+> <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
	342	+> </str:ConceptIdentity>
	343	+> <str:LocalRepresentation>
	344	+> <str:TextFormat textType=”String” isMultiLingual=”true” />
	345	+> </str:LocalRepresentation>
	346	+> <str:ConceptRole>
	347	+> <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
	348	+> </str:ConceptRole>
	349	+> </str:Measure>
	350	+> ...
	351	+> <str:Measure>
	352	+> </str:MeasureList>
383	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	410	=== Multi-value measures and attributes ===
411	411
412	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
...	...	@@ -425,7 +425,7 @@
425	425
426	426	That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.
427	427
428		-== //3.6 Geospatial Data Exchange// ==
	372	+== 3.6 Geospatial Data Exchange ==
429	429
430	430	The version 3.0 model has been extended to provide explicit support for geospatial data.
431	431
...	...	@@ -440,13 +440,13 @@
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	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.
442	442
443		-=== //3.7 Structure Mapping// ===
	387	+== 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 ====
	393	+=== Many-to-many source and target components ===
450	450
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
...	...	@@ -460,19 +460,19 @@
460	460
461	461	The Structure Map may now define input or output components which have a fixed value.
462	462
463		-==== Time representations mapping ====
	407	+=== Time representations mapping ===
464	464
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 ====
	411	+=== Regular expression and substring mappings ===
468	468
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 ====
	415	+=== Item maps validity period ===
472	472
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// ===
	419	+== 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// ===
	434	+== 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// ===
	440	+== 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// ===
	444	+== 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.
	450	+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
...	...	@@ -545,7 +545,7 @@
545	545
546	546	= 5 REST Web Services API =
547	547
548		-== //5.1 Simplified list of resources// ==
	492	+== 5.1 Simplified list of resources ==
549	549
550	550	The version 3.0 REST API has just five main resources:
551	551
...	...	@@ -559,7 +559,7 @@
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// ==
	506	+== 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
...	...	@@ -585,11 +585,12 @@
585	585
586	586	/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 Operators include:
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
	532	+(% style="width:531.039px" %)
	533	+|(% style="width:151px" %)eq|(% style="width:378px" %)Equals
	534	+|(% style="width:151px" %)ne|(% style="width:378px" %)Not equal to
	535	+|(% style="width:151px" %)le|(% style="width:378px" %)Less than
	536	+|(% style="width:151px" %)ge|(% style="width:378px" %)Greater than or equal to
	537	+|(% style="width:151px" %)sw|(% style="width:378px" %)Starts with
593	593
594	594	=== Support for multiple keys ===
595	595
...	...	@@ -597,7 +597,7 @@
597	597
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// ==
	545	+== 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// ==
	561	+== 5.4 Structural metadata maintenance ==
617	617
618	618	Support has been added for maintenance of structural metadata.
619	619
...	...	@@ -621,7 +621,7 @@
621	621
622	622	= 6 XML, JSON, CSV and EDI Transmission formats =
623	623
624		-== //6.1 SDMX-ML// ==
	569	+== 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
...	...	@@ -631,47 +631,49 @@
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
	579	+(% style="width:1102.04px" %)
	580	+|(% style="width:321px" %)**Artefact type**|(% style="width:351px" %)**Version 2.1 Collection**|(% style="width:426px" %)**Version 3.0 Collection**
	581	+|(% style="width:321px" %)AgencyScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)AgencySchemes
	582	+|(% style="width:321px" %)DataConsumerScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)DataConsumerSchemes
	583	+|(% style="width:321px" %)DataProviderScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)DataProviderSchemes
	584	+|(% style="width:321px" %)MetadataProviderScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)MetadataProviderSchemes
	585	+|(% style="width:321px" %)OrganisationUnitScheme|(% style="width:351px" %)OrganisationSchemes|(% style="width:426px" %)OrganisationUnitSchemes
	586	+|(% style="width:321px" %)GeographicCodelist|(% style="width:351px" %)Codelists|(% style="width:426px" %)GeographicCodelists
	587	+|(% style="width:321px" %)GeoGridCodelist|(% style="width:351px" %)Codelists|(% style="width:426px" %)GeoGridCodelists
	588	+|(% style="width:321px" %)ConceptScheme|(% style="width:351px" %)Concepts|(% style="width:426px" %)ConceptSchemes
	589	+|(% style="width:321px" %)ValueList|(% style="width:351px" %)Codelists|(% style="width:426px" %)ValueLists
	590	+|(% style="width:321px" %)StructureMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)StructureMaps
	591	+|(% style="width:321px" %)RepresentationMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)RepresentationMaps
	592	+|(% style="width:321px" %)ConceptSchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)ConceptSchemeMaps
	593	+|(% style="width:321px" %)CategorySchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)CategorySchemeMaps
	594	+|(% style="width:321px" %)OrganisationSchemeMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)OrganisationSchemeMaps
	595	+|(% style="width:321px" %)ReportingTaxonomyMap|(% style="width:351px" %)StructureMappings|(% style="width:426px" %)ReportingTaxonomyMaps
	596	+|(% style="width:321px" %)DataConstraint|(% style="width:351px" %)Constraints|(% style="width:426px" %)DataConstraints
	597	+|(% style="width:321px" %)MetadataConstraint|(% style="width:351px" %)Constraints|(% style="width:426px" %)MetadataConstraints
	598	+|(% style="width:321px" %)MetadataProvisionAgreement|(% style="width:351px" %)ProvisionAgreement|(% style="width:426px" %)MetadataProvisionAgreements
	599	+|(% style="width:321px" %)CustomTypeScheme|(% style="width:351px" %)CustomTypes|(% style="width:426px" %)CustomTypeSchemes
	600	+|(% style="width:321px" %)VtlMappingScheme|(% style="width:351px" %)VtlMappings|(% style="width:426px" %)VtlMappingSchemes
	601	+|(% style="width:321px" %)NamePersonalisationScheme|(% style="width:351px" %)NamePersonalisations|(% style="width:426px" %)NamePersonalisationSchemes
	602	+|(% style="width:321px" %)RulesetScheme|(% style="width:351px" %)Rulesets|(% style="width:426px" %)RulesetSchemes
	603	+|(% style="width:321px" %)TransformationScheme|(% style="width:351px" %)Transformations|(% style="width:426px" %)TransformationSchemes
	604	+|(% 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
	608	+(% style="width:1106.04px" %)
	609	+|(% style="width:326px" %)**Artefact type**|(% style="width:776px" %)**Collection**
	610	+|(% style="width:326px" %)Dataflow|(% style="width:776px" %)Dataflows
	611	+|(% style="width:326px" %)Metadataflow|(% style="width:776px" %)Metadataflows
	612	+|(% style="width:326px" %)CategoryScheme|(% style="width:776px" %)CategorySchemes
	613	+|(% style="width:326px" %)Categorisation|(% style="width:776px" %)Categorisations
	614	+|(% style="width:326px" %)Codelist|(% style="width:776px" %)Codelists
	615	+|(% style="width:326px" %)Hierarchy|(% style="width:776px" %)Hierarchies
	616	+|(% style="width:326px" %)HierarchyAssociation|(% style="width:776px" %)HierarchyAssociations
	617	+|(% style="width:326px" %)MetadataStructure|(% style="width:776px" %)MetadataStructures
	618	+|(% style="width:326px" %)DataStructure|(% style="width:776px" %)DataStructures
	619	+|(% style="width:326px" %)ReportingTaxonomy|(% style="width:776px" %)ReportingTaxonomies
	620	+|(% style="width:326px" %)Process|(% style="width:776px" %)Processes
	621	+|(% 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
...	...	@@ -705,7 +705,7 @@
705	705
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// ==
	655	+== 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
...	...	@@ -725,7 +725,7 @@
725	725
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// ==
	675	+== 6.3 SDMX-CSV ==
729	729
730	730	CSV in SDMX is used transmission of data and reference metadata only.
731	731
...	...	@@ -743,7 +743,7 @@
743	743
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// ===
	693	+=== 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_5f21cdf9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+103.2 KB

Content

SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+148.8 KB

Content

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

SDMX 3-0-0 Major Changes FINAL-1.0_en_f2695ed5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+5.7 KB

Content

SUZ.Methodology.Code.MethodologyClass[0]