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

Summary

Details

Page properties
Content
... ... @@ -94,10 +94,13 @@
94 94  The following legacy XML data messages have been deprecated:
95 95  
96 96  SDMX-ML 1.0/2.0 Generic (time-series) data message
97 +
97 97  SDMX-ML 1.0/2.0 Compact (time-series) data message
99 +
98 98  SDMX-ML 1.0/2.0 Utility (time-series) data message
99 -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)
100 100  
102 +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)
103 +
101 101  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.
102 102  
103 103  The SDMX-ML structure message is not backwardly compatible primarily due to:
... ... @@ -555,8 +555,8 @@
555 555  
556 556  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.
557 557  
558 -(% class="wikigeneratedid" id="HStructuremessage" %)
559 -**Structure message**
561 +=== Structure message ===
562 +
560 560  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.
561 561  
562 562  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:
... ... @@ -607,8 +607,8 @@
607 607  
608 608  From version 3.0, collections can appear in any order within a structure message.
609 609  
610 -(% class="wikigeneratedid" id="HDatamessages" %)
611 -**Data messages**
613 +=== Data messages ===
614 +
612 612  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.
613 613  
614 614  Specifically, the following data messages are not supported in version 3.0:
... ... @@ -625,16 +625,16 @@
625 625  
626 626  The time series variant of the Structure Specific Data message is no longer used.
627 627  
628 -(% class="wikigeneratedid" id="HReferencemetadatamessage" %)
629 -**Reference metadata message**
631 +=== Reference metadata message ===
632 +
630 630  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.
631 631  
632 -(% class="wikigeneratedid" id="HRegistrystructuralmetadata2018query2019messages" %)
633 -**Registry structural metadata ‘query’ messages**
635 +=== Registry structural metadata ‘query’ messages ===
636 +
634 634  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.
635 635  
636 -(% class="wikigeneratedid" id="HStructurereferencing" %)
637 -**Structure referencing**
639 +=== Structure referencing ===
640 +
638 638  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.
639 639  
640 640  == 6.2 SDMX-JSON ==
... ... @@ -641,20 +641,20 @@
641 641  
642 642  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.
643 643  
644 -(% class="wikigeneratedid" id="HStructuremessage-1" %)
645 -**Structure message**
647 +=== Structure message ===
648 +
646 646  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.
647 647  
648 -(% class="wikigeneratedid" id="HDatamessage" %)
649 -**Data message**
651 +=== Data message ===
652 +
650 650  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.
651 651  
652 -(% class="wikigeneratedid" id="HReferencemetadatamessage-1" %)
653 -**Reference metadata message**
655 +=== Reference metadata message ===
656 +
654 654  The SDMX-JSON metadata message has also been updated to support the version 3.0 reference metadata and Metadataset specifications.
655 655  
656 -(% class="wikigeneratedid" id="HStructurereferencing-1" %)
657 -**Structure referencing**
659 +=== Structure referencing ===
660 +
658 658  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.
659 659  
660 660  == 6.3 SDMX-CSV ==
... ... @@ -661,8 +661,8 @@
661 661  
662 662  CSV in SDMX is used transmission of data and reference metadata only.
663 663  
664 -(% class="wikigeneratedid" id="HDatamessage-1" %)
665 -**Data message**
667 +=== Data message ===
668 +
666 666  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:
667 667  
668 668  * 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
... ... @@ -671,11 +671,11 @@
671 671  
672 672  * 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.
673 673  
674 -(% class="wikigeneratedid" id="HReferencemetadatamessage-2" %)
675 -**Reference metadata message**
677 +=== Reference metadata message ===
678 +
676 676  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.
677 677  
678 -== 6.4 EDI deprecation ==
681 +=== 6.4 EDI deprecation ===
679 679  
680 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