Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.7
edited by Helena
on 2025/05/16 11:22
Change comment: There is no comment for this version
To version 4.5
edited by Helena
on 2025/05/16 11:19
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" %)^^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" %)^^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  
... ... @@ -319,9 +319,13 @@
319 319  **Examples:**
320 320  
321 321  **2010-Q2, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
322 +
322 322  ~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
324 +
323 323   b) [REPORTING_YEAR_BASE] = 2010-07-01
326 +
324 324  2. [PERIOD_DURATION] = P3M
328 +
325 325  3. (2-1) * P3M = P3M
326 326   2010-07-01 + P3M = 2010-10-01
327 327   [PERIOD_START] = 2010-10-01
... ... @@ -334,19 +334,30 @@
334 334  The actual calendar range covered by 2010-Q2 (assuming the reporting year begins July 1) is 2010-10-01T00:00:00/2010-12-31T23:59:59
335 335  
336 336  **2011-W36, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
337 -~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
338 - a) 2011-07-01 = Friday
339 - 2011-07-01 + P3D = 2011-07-04
340 - [REPORTING_YEAR_BASE] = 2011-07-04
341 -2. [PERIOD_DURATION] = P7D
342 -3. (36-1) * P7D = P245D
343 - 2011-07-04 + P245D = 2012-03-05
344 - [PERIOD_START] = 2012-03-05
345 -4. 36 * P7D = P252D
346 - 2011-07-04 + P252D =2012-03-12
347 - 2012-03-12 + -P1D = 2012-03-11
348 - [PERIOD_END] = 2012-03-11
349 349  
342 +1. [REPORTING_YEAR_START_DATE] = 2010-07-01
343 +
344 +a) 2011-07-01 = Friday
345 +
346 +2011-07-01 + P3D = 2011-07-04
347 +
348 +[REPORTING_YEAR_BASE] = 2011-07-04
349 +
350 +1. [PERIOD_DURATION] = P7D
351 +1. (36-1) * P7D = P245D
352 +
353 +2011-07-04 + P245D = 2012-03-05
354 +
355 +[PERIOD_START] = 2012-03-05
356 +
357 +1. 36 * P7D = P252D
358 +
359 +2011-07-04 + P252D =2012-03-12
360 +
361 +2012-03-12 + -P1D = 2012-03-11
362 +
363 +[PERIOD_END] = 2012-03-11
364 +
350 350  The actual calendar range covered by 2011-W36 (assuming the reporting year begins July 1) is 2012-03-05T00:00:00/2012-03-11T23:59:59
351 351  
352 352  === {{id name="_Toc291513"/}}4.2.7 Distinct Range ===
... ... @@ -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**
376 +|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