Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.9
edited by Helena
on 2025/06/08 23:31
Change comment: There is no comment for this version
To version 1.3
edited by Helena
on 2025/06/08 23:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -443,11 +443,15 @@
443 443  
444 444  There is no ambiguity in these formats so that for any given value of time, the category of the period (and thus the intended time period range) is always clear. It should also be noted that by utilizing the ISO 8601 format, and a format loosely based on it for the report periods, the values of time can easily be sorted chronologically without additional parsing.
445 445  
446 -=== 4.2.12 Effect on Time Ranges ===
446 +1.
447 +11.
448 +111. Effect on Time Ranges
447 447  
448 448  All SDMX-ML data messages are capable of functioning in a manner similar to SDMXEDI if the Dimension at the observation level is time: the time period for the first observation can be stated and the rest of the observations can omit the time value as it can be derived from the start time and the frequency. Since the frequency can be determined based on the actual format of the time value for everything but distinct points in time and time ranges, this makes is even simpler to process as the interval between time ranges is known directly from the time value.
449 449  
450 -=== 4.2.13 Time in Query Messages ===
452 +1.
453 +11.
454 +111. Time in Query Messages
451 451  
452 452  When querying for time values, the value of a time parameter can be provided as any of the Observational Time Period formats and must be paired with an operator. This section will detail how systems processing query messages should interpret these parameters.
453 453  
... ... @@ -501,11 +501,9 @@
501 501  * 2010-M07 or later (any reporting year start day)
502 502  * 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
503 503  * 2010-D182 or later (reporting year start day ~-~-01-01)
504 -* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
505 -* 2010-D185 or later (reporting year start day ~-~-07-01)
508 +* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^ • 2010-D185 or later (reporting year start day ~-~-07-01)
509 +*1. Versioning
506 506  
507 -= 4.3 Versioning ==
508 -
509 509  Versioning operates at the level of versionable and maintainable objects in the SDMX information model. Within the SDMX Structure and MetadataSet messages, there is a well-defined pattern for artefact versioning and referencing. The artefact identifiers are qualified by their version numbers – that is, an object with an Agency of "A", and ID of "X" and a version of "1.0.0" is a different object than one with an Agency of "A", an ID of "X", and a version of "1.1.0".
510 510  
511 511  As of SDMX 3.0, the versioning rules are extended to allow for truly versioned artefacts through the implementation of the rules of the well-known practice called "Semantic Versioning" [[(>>url:http://semver.org/]][[http:~~/~~/semver.org>>url:http://semver.org/]][[)>>url:http://semver.org/]], in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from
... ... @@ -514,13 +514,17 @@
514 514  
515 515  ‘1.0’.
516 516  
517 -=== 4.3.1 Non-versioned artefacts ===
519 +1.
520 +11.
521 +111. Non-versioned artefacts
518 518  
519 519  Indeed, some use cases do not need or are incompatible with versioning for some or all their structural artefacts, such as the Agency, Data Providers, Metadata Providers and Data Consumer Schemes. These artefacts follow the legacy versioning, with a fixed version set to ‘1.0’.
520 520  
521 521  Many existing organisation’s data management systems work with version-less structures and apply ad-hoc structural metadata governance processes. The new nonversioned artefacts will allow supporting those numerous situations, where organisations do not manage version numbers.
522 522  
523 -=== 4.3.2 Semantically versioned artefacts ===
527 +1.
528 +11.
529 +111. Semantically versioned artefacts
524 524  
525 525  Since the purpose of SDMX versioning is to allow communicating the structural artefact changes to data exchange partners and connected systems, SDMX 3.0 offers Semantic Versioning (aka SemVer) with a clear and unambiguous syntax to all semantically versioned SDMX 3.0 structural artefacts. Semantic versioning will thus better respond to situations where the SDMX standard itself is the only structural contract between data providers and data consumers and where changes in structures can only be communicated through the version number increases.
526 526  
... ... @@ -544,13 +544,17 @@
544 544  
545 545  The production versions of identifiable artefacts are assumed stable, i.e., they do not have an EXTENSION. This is because once in production, an artefact cannot change in any way, or it must change the version. For cases where an artefact is not static, like during the drafting, the version must indicate this by including an EXTENSION. Draft artefacts should not be used outside of a specific system designed to accommodate them. For most purposes, all artefacts should become stable before being used in production.
546 546  
547 -=== 4.3.3 Legacy-versioned artefacts ===
553 +1.
554 +11.
555 +111. Legacy-versioned artefacts
548 548  
549 549  Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for version numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new SDMX 3.0 standard does not add any strict rules or guarantees about changes in those artefacts, since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
550 550  
551 551  In order to make artefacts immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
552 552  
553 -=== 4.3.4 Dependency management and references ===
561 +1.
562 +11.
563 +111. Dependency management and references
554 554  
555 555  New flexible dependency specifications with wildcarding allow for easier data model maintenance and enhancements for semantically versioned SDMX artefacts. This allows implementing a smart referencing mechanism, whereby an artefact may reference:
556 556  
... ... @@ -579,7 +579,8 @@
579 579  
580 580  Full details can be found in the SDMX RESTful web services specification.
581 581  
582 -== 4.4 Structural Metadata Querying Best Practices ==
592 +1.
593 +11. Structural Metadata Querying Best Practices
583 583  
584 584  When querying for structural metadata, the ability to state how references should be resolved is quite powerful. However, this mechanism is not always necessary and can create an undue burden on the systems processing the queries if it is not used properly.
585 585  
... ... @@ -587,6 +587,7 @@
587 587  
588 588  When the referenced object is not known, then the reference resolution mechanism could be used. For example, suppose one wanted to find all category schemes and the related categorisations for a given maintenance agency. In this case, one could query for the category scheme by the maintenance agency and specify that parent and sibling references should be resolved. This would result in the categorisations which reference the categories in the matched schemes to be returned, as well as the object which they categorise.
589 589  
601 +
590 590  ----
591 591  
592 592  [[~[1~]>>path:#_ftnref1]] Regular expressions, as specified in [[W3C XML Schema Definition Language (XSD)>>url:https://www.w3.org/TR/xmlschema11-2/]][[ >>url:https://www.w3.org/TR/xmlschema11-2/]][[1.1 Part 2: Datatypes>>url:https://www.w3.org/TR/xmlschema11-2/]][[.>>url:https://www.w3.org/TR/xmlschema11-2/]]