Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 17.1
edited by Helena
on 2025/05/16 13:25
Change comment: There is no comment for this version
To version 16.6
edited by Helena
on 2025/05/16 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -523,11 +523,10 @@
523 523  |(% style="width:151px" %)ge|(% style="width:378px" %)Greater than or equal to
524 524  |(% style="width:151px" %)sw|(% style="width:378px" %)Starts with
525 525  
526 -(% class="wikigeneratedid" id="HSupportformultiplekeys" %)
527 -**Support for multiple keys**
526 +=== Support for multiple keys ===
527 +
528 528  Queries can now specify multiple series keys.
529 529  
530 -(% class="wikigeneratedid" %)
531 531  /data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG
532 532  
533 533  == 5.3 Improved reference metadata queries ==
... ... @@ -558,8 +558,8 @@
558 558  
559 559  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.
560 560  
561 -(% class="wikigeneratedid" id="HStructuremessage" %)
562 -**Structure message**
560 +=== Structure message ===
561 +
563 563  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.
564 564  
565 565  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:
... ... @@ -610,8 +610,8 @@
610 610  
611 611  From version 3.0, collections can appear in any order within a structure message.
612 612  
613 -(% class="wikigeneratedid" id="HDatamessages" %)
614 -**Data messages**
612 +=== Data messages ===
613 +
615 615  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.
616 616  
617 617  Specifically, the following data messages are not supported in version 3.0:
... ... @@ -628,16 +628,16 @@
628 628  
629 629  The time series variant of the Structure Specific Data message is no longer used.
630 630  
631 -(% class="wikigeneratedid" id="HReferencemetadatamessage" %)
632 -**Reference metadata message**
630 +=== Reference metadata message ===
631 +
633 633  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.
634 634  
635 -(% class="wikigeneratedid" id="HRegistrystructuralmetadata2018query2019messages" %)
636 -**Registry structural metadata ‘query’ messages**
634 +=== Registry structural metadata ‘query’ messages ===
635 +
637 637  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.
638 638  
639 -(% class="wikigeneratedid" id="HStructurereferencing" %)
640 -**Structure referencing**
638 +=== Structure referencing ===
639 +
641 641  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.
642 642  
643 643  == 6.2 SDMX-JSON ==
... ... @@ -644,20 +644,20 @@
644 644  
645 645  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.
646 646  
647 -(% class="wikigeneratedid" id="HStructuremessage-1" %)
648 -**Structure message**
646 +=== Structure message ===
647 +
649 649  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.
650 650  
651 -(% class="wikigeneratedid" id="HDatamessage" %)
652 -**Data message**
650 +=== Data message ===
651 +
653 653  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.
654 654  
655 -(% class="wikigeneratedid" id="HReferencemetadatamessage-1" %)
656 -**Reference metadata message**
654 +=== Reference metadata message ===
655 +
657 657  The SDMX-JSON metadata message has also been updated to support the version 3.0 reference metadata and Metadataset specifications.
658 658  
659 -(% class="wikigeneratedid" id="HStructurereferencing-1" %)
660 -**Structure referencing**
658 +=== Structure referencing ===
659 +
661 661  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.
662 662  
663 663  == 6.3 SDMX-CSV ==
... ... @@ -664,8 +664,8 @@
664 664  
665 665  CSV in SDMX is used transmission of data and reference metadata only.
666 666  
667 -(% class="wikigeneratedid" id="HDatamessage-1" %)
668 -**Data message**
666 +=== Data message ===
667 +
669 669  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:
670 670  
671 671  * 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
... ... @@ -674,8 +674,8 @@
674 674  
675 675  * 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.
676 676  
677 -(% class="wikigeneratedid" id="HReferencemetadatamessage-2" %)
678 -**Reference metadata message**
676 +=== Reference metadata message ===
677 +
679 679  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.
680 680  
681 681  === 6.4 EDI deprecation ===