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

Summary

Details

Page properties
Content
... ... @@ -443,15 +443,11 @@
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 -1.
447 -11.
448 -111. Effect on Time Ranges
446 +=== 4.2.12 Effect on Time Ranges ===
449 449  
450 450  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.
451 451  
452 -1.
453 -11.
454 -111. Time in Query Messages
450 +=== 4.2.13 Time in Query Messages ===
455 455  
456 456  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.
457 457  
... ... @@ -505,9 +505,11 @@
505 505  * 2010-M07 or later (any reporting year start day)
506 506  * 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
507 507  * 2010-D182 or later (reporting year start day ~-~-01-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
504 +* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
505 +* 2010-D185 or later (reporting year start day ~-~-07-01)
510 510  
507 += 4.3 Versioning ==
508 +
511 511  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".
512 512  
513 513  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
... ... @@ -516,9 +516,7 @@
516 516  
517 517  ‘1.0’.
518 518  
519 -1.
520 -11.
521 -111. Non-versioned artefacts
517 +=== 4.2.14 Non-versioned artefacts ===
522 522  
523 523  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’.
524 524