Interoperability Basis Platform

• 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/]]

25

26

**REST Web Services Application Programming Interface (API)**

27

28

* Change to a single ‘structure’ resource for structure queries simplifying the REST API specification by reducing the number of resources to five

29

* Improvements to data queries

30

* Improvements to reference metadata queries

31

* Support for structural metadata maintenance using HTTP PUT, POST and DELETE verbs

32

33

**SOAP Web Services API**

34

35

• The SOAP web services API has been deprecated with version 3.0 standardising on REST** **

36

37

**XML, JSON, CSV and EDI Transmission formats**

38

39

* The SDMX-ML, SDMX-JSON and SDMX-CSV specifications have been extended and modified where needed to support the new features and changes such as reference metadata and microdata

40

* Obsolete SDMX-ML data message variants including Generic, Compact, Utility and Cross-sectional have been deprecated standardising on Structure Specific Data as the sole XML format for data exchange

41

* The SDMX-EDI transmission format for structures and data has been deprecated

42

* The organisation of structures into ‘collections’ in SDMX-ML and SDMX-JSON structure messages has been flattened and simplified

43

* The option to reference structures in SDMX-ML and SDMX-JSON messages using Agency, ID and Version has been deprecated with URN now exclusively used for all non-local referencing purpose

**Breaking Changes**

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.

48

49

A summary of the main breaking changes is given in chapter 2.

50

51

**Content of the Document**

52

53

The remainder of the document provides a summary of the main changes. More detailed information can be found the SDMX 3.0 Technical Specifications, in particular:

54

55

* Section 2 – Information Model

56

* Section 5 – Registry Specification

57

* Section 6 – Technical Notes

58

* SDMX-TWG GitHub for the REST API and the XML, JSON and CSV formats

59

60

= 2 Summary of Breaking Changes in 3.0 =

61

62

Version 3.0 introduces breaking changes into the web services API, transmission formats and information model. A summary is given in the table below.

63

64

== //2.1 Web Services API// ==

65

66

|**REST API**|(((

67

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:

* Structure queries

* Data queries

* Metadata queries

* Availability queries

73

74

Schema queries are backwardly compatible.

75

76

//Guidance for implementors//

77

78

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.

79

80

Implementors are also recommended to version their API services providing users with an explicit choice of which version to use.

81

)))

82

|**SOAP API**|The SOAP API has been deprecated.

83

84

== //2.2 Transmission Formats// ==

:

(((

|**SDMX-ML**|(((

The following legacy XML data messages have been deprecated:

91

92

SDMX-ML 1.0/2.0 Generic (time-series) data message

93

94

SDMX-ML 1.0/2.0 Compact (time-series) data message

95

96

SDMX-ML 1.0/2.0 Utility (time-series) data message

97

98

SDMX-ML 1.0/2.0 Cross-Sectional data message SDMX-ML 2.1 Generic data messages (for observations, time-series and cross-sectional data)

99

100

Structure Specific is the only data message option in version 3.0 but is not backwardly compatible with version 2.1 due to several changes including deprecation of the option to reference structures like the DSD, Dataflow and Provision Agreement using their Agency, ID and Version. The time series variant of the message has also been deprecated.

101

102

The SDMX-ML structure message is not backwardly compatible primarily due to:

103

104

* Changes to the information model

105

* Changes to the way the structures are organised into

106

107

‘collections’ within the message

108

109

* Deprecation of the Agency, ID, Version option for referencing of structures in messages

110

)))

111

|**SDMX-JSON**|(((

112

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.

113

114

The JSON structure message is not backwardly compatible primarily due to:

115

116

* Changes to the information model

117

* Changes to the way the structures are organised into

118

119

‘collections’ within the message

120

121

* Deprecation of the Agency, ID, Version option for referencing of structures in messages

122

)))

123

|**SDMX-EDI**|The EDI format for both structures and data has been deprecated.

124

|**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.**     **

125

)))

126

127

== //2.3 Information Model// ==

:

