Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Helena
on 2025/05/16 11:25
Change comment: There is no comment for this version
To version 4.6
edited by Helena
on 2025/05/16 11:22
Change comment: There is no comment for this version

Summary

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 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 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  
... ... @@ -358,7 +358,7 @@
358 358  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.
359 359  
360 360  (% style="width:771.294px" %)
361 -|**Code**|(% style="width:659px" %)**Format**
361 +|Code|(% style="width:659px" %)Format
362 362  |OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
363 363  |STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
364 364  |GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time
... ... @@ -379,7 +379,7 @@
379 379  |RD|(% style="width:659px" %)Reporting Day (YYYY-Dddd)
380 380  
381 381  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
382 -**Table 1: SDMX-ML Time Format Codes**
382 +Table 1: SDMX-ML Time Format Codes
383 383  
384 384  === {{id name="_Toc291515"/}}4.2.9 Time Zones ===
385 385  
... ... @@ -406,11 +406,11 @@
406 406  
407 407  It has been possible since SDMX 2.0 for a Component to specify a representation of a time span. Depending on the format of the data message, this resulted in either an element with 2 XML attributes for holding the start time and the duration or two separate XML attributes based on the underlying Component identifier. For example, if REF_PERIOD were given a representation of time span, then in the Compact data format, it would be represented by two XML attributes; REF_PERIODStartTime (holding the start) and REF_PERIOD (holding the duration). If a new simple type is introduced in the SDMX schemas that can hold ISO 8601 time intervals, then this will no longer be necessary. What was represented as this:
408 408  
409 -> <Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
409 +<Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
410 410  
411 411  can now be represented with this:
412 412  
413 -> <Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
413 +<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
414 414  
415 415  === {{id name="_Toc291517"/}}4.2.11 Notes on Formats ===
416 416  
... ... @@ -439,8 +439,11 @@
439 439  **Examples:**
440 440  
441 441  **Gregorian Period**
442 +
442 442  Query Parameter: Greater than 2010
444 +
443 443  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
446 +
444 444  Example Matches:
445 445  
446 446  * 2011 or later
... ... @@ -456,10 +456,11 @@
456 456  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
457 457  
458 458  **Reporting Period**
462 +
459 459  Query Parameter: Greater than or equal to 2010-Q3
460 -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.
461 -Example Matches:
462 462  
465 +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:
466 +
463 463  * 2011 or later
464 464  * 2010-07 or later
465 465  * 2010-07-01 or later