Changes for page 4 General Notes for Implementers

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

From 2.4 to 2.3 From 2.13 to 2.12

From version 2.12

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

Change comment: There is no comment for this version

To version 2.4

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -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 wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]]
  === 4.2.6 Standard Reporting Period ===
@@ -191,50 +191,85 @@
  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 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
--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]):
++(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.
--**~1. Determine [REPORTING_YEAR_BASE]:**
++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]):
++
++1. **Determine [REPORTING_YEAR_BASE]:**
++
  Combine [REPORTING_YEAR] of the reporting period value (YYYY) with [REPORTING_YEAR_START_DAY] (MM-DD) to get a date (YYYY-MM-DD).
++
  This is the [REPORTING_YEAR_START_DATE]
 .
@@ -241,7 +241,7 @@
 . **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 wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
 .
 .
@@ -254,15 +254,14 @@
  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
--**2. Determine [PERIOD_DURATION]:**
--
--1. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
--1. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
--1. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
--1. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
--1. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
--1. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
--1. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
++1. **Determine [PERIOD_DURATION]:**
++11. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
++11. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
++11. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
++11. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
++11. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
++11. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
++11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
 . **Determine [PERIOD_START]:**
  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].
@@ -331,26 +331,25 @@
  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.
--(% style="width:890.835px" %)
--|(% style="width:95px" %)**Code**|(% style="width:793px" %)**Format**
--|(% 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)
--|(% style="width:95px" %)STP|(% style="width:793px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
--|(% style="width:95px" %)GTP|(% style="width:793px" %)Superset of all Gregorian Time Periods and date-time
--|(% style="width:95px" %)RTP|(% style="width:793px" %)Superset of all Reporting Time Periods
--|(% style="width:95px" %)TR|(% style="width:793px" %)(((
++|(% style="width:95px" %)Code|(% style="width:1520px" %)Format
++|(% 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)
++|(% style="width:95px" %)STP|(% style="width:1520px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
++|(% style="width:95px" %)GTP|(% style="width:1520px" %)Superset of all Gregorian Time Periods and date-time
++|(% style="width:95px" %)RTP|(% style="width:1520px" %)Superset of all Reporting Time Periods
++|(% style="width:95px" %)TR|(% style="width:1520px" %)(((
  Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
  )))
--|(% style="width:95px" %)GY|(% style="width:793px" %)Gregorian Year (YYYY)
--|(% style="width:95px" %)GTM|(% style="width:793px" %)Gregorian Year Month (YYYY-MM)
--|(% style="width:95px" %)GD|(% style="width:793px" %)Gregorian Day (YYYY-MM-DD)
--|(% style="width:95px" %)DT|(% style="width:793px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
--|(% style="width:95px" %)RY|(% style="width:793px" %)Reporting Year (YYYY-A1)
--|(% style="width:95px" %)RS|(% style="width:793px" %)Reporting Semester (YYYY-Ss)
--|(% style="width:95px" %)RT|(% style="width:793px" %)Reporting Trimester (YYYY-Tt)
--|(% style="width:95px" %)RQ|(% style="width:793px" %)Reporting Quarter (YYYY-Qq)
--|(% style="width:95px" %)RM|(% style="width:793px" %)Reporting Month (YYYY-Mmm)
--|(% style="width:95px" %)RW|(% style="width:793px" %)Reporting Week (YYYY-Www)
--|(% style="width:95px" %)RD|(% style="width:793px" %)Reporting Day (YYYY-Dddd)
++|(% style="width:95px" %)GY|(% style="width:1520px" %)Gregorian Year (YYYY)
++|(% style="width:95px" %)GTM|(% style="width:1520px" %)Gregorian Year Month (YYYY-MM)
++|(% style="width:95px" %)GD|(% style="width:1520px" %)Gregorian Day (YYYY-MM-DD)
++|(% style="width:95px" %)DT|(% style="width:1520px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
++|(% style="width:95px" %)RY|(% style="width:1520px" %)Reporting Year (YYYY-A1)
++|(% style="width:95px" %)RS|(% style="width:1520px" %)Reporting Semester (YYYY-Ss)
++|(% style="width:95px" %)RT|(% style="width:1520px" %)Reporting Trimester (YYYY-Tt)
++|(% style="width:95px" %)RQ|(% style="width:1520px" %)Reporting Quarter (YYYY-Qq)
++|(% style="width:95px" %)RM|(% style="width:1520px" %)Reporting Month (YYYY-Mmm)
++|(% style="width:95px" %)RW|(% style="width:1520px" %)Reporting Week (YYYY-Www)
++|(% style="width:95px" %)RD|(% style="width:1520px" %)Reporting Day (YYYY-Dddd)
  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
  **Table 1: SDMX-ML Time Format Codes**
@@ -400,13 +400,12 @@
  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.
--(% style="width:770.835px" %)
--|(% style="width:220px" %)**Operator**|(% style="width:548px" %)**Rule**
--|(% style="width:220px" %)Greater Than|(% style="width:548px" %)Any data after the last moment of the period
--|(% style="width:220px" %)Less Than|(% style="width:548px" %)Any data before the first moment of the period
--|(% style="width:220px" %)Greater Than or Equal To|(% style="width:548px" %)Any data on or after the first moment of the period
--|(% style="width:220px" %)Less Than or Equal To|(% style="width:548px" %)Any data on or before the last moment of the period
--|(% 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
++|**Operator**|**Rule**
++|Greater Than|Any data after the last moment of the period
++|Less Than|Any data before the first moment of the period
++|Greater Than or Equal To|Any data on or after the first moment of the period
++|Less Than or Equal To|Any data on or before the last moment of the period
++|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
  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.
@@ -413,8 +413,11 @@
  **Examples:**
  **Gregorian Period**
++
  Query Parameter: Greater than 2010
++
  Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
++
  Example Matches:
  * 2011 or later
@@ -430,7 +430,9 @@
  * 2010-D185 or later (reporting year start day ~-~-07-01 or later)
  **Reporting Period**
++
  Query Parameter: Greater than or equal to 2010-Q3
++
  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:
  * 2011 or later
@@ -451,8 +451,12 @@
  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".
--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’.
++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
++//MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version
++
++‘1.0’.
++
  === 4.3.1 Non-versioned artefacts ===
  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’.