Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.7
edited by Helena
on 2025/05/15 23:55
Change comment: There is no comment for this version
To version 3.5
edited by Helena
on 2025/05/15 23:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -83,47 +83,76 @@
83 83  
84 84  For example, for the id type, this is the XML schema definition:
85 85  
86 -> <xs:simpleType name="IDType">
87 -> <xs:restriction base="NestedIDType">
88 -> <xs:pattern value="[A-Za-z0-9_@$\-]+"/>
89 -> </xs:restriction>
90 -> </xs:simpleType>
86 +<xs:simpleType name="IDType">
91 91  
88 +<xs:restriction base="NestedIDType">
89 +
90 +<xs:pattern value="[A-Za-z0-9_@$\-]+"/>
91 +
92 +</xs:restriction>
93 +
94 +</xs:simpleType>
95 +
92 92  Where the NestedIDType is also a restriction of string.
93 93  
94 94  The above looks like this, in JSON schema:
95 95  
96 -> "idType": {
97 -> "type": "string",
98 -> "pattern": "^[A-Za-z0-9_@$-]+$"
99 -> }
100 +"idType": {
100 100  
102 +"type": "string",
103 +
104 +"pattern": "^[A-Za-z0-9_@$-]+$"
105 +
106 +}
107 +
101 101  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.
102 102  
103 103  Further to the above, the mapping between the non-native data types is presented in the table below:
104 104  
105 -(% style="width:1146.29px" %)
106 -|(% 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**
107 -|(% style="width:159px" %)GregorianYear|(% style="width:179px" %)xsd:gYear|(% style="width:800px" %)(((
108 -"^-?( [1-9] [0-9] {3,}|0[0-9]{3}) (Z| (\ + | -) ((0 [0 - 9]| 1[0 - 3]):[0 - 5] [0 - 9] | 14:00))?$"
112 +|**SDMX Facet**|**XML Schema**|**JSON schema **"**pattern**"^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ **for "string" type**
113 +|GregorianYear|xsd:gYear|(((
114 +"^-?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\+|-)((0[0-
115 +
116 +9]|1[0-3]):[0-5][0-9]|14:00))?$"
109 109  )))
110 -|(% style="width:159px" %)GregorianMonth|(% style="width:179px" %)xsd:gYearMonth|(% style="width:800px" %)(((
111 -"^-?([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))?$"
118 +|GregorianMonth|xsd:gYearMonth|(((
119 +"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-
120 +
121 +2])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-
122 +
123 +9]|14:00))?$"
112 112  )))
113 -|(% style="width:163px" %)GregorianDay|(% style="width:179px" %)xsd:date|(% style="width:800px" %)(((
114 -"^-?([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))?$"
125 +
126 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape1" height="1" width="192"]]
127 +
128 +|GregorianDay|xsd:date|(((
129 +"^-?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-
130 +
131 +(0[1-9]|[12][0-9]|3[01])(Z|(\+|-)((0[0-9]|1[0-
132 +
133 +3]):[0-5][0-9]|14:00))?$"
115 115  )))
116 -|(% style="width:163px" %)Day|(% style="width:179px" %)xsd:gDay|(% style="width:800px" %)(((
117 -"^~-~--(0[1-9]|[12][0-9]|3[01])(Z|(\+|- )((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
135 +|Day|xsd:gDay|(((
136 +"^~-~--(0[1-9]|[12][0-9]|3[01])(Z|(\+|-
137 +
138 +)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?$"
118 118  )))
119 -|(% style="width:163px" %)MonthDay|(% style="width:179px" %)xsd:gMonthDay|(% style="width:800px" %)(((
120 -"^~-~-(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))?$"
140 +|MonthDay|xsd:gMonthDay|(((
141 +"^~-~-(0[1-9]|1[0-2])-(0[1-9]|[12][0-
142 +
143 +9]|3[01])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-
144 +
145 +9]|14:00))?$"
121 121  )))
122 -|(% style="width:163px" %)Month|(% style="width:179px" %)xsd:Month|(% style="width:800px" %)(((
123 -"^~-~-(0[1-9]|1[0-2])(Z|(\+|-)((0[0-9]|1[0- 3]):[0-5][0-9]|14:00))?$"
147 +|Month|xsd:Month|(((
148 +"^~-~-(0[1-9]|1[0-2])(Z|(\+|-)((0[0-9]|1[0-
149 +
150 +3]):[0-5][0-9]|14:00))?$"
124 124  )))
125 -|(% style="width:163px" %)Duration|(% style="width:179px" %)xsd:duration|(% style="width:800px" %)(((
126 -"^-?P[0-9]+Y?([0-9]+M)?([0-9]+D)?(T([0- 9]+H)?([0-9]+M)?([0-9]+(\.[0-9]+)?S)?)?$"
152 +|Duration|xsd:duration|(((
153 +"^-?P[0-9]+Y?([0-9]+M)?([0-9]+D)?(T([0-
154 +
155 +9]+H)?([0-9]+M)?([0-9]+(\.[0-9]+)?S)?)?$"
127 127  )))
128 128  
129 129  == {{id name="_Toc291506"/}}4.2 Time and Time Format ==
... ... @@ -181,7 +181,7 @@
181 181  
182 182  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.
183 183  
184 -Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^
213 +Representation: xs:dateTime (YYYY-MM-DDThh:mm:ss)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^
185 185  
186 186  === {{id name="_Toc291512"/}}4.2.6 Standard Reporting Period ===
187 187  
... ... @@ -255,7 +255,7 @@
255 255  
256 256  Representation: common:ReportingWeekType (YYYY-Www, e.g. 2000-W53)
257 257  
258 -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" %)^^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.
287 +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.
259 259  
260 260  **Reporting Day**:
261 261  
... ... @@ -289,19 +289,19 @@
289 289  
290 290  This is the [REPORTING_YEAR_START_DATE]
291 291  
292 -1.
321 +1.
293 293  11. **If the [PERIOD_INDICATOR] is W:**
294 294  111. **If [REPORTING_YEAR_START_DATE] is a Friday, Saturday, or Sunday:**
295 295  
296 -Add^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink 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].
325 +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].
297 297  
298 -1.
299 -11.
327 +1.
328 +11.
300 300  111. **If [REPORTING_YEAR_START_DATE] is a Monday, Tuesday, Wednesday, or Thursday:**
301 301  
302 302  Add^^4^^ (P0D, -P1D, -P2D, or -P3D respectively) to the [REPORTING_YEAR_START_DATE]. The result is the [REPORTING_YEAR_BASE].
303 303  
304 -1.
333 +1.
305 305  11. **Else:**
306 306  
307 307  The [REPORTING_YEAR_START_DATE] is the [REPORTING_YEAR_BASE].
... ... @@ -585,5 +585,3 @@
585 585  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.
586 586  
587 587  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.
588 -
589 -{{putFootnotes/}}