Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 16.8
edited by Helena
on 2025/05/16 13:24
Change comment: There is no comment for this version
To version 16.3
edited by Helena
on 2025/05/16 13:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -457,8 +457,8 @@
457 457  
458 458  Additional constructs are possible for dependency management when referencing structures. For instance:
459 459  
460 -2.3+.1  Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
461 -2+.3.1  Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
460 +2.3+.1 Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
461 +2+.3.1 Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
462 462  
463 463  == Draft structures ==
464 464  
... ... @@ -466,10 +466,12 @@
466 466  
467 467  MAJOR.MINOR.PATCH-EXTENSION
468 468  
469 -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.
470 -1.10.0-unstable  Alternative to -draft.
471 -1.10.0-notfinal  Alternative to -draft.
469 +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.
472 472  
471 +1.10.0-unstable Alternative to -draft.
472 +
473 +1.10.0-notfinal Alternative to -draft.
474 +
473 473  The SDMX 2.1 isFinal property is deprecated in 3.0.
474 474  
475 475  = 5 REST Web Services API =
... ... @@ -492,8 +492,8 @@
492 492  
493 493  Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow.
494 494  
495 -(% class="wikigeneratedid" id="HExtendthecontextofdataretrieval" %)
496 -**Extend the context of data retrieval**
497 +=== Extend the context of data retrieval ===
498 +
497 497  Version 2.1 data queries always retrieved data from a single specific Dataflow. In version 3.0, the query context may be specified as:
498 498  
499 499  * Dataflow;
... ... @@ -502,20 +502,18 @@
502 502  
503 503  Data queries may also search across datasets, for instance “retrieve all data about a country”.
504 504  
505 -(% class="wikigeneratedid" id="HComponent-basedfilters" %)
506 -**Component-based filters**
507 +=== Component-based filters ===
508 +
507 507  Expressions filtering on individual components can now be included as part of the data query URL.
508 508  
509 509  /data/dataflow/ESTAT/ICP?c[REF_AREA]=CH&c[CONF_STATUS]=F
510 510  
511 -(% class="wikigeneratedid" id="HSupportforoperators" %)
512 -**Support for operators**
513 +=== Support for operators ===
514 +
513 513  Filter expressions can also include operators.
514 514  
515 -/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015
517 +/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 Operators include:
516 516  
517 -Operators include:
518 -
519 519  (% style="width:531.039px" %)
520 520  |(% style="width:151px" %)eq|(% style="width:378px" %)Equals
521 521  |(% style="width:151px" %)ne|(% style="width:378px" %)Not equal to
... ... @@ -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 ==