Changes for page 4 General Notes for Implementers

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

From 3.2 to 3.1 From 5.3 to 5.2

From version 5.2

edited by Helena
on 2025/05/16 23:55

Change comment: There is no comment for this version

To version 3.2

edited by Helena
on 2025/05/15 23:44

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -2,13 +2,13 @@
  {{toc/}}
  {{/box}}
--This section discusses a number of topics other than the exchange of [[data sets>>doc:xwiki:Glossary.Data set.WebHome]] in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] formats. Supported only in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] (and some in [[SDMX-JSON>>doc:xwiki:Glossary.SDMX-JSON.WebHome]]), these topics include the use of the [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] mechanism in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], the use of [[Structure Sets>>doc:xwiki:Glossary.Structure set.WebHome]] and [[Reporting Taxonomies>>doc:xwiki:Glossary.Reporting taxonomy.WebHome]], the use of Processes, a discussion of time and datatyping, and the conventional mechanisms within the [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] Structure message regarding versioning and referencing.
++This section discusses a number of topics other than the exchange of data sets in SDMX formats. Supported only in SDMX-ML (and some in SDMX-JSON), these topics include the use of the reference metadata mechanism in SDMX, the use of Structure Sets and Reporting Taxonomies, the use of Processes, a discussion of time and datatyping, and the conventional mechanisms within the SDMX-ML Structure message regarding versioning and referencing.
  == {{id name="_Toc291504"/}}4.1 Representations ==
  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.
--There are several different [[representations>>doc:xwiki:Glossary.Representation.WebHome]] in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]], taken from XML Schemas and common programming languages. The table below describes the various [[representations>>doc:xwiki:Glossary.Representation.WebHome]], which are found in [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]], and their equivalents.
++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.
  (% style="width:1185.29px" %)
  |(% style="width:250px" %)**SDMX-ML Data Type**|(% style="width:285px" %)**XML Schema Data Type**|(% style="width:271px" %)**.NET Framework Type**|(% style="width:354px" %)**Java Data Type**
