Changes for page Guidelines on Non-Calendar Year Reporting of Data

Last modified by Artur K. on 2026/05/29 14:28

From 1.2 to 1.1

From version 2.1

edited by Artur K.
on 2026/05/29 14:28

Change comment: Copied from sdmxsrlocalization:Methodology.Guidelines on Non-Calendar Year Reporting of Data.WebHome

To version 1.2

edited by Helena K.
on 2026/01/16 11:47

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--xwiki:XWiki.arturkryazhev
++xwiki:XWiki.helena

Content

@@ -4,7 +4,7 @@
  = 1. Problem statement =
--In many cases, data that are exchanged in SDMX data messages do not relate to the calendar year. However, many statistical system implementations require that data are mapped to and stored as the real calendar.
++In many cases, data that are exchanged in SDMX data messages do not relate to the calendar year.  However, many statistical system implementations require that data are mapped to and stored as the real calendar.
  This guideline provides recommendations for the following four use cases of such non-calendar year data:
@@ -20,7 +20,7 @@
  [[image:1768553211015-575.png]]
--Assuming that the time dimension has the ID TIME_PERIOD, case 1 could use TIME_PERIOD=”2015”. All other cases would need to use the notation TIME_PERIOD=”2015-A1”. For the rest of the document we use the more general notation “2015-A1”.{{footnote}}The YYYY format is reserved for Gregorian years, i.e. from January 1 to December 31. For reporting years that are not Gregorian years, the format YYYY-A1 (e.g. 2016-A1) must be used for the time dimension.{{/footnote}}
++Assuming that the time dimension has the ID TIME_PERIOD, case 1 could use TIME_PERIOD=”2015”. All other cases would need to use the notation TIME_PERIOD=”2015-A1”. For the rest of the document we use the more general notation “2015-A1”. [[~[1~]>>path:#_ftn1||style="background-color: rgb(255, 255, 255);"]]
  For quarterly or monthly data, the first period of the reporting year would also need to be read as relative to the start of the reporting year. Here are examples for case 2 if the data is quarterly (2a) or monthly (2b):
@@ -28,7 +28,7 @@
  Note that in case 2a, the third quarter of reporting year 2015 (TIME_PERIOD=2015-Q3) is covering data from March until June 2016. In case 2b, the seventh month of reporting year 2015 (TIME_PERIOD=2015-M07) is covering data for January 2016.
--It is clear in the graphical view that time series under case 2b should not be directly compared with time series under case 4. If it is required to compare figures of the same time period, the 2015 observation of the type 2b series is compared with the 2016 figure of the type 4 series. Comparing a 2a series with others from the example may be more complicated, because exact alignment of the timelines might not be possible without additional data. It is possible to estimate aligned timelines by doing a time transformation using formulas; for instance, shifting the time series to comply with the calendar year. The methodological aspects of time transformation are not part of these guidelines. For coding the results of such transformations, please refer to the guidelines on coding time transformations in SDMX{{footnote}}https://sdmx.org/wp-content/uploads/SWG_TimeTransformation_V1.0.docx{{/footnote}}.
++It is clear in the graphical view that time series under case 2b should not be directly compared with time series under case 4. If it is required to compare figures of the same time period, the 2015 observation of the type 2b series is compared with the 2016 figure of the type 4 series. Comparing a 2a series with others from the example may be more complicated, because exact alignment of the timelines might not be possible without additional data. It is possible to estimate aligned timelines by doing a time transformation using formulas; for instance, shifting the time series to comply with the calendar year. The methodological aspects of time transformation are not part of these guidelines. For coding the results of such transformations, please refer to the guidelines on coding time transformations in SDMX[[~[2~]>>path:#_ftn2]].
  = 2. SDMX Concepts for Non-Calendar Year Series =
@@ -36,7 +36,7 @@
  In SDMX messages, the time period concept (concept ID TIME_PERIOD) specifies the **reporting period**. This reporting period, as outlined above, is in many cases not aligned with the calendar year.
--To specify the calendar period that a reporting period is covering, the SDMX technical standard already defines an attribute “reporting year start” on series level with format xs:gMonthDay{{footnote}}https://sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf, row 658.{{/footnote}}. It gives a day and month when the reporting year starts. It is optional and if not provided the default is 1^^st^^ January. Using this attribute can cover cases 1, 2 and 3 from above. When added to a series, the attribute will specify on which day of the calendar year the reporting year starts.
++To specify the calendar period that a reporting period is covering, the SDMX technical standard already defines an attribute “reporting year start” on series level with format xs:gMonthDay[[~[3~]>>path:#_ftn3]]. It gives a day and month when the reporting year starts. It is optional and if not provided the default is 1^^st^^ January. Using this attribute can cover cases 1, 2 and 3 from above. When added to a series, the attribute will specify on which day of the calendar year the reporting year starts.
  This is not sufficient to cover case 4, because in this case the reporting year 2015 starts in 2014. In order to specify this case, a different attribute “reporting year end” should be used. It is also on series level with format xs:gMonthDay and gives a day and month when the reporting year ends. It is optional and if not provided the default is 31^^st^^ December.
@@ -46,8 +46,7 @@
  == //ISO 8601 time interval// ==
--As outlined above, in some cases reporting periods might not have the same duration as calendar periods. A crop year in agriculture may only last for a couple of months. To specify these periods on a more granular level, the SDMX technical standard suggests using the time intervals as defined by ISO 8601. ISO specifies four ways to express a time interval{{footnote}}http://www.iso.org/iso/home/standards/iso8601.htm and
--https://sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf, row 749.{{/footnote}}:
++As outlined above, in some cases reporting periods might not have the same duration as calendar periods. A crop year in agriculture may only last for a couple of months. To specify these periods on a more granular level, the SDMX technical standard suggests using the time intervals as defined by ISO 8601. ISO specifies four ways to express a time interval[[~[4~]>>path:#_ftn4]]:
 . Start and end, such as "2007-03-01T13:00:00Z/2008-05-11T15:30:00Z"
 . Start and duration, such as "2007-03-01T13:00:00Z/P1Y2M10DT2H30M"
@@ -54,6 +54,8 @@
 . Duration and end, such as "P1Y2M10DT2H30M/2008-05-11T15:30:00Z"
 . Duration only, such as "P1Y2M10DT2H30M", with additional context information
++
++
  An attribute time range (ID:TIME_RANGE) is suggested at the observation level to specify further in which particular time range a specific observation was collected. The series will still specify when the reporting period starts or ends for the whole series and each observation can have a specific time range within that reporting period. It is suggested for that case to use only option 1, the start and end date, and not the other options in SDMX context.
  = 3. Example 1: Based on National Accounts data exchange =
@@ -66,47 +66,49 @@
  The code list for “reference period detail” previously used in the National Accounts DSDs is as follows:
--|(% style="width:168px" %)**Code**|(% style="width:2050px" %)**Description**
--|(% style="width:168px" %)C|(% style="width:2050px" %)Calendar year
--|(% style="width:168px" %)F_O|(% style="width:2050px" %)Fiscal year (other definition)
--|(% style="width:168px" %)F02|(% style="width:2050px" %)Fiscal year starting in February
--|(% style="width:168px" %)F03|(% style="width:2050px" %)Fiscal year starting in March
--|(% style="width:168px" %)F04|(% style="width:2050px" %)Fiscal year starting in April
--|(% style="width:168px" %)F05|(% style="width:2050px" %)Fiscal year starting in May
--|(% style="width:168px" %)F06|(% style="width:2050px" %)Fiscal year starting in June
--|(% style="width:168px" %)F07|(% style="width:2050px" %)Fiscal year starting in July
--|(% style="width:168px" %)F08|(% style="width:2050px" %)Fiscal year starting in August
--|(% style="width:168px" %)F09|(% style="width:2050px" %)Fiscal year starting in September
--|(% style="width:168px" %)F10|(% style="width:2050px" %)Fiscal year starting in October
--|(% style="width:168px" %)F11|(% style="width:2050px" %)Fiscal year starting in November
--|(% style="width:168px" %)F12|(% style="width:2050px" %)Fiscal year starting in December
++|**Code**|**Description**
++|C|Calendar year
++|F_O|Fiscal year (other definition)
++|F02|Fiscal year starting in February
++|F03|Fiscal year starting in March
++|F04|Fiscal year starting in April
++|F05|Fiscal year starting in May
++|F06|Fiscal year starting in June
++|F07|Fiscal year starting in July
++|F08|Fiscal year starting in August
++|F09|Fiscal year starting in September
++|F10|Fiscal year starting in October
++|F11|Fiscal year starting in November
++|F12|Fiscal year starting in December
++
++
  Following this code list, the cases lined out in the problem statement could be coded as such:
--1) Reporting year is equal to the calendar year
++1. Reporting year is equal to the calendar year
  <na_:Series **REF_PERIOD_DETAIL="C" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  REF_PERIOD_DETAIL="C" à reporting year 1995 starts 1^^st^^ January 1995
--2) Reporting year starts on the first day of a month different to January
++1. Reporting year starts on the first day of a month different to January
  Example: fiscal year starting on the 1^^st^^ of July
  <na_:Series **REF_PERIOD_DETAIL="F07" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  REF_PERIOD_DETAIL="F07" à reporting year 1995 starts 1^^st^^ July 1995 and Q1 projected on the calendar year goes from: 07-09/1995
--3) Reporting year starts on a given day in the year
++1. Reporting year starts on a given day in the year
  Example: tax year starting on the 5^^th^^ of April
  <na_:Series **REF_PERIOD_DETAIL="F04" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
@@ -113,17 +113,17 @@
  REF_PERIOD_DETAIL="F04" à reporting year 1995 would start 1^^st^^ April 1995. The case is not solved because we do not know anymore that it should be on the 5^^th^^. Another option would be to use the “F_O” code:
  <na_:Series **REF_PERIOD_DETAIL="F_O" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  REF_PERIOD_DETAIL="F_O" à reporting year 1995 has another definition. The case is only partly solved because we do not know the exact date. Additional metadata are needed and the reporting period cannot directly be parsed by a system.
--4) Reporting year **ends** on a given day in the year
++1. Reporting year **ends** on a given day in the year
  Example: fiscal year ending on the 30^^th^^ of June, equivalent to fiscal year starting on the 1^^st^^ of July Y-1
  <na_:Series **REF_PERIOD_DETAIL="??" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
@@ -133,42 +133,43 @@
  Using the attributes as suggested above, all cases outlined in the National Account examples can be fully covered:
--1) Reporting year is equal to the calendar year
++1. Reporting year is equal to the calendar year
  <na_:Series **REF_PERIOD_DETAIL="C" REPYEARSTART="~-~-01-01"// //**STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
++
 -Q1 is the same as the calendar definition: from 1^^st^^ January 1995 until 31^^st^^ March 1995. In this case, the attribute REPYEARSTART may be omitted, since it expressed the default value of 1^^st^^ January.
--2) Reporting year starts on the first day of a month different to January
++Reporting year starts on the first day of a month different to January
  Example: fiscal year starting on the 1^^st^^ of July
  <na_:Series **REF_PERIOD_DETAIL="F07" REPYEARSTART="~-~-07-01" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  Reporting period 1995-Q1 lasts in that case from 1^^st^^ July 1995 until 30^^th^^ September 1995.
--3) Reporting year starts on a given day in the year
++1. Reporting year starts on a given day in the year
  Example: tax year starting on the 5^^th^^ of April
  <na_:Series **REF_PERIOD_DETAIL="F04" REPYEARSTART="~-~-04-05" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  Reporting period 1995-Q1 lasts in that case from 5^^th^^ April 1995 until 4^^th^^ July 1995.
--4) Reporting year **ends** on a given day in the year
++1. Reporting year **ends** on a given day in the year
  Example: fiscal year ending on the 30^^th^^ of June, equivalent to fiscal year starting on the 1^^st^^ of July Y-1
  <na_:Series **REF_PERIOD_DETAIL="??" REPYEAREND="~-~-06-30" **STO="B1G" REF_AREA="LU" FREQ="Q">
