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 version 1.1

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

Change comment: There is no comment for this version

To version 2.9

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -10,26 +10,26 @@
  There are several different representations in SDMX-ML, taken from XML Schemas and common programming languages. The table below describes the various representations, which are found in SDMX-ML, and their equivalents.
--|SDMX-ML Data Type|XML Schema Data Type|.NET Framework Type|(((
--Java Data Type
++|(% style="width:191px" %)**SDMX-ML Data Type**|(% style="width:232px" %)**XML Schema Data Type**|(% style="width:212px" %)**.NET Framework Type**|(% style="width:980px" %)(((
++**Java Data Type**
  )))
--|**String**|**xsd:string**|**System.String**|**java.lang.String**
--|**Big Integer**|**xsd:integer**|**System.Decimal**|**java.math.BigInteger**
--|**Integer**|**xsd:int**|**System.Int32**|**int**
--|**Long**|**xsd.long**|**System.Int64**|**long**
--|**Short**|**xsd:short**|**System.Int16**|**short**
--|**Decimal**|**xsd:decimal**|**System.Decimal**|**java.math.BigDecimal**
--|**Float**|**xsd:float**|**System.Single**|**float**
--|**Double**|**xsd:double**|**System.Double**|**double**
--|**Boolean**|**xsd:boolean**|**System.Boolean**|**boolean**
--|**URI**|**xsd:anyURI**|**System.Uri**|**Java.net.URI or java.lang.String**
--|**DateTime**|**xsd:dateTime**|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**Time**|**xsd:time**|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**GregorianYear**|**xsd:gYear**|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**GregorianMonth**|**xsd:gYearMonth**|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**GregorianDay**|**xsd:date**|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**Day, MonthDay, Month**|**xsd:g***|**System.DateTime**|**javax.xml.datatype.XMLG regorianCalendar**
--|**Duration**|**xsd:duration**|**System.TimeSpan**|**javax.xml.datatype.Dura tion**
++|(% style="width:191px" %)String|(% style="width:232px" %)xsd:string|(% style="width:212px" %)System.String|(% style="width:980px" %)java.lang.String
++|(% style="width:191px" %)Big Integer|(% style="width:232px" %)xsd:integer|(% style="width:212px" %)System.Decimal|(% style="width:980px" %)java.math.BigInteger
++|(% style="width:191px" %)Integer|(% style="width:232px" %)xsd:int|(% style="width:212px" %)System.Int32|(% style="width:980px" %)int
++|(% style="width:191px" %)Long|(% style="width:232px" %)xsd.long|(% style="width:212px" %)System.Int64|(% style="width:980px" %)long
++|(% style="width:191px" %)Short|(% style="width:232px" %)xsd:short|(% style="width:212px" %)System.Int16|(% style="width:980px" %)short
++|(% style="width:191px" %)Decimal|(% style="width:232px" %)xsd:decimal|(% style="width:212px" %)System.Decimal|(% style="width:980px" %)java.math.BigDecimal
++|(% style="width:191px" %)Float|(% style="width:232px" %)xsd:float|(% style="width:212px" %)System.Single|(% style="width:980px" %)float
++|(% style="width:191px" %)Double|(% style="width:232px" %)xsd:double|(% style="width:212px" %)System.Double|(% style="width:980px" %)double
++|(% style="width:191px" %)Boolean|(% style="width:232px" %)xsd:boolean|(% style="width:212px" %)System.Boolean|(% style="width:980px" %)boolean
++|(% style="width:191px" %)URI|(% style="width:232px" %)xsd:anyURI|(% style="width:212px" %)System.Uri|(% style="width:980px" %)Java.net.URI or java.lang.String
++|(% style="width:191px" %)DateTime|(% style="width:232px" %)xsd:dateTime|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)Time|(% style="width:232px" %)xsd:time|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)GregorianYear|(% style="width:232px" %)xsd:gYear|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)GregorianMonth|(% style="width:232px" %)xsd:gYearMonth|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)GregorianDay|(% style="width:232px" %)xsd:date|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)Day, MonthDay, Month|(% style="width:232px" %)xsd:g*|(% style="width:212px" %)System.DateTime|(% style="width:980px" %)javax.xml.datatype.XMLGregorianCalendar
++|(% style="width:191px" %)Duration|(% style="width:232px" %)xsd:duration|(% style="width:212px" %)System.TimeSpan|(% style="width:980px" %)javax.xml.datatype.Duration
  There are also a number of SDMX-ML data types which do not have these direct correspondences, often because they are composite representations or restrictions of a broader data type. For most of these, there are simple types which can be referenced from the SDMX schemas, for others a derived simple type will be necessary:
