Changes for page 4 General Notes for Implementers

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

From 2.9 to 2.10 From 2.16 to 3.1

From version 2.10

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

Change comment: There is no comment for this version

To version 2.16

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -237,20 +237,18 @@
  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]
--1.
--11. **If the [PERIOD_INDICATOR] is W:**
--111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
++a) **If the [PERIOD_INDICATOR] is W:**
--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].
++**~1. If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
++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].
--1.
--11.
--111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
++2. **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].
++Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the
++[REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
--1.
--11. **Else:**
++**b)** **Else:**
  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
@@ -265,7 +265,7 @@
 . 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].
++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].
 . **Determine the [PERIOD_END]:**
@@ -331,25 +331,26 @@
  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: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" %)(((
++(% 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" %)(((
  Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
  )))
--|(% 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)
++|(% 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)
  (% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
  **Table 1: SDMX-ML Time Format Codes**
@@ -399,12 +399,13 @@
  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.
--|**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
++(% 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
  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.
@@ -411,11 +411,8 @@
  **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
@@ -431,9 +431,7 @@
  * 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
@@ -445,9 +445,9 @@
  * 2010-T3 (any reporting year start day)
  * 2010-Q3 or later (any reporting year start day)
  * 2010-M07 or later (any reporting year start day)
--* 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
++* 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}}
  * 2010-D182 or later (reporting year start day ~-~-01-01)
--* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
++* 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}}
  * 2010-D185 or later (reporting year start day ~-~-07-01)
  == 4.3 Versioning ==
@@ -454,12 +454,8 @@
  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" [[(>>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
++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’.
--//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’.
@@ -535,13 +535,4 @@
  ----
--[[~[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/]]
--
--[[~[2~]>>path:#_ftnref2]] The seconds can be reported fractionally
--
--[[~[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.
--
--[[~[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/}}