(((

|**Data Structure Definition**|(((

133

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.

134

135

//Conversion guidance for implementors//

136

137

Version 2.1 DSDs can be converted to the 3.0 model by creating a measure with the “MEASURE” concept role applied as described in paragraph 3.5.

138

139

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.

140

)))

141

|**Structure mapping model**|(((

142

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.

143

144

//Conversion guidance for implementors//

145

146

Version 2.1 structure sets can be practically converted to the version 3.0 structure mapping model.

147

148

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.

149

)))

150

|**Reference metadata model**|(((

151

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.

152

153

Version 2.1 reference metadata models are not valid in version 3.0.

154

155

//Conversion guidance for implementors//

156

157

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

158

)))

159

| |(((

160

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.

161

162

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.

163

)))

164

|**Constraint model**|(((

165

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.

166

167

//Conversion guidance for implementors//

168

169

2.1 Content Constraints can be converted without loss to the equivalent version 3.0 Data Constraint model.

170

171

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.

172

)))

173

|**Hierarchical codelist structures**|(((

174

The version 2.1 Hierarchical Codelist artefact has been deprecated in version 3.0 and replaced by two new artefacts, Hierarchy and Hierarchy Association.

175

176

//Conversion guidance for implementors//

177

178

Version 2.1 Hierarchical Codelists can be successfully converted to the version 3.0 hierarchy model. Information on which artefacts to link the hierarchies to on what context would need to be added as a separate procedure.

179

180

Conversion from the version 3.0 model to version 2.1 is possible, but with loss of the linking information

)))

)))

= 3 Information Model =

185

186

== //3.1 Version 3.0 Information Model// ==

187

188

[[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png||height="404" width="718"]]

189

190

//Figure 1 Version 3.0 simplified Information Model UML class diagram with ‘heat map’ illustrating the areas with most change//

191

192

The schematic above is a simplified UML class diagram of the SDMX 3.0 information model illustrating the major areas of change as a ‘heat map’. Darker colours indicate where new structures have been added in version 3.0 or where structures have been significantly changed.

193

194

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.

195

196

== //3.2 Key Changes from Version 2.1// ==

197

198

New Maintainable Artefacts

* Structure Map

* Representation Map

* Organisation Scheme Map

203

* Concept Scheme Map

204

* Category Scheme Map

205

* Reporting Taxonomy Map

206

* Value List

207

* Hierarchy

208

* Hierarchy Association

209

* Metadata Constraint

210

* Data Constraint

211

* Metadata Provision Agreement

212

* Metadata Provider Scheme

213

* Metadataset

214

215

New Identifiable Artefacts

* GeoFeatureSetCode

* GeoGridCode

* Metadata Provider

Removed Maintainable Artefacts

222

223

* Structure Set – replaced by Structure Map and the four item scheme maps

224

* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association • Constraint – replaced by Data Constraint and Metadata Constraint

225

226

Changed Maintainable Artefacts

227

228

* Data Structure Definition – support for microdatasets and reference metadata linked to data

229

* Metadataflow – simplifies exchange of reference metadata, in particular those linked to structures

230

* Metadata Structure Definition – simplified model for reference metadata

231

* Codelist – support for codelist extension and geospatial specialised codelists (GeographicCodelist, GeoGridCodelist)

232

* VTL Mapping Scheme – VTL Concept Mapping Scheme removed to align the VTL / SDMX interface with the 3.0 model

233

234

New Component Representation Types

235

236

* GeospatialInformation – a string type where the value is an expression defining a set of geographical features using a purpose-designed syntax

237

238

== //3.3 Areas Unchanged from Version 2.1// ==

239

240

The following areas of the information model are unchanged from version 2.1:

* Categories

* Concepts

* Data providers

* Agencies

* Data consumers

* VTL transformation and expressions – with the exception of VTL mapping scheme as already noted

* Reporting taxonomy

* Process

== //3.4 Reference Metadata// ==

252

253

Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.

254

255

=== Simplify Metadata Structure Definition ===

256

257

The Metadata Structure Definition (MSD) has been simplified to remove target information, and the support of multiple report structures. The MSD now only contains Metadata Attributes which are used to define the structure of a report.

