Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.5
edited by Helena
on 2025/05/16 11:19
Change comment: There is no comment for this version
To version 5.1
edited by Helena
on 2025/05/16 11:25
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" %)^^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 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,13 +319,9 @@
319 319  **Examples:**
320 320  
321 321  **2010-Q2, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
322 -
323 323  ~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
324 -
325 325   b) [REPORTING_YEAR_BASE] = 2010-07-01
326 -
327 327  2. [PERIOD_DURATION] = P3M
328 -
329 329  3. (2-1) * P3M = P3M
330 330   2010-07-01 + P3M = 2010-10-01
331 331   [PERIOD_START] = 2010-10-01
... ... @@ -338,30 +338,19 @@
338 338  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
339 339  
340 340  **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
341 341  
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 -
365 365  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
366 366  
367 367  === {{id name="_Toc291513"/}}4.2.7 Distinct Range ===
... ... @@ -373,7 +373,7 @@
373 373  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.
374 374  
375 375  (% style="width:771.294px" %)
376 -|Code|(% style="width:659px" %)Format
361 +|**Code**|(% style="width:659px" %)**Format**
377 377  |OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
378 378  |STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
379 379  |GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time
... ... @@ -394,7 +394,7 @@
394 394  |RD|(% style="width:659px" %)Reporting Day (YYYY-Dddd)
395 395  
396 396  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
397 -Table 1: SDMX-ML Time Format Codes
382 +**Table 1: SDMX-ML Time Format Codes**
398 398  
399 399  === {{id name="_Toc291515"/}}4.2.9 Time Zones ===
400 400  
... ... @@ -421,11 +421,11 @@
421 421  
422 422  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:
423 423  
424 -<Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
409 +> <Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
425 425  
426 426  can now be represented with this:
427 427  
428 -<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
413 +> <Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
429 429  
430 430  === {{id name="_Toc291517"/}}4.2.11 Notes on Formats ===
431 431  
... ... @@ -454,11 +454,8 @@
454 454  **Examples:**
455 455  
456 456  **Gregorian Period**
457 -
458 458  Query Parameter: Greater than 2010
459 -
460 460  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
461 -
462 462  Example Matches:
463 463  
464 464  * 2011 or later
... ... @@ -474,11 +474,10 @@
474 474  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
475 475  
476 476  **Reporting Period**
477 -
478 478  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:
479 479  
480 -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:
481 -
482 482  * 2011 or later
483 483  * 2010-07 or later
484 484  * 2010-07-01 or later