Changes for page 4 General Notes for Implementers

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

...	...	@@ -237,33 +237,34 @@
237	237	Combine [REPORTING_YEAR] of the reporting period value (YYYY) with [REPORTING_YEAR_START_DAY] (MM-DD) to get a date (YYYY-MM-DD).
238	238	This is the [REPORTING_YEAR_START_DATE]
239	239
240		-a) **If the [PERIOD_INDICATOR] is W:**
	240	+1.
	241	+11. **If the [PERIOD_INDICATOR] is W:**
	242	+111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
241	241
242		-**~1. If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
243		-Add[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the
244		-[REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
	244	+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].
245	245
246		-2. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
	246	+1.
	247	+11.
	248	+111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
247	247
248		-Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the
249		-[REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
	250	+Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
250	250
251		-**​​​​​​​b)** **Else:**
	252	+1.
	253	+11. **Else:**
252	252
253	253	The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
254	254
255		-**2. Determine [PERIOD_DURATION]:**
256		-
257		-1. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
258		-1. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
259		-1. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
260		-1. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
261		-1. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
262		-1. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
263		-1. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
	257	+1. **Determine [PERIOD_DURATION]:**
	258	+11. If the [PERIOD_INDICATOR] is A, the [PERIOD_DURATION] is P1Y.
	259	+11. If the [PERIOD_INDICATOR] is S, the [PERIOD_DURATION] is P6M.
	260	+11. If the [PERIOD_INDICATOR] is T, the [PERIOD_DURATION] is P4M.
	261	+11. If the [PERIOD_INDICATOR] is Q, the [PERIOD_DURATION] is P3M.
	262	+11. If the [PERIOD_INDICATOR] is M, the [PERIOD_DURATION] is P1M.
	263	+11. If the [PERIOD_INDICATOR] is W, the [PERIOD_DURATION] is P7D.
	264	+11. If the [PERIOD_INDICATOR] is D, the [PERIOD_DURATION] is P1D.
264	264	1. **Determine [PERIOD_START]:**
265	265
266		-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].
	267	+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].
