Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/16 00:05
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" %)^^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  
... ... @@ -280,46 +280,33 @@
280 280  
281 281  (REPORTING_YEAR_START_DAY) and a fixed representation (xs:gMonthDay) so that it can always be easily identified and processed in a data message. Although this attribute exists in specialized sub-class, it functions the same as any other attribute outside of its identification and representation. It must takes its identity from a concept and state its relationship with other components of the data structure definition. The ability to state this relationship allows this reporting year start day attribute to exist at the appropriate levels of a data message. In the absence of this attribute, the reporting year start date is assumed to be January 1; therefore if the reporting year coincides with the calendar year, this Attribute is not necessary.
282 282  
283 -Since the duration and the reporting year start day are known for any reporting period, it is possible to relate any reporting period to a distinct calendar period. The actual
283 +Since the duration and the reporting year start day are known for any reporting period, it is possible to relate any reporting period to a distinct calendar period. The actual Gregorian calendar period covered by the reporting period can be computed as follows (based on the standard format of [REPROTING_YEAR]-[PERIOD_INDICATOR][PERIOD_VALUE] and the reporting year start day as [REPORTING_YEAR_START_DAY]):
284 284  
285 -Gregorian calendar period covered by the reporting period can be computed as follows
285 +**~1. Determine [REPORTING_YEAR_BASE]:**
286 286  
287 -(based on the standard format of [REPROTING_YEAR]-
288 -
289 -[PERIOD_INDICATOR][PERIOD_VALUE] and the reporting year start day as [REPORTING_YEAR_START_DAY]):
290 -
291 -1. **Determine [REPORTING_YEAR_BASE]:**
292 -
293 293  Combine [REPORTING_YEAR] of the reporting period value (YYYY) with [REPORTING_YEAR_START_DAY] (MM-DD) to get a date (YYYY-MM-DD).
294 -
295 295  This is the [REPORTING_YEAR_START_DATE]
296 296  
297 -1.
298 -11. **If the [PERIOD_INDICATOR] is W:**
299 -111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
290 +**a) If the [PERIOD_INDICATOR] is W:**
300 300  
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 + ~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].
302 302  
303 -1.
304 -11.
305 -111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
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].
306 306  
307 -Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
308 -
309 -1.
310 -11. **Else:**
311 -
298 +**b) Else:**
312 312  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
313 313  
314 -1. **Determine [PERIOD_DURATION]:**
315 -11. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
316 -11. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
317 -11. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
318 -11. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
319 -11. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
320 -11. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
321 -11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
322 -1. **Determine [PERIOD_START]:**
301 +**2. Determine [PERIOD_DURATION]:**
302 +a) If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
303 +b) If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
304 +c) If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
305 +d) If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
306 +e) If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
307 +f) If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
308 +g) If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
309 +**3. Determine [PERIOD_START]:**
323 323  
324 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].
325 325  
... ... @@ -332,53 +332,34 @@
332 332  **Examples:**
333 333  
334 334  **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
335 335  
336 -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
337 337  
338 -b) [REPORTING_YEAR_BASE] = 2010-07-01
339 -
340 -1. [PERIOD_DURATION] = P3M
341 -1. (2-1) * P3M = P3M
342 -
343 -2010-07-01 + P3M = 2010-10-01
344 -
345 -[PERIOD_START] = 2010-10-01
346 -
347 -1. 2 * P3M = P6M
348 -
349 -2010-07-01 + P6M = 2010-13-01 = 2011-01-01
350 -
351 -2011-01-01 + -P1D = 2010-12-31
352 -
353 -[PERIOD_END] = 2010-12-31
354 -
355 355  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
356 356  
357 357  **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
358 358  
359 -1. [REPORTING_YEAR_START_DATE] = 2010-07-01
360 -
361 -a) 2011-07-01 = Friday
362 -
363 -2011-07-01 + P3D = 2011-07-04
364 -
365 -[REPORTING_YEAR_BASE] = 2011-07-04
366 -
367 -1. [PERIOD_DURATION] = P7D
368 -1. (36-1) * P7D = P245D
369 -
370 -2011-07-04 + P245D = 2012-03-05
371 -
372 -[PERIOD_START] = 2012-03-05
373 -
374 -1. 36 * P7D = P252D
375 -
376 -2011-07-04 + P252D =2012-03-12
377 -
378 -2012-03-12 + -P1D = 2012-03-11
379 -
380 -[PERIOD_END] = 2012-03-11
381 -
382 382  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
383 383  
384 384  === {{id name="_Toc291513"/}}4.2.7 Distinct Range ===
... ... @@ -390,7 +390,7 @@
390 390  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.
391 391  
392 392  (% style="width:771.294px" %)
393 -|Code|(% style="width:659px" %)Format
361 +|**Code**|(% style="width:659px" %)**Format**
394 394  |OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
395 395  |STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
396 396  |GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time
... ... @@ -411,7 +411,7 @@
411 411  |RD|(% style="width:659px" %)Reporting Day (YYYY-Dddd)
412 412  
413 413  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
414 -Table 1: SDMX-ML Time Format Codes
382 +**Table 1: SDMX-ML Time Format Codes**
415 415  
416 416  === {{id name="_Toc291515"/}}4.2.9 Time Zones ===
417 417  
... ... @@ -438,11 +438,11 @@
438 438  
439 439  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:
440 440  
441 -<Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
409 +> <Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
442 442  
443 443  can now be represented with this:
444 444  
445 -<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
413 +> <Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
446 446  
447 447  === {{id name="_Toc291517"/}}4.2.11 Notes on Formats ===
448 448  
... ... @@ -471,11 +471,8 @@
471 471  **Examples:**
472 472  
473 473  **Gregorian Period**
474 -
475 475  Query Parameter: Greater than 2010
476 -
477 477  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
478 -
479 479  Example Matches:
480 480  
481 481  * 2011 or later
... ... @@ -491,11 +491,10 @@
491 491  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
492 492  
493 493  **Reporting Period**
494 -
495 495  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:
496 496  
497 -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:
498 -
499 499  * 2011 or later
500 500  * 2010-07 or later
501 501  * 2010-07-01 or later