Changes for page 4 General Notes for Implementers

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

From 1.1 to 1.2 From 1.3 to 1.4

From version 1.2

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

Change comment: There is no comment for this version

To version 1.3

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -181,32 +181,22 @@
  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**:
--
  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**:
--
  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]]
--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:
@@ -215,7 +215,6 @@
  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:
@@ -387,15 +387,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
--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.
@@ -423,9 +423,7 @@
  ==== 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):
@@ -446,9 +446,7 @@
  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:
@@ -458,9 +458,7 @@
  <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.