Changes for page SDMX 3.0 Standards. Summary of Major Changes and New Functionality
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -247,8 +247,8 @@ 247 247 248 248 Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases. 249 249 250 -= ==SimplifyMetadataStructureDefinition===251 - 250 +(% class="wikigeneratedid" id="HSimplifyMetadataStructureDefinition" %) 251 +**Simplify Metadata Structure Definition** 252 252 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. 253 253 254 254 [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png||height="346" width="494"]] ... ... @@ -363,12 +363,12 @@ 363 363 364 364 The version 3.0 model has been extended to provide explicit support for geospatial data. 365 365 366 -= ==GeospatialInformationtype===367 - 366 +(% class="wikigeneratedid" id="HGeospatialInformationtype" %) 367 +**GeospatialInformation type** 368 368 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. 369 369 370 -= ==Geospatialcodelists===371 - 370 +(% class="wikigeneratedid" id="HGeospatialcodelists" %) 371 +**Geospatial code lists** 372 372 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: 373 373 374 374 * 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. ... ... @@ -451,7 +451,6 @@ 451 451 Examples: 452 452 453 453 SDMX:CL_AREA(1.0.0) 454 - 455 455 SDMX:CL_AREA(2.3.2) 456 456 457 457 == Dependency management == ... ... @@ -458,10 +458,9 @@ 458 458 459 459 Additional constructs are possible for dependency management when referencing structures. For instance: 460 460 461 -2.3+.1 Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”). 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 -2+.3.1 Means the currently latest available version >= “2.3.1” (even if not backwards compatible). 464 - 465 465 == Draft structures == 466 466 467 467 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. ... ... @@ -468,12 +468,10 @@ 468 468 469 469 MAJOR.MINOR.PATCH-EXTENSION 470 470 471 -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. 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. 472 472 473 -1.10.0-unstable Alternative to -draft. 474 - 475 -1.10.0-notfinal Alternative to -draft. 476 - 477 477 The SDMX 2.1 isFinal property is deprecated in 3.0. 478 478 479 479 = 5 REST Web Services API = ... ... @@ -496,8 +496,8 @@ 496 496 497 497 Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow. 498 498 499 -= ==Extendthecontextofdataretrieval===500 - 495 +(% class="wikigeneratedid" id="HExtendthecontextofdataretrieval" %) 496 +**Extend the context of data retrieval** 501 501 Version 2.1 data queries always retrieved data from a single specific Dataflow. In version 3.0, the query context may be specified as: 502 502 503 503 * Dataflow; ... ... @@ -506,18 +506,20 @@ 506 506 507 507 Data queries may also search across datasets, for instance “retrieve all data about a country”. 508 508 509 -= ==Component-basedfilters===510 - 505 +(% class="wikigeneratedid" id="HComponent-basedfilters" %) 506 +**Component-based filters** 511 511 Expressions filtering on individual components can now be included as part of the data query URL. 512 512 513 513 /data/dataflow/ESTAT/ICP?c[REF_AREA]=CH&c[CONF_STATUS]=F 514 514 515 -= ==Supportforoperators===516 - 511 +(% class="wikigeneratedid" id="HSupportforoperators" %) 512 +**Support for operators** 517 517 Filter expressions can also include operators. 518 518 519 -/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 Operators include:515 +/data/dataflow/ESTAT/ICP?c[REF_AREA]=DE&c[ICP_ITEM]=sw:01&c[TIME_PERIOD]=ge:2015 520 520 517 +Operators include: 518 + 521 521 (% style="width:531.039px" %) 522 522 |(% style="width:151px" %)eq|(% style="width:378px" %)Equals 523 523 |(% style="width:151px" %)ne|(% style="width:378px" %)Not equal to ... ... @@ -525,10 +525,11 @@ 525 525 |(% style="width:151px" %)ge|(% style="width:378px" %)Greater than or equal to 526 526 |(% style="width:151px" %)sw|(% style="width:378px" %)Starts with 527 527 528 -= ==Supportformultiplekeys===529 - 526 +(% class="wikigeneratedid" id="HSupportformultiplekeys" %) 527 +**Support for multiple keys** 530 530 Queries can now specify multiple series keys. 531 531 530 +(% class="wikigeneratedid" %) 532 532 /data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG 533 533 534 534 == 5.3 Improved reference metadata queries ==