Changes for page 4 General Notes for Implementers
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -260,7 +260,7 @@ 260 260 261 261 Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53) 262 262 263 -Notes: There are either 52 or 53 weeks in a reporting year. This is based on the ISO 8601 definition of a week (Monday - Saturday), where the first week of a reporting year is defined as the week with the first Thursday on or after the reporting year start day.^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^ The reporting week is always represented as two digits, therefore 1-9 are 0 padded (e.g. 01). This allows the values to be sorted chronologically using textual sorting methods.263 +Notes: There are either 52 or 53 weeks in a reporting year. This is based on the ISO 8601 definition of a week (Monday - Saturday), where the first week of a reporting year is defined as the week with the first Thursday on or after the reporting year start day.^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^ The reporting week is always represented as two digits, therefore 1-9 are 0 padded (e.g. 01). This allows the values to be sorted chronologically using textual sorting methods. 264 264 265 265 **Reporting Day**: 266 266 ... ... @@ -294,19 +294,19 @@ 294 294 295 295 This is the [REPORTING_YEAR_START_DATE] 296 296 297 -1. 297 +1. 298 298 11. **If the [PERIOD_INDICATOR] is W:** 299 299 111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:** 300 300 301 301 Add{{footnote}}The rules for adding durations to a date time are described in the W3C XML Schema specification. See http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes for further details.{{/footnote}} (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE]. 302 302 303 -1. 304 -11. 303 +1. 304 +11. 305 305 111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:** 306 306 307 307 Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE]. 308 308 309 -1. 309 +1. 310 310 11. **Else:** 311 311 312 312 The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE]. ... ... @@ -321,10 +321,8 @@ 321 321 11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D. 322 322 1. **Determine [PERIOD_START]:** 323 323 324 -Subtract one from the [PERIOD_VALUE] and multiply this by the [PERIOD_DURATION]. Add^^4^^ this to the [REPORTING_YEAR_BASE]. The result is the [PERIOD_START]. 324 +Subtract one from the [PERIOD_VALUE] and multiply this by the [PERIOD_DURATION]. Add^^4^^ this to the [REPORTING_YEAR_BASE]. The result is the [PERIOD_START]. **4. Determine the [PERIOD_END]:** 325 325 326 -**4. Determine the [PERIOD_END]:** 327 - 328 328 Multiply the [PERIOD_VALUE] by the [PERIOD_DURATION]. Add^^4^^ this to the [REPORTING_YEAR_BASE] add^^4^^ -P1D. The result is the [PERIOD_END]. 329 329 330 330 For all of these ranges, the bounds include the beginning of the [PERIOD_START] (i.e. 00:00:00) and the end of the [PERIOD_END] (i.e. 23:59:59). ... ... @@ -389,29 +389,29 @@ 389 389 390 390 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. 391 391 392 -(% style="width:771.294px" %) 393 -|Code|(% style="width:659px" %)Format 394 -|OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range) 395 -|STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods 396 -|GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time 397 -|RTP|(% style="width:659px" %)Superset of all Reporting Time Periods 398 -|TR|(% style="width:659px" %)((( 399 -Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>) 390 +|Code|Format 391 +|OTP|Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range) 392 +|STP|Standard Time Period: Superset of Gregorian and Reporting Time Periods 393 +|GTP|Superset of all Gregorian Time Periods and date-time 394 +|RTP|Superset of all Reporting Time Periods 395 +|TR|((( 396 +Time Range: Start time and duration (YYYY-MM- 397 + 398 +DD(Thh:mm:ss)?/<duration>) 400 400 ))) 401 -|GY| (% style="width:659px" %)Gregorian Year (YYYY)402 -|GTM| (% style="width:659px" %)Gregorian Year Month (YYYY-MM)403 -|GD| (% style="width:659px" %)Gregorian Day (YYYY-MM-DD)404 -|DT| (% style="width:659px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)405 -|RY| (% style="width:659px" %)Reporting Year (YYYY-A1)406 -|RS| (% style="width:659px" %)Reporting Semester (YYYY-Ss)407 -|RT| (% style="width:659px" %)Reporting Trimester (YYYY-Tt)408 -|RQ| (% style="width:659px" %)Reporting Quarter (YYYY-Qq)409 -|RM| (% style="width:659px" %)Reporting Month (YYYY-Mmm)410 -|RW| (% style="width:659px" %)Reporting Week (YYYY-Www)411 -|RD| (% style="width:659px" %)Reporting Day (YYYY-Dddd)400 +|GY|Gregorian Year (YYYY) 401 +|GTM|Gregorian Year Month (YYYY-MM) 402 +|GD|Gregorian Day (YYYY-MM-DD) 403 +|DT|Distinct Point: date-time (YYYY-MM-DDThh:mm:ss) 404 +|RY|Reporting Year (YYYY-A1) 405 +|RS|Reporting Semester (YYYY-Ss) 406 +|RT|Reporting Trimester (YYYY-Tt) 407 +|RQ|Reporting Quarter (YYYY-Qq) 408 +|RM|Reporting Month (YYYY-Mmm) 409 +|RW|Reporting Week (YYYY-Www) 410 +|RD|Reporting Day (YYYY-Dddd) 412 412 413 -(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %) 414 -Table 1: SDMX-ML Time Format Codes 412 +==== Table 1: SDMX-ML Time Format Codes ==== 415 415 416 416 === {{id name="_Toc291515"/}}4.2.9 Time Zones === 417 417 ... ... @@ -458,13 +458,12 @@ 458 458 459 459 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. 460 460 461 -(% style="width:1020.29px" %) 462 -|(% style="width:236px" %)**Operator**|(% style="width:781px" %)**Rule** 463 -|(% style="width:236px" %)Greater Than|(% style="width:781px" %)Any data after the last moment of the period 464 -|(% style="width:236px" %)Less Than|(% style="width:781px" %)Any data before the first moment of the period 465 -|(% style="width:236px" %)Greater Than or Equal To|(% style="width:781px" %)Any data on or after the first moment of the period 466 -|(% style="width:236px" %)Less Than or Equal To|(% style="width:781px" %)Any data on or before the last moment of the period 467 -|(% style="width:236px" %)Equal To|(% style="width:781px" %)Any data which falls on or after the first moment of the period and before or on the last moment of the period 459 +|**Operator**|**Rule** 460 +|Greater Than|Any data after the last moment of the period 461 +|Less Than|Any data before the first moment of the period 462 +|Greater Than or Equal To|Any data on or after the first moment of the period 463 +|Less Than or Equal To|Any data on or before the last moment of the period 464 +|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 468 468 469 469 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. 470 470 ... ... @@ -513,7 +513,7 @@ 513 513 514 514 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". 515 515 516 -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__>>http s://http:semver.org]]), in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from //MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version ‘1.0’.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 //MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version ‘1.0’. 517 517 518 518 === 4.3.1 Non-versioned artefacts === 519 519 ... ... @@ -521,6 +521,8 @@ 521 521 522 522 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. 523 523 521 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape3" height="1" width="192"]] 522 + 524 524 2010-Q3 (with a reporting year start day of ~-~-01-01) starts on 2010-07-01. This is day 4 of week 26, therefore the first week matched is week 27. 525 525 526 526 2010-Q3 (with a reporting year start day of ~-~-07-01) starts on 2011-01-01. This is day 6 of week 27, therefore the first week matched is week 28.