258

259

[[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png||height="346" width="494"]]

260

261

//Figure 2 version 2.1 Metadata Structure Definition (MSD)//

262

263

[[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_f2695ed5.png||height="172" width="374"]]

264

265

//Figure 3 the simplified version 3.0 MSD//

266

267

=== Change to reference metadata reported against data ===

268

269

Reference metadata associated with datasets, data series or observations are now reported with the data. The dataset’s DSD must reference an MSD to define the structure of its reference metadata. In practice reference metadata for data are transmitted as part of the data message. The metadata attributes are treated in a similar way to the data attributes appearing in the message at the dataset, data series or individual observation level as appropriate. In contrast to simple data attributes, metadata attributes defined by an MSD can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata attributes appear in data messages structured in the same way as metadata messages.

270

271

The SDMX-ML example below is an excerpt from a structure specific data message illustrating reporting of reference metadata with a hierarchical structure at the observation level.

272

273

For completeness, the excerpt also shows:

274

275

* OBS_STATUS – a simple observation-level data attribute

276

* TITLE – a multi-lingual data attribute

277

* SOURCE_AGENCY – a multi-value data attribute

<!—- complex multi-value and multi-lingual data attributes ~-~->

<Value>

<common:Text xml:lang="en">Some English Text</common:Text>

288

289

<common:Text xml:lang="fr">Quelques textes en anglais</common:Text>

</Value>

</Comp>

</Comp>

<!—- metadata attributes are reported like in metadata messages ~-~->

</Attribute>

</Attribute>

<Value>CONTACT 1</Value>

<Value>Contact 1 Name 1</Value>

</Attribute>

<Value>Contact 1 Name 2</Value>

</Attribute>

</Attribute>

<Value>CONTACT 2</Value>

<Value>Contact 2 Name 1</Value>

</Attribute>

<Value>Contact 2 Name 2</Value>

</Attribute>

</Attribute>

</Metadata>

</Obs>

=== New - Metadata Provision Agreement ===

360

361

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.

362

363

=== Move target to Metadataflow and Metadata Provision Agreement ===

364

365

For reference metadata that is reported against structures, the allowable targets information which is used to specify what structures the reference metadata can be reported against, has moved to the Metadataflow and can be further refined in the Metadata Provision Agreement.

366

367

=== Add maintainable properties to reference metadata ===

368

369

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.

370

371

== //3.5 Microdata Exchange// ==

372

373

Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series.

374

375

=== Multiple measures ===

376

377

Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the

378

379

Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1

380

381

MeasureDimension behaviour as illustrated in the SDMX-ML example below:

382

383

<str:MeasureList id=”MeasureDescriptor”>

384

385

<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>

</str:ConceptIdentity>

390

391

<str:LocalRepresentation>

392

393

<str:TextFormat textType=”String” isMultiLingual=”true” />

394

395

</str:LocalRepresentation>

<str:ConceptRole>

</str:ConceptRole>

</str:Measure>

...

<str:Measure>

</str:MeasureList>

=== Multi-value measures and attributes ===

412

413

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

414

415

//mandatory// or optional. In the SDMX-ML measure example above, the properties

416

417

//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.

418

419

=== Attributes relationship to measures ===

420

421

In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.

=== Value lists ===

Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers.

426

427

That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.

428

429

== //3.6 Geospatial Data Exchange// ==

430

431

The version 3.0 model has been extended to provide explicit support for geospatial data.

432

433

=== GeospatialInformation type ===

434

435

A new GeospatialInformation string type has been added which can be used as the 214 representation for any dimension, attribute or measure component. The value which is a 215 string expression conforming to the syntax defined in Section 6 of the technical 216 specifications precisely defines a ‘Geo Feature Set’ – a collection of geographical 217 features like points, lines or polygons. Its use is recommended in conjunction with the “GEO_FEATURE_SET” concept role.

436

437

=== Geospatial code lists ===

438

439

