Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 2.1
edited by Helena
on 2025/06/08 23:36
Change comment: There is no comment for this version
To version 2.2
edited by Helena
on 2025/06/08 23:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -95,8 +95,8 @@
95 95  The above looks like this, in JSON schema:
96 96  
97 97  > "idType": {
98 -> "type": "string",
99 -> "pattern": "^[A-Za-z0-9_@$-]+$"
98 +> "type": "string",
99 +> "pattern": "^[A-Za-z0-9_@$-]+$"
100 100  > }
101 101  
102 102  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,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 wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) **for "string" type**
106 +|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[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 wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]]
197 +Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[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 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.[[(% class="wikiinternallink wikiinternallink 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.
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 wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) (P3D, P2D, or P1D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
298 +Add[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[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].