Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 2.15
edited by Helena
on 2025/06/08 23:51
Change comment: There is no comment for this version
To version 2.6
edited by Helena
on 2025/06/08 23:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -191,50 +191,85 @@
191 191  The following section details each of the standard reporting periods defined in SDMX:
192 192  
193 193  **Reporting Year**:
194 -Period Indicator: A
194 +
195 + Period Indicator: A
196 +
195 195  Period Duration: P1Y (one year)
198 +
196 196  Limit per year: 1
197 -Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1)
198 -**Reporting Semester:**
199 -Period Indicator: S
200 +
201 +Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1) **Reporting Semester:**
202 +
203 + Period Indicator: S
204 +
200 200  Period Duration: P6M (six months)
206 +
201 201  Limit per year: 2
208 +
202 202  Representation: common:ReportingSemesterType (YYYY-Ss, e.g. 2000-S2)
210 +
203 203  **Reporting Trimester:**
204 -Period Indicator: T
212 +
213 + Period Indicator: T
214 +
205 205  Period Duration: P4M (four months)
216 +
206 206  Limit per year: 3
207 -Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3)
208 -**Reporting Quarter:**
209 -Period Indicator: Q
218 +
219 +Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3) **Reporting Quarter:**
220 +
221 + Period Indicator: Q
222 +
210 210  Period Duration: P3M (three months)
224 +
211 211  Limit per year: 4
212 -Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4)
213 -**Reporting Month**:
226 +
227 +Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4) **Reporting Month**:
228 +
214 214  Period Indicator: M
230 +
215 215  Period Duration: P1M (one month)
232 +
216 216  Limit per year: 1
234 +
217 217  Representation: common:ReportingMonthType (YYYY-Mmm, e.g. 2000-M12) Notes: The reporting month 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.
236 +
218 218  **Reporting Week**:
238 +
219 219  Period Indicator: W
240 +
220 220  Period Duration: P7D (seven days)
242 +
221 221  Limit per year: 53
244 +
222 222  Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53)
223 -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.{{footnote}}ISO 8601 defines alternative definitions for the first week, all of which produce equivalent results. Any of these definitions could be substituted so long as they are in
224 -relation to the reporting year start day.{{/footnote}} 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.
246 +
247 +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" %)^^~[3~]^^>>path:#_ftn3]](%%) 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.
248 +
225 225  **Reporting Day**:
250 +
226 226  Period Indicator: D
252 +
227 227  Period Duration: P1D (one day)
254 +
228 228  Limit per year: 366
256 +
229 229  Representation: common:ReportingDayType (YYYY-Dddd, e.g. 2000-D366) Notes: There are either 365 or 366 days in a reporting year, depending on whether the reporting year includes leap day (February 29). The reporting day is always represented as three digits, therefore 1-99 are 0 padded (e.g. 001). This allows the values to be sorted chronologically using textual sorting methods.
258 +
230 230  The meaning of a reporting year is always based on the start day of the year and requires that the reporting year is expressed as the year at the start of the period. This start day is always the same for a reporting year, and is expressed as a day and a month (e.g. July 1). Therefore, the reporting year 2000 with a start day of July 1 begins on July 1, 2000.
231 231  
232 -A specialized attribute (reporting year start day) exists for the purpose of communicating the reporting year start day. This attribute has a fixed identifier (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.
261 +A specialized attribute (reporting year start day) exists for the purpose of communicating the reporting year start day. This attribute has a fixed identifier
233 233  
234 -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]):
263 +(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.
235 235  
236 -**~1. Determine [REPORTING_YEAR_BASE]:**
265 +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]-
266 +
267 +[PERIOD_INDICATOR][PERIOD_VALUE] and the reporting year start day as [REPORTING_YEAR_START_DAY]):
268 +
269 +1. **Determine [REPORTING_YEAR_BASE]:**
270 +
237 237  Combine [REPORTING_YEAR] of the reporting period value (YYYY) with [REPORTING_YEAR_START_DAY] (MM-DD) to get a date (YYYY-MM-DD).
272 +
238 238  This is the [REPORTING_YEAR_START_DATE]
239 239  
240 240  1.
... ... @@ -241,7 +241,7 @@
241 241  11. **If the [PERIOD_INDICATOR] is W:**
242 242  111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
243 243  
244 -Add[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
279 +Add[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
245 245  
246 246  1.
247 247  11.
... ... @@ -254,18 +254,17 @@
254 254  
255 255  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
256 256  
257 -**2. Determine [PERIOD_DURATION]:**
258 -
259 -1. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
260 -1. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
261 -1. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
262 -1. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
263 -1. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
264 -1. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
265 -1. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
292 +1. **Determine [PERIOD_DURATION]:**
293 +11. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
294 +11. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
295 +11. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
296 +11. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
297 +11. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
298 +11. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
299 +11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
266 266  1. **Determine [PERIOD_START]:**
267 267  
268 -Subtract one from the [PERIOD_VALUE] and multiply this by the [PERIOD_DURATION]. 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-todateTimes for further details.{{/footnote}} this to the [REPORTING_YEAR_BASE]. The result is the [PERIOD_START].
302 +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].
269 269  
270 270  1. **Determine the [PERIOD_END]:**
271 271  
... ... @@ -331,26 +331,25 @@
331 331  
332 332  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.
333 333  
334 -(% style="width:890.835px" %)
335 -|(% style="width:95px" %)**Code**|(% style="width:793px" %)**Format**
336 -|(% style="width:95px" %)OTP|(% style="width:793px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
337 -|(% style="width:95px" %)STP|(% style="width:793px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
338 -|(% style="width:95px" %)GTP|(% style="width:793px" %)Superset of all Gregorian Time Periods and date-time
339 -|(% style="width:95px" %)RTP|(% style="width:793px" %)Superset of all Reporting Time Periods
340 -|(% style="width:95px" %)TR|(% style="width:793px" %)(((
368 +|(% style="width:95px" %)Code|(% style="width:1520px" %)Format
369 +|(% style="width:95px" %)OTP|(% style="width:1520px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
370 +|(% style="width:95px" %)STP|(% style="width:1520px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
371 +|(% style="width:95px" %)GTP|(% style="width:1520px" %)Superset of all Gregorian Time Periods and date-time
372 +|(% style="width:95px" %)RTP|(% style="width:1520px" %)Superset of all Reporting Time Periods
373 +|(% style="width:95px" %)TR|(% style="width:1520px" %)(((
341 341  Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
342 342  )))
343 -|(% style="width:95px" %)GY|(% style="width:793px" %)Gregorian Year (YYYY)
344 -|(% style="width:95px" %)GTM|(% style="width:793px" %)Gregorian Year Month (YYYY-MM)
345 -|(% style="width:95px" %)GD|(% style="width:793px" %)Gregorian Day (YYYY-MM-DD)
346 -|(% style="width:95px" %)DT|(% style="width:793px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
347 -|(% style="width:95px" %)RY|(% style="width:793px" %)Reporting Year (YYYY-A1)
348 -|(% style="width:95px" %)RS|(% style="width:793px" %)Reporting Semester (YYYY-Ss)
349 -|(% style="width:95px" %)RT|(% style="width:793px" %)Reporting Trimester (YYYY-Tt)
350 -|(% style="width:95px" %)RQ|(% style="width:793px" %)Reporting Quarter (YYYY-Qq)
351 -|(% style="width:95px" %)RM|(% style="width:793px" %)Reporting Month (YYYY-Mmm)
352 -|(% style="width:95px" %)RW|(% style="width:793px" %)Reporting Week (YYYY-Www)
353 -|(% style="width:95px" %)RD|(% style="width:793px" %)Reporting Day (YYYY-Dddd)
376 +|(% style="width:95px" %)GY|(% style="width:1520px" %)Gregorian Year (YYYY)
377 +|(% style="width:95px" %)GTM|(% style="width:1520px" %)Gregorian Year Month (YYYY-MM)
378 +|(% style="width:95px" %)GD|(% style="width:1520px" %)Gregorian Day (YYYY-MM-DD)
379 +|(% style="width:95px" %)DT|(% style="width:1520px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
380 +|(% style="width:95px" %)RY|(% style="width:1520px" %)Reporting Year (YYYY-A1)
381 +|(% style="width:95px" %)RS|(% style="width:1520px" %)Reporting Semester (YYYY-Ss)
382 +|(% style="width:95px" %)RT|(% style="width:1520px" %)Reporting Trimester (YYYY-Tt)
383 +|(% style="width:95px" %)RQ|(% style="width:1520px" %)Reporting Quarter (YYYY-Qq)
384 +|(% style="width:95px" %)RM|(% style="width:1520px" %)Reporting Month (YYYY-Mmm)
385 +|(% style="width:95px" %)RW|(% style="width:1520px" %)Reporting Week (YYYY-Www)
386 +|(% style="width:95px" %)RD|(% style="width:1520px" %)Reporting Day (YYYY-Dddd)
354 354  
355 355  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
356 356  **Table 1: SDMX-ML Time Format Codes**
... ... @@ -400,13 +400,12 @@
400 400  
401 401  Fundamental to processing a time value parameter in a query message is understanding that all time periods should be handled as a distinct range of time. Since the time parameter in the query is paired with an operator, this also effectively represents a distinct range of time. Therefore, a system processing the query must simply match the data where the time period for requested parameter is encompassed by the time period resulting from value of the query parameter. The following table details how the operators should be interpreted for any time period provided as a parameter.
402 402  
403 -(% style="width:770.835px" %)
404 -|(% style="width:220px" %)**Operator**|(% style="width:548px" %)**Rule**
405 -|(% style="width:220px" %)Greater Than|(% style="width:548px" %)Any data after the last moment of the period
406 -|(% style="width:220px" %)Less Than|(% style="width:548px" %)Any data before the first moment of the period
407 -|(% style="width:220px" %)Greater Than or Equal To|(% style="width:548px" %)Any data on or after the first moment of the period
408 -|(% style="width:220px" %)Less Than or Equal To|(% style="width:548px" %)Any data on or before the last moment of the period
409 -|(% style="width:220px" %)Equal To|(% style="width:548px" %)Any data which falls on or after the first moment of the period and before or on the last moment of the period
436 +|**Operator**|**Rule**
437 +|Greater Than|Any data after the last moment of the period
438 +|Less Than|Any data before the first moment of the period
439 +|Greater Than or Equal To|Any data on or after the first moment of the period
440 +|Less Than or Equal To|Any data on or before the last moment of the period
441 +|Equal To|Any data which falls on or after the first moment of the period and before or on the last moment of the period
410 410  
411 411  Reporting Time Periods as query parameters are handled like this: any data within the bounds of the reporting period for the year is matched, regardless of the actual start day of the reporting year. In addition, data reported against a normal calendar period is matched if it falls within the bounds of the time parameter based on a reporting year start day of January 1. When determining whether another reporting period falls within the bounds of a report period query parameter, one will have to take into account the actual time period to compare weeks and days to higher order report periods. This will be demonstrated in the examples to follow.
412 412  
... ... @@ -413,8 +413,11 @@
413 413  **Examples:**
414 414  
415 415  **Gregorian Period**
448 +
416 416  Query Parameter: Greater than 2010
450 +
417 417  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
452 +
418 418  Example Matches:
419 419  
420 420  * 2011 or later
... ... @@ -430,7 +430,9 @@
430 430  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
431 431  
432 432  **Reporting Period**
468 +
433 433  Query Parameter: Greater than or equal to 2010-Q3
470 +
434 434  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:
435 435  
436 436  * 2011 or later
... ... @@ -442,9 +442,9 @@
442 442  * 2010-T3 (any reporting year start day)
443 443  * 2010-Q3 or later (any reporting year start day)
444 444  * 2010-M07 or later (any reporting year start day)
445 -* 2010-W27 or later (reporting year start day ~-~-01-01){{footnote}}2010-Q3 (with a reporting year start day of --01-01) starts on 2010-07-01. This is day 4 of week 26, therefore the first week matched is week 27.{{/footnote}}
482 +* 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
446 446  * 2010-D182 or later (reporting year start day ~-~-01-01)
447 -* 2010-W28 or later (reporting year start day ~-~-07-01){{footnote}}2010-Q3 (with a reporting year start day of --07-01) starts on 2011-01-01. This is day 6 of week 27, therefore the first week matched is week 28.{{/footnote}}
484 +* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
448 448  * 2010-D185 or later (reporting year start day ~-~-07-01)
449 449  
450 450  == 4.3 Versioning ==
... ... @@ -451,8 +451,12 @@
451 451  
452 452  Versioning operates at the level of versionable and maintainable objects in the SDMX information model. Within the SDMX Structure and MetadataSet messages, there is a well-defined pattern for artefact versioning and referencing. The artefact identifiers are qualified by their version numbers – that is, an object with an Agency of "A", and ID of "X" and a version of "1.0.0" is a different object than one with an Agency of "A", an ID of "X", and a version of "1.1.0".
453 453  
454 -As of SDMX 3.0, the versioning rules are extended to allow for truly versioned artefacts through the implementation of the rules of the well-known practice called "Semantic Versioning" ([[http:~~/~~/semver.org>>https://http:semver.org]]), in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from //MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version ‘1.0’.
491 +As of SDMX 3.0, the versioning rules are extended to allow for truly versioned artefacts through the implementation of the rules of the well-known practice called "Semantic Versioning" [[(>>url:http://semver.org/]][[http:~~/~~/semver.org>>url:http://semver.org/]][[)>>url:http://semver.org/]], in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from
455 455  
493 +//MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version
494 +
495 +‘1.0’.
496 +
456 456  === 4.3.1 Non-versioned artefacts ===
457 457  
458 458  Indeed, some use cases do not need or are incompatible with versioning for some or all their structural artefacts, such as the Agency, Data Providers, Metadata Providers and Data Consumer Schemes. These artefacts follow the legacy versioning, with a fixed version set to ‘1.0’.
... ... @@ -528,4 +528,13 @@
528 528  
529 529  ----
530 530  
572 +[[~[1~]>>path:#_ftnref1]] Regular expressions, as specified in [[W3C XML Schema Definition Language (XSD)>>url:https://www.w3.org/TR/xmlschema11-2/]][[ >>url:https://www.w3.org/TR/xmlschema11-2/]][[1.1 Part 2: Datatypes>>url:https://www.w3.org/TR/xmlschema11-2/]][[.>>url:https://www.w3.org/TR/xmlschema11-2/]]
573 +
574 +[[~[2~]>>path:#_ftnref2]] The seconds can be reported fractionally
575 +
576 +[[~[3~]>>path:#_ftnref3]] ISO 8601 defines alternative definitions for the first week, all of which produce equivalent results. Any of these definitions could be substituted so long as they are in relation to the reporting year start day.
577 +
578 +[[~[4~]>>path:#_ftnref4]] The rules for adding durations to a date time are described in the W3C XML Schema specification. See [[http:~~/~~/www.w3.org/TR/xmlschema>>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[->>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[2/#adding>>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[->>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[durations>>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[->>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[to>>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[dateTimes>>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]][[ >>url:http://www.w3.org/TR/xmlschema-2/#adding-durations-to-dateTimes]]for further details.
579 +
580 +
531 531  {{putFootnotes/}}