Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.4
edited by Helena
on 2025/06/08 23:27
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  
... ... @@ -512,7 +512,9 @@
512 512  
513 513  ‘1.0’.
514 514  
515 -=== 4.2.14 Non-versioned artefacts ===
519 +1.
520 +11.
521 +111. Non-versioned artefacts
516 516  
517 517  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’.
518 518