Two new specialised types of code list have been added where the definition of each code includes additional geospatial information in addition to the standard ID, name and description:

440

441

* 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.

442

* 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.

443

444

=== //3.7 Structure Mapping// ===

445

446

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.

447

448

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.

449

450

==== Many-to-many source and target components ====

451

452

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:

453

454

Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.

455

456

Similarly, an n-n rule may also set the values of any number of output components:

457

458

Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.

459

460

**Fixed source and target**

461

462

The Structure Map may now define input or output components which have a fixed value.

463

464

==== Time representations mapping ====

465

466

Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.

467

468

==== Regular expression and substring mappings ====

469

470

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.

471

472

==== Item maps validity period ====

473

474

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.

475

476

=== //3.8 Constraints// ===

477

478

Constraints in version 3.0 are modelled using two separate artefacts which replace the version 2.1 content constraint:

479

480

* data constraint for data; and

481

* metadata constraint for reference metadata.

482

483

Metadata constraint differs from its data counterpart in having a simplified cube region model better suited to reference metadata reporting use cases and not carrying details of the constrained targets – that information instead being defined directly within the metadataflow and Metadata Provision Agreement. Thus, metadata related constraints only specify constraints to the values of metadata attributes.

484

485

The ‘%’ wildcard character can now be used when defining cube region constraints to match multiple codes with a single expression, for instance for economic activity, ISIC4_% matches all codes beginning with ‘ISIC4_’ avoiding the need to maintain an explicit list.

486

487

The validity period definition has been moved from the constraint to the individual constraining terms, specifically CubeRegion, DataKeySet and MetadataTargetRegion providing more granular control.

488

489

Attachment constraints have been deprecated due to a lack of use cases.

490

491

=== //3.9 Code List Extension// ===

492

493

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.

494

495

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.

496

497

=== //3.10 Discriminated Union of Code Lists// ===

498

499

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.

500

501

=== //3.11 Code Hierarchies// ===

502

503

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).

504

505

= 4 Versioning of Structural Metadata Artefacts =

506

507

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.

508

509

Semantic version numbers are three digits:

MAJOR.MINOR.PATCH

Where

* The first digit (major) indicates that changes (either new features or bug fixes) are not backward compatible.

516

* The second digit (minor) indicates that features have been added in a backward compatible manner.

517

* The third digit (patch) indicates that bugs have been fixed in a backward compatible manner.

Examples:

SDMX:CL_AREA(1.0.0)

SDMX:CL_AREA(2.3.2)

== Dependency management ==

526

527

Additional constructs are possible for dependency management when referencing structures. For instance:

528

529

2.3+.1 Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).

530

531

2+.3.1 Means the currently latest available version >= “2.3.1” (even if not backwards compatible).

532

533

== Draft structures ==

534

535

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.

536

537

MAJOR.MINOR.PATCH-EXTENSION

538

539

1.10.0-draft Means that version 1.10.0 is still being modified and may change – equivalent to setting isFinal=false in SDMX 2.1.

540

541

1.10.0-unstable Alternative to -draft.

542

543

1.10.0-notfinal Alternative to -draft.

544

545

The SDMX 2.1 isFinal property is deprecated in 3.0.

546

547

= 5 REST Web Services API =

548

549

== //5.1 Simplified list of resources// ==

550

551

The version 3.0 REST API has just five main resources:

* structure

* data

* schema

* availability

* metadata

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.

560

561

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.

562

563

== //5.2 Improved data queries// ==

564

565

Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow.

566

567

=== Extend the context of data retrieval ===

568

569

Version 2.1 data queries always retrieved data from a single specific Dataflow. In version 3.0, the query context may be specified as:

570

571

* Dataflow;

572

* Data Structure Definition – i.e., all Dataflows that use it; or

573

* Provision Agreement – i.e., all Dataflows associated with it.

574

575

Data queries may also search across datasets, for instance “retrieve all data about a country”.

576

577

=== Component-based filters ===

578

579

Expressions filtering on individual components can now be included as part of the data query URL.

580

581

/data/dataflow/ESTAT/ICP?c[REF_AREA]=CH&c[CONF_STATUS]=F

