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
-
... ... @@ -164,12 +164,16 @@ 164 164 165 165 Representation: xs:gYear (YYYY) 166 166 167 -Period: the start of January 1 to the end of December 31 **Gregorian Year Month**:167 +Period: the start of January 1 to the end of December 31 168 168 169 +**Gregorian Year Month**: 170 + 169 169 Representation: xs:gYearMonth (YYYY-MM) 170 170 171 -Period: the start of the first day of the month to end of the last day of the month **Gregorian Day**:173 +Period: the start of the first day of the month to end of the last day of the month 172 172 175 +**Gregorian Day**: 176 + 173 173 Representation: xs:date (YYYY-MM-DD) 174 174 175 175 Period: the start of the day (00:00:00) to the end of the day (23:59:59) ... ... @@ -202,8 +202,10 @@ 202 202 203 203 Limit per year: 1 204 204 205 -Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1) **Reporting Semester:**209 +Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1) 206 206 211 +**Reporting Semester:** 212 + 207 207 Period Indicator: S 208 208 209 209 Period Duration: P6M (six months) ... ... @@ -220,8 +220,10 @@ 220 220 221 221 Limit per year: 3 222 222 223 -Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3) **Reporting Quarter:**229 +Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3) 224 224 231 +**Reporting Quarter:** 232 + 225 225 Period Indicator: Q 226 226 227 227 Period Duration: P3M (three months) ... ... @@ -228,8 +228,10 @@ 228 228 229 229 Limit per year: 4 230 230 231 -Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4) **Reporting Month**:239 +Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4) 232 232 241 +**Reporting Month**: 242 + 233 233 Period Indicator: M 234 234 235 235 Period Duration: P1M (one month) ... ... @@ -250,7 +250,7 @@ 250 250 251 251 Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53) 252 252 253 -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" %)^^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 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. 254 254 255 255 **Reporting Day**: 256 256 ... ... @@ -288,7 +288,7 @@ 288 288 11. **If the [PERIOD_INDICATOR] is W:** 289 289 111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:** 290 290 291 -Add ^^[[(% class="wikiinternallink wikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallinkwikiinternallink" %)^^4^^>>path:#sdfootnote4sym||name="sdfootnote4anc"]](%%)^^(P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].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]. 292 292 293 293 1. 294 294 11. ... ... @@ -311,8 +311,10 @@ 311 311 11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D. 312 312 1. **Determine [PERIOD_START]:** 313 313 314 -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]:**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]. 315 315 326 +**4. Determine the [PERIOD_END]:** 327 + 316 316 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]. 317 317 318 318 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). ... ... @@ -377,29 +377,29 @@ 377 377 378 378 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. 379 379 380 -|Code|Format 381 -|OTP|Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range) 382 -|STP|Standard Time Period: Superset of Gregorian and Reporting Time Periods 383 -|GTP|Superset of all Gregorian Time Periods and date-time 384 -|RTP|Superset of all Reporting Time Periods 385 -|TR|((( 386 -Time Range: Start time and duration (YYYY-MM- 387 - 388 -DD(Thh:mm:ss)?/<duration>) 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>) 389 389 ))) 390 -|GY|Gregorian Year (YYYY) 391 -|GTM|Gregorian Year Month (YYYY-MM) 392 -|GD|Gregorian Day (YYYY-MM-DD) 393 -|DT|Distinct Point: date-time (YYYY-MM-DDThh:mm:ss) 394 -|RY|Reporting Year (YYYY-A1) 395 -|RS|Reporting Semester (YYYY-Ss) 396 -|RT|Reporting Trimester (YYYY-Tt) 397 -|RQ|Reporting Quarter (YYYY-Qq) 398 -|RM|Reporting Month (YYYY-Mmm) 399 -|RW|Reporting Week (YYYY-Www) 400 -|RD|Reporting Day (YYYY-Dddd) 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) 401 401 402 -==== Table 1: SDMX-ML Time Format Codes ==== 413 +(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %) 414 +Table 1: SDMX-ML Time Format Codes 403 403 404 404 === {{id name="_Toc291515"/}}4.2.9 Time Zones === 405 405 ... ... @@ -446,12 +446,13 @@ 446 446 447 447 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. 448 448 449 -|**Operator**|**Rule** 450 -|Greater Than|Any data after the last moment of the period 451 -|Less Than|Any data before the first moment of the period 452 -|Greater Than or Equal To|Any data on or after the first moment of the period 453 -|Less Than or Equal To|Any data on or before the last moment of the period 454 -|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 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 455 455 456 456 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. 457 457 ... ... @@ -500,7 +500,7 @@ 500 500 501 501 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". 502 502 503 -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’.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__>>https://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’. 504 504 505 505 === 4.3.1 Non-versioned artefacts === 506 506 ... ... @@ -508,8 +508,6 @@ 508 508 509 509 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. 510 510 511 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape3" height="1" width="192"]] 512 - 513 513 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. 514 514 515 515 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.