Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 2.10
edited by Helena
on 2025/06/08 23:46
Change comment: There is no comment for this version
To version 2.11
edited by Helena
on 2025/06/08 23:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -331,25 +331,26 @@
331 331  
332 332  In version 2.0 of SDMX there is a recommendation to use the time format attribute to gives additional information on the way time is represented in the message. Following an appraisal of its usefulness this is no longer required. However, it is still possible, if required , to include the time format attribute in SDMX-ML.
333 333  
334 -|(% style="width:95px" %)Code|(% style="width:1520px" %)Format
335 -|(% style="width:95px" %)OTP|(% style="width:1520px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
336 -|(% style="width:95px" %)STP|(% style="width:1520px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
337 -|(% style="width:95px" %)GTP|(% style="width:1520px" %)Superset of all Gregorian Time Periods and date-time
338 -|(% style="width:95px" %)RTP|(% style="width:1520px" %)Superset of all Reporting Time Periods
339 -|(% style="width:95px" %)TR|(% style="width:1520px" %)(((
334 +(% style="width:890.835px" %)
335 +|(% style="width:95px" %)**Code**|(% style="width:793px" %)**Format**
336 +|(% style="width:95px" %)OTP|(% style="width:793px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
337 +|(% style="width:95px" %)STP|(% style="width:793px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
338 +|(% style="width:95px" %)GTP|(% style="width:793px" %)Superset of all Gregorian Time Periods and date-time
339 +|(% style="width:95px" %)RTP|(% style="width:793px" %)Superset of all Reporting Time Periods
340 +|(% style="width:95px" %)TR|(% style="width:793px" %)(((
340 340  Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
341 341  )))
342 -|(% style="width:95px" %)GY|(% style="width:1520px" %)Gregorian Year (YYYY)
343 -|(% style="width:95px" %)GTM|(% style="width:1520px" %)Gregorian Year Month (YYYY-MM)
344 -|(% style="width:95px" %)GD|(% style="width:1520px" %)Gregorian Day (YYYY-MM-DD)
345 -|(% style="width:95px" %)DT|(% style="width:1520px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
346 -|(% style="width:95px" %)RY|(% style="width:1520px" %)Reporting Year (YYYY-A1)
347 -|(% style="width:95px" %)RS|(% style="width:1520px" %)Reporting Semester (YYYY-Ss)
348 -|(% style="width:95px" %)RT|(% style="width:1520px" %)Reporting Trimester (YYYY-Tt)
349 -|(% style="width:95px" %)RQ|(% style="width:1520px" %)Reporting Quarter (YYYY-Qq)
350 -|(% style="width:95px" %)RM|(% style="width:1520px" %)Reporting Month (YYYY-Mmm)
351 -|(% style="width:95px" %)RW|(% style="width:1520px" %)Reporting Week (YYYY-Www)
352 -|(% style="width:95px" %)RD|(% style="width:1520px" %)Reporting Day (YYYY-Dddd)
343 +|(% style="width:95px" %)GY|(% style="width:793px" %)Gregorian Year (YYYY)
344 +|(% style="width:95px" %)GTM|(% style="width:793px" %)Gregorian Year Month (YYYY-MM)
345 +|(% style="width:95px" %)GD|(% style="width:793px" %)Gregorian Day (YYYY-MM-DD)
346 +|(% style="width:95px" %)DT|(% style="width:793px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
347 +|(% style="width:95px" %)RY|(% style="width:793px" %)Reporting Year (YYYY-A1)
348 +|(% style="width:95px" %)RS|(% style="width:793px" %)Reporting Semester (YYYY-Ss)
349 +|(% style="width:95px" %)RT|(% style="width:793px" %)Reporting Trimester (YYYY-Tt)
350 +|(% style="width:95px" %)RQ|(% style="width:793px" %)Reporting Quarter (YYYY-Qq)
351 +|(% style="width:95px" %)RM|(% style="width:793px" %)Reporting Month (YYYY-Mmm)
352 +|(% style="width:95px" %)RW|(% style="width:793px" %)Reporting Week (YYYY-Www)
353 +|(% style="width:95px" %)RD|(% style="width:793px" %)Reporting Day (YYYY-Dddd)
353 353  
354 354  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
355 355  **Table 1: SDMX-ML Time Format Codes**
... ... @@ -399,12 +399,13 @@
399 399  
400 400  Fundamental to processing a time value parameter in a query message is understanding that all time periods should be handled as a distinct range of time. Since the time parameter in the query is paired with an operator, this also effectively represents a distinct range of time. Therefore, a system processing the query must simply match the data where the time period for requested parameter is encompassed by the time period resulting from value of the query parameter. The following table details how the operators should be interpreted for any time period provided as a parameter.
401 401  
402 -|**Operator**|**Rule**
403 -|Greater Than|Any data after the last moment of the period
404 -|Less Than|Any data before the first moment of the period
405 -|Greater Than or Equal To|Any data on or after the first moment of the period
406 -|Less Than or Equal To|Any data on or before the last moment of the period
407 -|Equal To|Any data which falls on or after the first moment of the period and before or on the last moment of the period
403 +(% style="width:770.835px" %)
404 +|(% style="width:220px" %)**Operator**|(% style="width:548px" %)**Rule**
405 +|(% style="width:220px" %)Greater Than|(% style="width:548px" %)Any data after the last moment of the period
406 +|(% style="width:220px" %)Less Than|(% style="width:548px" %)Any data before the first moment of the period
407 +|(% style="width:220px" %)Greater Than or Equal To|(% style="width:548px" %)Any data on or after the first moment of the period
408 +|(% style="width:220px" %)Less Than or Equal To|(% style="width:548px" %)Any data on or before the last moment of the period
409 +|(% style="width:220px" %)Equal To|(% style="width:548px" %)Any data which falls on or after the first moment of the period and before or on the last moment of the period
408 408  
409 409  Reporting Time Periods as query parameters are handled like this: any data within the bounds of the reporting period for the year is matched, regardless of the actual start day of the reporting year. In addition, data reported against a normal calendar period is matched if it falls within the bounds of the time parameter based on a reporting year start day of January 1. When determining whether another reporting period falls within the bounds of a report period query parameter, one will have to take into account the actual time period to compare weeks and days to higher order report periods. This will be demonstrated in the examples to follow.
410 410  
... ... @@ -411,11 +411,8 @@
411 411  **Examples:**
412 412  
413 413  **Gregorian Period**
414 -
415 415  Query Parameter: Greater than 2010
416 -
417 417  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
418 -
419 419  Example Matches:
420 420  
421 421  * 2011 or later
... ... @@ -431,9 +431,7 @@
431 431  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
432 432  
433 433  **Reporting Period**
434 -
435 435  Query Parameter: Greater than or equal to 2010-Q3
436 -
437 437  Literal Interpretation: Any data with a reporting period where the start period is on or after the start period of 2010-Q3 for the same reporting year start day, or and data where the start period is on or after 2010-07-01. Example Matches:
438 438  
439 439  * 2011 or later
... ... @@ -454,12 +454,10 @@
454 454  
455 455  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".
456 456  
457 -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
454 +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" ([[http:~~/~~/semver.org>>https://http:semver.org]]), in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from
458 458  
459 -//MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version
456 +//MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version ‘1.0’.
460 460  
461 -‘1.0’.
462 -
463 463  === 4.3.1 Non-versioned artefacts ===
464 464  
465 465  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’.