582

583

=== Support for operators ===

584

585

Filter expressions can also include operators.

586

587

/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 Operators include:

|eq|Equals

|ne|Not equal to

|le|Less than

|ge|Greater than or equal to

593

|sw|Starts with

594

595

=== Support for multiple keys ===

596

597

Queries can now specify multiple series keys.

598

599

/data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG

600

601

== //5.3 Improved reference metadata queries// ==

602

603

Reference metadata queries have been improved with a number of new options to retrieve metadata reports.

604

605

**Get metadata reports by ID**

606

607

/metadata/metadataset/ESTAT/QUALITY_REPORT/1.0.0

608

609

**Get metadata reports by Dataflow**

610

611

/metadata/metadataflow/ECB/METHODOLOGY/*/FR2

612

613

**Get metadata reports about a Data Structure Definition**

614

615

/metadata/structure/datastructure/BIS/BIS_CBS/1.0

616

617

== //5.4 Structural metadata maintenance// ==

618

619

Support has been added for maintenance of structural metadata.

620

621

HTTP verbs PUT, POST and DELETE may be used to submit SDMX-ML or SDMX-JSON structure messages to an SDMX registry for the purposes of adding, updating or deleting structural metadata artefacts.

622

623

= 6 XML, JSON, CSV and EDI Transmission formats =

624

625

== //6.1 SDMX-ML// ==

626

627

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.

628

629

=== Structure message ===

630

631

The SDMX-ML structure message is used for transmission of structural metadata. It closely reflects the SDMX information model and has therefore been significantly updated for version 3.0 with the addition of new structures, modifications where structures have changed, and removal of deprecated structures like Structure Set.

632

633

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:

634

635

|**Artefact type**|**Version 2.1 Collection**|**Version 3.0 Collection**

636

|AgencyScheme|OrganisationSchemes|AgencySchemes

637

|DataConsumerScheme|OrganisationSchemes|DataConsumerSchemes

638

|DataProviderScheme|OrganisationSchemes|DataProviderSchemes

639

|MetadataProviderScheme|OrganisationSchemes|MetadataProviderSchemes

640

|OrganisationUnitScheme|OrganisationSchemes|OrganisationUnitSchemes

641

|GeographicCodelist|Codelists|GeographicCodelists

642

|GeoGridCodelist|Codelists|GeoGridCodelists

643

|ConceptScheme|Concepts|ConceptSchemes

644

|ValueList|Codelists|ValueLists

645

|StructureMap|StructureMappings|StructureMaps

646

|RepresentationMap|StructureMappings|RepresentationMaps

647

|ConceptSchemeMap|StructureMappings|ConceptSchemeMaps

648

|CategorySchemeMap|StructureMappings|CategorySchemeMaps

649

|OrganisationSchemeMap|StructureMappings|OrganisationSchemeMaps

650

|ReportingTaxonomyMap|StructureMappings|ReportingTaxonomyMaps

651

|DataConstraint|Constraints|DataConstraints

652

|MetadataConstraint|Constraints|MetadataConstraints

653

|MetadataProvisionAgreement|ProvisionAgreement|MetadataProvisionAgreements

654

|CustomTypeScheme|CustomTypes|CustomTypeSchemes

655

|VtlMappingScheme|VtlMappings|VtlMappingSchemes

656

|NamePersonalisationScheme|NamePersonalisations|NamePersonalisationSchemes

657

|RulesetScheme|Rulesets|RulesetSchemes

658

|TransformationScheme|Transformations|TransformationSchemes

659

|UserDefinedOperatorScheme|UserDefinedOperators|UserDefinedOperatorSchemes

660

661

No changes have been made to the way the following artefacts are organised in the structure message:

662

663

|**Artefact type**|**Collection**

664

|Dataflow|Dataflows

665

|Metadataflow|Metadataflows

666

|CategoryScheme|CategorySchemes

667

|Categorisation|Categorisations

668

|Codelist|Codelists

669

|Hierarchy|Hierarchies

670

|HierarchyAssociation|HierarchyAssociations

671

|MetadataStructure|MetadataStructures

672

|DataStructure|DataStructures

673

|ReportingTaxonomy|ReportingTaxonomies

674

|Process|Processes

675

|ProvisionAgreement|ProvisionAgreements

676

677

From version 3.0, collections can appear in any order within a structure message.

678

679

=== Data messages ===

680

681

All legacy SDMX-ML data messages have been deprecated with the exception of Structure Specific Data which becomes the sole standard format for transmission of SDMX data in XML in version 3.0.

682

683

Specifically, the following data messages are not supported in version 3.0:

684

685

* SDMX-ML 1.0/2.0 Generic (time-series) data message

686

* SDMX-ML 1.0/2.0 Compact (time-series) data message

687

* SDMX-ML 1.0/2.0 Utility (time-series) data message

688

* SDMX-ML 1.0/2.0 Cross-Sectional data message

689

* SDMX-ML 2.1 Generic data messages (for observations, time-series and crosssectional data)

690

691

The Structure Specific Data message has been extended to support the transmission of microdata sets, in particular those with multiple measures and array values for measures and attributes.

692

693

As detailed in paragraph 3.4, the message now additionally allows data’s reference metadata to be reported as an integral part of the dataset. Like data attributes, these metadata attributes are included in the data message at the dataset, series or observation level as appropriate.

694

695

The time series variant of the Structure Specific Data message is no longer used.

696

697

=== Reference metadata message ===

698

699

The Generic Metadata message remains the standard format for transmission of reference metadata sets in XML but has been modified to support the revised version 3.0 reference metadata model.

700

701

=== Registry structural metadata ‘query’ messages ===

702

703

As a consequence of the deprecation of the SOAP API and standardisation on REST, the structural metadata ‘query’ messages have all been removed. In version 3.0, querying an SDMX Registry for structural metadata is performed solely using REST GET.

704

705

=== Structure referencing ===

706

707

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.

708

709

== //6.2 SDMX-JSON// ==

710

711

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.

712

713

=== Structure message ===

714

715

The SDMX-JSON structure message closely replicates the SDMX-ML equivalent. Like that of SDMX-ML it has been updated to align it with the version 3.0 information model with addition, deletion and modification of artefacts as required. The organisation of the structure collections has also been revised as detailed in paragraph 6.1.

=== Data message ===

The SDMX-JSON data message has similarly be updated. Additional changes have been made to allow a single message to carry data from multiple datasets with potentially different Data Structure Definitions to support REST data queries of the form “retrieve all data about a country”. For this reason, the version 3.0 SDMX-JSON is not backwardly compatible with version 2.1 data messages. Support has been added for the transmission of microdata and reporting of reference metadata on data as an integral part of the dataset.

720

721

=== Reference metadata message ===

722

723

The SDMX-JSON metadata message has also been updated to support the version 3.0 reference metadata and Metadataset specifications.

724

725

=== Structure referencing ===

726

727

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.

728

729

== //6.3 SDMX-CSV// ==

730

731

CSV in SDMX is used transmission of data and reference metadata only.

=== Data message ===

The SDMX-CSV data message has been modified to align with the version 3.0 information model, support the enhanced REST API and ensure that data can be freely converted to and from the XML and JSON formats without loss. These changes include:

736

737

* An additional column identifying the type if the artefact defining the structure of the data: “dataflow”, “datastructure” or “dataprovision”; • A column for the structure artefact’s identification of the form

738

739

ESTAT:NA_MAIN(1.6.0) which replaces the dataflow identifier in version 2.1; and

740

741

* A column for the dataset action: information, append, replace or delete, which is consistent with both the the SDMX-ML and SDMX-JSON data messages.

742

743

=== Reference metadata message ===

744

745

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.

746

747

=== //6.4 EDI deprecation// ===

748

749

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.

750

751

= Appendix A – Version 2.1 Information Model =

752

753

[[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_5f21cdf9.png||height="319" width="718"]]

Wiki source code of 1 Overview