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

Summary

Details

Page properties
Content
... ... @@ -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 -(% class="wikigeneratedid" id="HGeospatialInformationtype" %)
367 -**GeospatialInformation type**
366 +=== GeospatialInformation type ===
367 +
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 -(% class="wikigeneratedid" id="HGeospatialcodelists" %)
371 -**Geospatial code lists**
370 +=== Geospatial code lists ===
371 +
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,6 +451,7 @@
451 451  Examples:
452 452  
453 453  SDMX:CL_AREA(1.0.0)
454 +
454 454  SDMX:CL_AREA(2.3.2)
455 455  
456 456  == Dependency management ==
... ... @@ -457,9 +457,10 @@
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).
461 +2.3+.1 Means the currently latest available version >= “2.3.1” and < “3.0.0” (all backwards compatible versions >= “2.3.1”).
462 462  
463 +2+.3.1 Means the currently latest available version >= “2.3.1” (even if not backwards compatible).
464 +
463 463  == Draft structures ==
464 464  
465 465  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.
... ... @@ -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.
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.
472 472  
473 +1.10.0-unstable Alternative to -draft.
474 +
475 +1.10.0-notfinal Alternative to -draft.
476 +
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**
499 +=== Extend the context of data retrieval ===
500 +
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**
509 +=== Component-based filters ===
510 +
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**
515 +=== Support for operators ===
516 +
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
519 +/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**
528 +=== Support for multiple keys ===
529 +
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 ==