267	267
268	268	1. **Determine the [PERIOD_END]:**
269	269
...	...	@@ -329,26 +329,25 @@
329	329
330	330	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.
331	331
332		-(% style="width:890.835px" %)
333		-|(% style="width:95px" %)**Code**|(% style="width:793px" %)**Format**
334		-|(% 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)
335		-|(% style="width:95px" %)STP|(% style="width:793px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
336		-|(% style="width:95px" %)GTP|(% style="width:793px" %)Superset of all Gregorian Time Periods and date-time
337		-|(% style="width:95px" %)RTP|(% style="width:793px" %)Superset of all Reporting Time Periods
338		-|(% style="width:95px" %)TR|(% style="width:793px" %)(((
	333	+|(% style="width:95px" %)Code|(% style="width:1520px" %)Format
	334	+|(% 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)
	335	+|(% style="width:95px" %)STP|(% style="width:1520px" %)Standard Time Period: Superset of Gregorian and Reporting Time Periods
	336	+|(% style="width:95px" %)GTP|(% style="width:1520px" %)Superset of all Gregorian Time Periods and date-time
	337	+|(% style="width:95px" %)RTP|(% style="width:1520px" %)Superset of all Reporting Time Periods
	338	+|(% style="width:95px" %)TR|(% style="width:1520px" %)(((
339	339	Time Range: Start time and duration (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
340	340	)))
341		-|(% style="width:95px" %)GY|(% style="width:793px" %)Gregorian Year (YYYY)
342		-|(% style="width:95px" %)GTM|(% style="width:793px" %)Gregorian Year Month (YYYY-MM)
343		-|(% style="width:95px" %)GD|(% style="width:793px" %)Gregorian Day (YYYY-MM-DD)
344		-|(% style="width:95px" %)DT|(% style="width:793px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
345		-|(% style="width:95px" %)RY|(% style="width:793px" %)Reporting Year (YYYY-A1)
346		-|(% style="width:95px" %)RS|(% style="width:793px" %)Reporting Semester (YYYY-Ss)
347		-|(% style="width:95px" %)RT|(% style="width:793px" %)Reporting Trimester (YYYY-Tt)
348		-|(% style="width:95px" %)RQ|(% style="width:793px" %)Reporting Quarter (YYYY-Qq)
349		-|(% style="width:95px" %)RM|(% style="width:793px" %)Reporting Month (YYYY-Mmm)
350		-|(% style="width:95px" %)RW|(% style="width:793px" %)Reporting Week (YYYY-Www)
351		-|(% style="width:95px" %)RD|(% style="width:793px" %)Reporting Day (YYYY-Dddd)
	341	+|(% style="width:95px" %)GY|(% style="width:1520px" %)Gregorian Year (YYYY)
	342	+|(% style="width:95px" %)GTM|(% style="width:1520px" %)Gregorian Year Month (YYYY-MM)
	343	+|(% style="width:95px" %)GD|(% style="width:1520px" %)Gregorian Day (YYYY-MM-DD)
	344	+|(% style="width:95px" %)DT|(% style="width:1520px" %)Distinct Point: date-time (YYYY-MM-DDThh:mm:ss)
	345	+|(% style="width:95px" %)RY|(% style="width:1520px" %)Reporting Year (YYYY-A1)
	346	+|(% style="width:95px" %)RS|(% style="width:1520px" %)Reporting Semester (YYYY-Ss)
	347	+|(% style="width:95px" %)RT|(% style="width:1520px" %)Reporting Trimester (YYYY-Tt)
	348	+|(% style="width:95px" %)RQ|(% style="width:1520px" %)Reporting Quarter (YYYY-Qq)
	349	+|(% style="width:95px" %)RM|(% style="width:1520px" %)Reporting Month (YYYY-Mmm)
	350	+|(% style="width:95px" %)RW|(% style="width:1520px" %)Reporting Week (YYYY-Www)
	351	+|(% style="width:95px" %)RD|(% style="width:1520px" %)Reporting Day (YYYY-Dddd)
352	352
353	353	(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
354	354	**Table 1: SDMX-ML Time Format Codes**
...	...	@@ -398,13 +398,12 @@
398	398
399	399	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.
400	400
401		-(% style="width:770.835px" %)
402		-|(% style="width:220px" %)**Operator**|(% style="width:548px" %)**Rule**
403		-|(% style="width:220px" %)Greater Than|(% style="width:548px" %)Any data after the last moment of the period
404		-|(% style="width:220px" %)Less Than|(% style="width:548px" %)Any data before the first moment of the period
405		-|(% style="width:220px" %)Greater Than or Equal To|(% style="width:548px" %)Any data on or after the first moment of the period
406		-|(% style="width:220px" %)Less Than or Equal To|(% style="width:548px" %)Any data on or before the last moment of the period
407		-|(% 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
	401	+|**Operator**|**Rule**
	402	+|Greater Than|Any data after the last moment of the period
	403	+|Less Than|Any data before the first moment of the period
	404	+|Greater Than or Equal To|Any data on or after the first moment of the period
	405	+|Less Than or Equal To|Any data on or before the last moment of the period
	406	+|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
408	408
409	409	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.
410	410
...	...	@@ -411,8 +411,11 @@
411	411	**Examples:**
412	412
413	413	**Gregorian Period**
	413	+
414	414	Query Parameter: Greater than 2010
	415	+
415	415	Literal Interpretation: Any data where the start period occurs after 2010-1231T23:59:59.
	417	+
416	416	Example Matches:
417	417
418	418	* 2011 or later
...	...	@@ -428,7 +428,9 @@
428	428	* 2010-D185 or later (reporting year start day ~-~-07-01 or later)
429	429
430	430	**Reporting Period**
	433	+
431	431	Query Parameter: Greater than or equal to 2010-Q3
	435	+
432	432	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:
433	433
434	434	* 2011 or later
...	...	@@ -440,9 +440,9 @@
440	440	* 2010-T3 (any reporting year start day)
441	441	* 2010-Q3 or later (any reporting year start day)
442	442	* 2010-M07 or later (any reporting year start day)
443		-* 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}}
	447	+* 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
444	444	* 2010-D182 or later (reporting year start day ~-~-01-01)
445		-* 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}}
	449	+* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
446	446	* 2010-D185 or later (reporting year start day ~-~-07-01)
447	447
448	448	== 4.3 Versioning ==
...	...	@@ -449,8 +449,12 @@
449	449
450	450	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".
451	451
452		-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’.
	456	+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
453	453
	458	+//MaintainableArtefact//. According to the legacy versioning, any artefact defined without a version is equivalent to following the legacy versioning, thus having version
	459	+
	460	+‘1.0’.
	461	+
454	454	=== 4.3.1 Non-versioned artefacts ===
455	455
456	456	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’.
...	...	@@ -526,4 +526,13 @@
526	526
527	527	----
528	528
	537	+[[~[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/]]
	538	+
	539	+[[~[2~]>>path:#_ftnref2]] The seconds can be reported fractionally
	540	+
	541	+[[~[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.
	542	+
	543	+[[~[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.
	544	+
	545	+
529	529	{{putFootnotes/}}

SUZ.Methodology.Code.MethodologyClass[0]

index

...	...	@@ -1,1 +1,0 @@
1		-4