@@ -30,100 +30,160 @@
  |(% style="width:250px" %)Day, MonthDay, Month|(% style="width:285px" %)xsd:g*|(% style="width:271px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
  |(% style="width:250px" %)Duration|(% style="width:285px" %)xsd:duration|(% style="width:271px" %)System.TimeSpan|(% style="width:354px" %)javax.xml.datatype.Dura tion
--There are also a number of [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] data types which do not have these direct correspondences, often because they are composite [[representations>>doc:xwiki:Glossary.Representation.WebHome]] or restrictions of a broader data type. For most of these, there are simple types which can be referenced from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] schemas, for others a derived simple type will be necessary:
++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:
--* AlphaNumeric (common:AlphaNumericType, string which only allows A-z and 0-9)
--* Alpha (common:AlphaType, string which only allows A-z)
--* Numeric (common:NumericType, string which only allows 0-9, but is not numeric so that is can having leading zeros)
--* Count (xs:integer, a sequence with an interval of "1")
--* InclusiveValueRange (xs:decimal with the minValue and maxValue facets supplying the bounds)
--* ExclusiveValueRange (xs:decimal with the minValue and maxValue [[facets>>doc:xwiki:Glossary.Facet.WebHome]] supplying the bounds)
--* Incremental (xs:decimal with a specified interval; the interval is typically enforced outside of the XML validation)
--* TimeRange (common:TimeRangeType, startDateTime + Duration)
--* ObservationalTimePeriod (common:ObservationalTimePeriodType, a union of StandardTimePeriod and TimeRange).
--* StandardTimePeriod (common:StandardTimePeriodType, a union of BasicTimePeriod and ReportingTimePeriod).
--* BasicTimePeriod (common:BasicTimePeriodType, a union of GregorianTimePeriod and DateTime)
--* GregorianTimePeriod (common:GregorianTimePeriodType, a union of GregorianYear, GregorianMonth, and GregorianDay)
--* ReportingTimePeriod (common:ReportingTimePeriodType, a union of ReportingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, and ReportingDay).
--* ReportingYear (common:ReportingYearType)
--* ReportingSemester (common:ReportingSemesterType)
--* ReportingTrimester (common:ReportingTrimesterType)
--* ReportingQuarter (common:ReportingQuarterType)
--* ReportingMonth (common:ReportingMonthType)
--* ReportingWeek (common:ReportingWeekType)
--* ReportingDay (common:ReportingDayType)
--* XHTML (common:StructuredText, allows for multi-lingual text content that has XHTML markup)
--* KeyValues (common:DataKeyType)
--* IdentifiableReference (types for each IdentifiableObject)
--* GeospatialInformation (a geo feature set, according to the pattern in section 7.2)
++• **AlphaNumeric** (**common:AlphaNumericType**, string which only allows A-z and 0-9)
--Data types also have a set of [[facets>>doc:xwiki:Glossary.Facet.WebHome]]:
++• **Alpha** (**common:AlphaType**, string which only allows A-z)
--* isSequence = true | false (indicates a sequentially increasing value)
--* minLength = positive integer (# of characters/digits)
--* maxLength = positive integer (# of characters/digits)
--* startValue = [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (for numeric sequence)
--* endValue = [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (for numeric sequence)
--* interval = [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (for numeric sequence)
--* timeInterval = duration
--* startTime = BasicTimePeriod (for time range) endTime = BasicTimePeriod (for time range)
--* minValue = [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (for numeric range)
--* maxValue = [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (for numeric range)
--* [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] = Integer (# of digits to right of [[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] point)
--* pattern = (a regular expression, as per W3C XML Schema)
--* isMultiLingual = boolean (for specifying text can occur in more than one language)
++• ,,**Numeric**,, (,,**common:NumericType**,,, string which only allows 0-9, but is not numeric so that is can having leading zeros)
--Note that [[code lists>>doc:xwiki:Glossary.Code list.WebHome]] may also have textual [[representations>>doc:xwiki:Glossary.Representation.WebHome]] assigned to them, in addition to their enumeration of [[codes>>doc:xwiki:Glossary.Code.WebHome]].
++• ,,**Count**,, (,,**xs:integer**,,, a sequence with an interval of "1")
++• **InclusiveValueRange** (**xs:decimal** with the **minValue** and **maxValue** facets supplying the bounds)
++
++• **ExclusiveValueRange** (**xs:decimal** with the **minValue** and **maxValue** facets supplying the bounds)
++
++• **Incremental** (**xs:decimal** with a specified **interval**; the interval is typically enforced outside of the XML validation)
++
++• **TimeRange** (**common:TimeRangeType**, **startDateTime** + **Duration**)
++
++• **ObservationalTimePeriod** (**common:ObservationalTimePeriodType**, a union of **StandardTimePeriod** and **TimeRange**).
++
++• **StandardTimePeriod** (**common:StandardTimePeriodType**, a union of **BasicTimePeriod** and **ReportingTimePeriod**).
++
++• **BasicTimePeriod** (**common:BasicTimePeriodType**, a union of **GregorianTimePeriod** and **DateTime**)
++
++• **GregorianTimePeriod** (**common:GregorianTimePeriodType**, a union of **GregorianYear**, **GregorianMonth**, and **GregorianDay**)
++
++• **ReportingTimePeriod** (**common:ReportingTimePeriodType**, a union of **ReportingYear**, **ReportingSemester**, **ReportingTrimester**, **ReportingQuarter**, **ReportingMonth**, **ReportingWeek**, and **ReportingDay**).
++
++• **ReportingYear** (**common:ReportingYearType**)
++
++• **ReportingSemester** (**common:ReportingSemesterType**)
++
++• **ReportingTrimester** (**common:ReportingTrimesterType**)
++
++• **ReportingQuarter** (**common:ReportingQuarterType**)
++
++• **ReportingMonth** (**common:ReportingMonthType**)
++
++• **ReportingWeek** (**common:ReportingWeekType**)
++
++• **ReportingDay** (**common:ReportingDayType**)
++
++• ,,**XHTML**,, (,,**common:StructuredText**,,, allows for multi-lingual text content that has ,,**XHTML**,, markup)
++
++• **KeyValues** (**common:DataKeyType**)
++
++• ,,**IdentifiableReference**,, (types for each IdentifiableObject)
++
++• ,,**GeospatialInformation**,, (a geo feature set, according to the pattern in section 7.2)
++
++Data types also have a set of facets:
++
++• ,,**isSequence = true | false**,, (indicates a sequentially increasing value)
++
++• ,,**minLength = positive integer**,, (# of characters/digits)
++
++• ,,**maxLength = positive integer**,, (# of characters/digits)
++
++• ,,**startValue = decimal**,, (for numeric sequence)
++
++• ,,**endValue = decimal**,, (for numeric sequence)
++
++• ,,**interval = decimal**,, (for numeric sequence)
++
++• **timeInterval = duration**
++
++• **startTime = BasicTimePer,,iod,,** (for time range) ,,**endTime = BasicTimePeriod**,, (for time range)
++
++* ,,**minValue = decimal**,, (for numeric range)
++* ,,**maxValue = decimal**,, (for numeric range)
++* ,,**decimal = Integer**,, (# of digits to right of decimal point)
++* ,,**pattern =**,, (a regular expression, as per W3C XML Schema)
++* ,,**isMultiLingual = boolean**,, (for specifying text can occur in more than one language)
++
++Note that code lists may also have textual representations assigned to them, in addition to their enumeration of codes.
++
  === {{id name="_Toc291505"/}}4.1.1 Data Types ===
--XML and JSON schemas support a variety of data types that, although rich, are not (% style="color:#2ecc71" %)mapped(%%) one-to-one in all cases. This section provides an explanation of the mapping performed in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, between such cases.
++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.
--For identifiers, text fields and [[Codes>>doc:xwiki:Glossary.Code.WebHome]] there are no restriction from either side, since a generic type (e.g., that of string) accompanied by the proper regular expression works equally well for both XML and JSON.
++For identifiers, text fields and Codes there are no restriction from either side, since a generic type (e.g., that of string) accompanied by the proper regular expression works equally well for both XML and JSON.
  For example, for the id type, this is the XML schema definition:
--> <xs:simpleType name="IDType">
-->   <xs:restriction base="NestedIDType">
-->     <xs:pattern value="[A-Za-z0-9_@$\-]+"/>
-->   </xs:restriction>
--> </xs:simpleType>
++<xs:simpleType name="IDType">
++<xs:restriction base="NestedIDType">
++
++<xs:pattern value="[A-Za-z0-9_@$\-]+"/>
++
++</xs:restriction>
++
++</xs:simpleType>
++
  Where the NestedIDType is also a restriction of string.
  The above looks like this, in JSON schema:
--> "idType": {
-->   "type": "string",
-->   "pattern": "^[A-Za-z0-9_@$-]+$"
--> }
++"idType": {
++"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.
  Further to the above, the mapping between the non-native data types is presented in the table below:
--(% style="width:1146.29px" %)
--|(% style="width:159px" %)**SDMX Facet**|(% style="width:179px" %)**XML Schema**|(% style="width:800px" %)**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:159px" %)GregorianYear|(% style="width:179px" %)xsd:gYear|(% style="width:800px" %)(((
--"^-?( [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 wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ **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:159px" %)GregorianMonth|(% style="width:179px" %)xsd:gYearMonth|(% style="width:800px" %)(((
--"^-?([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:163px" %)GregorianDay|(% style="width:179px" %)xsd:date|(% style="width:800px" %)(((
--"^-?([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))?$"
++
++[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape1" height="1" width="192"]]
++
++|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:163px" %)Day|(% style="width:179px" %)xsd:gDay|(% style="width:800px" %)(((
--"^~-~--(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:163px" %)MonthDay|(% style="width:179px" %)xsd:gMonthDay|(% style="width:800px" %)(((
--"^~-~-(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:163px" %)Month|(% style="width:179px" %)xsd:Month|(% style="width:800px" %)(((
--"^~-~-(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:163px" %)Duration|(% style="width:179px" %)xsd:duration|(% style="width:800px" %)(((
--"^-?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)?)?$"
  )))
  == {{id name="_Toc291506"/}}4.2 Time and Time Format ==
@@ -138,14 +138,17 @@
  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.
  === {{id name="_Toc291508"/}}4.2.2 Observational Time Period ===
@@ -164,16 +164,12 @@
  Representation: xs:gYear (YYYY)
--Period: the start of January 1 to the end of December 31
++Period: the start of January 1 to the end of December 31 **Gregorian Year Month**:
--**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
++Period: the start of the first day of the month to end of the last day of the month **Gregorian Day**:
--**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)
@@ -182,7 +182,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:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^
  === {{id name="_Toc291512"/}}4.2.6 Standard Reporting Period ===
@@ -206,10 +206,8 @@
  Limit per year: 1
--Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1)
++Representation: common:ReportingYearType (YYYY-A1, e.g. 2000-A1) **Reporting Semester:**
--**Reporting Semester:**
--
  Period Indicator: S
  Period Duration: P6M (six months)
@@ -218,6 +218,8 @@
  Representation: common:ReportingSemesterType (YYYY-Ss, e.g. 2000-S2)
++[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape2" height="1" width="192"]]
++
  **Reporting Trimester:**
  Period Indicator: T
@@ -226,10 +226,8 @@
  Limit per year: 3
--Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3)
++Representation: common:ReportingTrimesterType (YYYY-Tt, e.g. 2000-T3) **Reporting Quarter:**
--**Reporting Quarter:**
--
  Period Indicator: Q
  Period Duration: P3M (three months)
@@ -236,10 +236,8 @@
  Limit per year: 4
--Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4)
++Representation: common:ReportingQuarterType (YYYY-Qq, e.g. 2000-Q4) **Reporting Month**:
--**Reporting Month**:
--
  Period Indicator: M
  Period Duration: P1M (one month)
@@ -260,7 +260,7 @@
  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.^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^ 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:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^ 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**:
@@ -280,38 +280,49 @@
  (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
--**~1. Determine [REPORTING_YEAR_BASE]:**
++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]
--**a) If the [PERIOD_INDICATOR] is W:**
++1.
++11. **If the [PERIOD_INDICATOR] is W:**
++111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
--      ~1. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday**:
--       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-to-dateTimes for further details.{{/footnote}} (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:#sdfootnote4sym||name="sdfootnote4anc"]](%%)^^ (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
--**~      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].
++1.
++11.
++111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
--**b) Else:**
--The [REPORTING_YEAR_START_DATE] 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].
--**2. Determine [PERIOD_DURATION]:**
--a) If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
--b) If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
--c) If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
--d) If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
--e) If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
--f) If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
--g) If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
--**3. Determine [PERIOD_START]:**
++1.
++11. **Else:**
--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].
++The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
--**4. Determine the [PERIOD_END]:**
++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.
++1. **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]. **4. Determine the [PERIOD_END]:**
++
  Multiply the [PERIOD_VALUE] by the [PERIOD_DURATION]. Add^^4^^ this to the [REPORTING_YEAR_BASE] add^^4^^ -P1D. The result is the [PERIOD_END].
  For all of these ranges, the bounds include the beginning of the [PERIOD_START] (i.e. 00:00:00) and the end of the [PERIOD_END] (i.e. 23:59:59).
@@ -319,34 +319,53 @@
  **Examples:**
  **2010-Q2, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
--~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
--        b) [REPORTING_YEAR_BASE] = 2010-07-01
--2. [PERIOD_DURATION] = P3M
--3. (2-1) * P3M = P3M
--     2010-07-01 + P3M = 2010-10-01
--     [PERIOD_START] = 2010-10-01
--4. 2 * P3M = P6M
--     2010-07-01 + P6M = 2010-13-01 = 2011-01-01
--     2011-01-01 + -P1D = 2010-12-31
--     [PERIOD_END] = 2010-12-31
++1. [REPORTING_YEAR_START_DATE] = 2010-07-01
++b) [REPORTING_YEAR_BASE] = 2010-07-01
++
++1. [PERIOD_DURATION] = P3M
++1. (2-1) * P3M = P3M
++
++2010-07-01 + P3M = 2010-10-01
++
++[PERIOD_START] = 2010-10-01
++
++1. 2 * P3M = P6M
++
++2010-07-01 + P6M = 2010-13-01 = 2011-01-01
++
++2011-01-01 + -P1D = 2010-12-31
++
++[PERIOD_END] = 2010-12-31
++
  The actual calendar range covered by 2010-Q2 (assuming the reporting year begins July 1) is 2010-10-01T00:00:00/2010-12-31T23:59:59
  **2011-W36, REPORTING_YEAR_START_DAY = ~-~-07-01 (July 1)**
--~1. [REPORTING_YEAR_START_DATE] = 2010-07-01
--       a) 2011-07-01 = Friday
--           2011-07-01 + P3D = 2011-07-04
--           [REPORTING_YEAR_BASE] = 2011-07-04
--2. [PERIOD_DURATION] = P7D
--3. (36-1) * P7D = P245D
--        2011-07-04 + P245D = 2012-03-05
--        [PERIOD_START] = 2012-03-05
--4. 36 * P7D = P252D
--     2011-07-04 + P252D =2012-03-12
--     2012-03-12 + -P1D = 2012-03-11
--     [PERIOD_END] = 2012-03-11
++1. [REPORTING_YEAR_START_DATE] = 2010-07-01
++
++a) 2011-07-01 = Friday
++
++2011-07-01 + P3D = 2011-07-04
++
++[REPORTING_YEAR_BASE] = 2011-07-04
++
++1. [PERIOD_DURATION] = P7D
++1. (36-1) * P7D = P245D
++
++2011-07-04 + P245D = 2012-03-05
++
++[PERIOD_START] = 2012-03-05
++
++1. 36 * P7D = P252D
++
++2011-07-04 + P252D =2012-03-12
++
++2012-03-12 + -P1D = 2012-03-11
++
++[PERIOD_END] = 2012-03-11
++
  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
  === {{id name="_Toc291513"/}}4.2.7 Distinct Range ===
@@ -357,29 +357,29 @@
  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:771.294px" %)
--|**Code**|(% style="width:659px" %)**Format**
--|OTP|(% style="width:659px" %)Observational Time Period: Superset of all SDMX time formats (Gregorian Time Period, Reporting Time Period, and Time Range)
--|STP|(% style="width:659px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
--|GTP|(% style="width:659px" %)Superset of all Gregorian Time Periods and date-time
--|RTP|(% style="width:659px" %)Superset of all Reporting Time Periods
--|TR|(% style="width:659px" %)(((
--Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
++|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>)
  )))
--|GY|(% style="width:659px" %)Gregorian Year (YYYY)
--|GTM|(% style="width:659px" %)Gregorian Year Month (YYYY-MM)
--|GD|(% style="width:659px" %)Gregorian Day (YYYY-MM-DD)
--|DT|(% style="width:659px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
--|RY|(% style="width:659px" %)Reporting Year (YYYY-A1)
--|RS|(% style="width:659px" %)Reporting Semester (YYYY-Ss)
--|RT|(% style="width:659px" %)Reporting Trimester (YYYY-Tt)
--|RQ|(% style="width:659px" %)Reporting Quarter (YYYY-Qq)
--|RM|(% style="width:659px" %)Reporting Month (YYYY-Mmm)
--|RW|(% style="width:659px" %)Reporting Week (YYYY-Www)
--|RD|(% style="width:659px" %)Reporting Day (YYYY-Dddd)
++|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)
--(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
--**Table 1: SDMX-ML Time Format Codes**
++==== Table 1: SDMX-ML Time Format Codes ====
  === {{id name="_Toc291515"/}}4.2.9 Time Zones ===
@@ -406,11 +406,11 @@
  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"/>
++<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"/>
++<Series REF_PERIOD="2000-01-01T00:00:00/P2M"/>
  === {{id name="_Toc291517"/}}4.2.11 Notes on Formats ===
@@ -426,13 +426,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:1020.29px" %)
--|(% style="width:236px" %)**Operator**|(% style="width:781px" %)**Rule**
--|(% style="width:236px" %)Greater Than|(% style="width:781px" %)Any data after the last moment of the period
--|(% style="width:236px" %)Less Than|(% style="width:781px" %)Any data before the first moment of the period
--|(% style="width:236px" %)Greater Than or Equal To|(% style="width:781px" %)Any data on or after the first moment of the period
--|(% style="width:236px" %)Less Than or Equal To|(% style="width:781px" %)Any data on or before the last moment of the period
--|(% style="width:236px" %)Equal To|(% style="width:781px" %)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.
@@ -439,8 +439,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
@@ -456,10 +456,11 @@
  * 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:
++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
  * 2010-07 or later
  * 2010-07-01 or later
@@ -477,7 +477,7 @@
  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 ===
@@ -485,6 +485,8 @@
  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.
++[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape3" height="1" width="192"]]
++
 -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.
 -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.
@@ -555,5 +555,3 @@
  Any structural metadata object which contains a reference to an object can be queried based on that reference. For example, a categorisation references both a category and the object is it categorising. As this is the case, one can query for categorisations which categorise a particular object or which categorise against a particular category or category scheme. This mechanism should be used when the referenced object is known.
  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.
--
--{{putFootnotes/}}