@@ -76,7 +76,7 @@
  Note that code lists may also have textual representations assigned to them, in addition to their enumeration of codes.
--4.1.1 Data Types
++=== 4.1.1 Data Types ===
  XML and JSON schemas support a variety of data types that, although rich, are not mapped one-to-one in all cases. This section provides an explanation of the mapping performed in SDMX 3.0, between such cases.
@@ -95,8 +95,8 @@
  The above looks like this, in JSON schema:
  > "idType": {
--> "type": "string",
--> "pattern": "^[A-Za-z0-9_@$-]+$"
++>    "type": "string",
++>    "pattern": "^[A-Za-z0-9_@$-]+$"
  > }
  There are also cases, though, that data types cannot be mapped like above. One such case is the array data type, which was introduced in SDMX 3.0 as a new representation. In JSON schema an array is already natively foreseen, while in the XML schema, this has to be defined as a complex type, with an SDMX specific definition (i.e., specific element/attribute names for SDMX). Beyond that, the minimum and/or maximum number of items within an array is possible in both cases.
@@ -103,57 +103,35 @@
  Further to the above, the mapping between the non-native data types is presented in the table below:
--|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"[[^^~[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: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))?$"
  )))
--|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" %)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))?$"
  )))
--|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" %)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))?$"
  )))
--|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" %)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))?$"
  )))
--|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" %)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))?$"
  )))
--|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" %)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))?$"
  )))
--|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)?)?$"
++|(% 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)?)?$"
  )))
--1.
--11. Time and Time Format
++== 4.2 Time and Time Format ==
  This section does not go into great detail on these topics but provides a useful overview of these features to assist implementors in further use of the parts of the specification which are relevant to them.
--1.
--11.
--111. Introduction
++=== 4.2.1 Introduction ===
  First, it is important to recognize that most observation times are a period. SDMX specifies precisely how Time is handled.
@@ -161,61 +161,45 @@
  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 **o **Standard Time Period**
++* **Observational Time Period**
++** **Standard Time Period**
++*** **Basic Time Period**
++**** **Gregorian Time Period**
++**** //Date Time//
++*** **Reporting Time Period**
++** //Time Range//
--                                      §     **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.
--1.
--11.
--111. Observational Time Period
++=== 4.2.2 Observational Time Period ===
  This is the superset of all time representations in SDMX. This allows for time to be expressed as any of the allowable formats.
--1.
--11.
--111. Standard Time Period
++=== 4.2.3 Standard Time Period ===
  This is the superset of any predefined time period or a distinct point in time. A time period consists of a distinct start and end point. If the start and end of a period are expressed as date instead of a complete date time, then it is implied that the start of the period is the beginning of the start day (i.e. 00:00:00) and the end of the period is the end of the end day (i.e. 23:59:59).
--1.
--11.
--111. Gregorian Time Period
++=== 4.2.4 Gregorian Time Period ===
  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)
