Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.4
edited by Helena
on 2025/05/16 11:16
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  
... ... @@ -289,11 +289,11 @@
289 289  
290 290  **a) If the [PERIOD_INDICATOR] is W:**
291 291  
292 -~1. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday**:
293 -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 + ~1. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday**:
293 + 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].
294 294  
295 -**2. If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
296 -Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
295 +**~ 2. If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
296 + Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
297 297  
298 298  **b) Else:**
299 299  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
... ... @@ -319,53 +319,34 @@
319 319  **Examples:**
320 320  
321 321  **2010-Q2, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
322 +~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
323 + b) [REPORTING_YEAR_BASE] = 2010-07-01
324 +2. [PERIOD_DURATION] = P3M
325 +3. (2-1) * P3M = P3M
326 + 2010-07-01 + P3M = 2010-10-01
327 + [PERIOD_START] = 2010-10-01
322 322  
323 -1. [REPORTING_YEAR_START_DATE] = 2010-07-01
329 +4. 2 * P3M = P6M
330 + 2010-07-01 + P6M = 2010-13-01 = 2011-01-01
331 + 2011-01-01 + -P1D = 2010-12-31
332 + [PERIOD_END] = 2010-12-31
324 324  
325 -b) [REPORTING_YEAR_BASE] = 2010-07-01
326 -
327 -1. [PERIOD_DURATION] = P3M
328 -1. (2-1) * P3M = P3M
329 -
330 -2010-07-01 + P3M = 2010-10-01
331 -
332 -[PERIOD_START] = 2010-10-01
333 -
334 -1. 2 * P3M = P6M
335 -
336 -2010-07-01 + P6M = 2010-13-01 = 2011-01-01
337 -
338 -2011-01-01 + -P1D = 2010-12-31
339 -
340 -[PERIOD_END] = 2010-12-31
341 -
342 342  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
343 343  
344 344  **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
345 345  
346 -1. [REPORTING_YEAR_START_DATE] = 2010-07-01
347 -
348 -a) 2011-07-01 = Friday
349 -
350 -2011-07-01 + P3D = 2011-07-04
351 -
352 -[REPORTING_YEAR_BASE] = 2011-07-04
353 -
354 -1. [PERIOD_DURATION] = P7D
355 -1. (36-1) * P7D = P245D
356 -
357 -2011-07-04 + P245D = 2012-03-05
358 -
359 -[PERIOD_START] = 2012-03-05
360 -
361 -1. 36 * P7D = P252D
362 -
363 -2011-07-04 + P252D =2012-03-12
364 -
365 -2012-03-12 + -P1D = 2012-03-11
366 -
367 -[PERIOD_END] = 2012-03-11
368 -
369 369  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
370 370  
371 371  === {{id name="_Toc291513"/}}4.2.7 Distinct Range ===
... ... @@ -377,7 +377,7 @@
377 377  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.
378 378  
379 379  (% style="width:771.294px" %)
380 -|Code|(% style="width:659px" %)Format
361 +|**Code**|(% style="width:659px" %)**Format**
381 381  |OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
382 382  |STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
383 383  |GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time
... ... @@ -398,7 +398,7 @@
398 398  |RD|(% style="width:659px" %)Reporting Day (YYYY-Dddd)
399 399  
400 400  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
401 -Table 1: SDMX-ML Time Format Codes
382 +**Table 1: SDMX-ML Time Format Codes**
402 402  
403 403  === {{id name="_Toc291515"/}}4.2.9 Time Zones ===
404 404  
... ... @@ -425,11 +425,11 @@
425 425  
426 426  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:
427 427  
428 -<Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
409 +> <Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
429 429  
430 430  can now be represented with this:
431 431  
432 -<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
413 +> <Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
433 433  
434 434  === {{id name="_Toc291517"/}}4.2.11 Notes on Formats ===
435 435  
... ... @@ -458,11 +458,8 @@
458 458  **Examples:**
459 459  
460 460  **Gregorian Period**
461 -
462 462  Query Parameter: Greater than 2010
463 -
464 464  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
465 -
466 466  Example Matches:
467 467  
468 468  * 2011 or later
... ... @@ -478,11 +478,10 @@
478 478  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
479 479  
480 480  **Reporting Period**
481 -
482 482  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:
483 483  
484 -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:
485 -
486 486  * 2011 or later
487 487  * 2010-07 or later
488 488  * 2010-07-01 or later