Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.10
edited by Helena
on 2025/06/08 23:31
Change comment: There is no comment for this version
To version 1.8
edited by Helena
on 2025/06/08 23:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -103,7 +103,7 @@
103 103  
104 104  Further to the above, the mapping between the non-native data types is presented in the table below:
105 105  
106 -|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"[[(% class="wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) **for "string" type**
106 +|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"[[^^~[1~]^^>>path:#_ftn1]] **for "string" type**
107 107  |GregorianYear|xsd:gYear|(((
108 108  "^-?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\+|-)((0[0-
109 109  
... ... @@ -194,7 +194,7 @@
194 194  
195 195  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.
196 196  
197 -Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)[[(% class="wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]]
197 +Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)[[^^~[2~]^^>>path:#_ftn2]]
198 198  
199 199  === 4.2.6 Standard Reporting Period ===
200 200  
... ... @@ -263,7 +263,7 @@
263 263  
264 264  Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53)
265 265  
266 -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" %)^^~[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.
266 +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.
267 267  
268 268  **Reporting Day**:
269 269  
... ... @@ -291,19 +291,19 @@
291 291  
292 292  This is the [REPORTING_YEAR_START_DATE]
293 293  
294 -1.
294 +1.
295 295  11. **If the [PERIOD_INDICATOR] is W:**
296 296  111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
297 297  
298 -Add[[(% class="wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
298 +Add[[^^~[4~]^^>>path:#_ftn4]] (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
299 299  
300 -1.
301 -11.
300 +1.
301 +11.
302 302  111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
303 303  
304 304  Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
305 305  
306 -1.
306 +1.
307 307  11. **Else:**
308 308  
309 309  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
... ... @@ -406,8 +406,7 @@
406 406  |RW|Reporting Week (YYYY-Www)
407 407  |RD|Reporting Day (YYYY-Dddd)
408 408  
409 -(% class="wikigeneratedid" id="HTable1:SDMX-MLTimeFormatCodes" %)
410 -**Table 1: SDMX-ML Time Format Codes**
409 +==== Table 1: SDMX-ML Time Format Codes ====
411 411  
412 412  === 4.2.9 Time Zones ===
413 413  
... ... @@ -505,7 +505,7 @@
505 505  * 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
506 506  * 2010-D185 or later (reporting year start day ~-~-07-01)
507 507  
508 -= 4.3 Versioning =
507 += 4.3 Versioning ==
509 509  
510 510  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".
511 511  
... ... @@ -580,7 +580,8 @@
580 580  
581 581  Full details can be found in the SDMX RESTful web services specification.
582 582  
583 -== 4.4 Structural Metadata Querying Best Practices ==
582 +1.
583 +11. Structural Metadata Querying Best Practices
584 584  
585 585  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.
586 586  
... ... @@ -588,6 +588,7 @@
588 588  
589 589  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.
590 590  
591 +
591 591  ----
592 592  
593 593  [[~[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/]]