--      <na_:Obs OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
++      <na_:Obs  OBS_VALUE="44" TIME_PERIOD="**1995**-Q1"/>
  </na_:Series>
  Reporting period 1995-Q1 lasts in that case from 1^^st^^ July 1994 until 30^^th^^ September 1994
--= 4. Example 2: Based on Agriculture data exchange =
++1. Example 2: Based on Agriculture data exchange
  == //Problem statement// ==
@@ -188,6 +188,7 @@
  Note that the DSD proposal below does not constitute a real usable DSD for agriculture statistics. It is heavily simplified to only include concepts that are relevant for the purpose of these guidelines. Also the SDMX fragments shown in the example are not syntactically correct. They just serve the purpose of explaining the issue and show the coding in a readable way (pseudo code).
++
  |**Concept ID**|**Description**|**Role**|**Code List / Format**
  |**FREQ**|Frequency|Dimension|A (annual), S (Half-yearly)
  |**REF_AREA**|Reference area|Dimension|IN (India), CN (China)
@@ -242,16 +242,15 @@
  **Sample Data for China**
--(% style="width:918.446px" %)
--|(% style="width:121px" %)**Crop year**|(% style="width:165px" %)**Season**|(% style="width:191px" %)**Calendar period**|(% style="width:438px" %)**Units**
--|(% style="width:121px" %)**2011**|(% style="width:165px" %)Winter|(% style="width:191px" %)Sep-Oct 2010|(% style="width:438px" %)100 planted
--|(% style="width:121px" %) |(% style="width:165px" %) |(% style="width:191px" %)May-Jun 2011|(% style="width:438px" %)100 harvested
--|(% style="width:121px" %) |(% style="width:165px" %)Summer|(% style="width:191px" %)Mar-Apr 2011|(% style="width:438px" %)200 planted
--|(% style="width:121px" %) |(% style="width:165px" %) |(% style="width:191px" %)Jul-Aug 2011|(% style="width:438px" %)200 harvested
--|(% style="width:121px" %)**2012**|(% style="width:165px" %)Winter|(% style="width:191px" %)Sep-Oct 2011|(% style="width:438px" %)120 planted
--|(% style="width:121px" %) |(% style="width:165px" %) |(% style="width:191px" %)May-Jun 2011|(% style="width:438px" %)120 harvested
--|(% style="width:121px" %) |(% style="width:165px" %)Summer|(% style="width:191px" %)Mar-Apr 2012|(% style="width:438px" %)220 planted
--|(% style="width:121px" %) |(% style="width:165px" %) |(% style="width:191px" %)Jul-Aug 2012|(% style="width:438px" %)220 harvested
++|**Crop year**|**Season**|**Calendar period**|**Units**
++|**2011**|Winter|Sep-Oct 2010|100 planted
++| | |May-Jun 2011|100 harvested
++| |Summer|Mar-Apr 2011|200 planted
++| | |Jul-Aug 2011|200 harvested
++|**2012**|Winter|Sep-Oct 2011|120 planted
++| | |May-Jun 2011|120 harvested
++| |Summer|Mar-Apr 2012|220 planted
++| | |Jul-Aug 2012|220 harvested
  == //Recommendations based on the Use Cases from Agriculture// ==
@@ -342,4 +342,11 @@
  ----
--{{putFootnotes/}}
++[[~[1~]>>path:#_ftnref1]] The //YYYY// format is reserved for Gregorian years, i.e. from January 1 to December 31. For reporting years that are not Gregorian years, the format YYYY-A1 (e.g. 2016-A1) must be used for the time dimension
++
++[[~[2~]>>path:#_ftnref2]] [[https:~~/~~/sdmx.org/wp-content/uploads/SWG_TimeTransformation_V1.0.docx>>url:https://sdmx.org/wp-content/uploads/SWG_TimeTransformation_V1.0.docx]]
++
++[[~[3~]>>path:#_ftnref3]] [[https:~~/~~/sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf>>url:https://sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf]], row 658
++
++[[~[4~]>>path:#_ftnref4]] [[http:~~/~~/www.iso.org/iso/home/standards/iso8601.htm>>url:http://www.iso.org/iso/home/standards/iso8601.htm]] and
++[[https:~~/~~/sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf>>url:https://sdmx.org/wp-content/uploads/SDMX_2-1-1-SECTION_6_TechnicalNotes-march-2013.pdf]], row 749.