--1.
--11.
--111. Date Time
++=== 4.2.5 Date Time ===
  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)[[^^~[2~]^^>>path:#_ftn2]]
++Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss){{footnote}}The seconds can be reported fractionally{{/footnote}}
--1.
--11.
--111. Standard Reporting Period
++=== 4.2.6 Standard Reporting Period ===
  Standard reporting periods are periods of time in relation to a reporting year. Each of these standard reporting periods has a duration (based on the ISO 8601 definition) associated with it. The general format of a reporting period is as follows:
@@ -224,91 +224,55 @@
  Where:
  REPORTING_YEAR represents the reporting year as four digits (YYYY) PERIOD_INDICATOR identifies the type of period which determines the duration of the period
--
  PERIOD_VALUE indicates the actual period within the year
  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.[[^^~[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.
--
++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.
  **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
++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.
--(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]):
--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]:**
--
++**~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]
 .
@@ -315,7 +315,7 @@
 . **If the [PERIOD_INDICATOR] is W:**
 . **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
--Add[[^^~[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 wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
 .
 .
@@ -396,45 +396,38 @@
  The actual calendar range covered by 2011-W36 (assuming the reporting year begins July 1) is 2012-03-05T00:00:00/2012-03-11T23:59:59
--1.
--11.
--111. Distinct Range
++=== 4.2.7 Distinct Range ===
  In the case that the reporting period does not fit into one of the prescribe periods above, a distinct time range can be used. The value of these ranges is based on the ISO 8601 time interval format of start/duration. Start can be expressed as either an ISO 8601 date or a date-time, and duration is expressed as an ISO 8601 duration. However, the duration can only be positive.
--1.
--11.
--111. Time Format
++=== 4.2.8 Time Format ===
  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.
--|Code|Format
--|OTP|Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
--|STP|Standard Time Period: Superset of Gregorian and Reporting Time Periods
--|GTP|Superset of all Gregorian Time Periods and date-time
--|RTP|Superset of all Reporting Time Periods
--|TR|(((
--Time        Range:        Start        time        and        duration          (YYYY-MM-
--
--DD(Thh:mm:ss)?/<duration>)
++|(% 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>)
  )))
--|GY|Gregorian Year (YYYY)
--|GTM|Gregorian Year Month (YYYY-MM)
--|GD|Gregorian Day (YYYY-MM-DD)
--|DT|Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
--|RY|Reporting Year (YYYY-A1)
--|RS|Reporting Semester (YYYY-Ss)
--|RT|Reporting Trimester (YYYY-Tt)
--|RQ|Reporting Quarter (YYYY-Qq)
--|RM|Reporting Month (YYYY-Mmm)
--|RW|Reporting Week (YYYY-Www)
--|RD|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)
--==== Table 1: SDMX-ML Time Format Codes ====
++(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
++**Table 1: SDMX-ML Time Format Codes**
--1.
--11.
--111. Time Zones
++=== 4.2.9 Time Zones ===
  In alignment with ISO 8601, SDMX allows the specification of a time zone on all time periods and on the reporting year start day. If a time zone is provided on a reporting year start day, then the same time zone (or none) should be reported for each reporting time period. If the reporting year start day and the reporting period time zone differ, the time zone of the reporting period will take precedence. Examples of each format with time zones are as follows (time zone indicated in bold):
@@ -455,33 +455,25 @@
  According to ISO 8601, a date without a time-zone is considered "local time". SDMX assumes that local time is that of the sender of the message. In this version of SDMX, an optional field is added to the sender definition in the header for specifying a time zone. This field has a default value of 'Z' (UTC). This determination of local time applies for all dates in a message.
--1.
--11.
--111. Representing Time Spans Elsewhere
++=== 4.2.10 Representing Time Spans Elsewhere ===
  It has been possible since SDMX 2.0 for a Component to specify a representation of a time span. Depending on the format of the data message, this resulted in either an element with 2 XML attributes for holding the start time and the duration or two separate XML attributes based on the underlying Component identifier. For example, if REF_PERIOD were given a representation of time span, then in the Compact data format, it would be represented by two XML attributes; REF_PERIODStartTime (holding the start) and REF_PERIOD (holding the duration). If a new simple type is introduced in the SDMX schemas that can hold ISO 8601 time intervals, then this will no longer be necessary. What was represented as this:
--<Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
++>(% style="font-size:18px" %) <Series REF_PERIODStartTime="2000-01-01T00:00:00" REF_PERIOD="P2M"/>
  can now be represented with this:
--<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
++>(% style="font-size:18px" %) <Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
--1.
--11.
--111. Notes on Formats
++=== 4.2.11 Notes on Formats ===
  There is no ambiguity in these formats so that for any given value of time, the category of the period (and thus the intended time period range) is always clear. It should also be noted that by utilizing the ISO 8601 format, and a format loosely based on it for the report periods, the values of time can easily be sorted chronologically without additional parsing.
--1.
--11.
--111. Effect on Time Ranges
++=== 4.2.12 Effect on Time Ranges ===
  All SDMX-ML data messages are capable of functioning in a manner similar to SDMXEDI if the Dimension at the observation level is time: the time period for the first observation can be stated and the rest of the observations can omit the time value as it can be derived from the start time and the frequency. Since the frequency can be determined based on the actual format of the time value for everything but distinct points in time and time ranges, this makes is even simpler to process as the interval between time ranges is known directly from the time value.
--1.
--11.
--111. Time in Query Messages
++=== 4.2.13 Time in Query Messages ===
  When querying for time values, the value of a time parameter can be provided as any of the Observational Time Period formats and must be paired with an operator. This section will detail how systems processing query messages should interpret these parameters.
@@ -535,9 +535,11 @@
  * 2010-M07 or later (any reporting year start day)
  * 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
  * 2010-D182 or later (reporting year start day ~-~-01-01)
--* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^ •    2010-D185 or later (reporting year start day ~-~-07-01)
--*1. Versioning
++* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
++* 2010-D185 or later (reporting year start day ~-~-07-01)
++== 4.3 Versioning ==
++
  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
@@ -546,17 +546,13 @@
  ‘1.0’.
--1.
--11.
--111. Non-versioned artefacts
++=== 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’.
  Many existing organisation’s data management systems work with version-less structures and apply ad-hoc structural metadata governance processes. The new nonversioned artefacts will allow supporting those numerous situations, where organisations do not manage version numbers.
--1.
--11.
--111. Semantically versioned artefacts
++=== 4.3.2 Semantically versioned artefacts ===
  Since the purpose of SDMX versioning is to allow communicating the structural artefact changes to data exchange partners and connected systems, SDMX 3.0 offers Semantic Versioning (aka SemVer) with a clear and unambiguous syntax to all semantically versioned SDMX 3.0 structural artefacts. Semantic versioning will thus better respond to situations where the SDMX standard itself is the only structural contract between data providers and data consumers and where changes in structures can only be communicated through the version number increases.
@@ -580,17 +580,13 @@
  The production versions of identifiable artefacts are assumed stable, i.e., they do not have an EXTENSION. This is because once in production, an artefact cannot change in any way, or it must change the version. For cases where an artefact is not static, like during the drafting, the version must indicate this by including an EXTENSION. Draft artefacts should not be used outside of a specific system designed to accommodate them. For most purposes, all artefacts should become stable before being used in production.
--1.
--11.
--111. Legacy-versioned artefacts
++=== 4.3.3 Legacy-versioned artefacts ===
  Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for version numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new SDMX 3.0 standard does not add any strict rules or guarantees about changes in those artefacts, since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
  In order to make artefacts immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
--1.
--11.
--111. Dependency management and references
++=== 4.3.4 Dependency management and references ===
  New flexible dependency specifications with wildcarding allow for easier data model maintenance and enhancements for semantically versioned SDMX artefacts. This allows implementing a smart referencing mechanism, whereby an artefact may reference:
@@ -619,8 +619,7 @@
  Full details can be found in the SDMX RESTful web services specification.
--1.
--11. Structural Metadata Querying Best Practices
++== 4.4 Structural Metadata Querying Best Practices ==
  When querying for structural metadata, the ability to state how references should be resolved is quite powerful. However, this mechanism is not always necessary and can create an undue burden on the systems processing the queries if it is not used properly.
@@ -628,7 +628,6 @@
  When the referenced object is not known, then the reference resolution mechanism could be used. For example, suppose one wanted to find all category schemes and the related categorisations for a given maintenance agency. In this case, one could query for the category scheme by the maintenance agency and specify that parent and sibling references should be resolved. This would result in the categorisations which reference the categories in the matched schemes to be returned, as well as the object which they categorise.
--
  ----
  [[~[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/]]
@@ -639,4 +639,5 @@
  [[~[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/}}