Changes for page 4 General Notes for Implementers

Last modified by Artur on 2025/09/10 11:19

From 2.2 to 2.1 From 2.8 to 2.7

From version 2.7

edited by Helena
on 2025/06/08 23:44

Change comment: There is no comment for this version

To version 2.2

edited by Helena
on 2025/06/08 23:37

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -103,28 +103,47 @@
  Further to the above, the mapping between the non-native data types is presented in the table below:
--(% style="width:1005.83px" %)
--|(% style="width:198px" %)**SDMX Facet**|(% style="width:241px" %)**XML Schema**|(% style="width:563px" %)**JSON schema **"**pattern**"{{footnote}}Regular expressions, as specified in W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.{{/footnote}} **for "string" type**
--|(% style="width:198px" %)GregorianYear|(% style="width:241px" %)xsd:gYear|(% style="width:563px" %)(((
--"^-?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) **for "string" type**
++|GregorianYear|xsd:gYear|(((
++"^-?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\+|-)((0[0-
++
++9]|1[0-3]):[0-5][0-9]|14:00))?$"
  )))
--|(% style="width:198px" %)GregorianMonth|(% style="width:241px" %)xsd:gYearMonth|(% style="width:563px" %)(((
--"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|GregorianMonth|xsd:gYearMonth|(((
++"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-
++
++2])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-
++
++9]|14:00))?$"
  )))
--|(% style="width:198px" %)GregorianDay|(% style="width:241px" %)xsd:date|(% style="width:563px" %)(((
--"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|GregorianDay|xsd:date|(((
++"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-
++
++(0[1-9]|[12][0-9]|3[01])(Z|(\+|-)((0[0-9]|1[0-
++
++3]):[0-5][0-9]|14:00))?$"
  )))
--|(% style="width:198px" %)Day|(% style="width:241px" %)xsd:gDay|(% style="width:563px" %)(((
--"^~-~--(0[1-9]|[12][0-9]|3[01])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|Day|xsd:gDay|(((
++"^~-~--(0[1-9]|[12][0-9]|3[01])(Z|(\+|-
++
++)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
  )))
--|(% style="width:198px" %)MonthDay|(% style="width:241px" %)xsd:gMonthDay|(% style="width:563px" %)(((
--"^~-~-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|MonthDay|xsd:gMonthDay|(((
++"^~-~-(0[1-9]|1[0-2])-(0[1-9]|[12][0-
++
++9]|3[01])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-
++
++9]|14:00))?$"
  )))
--|(% style="width:198px" %)Month|(% style="width:241px" %)xsd:Month|(% style="width:563px" %)(((
--"^~-~-(0[1-9]|1[0-2])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
++|Month|xsd:Month|(((
++"^~-~-(0[1-9]|1[0-2])(Z|(\+|-)((0[0-9]|1[0-
++
++3]):[0-5][0-9]|14:00))?$"
  )))
--|(% style="width:198px" %)Duration|(% style="width:241px" %)xsd:duration|(% style="width:563px" %)(((
--"^-?P[0-9]+Y?([0-9]+M)?([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+(\.[0-9]+)?S)?)?$"
++|Duration|xsd:duration|(((
++"^-?P[0-9]+Y?([0-9]+M)?([0-9]+D)?(T([0-
++
++9]+H)?([0-9]+M)?([0-9]+(\.[0-9]+)?S)?)?$"
  )))
  == 4.2 Time and Time Format ==
@@ -139,14 +139,15 @@
  The hierarchy of time formats is as follows (**bold** indicates a category which is made up of multiple formats, //italic// indicates a distinct format):
--* **Observational Time Period**
--** **Standard Time Period**
--*** **Basic Time Period**
--**** **Gregorian Time Period**
--**** //Date Time//
--*** **Reporting Time Period**
--** //Time Range//
++* **Observational Time Period **o **Standard Time Period**
++                                      §     **Basic Time Period**
++
++* **Gregorian Time Period**
++* //Date Time//
++
++§    **Reporting Time Period **o //Time Range//
++
  The details of these time period categories and of the distinct formats which make them up are detailed in the sections to follow.
  === 4.2.2 Observational Time Period ===
@@ -162,12 +162,11 @@
  A Gregorian time period is always represented by a Gregorian year, year-month, or day. These are all based on ISO 8601 dates. The representation in SDMX-ML messages and the period covered by each of the Gregorian time periods are as follows:
  **Gregorian Year:**
++
  Representation: xs:gYear (YYYY)
--Period: the start of January 1 to the end of December 31
--**Gregorian Year Month**:
++Period: the start of January 1 to the end of December 31 **Gregorian Year Month**:
  Representation: xs:gYearMonth (YYYY-MM)
--Period: the start of the first day of the month to end of the last day of the month
--**Gregorian Day**:
++Period: the start of the first day of the month to end of the last day of the month **Gregorian Day**:
  Representation: xs:date (YYYY-MM-DD)
  Period: the start of the day (00:00:00) to the end of the day (23:59:59)
@@ -175,7 +175,7 @@
  This is used to unambiguously state that a date-time represents an observation at a single point in time. Therefore, if one wants to use SDMX for data which is measured at a distinct point in time rather than being reported over a period, the date-time representation can be used.
--Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss){{footnote}}The seconds can be reported fractionally{{/footnote}}
++Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]]
  === 4.2.6 Standard Reporting Period ===
@@ -191,46 +191,77 @@
  The following section details each of the standard reporting periods defined in SDMX:
  **Reporting Year**:
--Period Indicator: A
++
++           Period Indicator: A
++
  Period Duration: P1Y (one year)
++
  Limit per year: 1
--Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1)
--**Reporting Semester:**
--Period Indicator: S
++
++Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1) **Reporting Semester:**
++
++           Period Indicator: S
++
  Period Duration: P6M (six months)
++
  Limit per year: 2
++
  Representation: common:ReportingSemesterType (YYYY-Ss, e.g. 2000-S2)
++
  **Reporting Trimester:**
--Period Indicator: T
++
++           Period Indicator: T
++
  Period Duration: P4M (four months)
++
  Limit per year: 3
--Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3)
--**Reporting Quarter:**
--Period Indicator: Q
++
++Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3) **Reporting Quarter:**
++
++           Period Indicator: Q
++
  Period Duration: P3M (three months)
++
  Limit per year: 4
--Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4)
--**Reporting Month**:
++
++Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4) **Reporting Month**:
++
  Period Indicator: M
++
  Period Duration: P1M (one month)
++
  Limit per year: 1
++
  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.
++
  **Reporting Week**:
++
  Period Indicator: W
++
  Period Duration: P7D (seven days)
++
  Limit per year: 53
++
  Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53)
--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
--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.
++
++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" %)^^~[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.
++
  **Reporting Day**:
++
  Period Indicator: D
++
  Period Duration: P1D (one day)
++
  Limit per year: 366
++
  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.
++
  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.
--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.
++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.
++
  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]):
@@ -241,19 +241,19 @@
  This is the [REPORTING_YEAR_START_DATE]
--1.
++1.
 . **If the [PERIOD_INDICATOR] is W:**
 . **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
--Add[[(% class="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].
++Add[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
--1.
--11.
++1.
++11.
 . **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
  Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
--1.
++1.
 . **Else:**
  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
@@ -546,5 +546,4 @@
  [[~[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.
--
--{{putFootnotes/}}
++