Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena K. on 2026/06/10 10:18
From version 4.9
edited by Helena K.
on 2025/06/16 14:50
Change comment: There is no comment for this version
To version 15.1
edited by Helena K.
on 2026/06/10 10:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Adjustment|Age|Attribute|Code|Codelist|Component|Data Set|Data Structure Definition|Dimension|Observation Value|Representation|Series|Series Key|Statistical Data and Metadata eXchange|Statistical classification|Statistical indicator|Time format|Time period|Validation and Transformation Language
Content
... ... @@ -4,28 +4,28 @@
4 4  
5 5  == 13.1 Introduction ==
6 6  
7 -The purpose of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure mapping is to transform [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] from one dimensionality to another. In practice, this means that the input and output [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] conform to different Data Structure Definition.
7 +The purpose of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] structure mapping is to transform [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] from one dimensionality to another. In practice, this means that the input and output [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] conform to different [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].
8 8  
9 -Structure mapping does not alter the [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
9 +Structure mapping does not alter the [[observation values>>doc:sdmx:Glossary 2\.1.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
10 10  
11 -An input series (% style="color:#e74c3c" %)maps(%%) to:
11 +An input [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] maps to:
12 12  
13 -1. Exactly one output series; or
14 -1. Multiple output series with different [[Series Keys>>doc:sdmx:Glossary.Series key.WebHome]], but the same [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]]; or
15 -1. Zero output series where no source rule matches the input [[Component>>doc:sdmx:Glossary.Component.WebHome]] values.
13 +1. Exactly one output [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]; or
14 +1. Multiple output [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] with different [[Series Keys>>doc:sdmx:Glossary 2\.1.Series key.WebHome]], but the same [[observation values>>doc:sdmx:Glossary 2\.1.Observation value.WebHome]]; or
15 +1. Zero output [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] where no source rule matches the input [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values.
16 16  
17 17  Typical use cases include:
18 18  
19 19  * Transforming received data into a common internal structure;
20 20  * Transforming reported data into the data collector's preferred structure;
21 -* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
22 -* Transforming internal [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with a complex structure to a simpler structure with fewer [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] suitable for dissemination.
21 +* Transforming unidimensional [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}}^^{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}}^^ to multi-dimensional; and
22 +* Transforming internal [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] with a complex structure to a simpler structure with fewer [[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] suitable for dissemination.
23 23  
24 24  == 13.2 1-1 structure maps ==
25 25  
26 -1-1 (pronounced 'one to one') mappings support the simple use case where the value of a [[Component>>doc:sdmx:Glossary.Component.WebHome]] in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept.
26 +1-1 (pronounced 'one to one') mappings support the simple use case where the value of a [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in the source structure is translated to a different value in the target, usually where different [[classification>>doc:sdmx:Glossary 2\.1.Statistical Classification.WebHome]] schemes are used for the same Concept.
27 27  
28 -In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary.Code.WebHome]] are (% style="color:#e74c3c" %)mapped(%%) to their ISO 3character equivalent.
28 +In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] are mapped to their ISO 3character equivalent.
29 29  
30 30  (% style="width:585.294px" %)
31 31  |(% style="width:173px" %)**Country**|(% style="width:180px" %)**Alpha-2 code**|(% style="width:229px" %)**Alpha-3 code**
... ... @@ -36,7 +36,7 @@
36 36  |(% style="width:173px" %)Andorra|(% style="width:180px" %)AD|(% style="width:229px" %)AND
37 37  |(% style="width:173px" %)etc…|(% style="width:180px" %) |(% style="width:229px" %)
38 38  
39 -Different source values can also (% style="color:#e74c3c" %)map(%%) to the same target value, for example when deriving regions from country [[codes>>doc:sdmx:Glossary.Code.WebHome]].
39 +Different source values can also map to the same target value, for example when deriving regions from country [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
40 40  
41 41  (% style="width:490.294px" %)
42 42  |(% style="width:260px" %)Source Component: REF_AREA|(% style="width:227px" %)Target Component: REGION
... ... @@ -48,7 +48,7 @@
48 48  
49 49  == 13.3 N-n structure maps ==
50 50  
51 -N-n (pronounced 'N to N') mappings describe rules where a specified combination of values in multiple source [[Components>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)map(%%) to specified values in one or more target [[Components>>doc:sdmx:Glossary.Component.WebHome]]. For example, when mapping a partial [[Series Key>>doc:sdmx:Glossary.Series key.WebHome]] from a highly multidimensional cube (like Balance of Payments) to a single 'Indicator' [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in a target Data Structure.
51 +N-n (pronounced 'N to N') mappings describe rules where a specified combination of values in multiple source [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] map to specified values in one or more target [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]]. For example, when mapping a partial [[Series Key>>doc:sdmx:Glossary 2\.1.Series key.WebHome]] from a highly multidimensional cube (like Balance of Payments) to a single '[[Indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]' [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in a target Data Structure.
52 52  
53 53  Example:
54 54  
... ... @@ -57,40 +57,40 @@
57 57  |(% style="width:65px" %)1|(% style="width:519px" %)(((
58 58  If
59 59  FREQUENCY=A; and
60 -ADJUSTMENT=N; and
60 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and
61 61  MATURITY=L.
62 62  )))|(% style="width:378px" %)(((
63 63  Set
64 -INDICATOR=A_N_L
64 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L
65 65  )))
66 66  |(% style="width:65px" %)2|(% style="width:519px" %)(((
67 67  If
68 68  FREQUENCY=M; and
69 -ADJUSTMENT=S_A1; and
69 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=S_A1; and
70 70  MATURITY=TY12.
71 71  )))|(% style="width:378px" %)(((
72 72  Set
73 -INDICATOR=MON_SAX_12
73 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12
74 74  )))
75 75  
76 -N-n rules can also set values for multiple source Components.
76 +N-n rules can also set values for multiple source [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
77 77  
78 78  (% style="width:965.294px" %)
79 79  |(% style="width:73px" %)Rule|(% style="width:506px" %)Source|(% style="width:383px" %)Target
80 80  |(% style="width:73px" %)1|(% style="width:506px" %)(((
81 81  If
82 -FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
82 +FREQUENCY=A; and [[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and MATURITY=L.
83 83  )))|(% style="width:383px" %)(((
84 84  Set
85 -INDICATOR=A_N_L, STATUS=QXR15,
85 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L, STATUS=QXR15,
86 86  NOTE="Unadjusted".
87 87  )))
88 88  |(% style="width:73px" %)2|(% style="width:506px" %)(((
89 89  If
90 -FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
90 +FREQUENCY=M; and [[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=S_A1; and MATURITY=TY12.
91 91  )))|(% style="width:383px" %)(((
92 92  Set
93 -INDICATOR=MON_SAX_12,
93 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12,
94 94  STATUS=MPM12,
95 95  NOTE="Seasonally Adjusted"
96 96  )))
... ... @@ -97,18 +97,18 @@
97 97  
98 98  == 13.4 Ambiguous mapping rules ==
99 99  
100 -A structure map is ambiguous if the rules result in a dataset containing multiple series with the same Series Key.
100 +A structure map is ambiguous if the rules result in a [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] containing multiple [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] with the same [[Series Key>>doc:sdmx:Glossary 2\.1.Series key.WebHome]].
101 101  
102 -A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
102 +A simple example mapping a source [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] with a single [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] to one with multiple [[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] is shown below:
103 103  
104 104  (% style="width:972.294px" %)
105 -|(% style="width:257px" %)Source|(% style="width:315px" %)Target|(% style="width:397px" %)Output Series Key
105 +|(% style="text-align:center; width:257px" %)**Source**|(% style="text-align:center; width:315px" %)**Target**|(% style="text-align:center; width:397px" %)**Output Series Key**
106 106  |(% style="width:257px" %)SERIES_CODE=XMAN_Z_21|(% style="width:315px" %)(((
107 -Dimensions
108 -INDICATOR=XM
107 +[[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]
108 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM
109 109  FREQ=A
110 -ADJUSTMENT=N
111 -Attributes
110 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N
111 +[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]
112 112  UNIT_MEASURE=_Z
113 113  COMP_ORG=21
114 114  )))|(% style="width:397px" %)XM:A:N
... ... @@ -117,28 +117,28 @@
117 117  
118 118  
119 119  )))|(% style="width:315px" %)(((
120 -Dimensions
121 -INDICATOR=XM
120 +[[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]
121 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM
122 122  FREQ=A
123 -ADJUSTMENT=N
124 -Attributes
123 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N
124 +[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]
125 125  UNIT_MEASURE=_Z
126 126  COMP_ORG=34
127 127  )))|(% style="width:397px" %)XM:A:N
128 128  
129 -The above behaviour can be okay if the series XMAN_Z_21 contains observations for different periods of time then the series XMAN_Z_34. If however both series contain observations for the same point in time, the output for this mapping will be two observations with the same [[series key>>doc:sdmx:Glossary.Series key.WebHome]], for the same period in time.
129 +The above behaviour can be okay if the [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] XMAN_Z_21 contains observations for different periods of time then the [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] XMAN_Z_34. If however both [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] contain observations for the same point in time, the output for this mapping will be two observations with the same [[series key>>doc:sdmx:Glossary 2\.1.Series key.WebHome]], for the same period in time.
130 130  
131 131  == 13.5 Representation maps ==
132 132  
133 -[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Maps(%%) replace the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Codelist (% style="color:#e74c3c" %)Maps(%%) and are used describe explicit mappings between source and target [[Component>>doc:sdmx:Glossary.Component.WebHome]] values.
133 +[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Maps replace the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 2.1 [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] Maps and are used describe explicit mappings between source and target [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values.
134 134  
135 -The source and target of a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) can reference any of the following:
135 +The source and target of a [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map can reference any of the following:
136 136  
137 -1. Codelist
137 +1. [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
138 138  1. Free Text (restricted by type, e.g String, Integer, Boolean)
139 139  1. Valuelist
140 140  
141 -A [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) mapping ISO 2-character to ISO 3-character Codelists would take the following form:
141 +A [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map mapping ISO 2-character to ISO 3-character [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] would take the following form:
142 142  
143 143  (% style="width:356.294px" %)
144 144  |(% style="width:167px" %)CL_ISO_ALPHA2|(% style="width:186px" %)CL_ISO_ALPHA3
... ... @@ -149,7 +149,7 @@
149 149  |(% style="width:167px" %)AD|(% style="width:186px" %)AND
150 150  |(% style="width:167px" %)etc…|(% style="width:186px" %)
151 151  
152 -A [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) mapping free text country names to an ISO 2-character Codelist could be similarly described:
152 +A [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map mapping free text country names to an ISO 2-character [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] could be similarly described:
153 153  
154 154  (% style="width:364.294px" %)
155 155  |(% style="width:169px" %)Text|(% style="width:192px" %)CL_ISO_ALPHA2
... ... @@ -161,11 +161,11 @@
161 161  |(% style="width:169px" %)"Eire"|(% style="width:192px" %)IE
162 162  |(% style="width:169px" %)etc…|(% style="width:192px" %)
163 163  
164 -Valuelists, introduced in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, are equivalent to Codelists but allow the maintenance of non-[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifiers. Importantly, their IDs do not need to conform to IDType, but as a consequence are not Identifiable.
164 +Valuelists, introduced in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 3.0, are equivalent to [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] but allow the maintenance of non-[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] identifiers. Importantly, their IDs do not need to conform to IDType, but as a consequence are not Identifiable.
165 165  
166 -When used in [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Maps(%%), Valuelists allow Non-[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifiers containing characters like £, $, % to be (% style="color:#e74c3c" %)mapped(%%) to [[Code>>doc:sdmx:Glossary.Code.WebHome]] IDs, or [[Codes>>doc:sdmx:Glossary.Code.WebHome]] (% style="color:#e74c3c" %)mapped(%%) to non-[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifiers.
166 +When used in [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Maps, Valuelists allow Non-[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] identifiers containing characters like £, $, % to be mapped to [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] IDs, or [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] mapped to non-[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] identifiers.
167 167  
168 -In common with Codelists, each item in a Valuelist has a multilingual name giving it a human-readable label and an optional description. For example:
168 +In common with [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], each item in a Valuelist has a multilingual name giving it a human-readable label and an optional description. For example:
169 169  
170 170  (% style="width:435.294px" %)
171 171  |(% style="width:126px" %)Value|(% style="width:133px" %)Locale|(% style="width:173px" %)Name
... ... @@ -173,17 +173,17 @@
173 173  |(% style="width:126px" %)%|(% style="width:133px" %)En|(% style="width:173px" %)Percentage
174 174  |(% style="width:126px" %) |(% style="width:133px" %)fr|(% style="width:173px" %)Pourcentage
175 175  
176 -Other characteristics of [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Maps(%%):
176 +Other characteristics of [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Maps:
177 177  
178 -* Support the (% style="color:#e74c3c" %)mapping(%%) of multiple source [[Component>>doc:sdmx:Glossary.Component.WebHome]] values to multiple Target [[Component>>doc:sdmx:Glossary.Component.WebHome]] values as described in section 13.3 on n-to-n mappings; this covers also the case of (% style="color:#e74c3c" %)mapping(%%) an [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] with an array [[representation>>doc:sdmx:Glossary.Representation.WebHome]] to (% style="color:#e74c3c" %)map(%%) combinations of values to a single target value;
179 -* Allow source or target mappings for an Item to be optional allowing rules such as 'A (% style="color:#e74c3c" %)maps(%%) to nothing' or 'nothing (% style="color:#e74c3c" %)maps(%%) to A'; and
180 -* Support for (% style="color:#e74c3c" %)mapping(%%) rules where regular expressions or substrings are used to match source [[Component>>doc:sdmx:Glossary.Component.WebHome]] values. Refer to section 13.6 for more on this topic.
178 +* Support the mapping of multiple source [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values to multiple Target [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values as described in section 13.3 on n-to-n mappings; this covers also the case of mapping an [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] with an array [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] to map combinations of values to a single target value;
179 +* Allow source or target mappings for an Item to be optional allowing rules such as 'A maps to nothing' or 'nothing maps to A'; and
180 +* Support for mapping rules where regular expressions or substrings are used to match source [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values. Refer to section 13.6 for more on this topic.
181 181  
182 182  == 13.6 Regular expression and substring rules ==
183 183  
184 -It is common for classifications to contain meanings within the identifier, for example the [[code>>doc:sdmx:Glossary.Code.WebHome]] Id 'XULADS' may refer to a particular seasonality because it starts with the letters XU.
184 +It is common for [[classifications>>doc:sdmx:Glossary 2\.1.Statistical Classification.WebHome]] to contain meanings within the identifier, for example the [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] Id 'XULADS' may refer to a particular seasonality because it starts with the letters XU.
185 185  
186 -With [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 each [[code>>doc:sdmx:Glossary.Code.WebHome]] that starts with XU had to be individually (% style="color:#e74c3c" %)mapped(%%) to the same seasonality, and additional mappings added when new [[Codes>>doc:sdmx:Glossary.Code.WebHome]] were added to the Codelists. This led to many hundreds or thousands of mappings which can be more efficiently summarised in a single conceptual rule:
186 +With [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 2.1 each [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that starts with XU had to be individually mapped to the same seasonality, and additional mappings added when new [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] were added to the [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. This led to many hundreds or thousands of mappings which can be more efficiently summarised in a single conceptual rule:
187 187  
188 188  //If starts with 'XU' map to 'Y'//
189 189  
... ... @@ -191,9 +191,9 @@
191 191  
192 192  === 13.6.1 Regular expressions ===
193 193  
194 -Regular expression mapping rules are defined in the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Map.
194 +Regular expression mapping rules are defined in the [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map.
195 195  
196 -Below is an example set of regular expression rules for a particular [[component>>doc:sdmx:Glossary.Component.WebHome]].
196 +Below is an example set of regular expression rules for a particular [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
197 197  
198 198  (% style="width:664.294px" %)
199 199  |(% style="width:141px" %)**Regex**|(% style="width:362px" %)**Description**|(% style="width:158px" %)**Output**
... ... @@ -201,7 +201,7 @@
201 201  |(% style="width:141px" %)^[A-G]|(% style="width:362px" %)Rule match if the input starts with letters A to G|(% style="width:158px" %)OUT_B
202 202  |(% style="width:141px" %)A~|B|(% style="width:362px" %)Rule match if input is either 'A' or 'B'|(% style="width:158px" %)OUT_C
203 203  
204 -Like all mapping rules, the output is either a [[Code>>doc:sdmx:Glossary.Code.WebHome]], a Value or free text depending on the [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the [[Component>>doc:sdmx:Glossary.Component.WebHome]] in the target [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]].
204 +Like all mapping rules, the output is either a [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], a Value or free text depending on the [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in the target [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].
205 205  
206 206  If the regular expression contains capture groups, these can be used in the definition of the output value, by specifying \**//n//**// //as an output value where **//n//** is the number of the capture group starting from 1. For example
207 207  
... ... @@ -225,7 +225,7 @@
225 225  
226 226  The input 'G' matches on the last rule which is used as a catch-all or default in this example.
227 227  
228 -=== 13. Substrings ===
228 +=== 13.6.2 Substrings ===
229 229  
230 230  Substrings provide an alternative to regular expressions where the required section of an input value can be described using the number of the starting character, and the length of the substring in characters. The first character is at position 1.
231 231  
... ... @@ -236,7 +236,7 @@
236 236  |(% style="width:169px" %)ABC_DEF_XYZ|(% style="width:147px" %)5|(% style="width:133px" %)3|(% style="width:171px" %)DEF
237 237  |(% style="width:169px" %)XULADS|(% style="width:147px" %)1|(% style="width:133px" %)2|(% style="width:171px" %)XU
238 238  
239 -Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' (% style="color:#e74c3c" %)map(%%) to Y// as shown in the following example:
239 +Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example:
240 240  
241 241  (% style="width:628.294px" %)
242 242  |(% style="width:163px" %)Start|(% style="width:158px" %)Length|(% style="width:128px" %)Source|(% style="width:176px" %)Target
... ... @@ -244,7 +244,7 @@
244 244  
245 245  == 13.7 Mapping non-SDMX time formats to SDMX formats ==
246 246  
247 -Structure mapping allows non-[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant time values in source [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] to be (% style="color:#e74c3c" %)mapped(%%) to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant time format.
247 +Structure mapping allows non-[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] compliant time values in source [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] to be mapped to an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] compliant [[time format>>doc:sdmx:Glossary 2\.1.Time format.WebHome]].
248 248  
249 249  Two types of time input are defined:
250 250  
... ... @@ -251,7 +251,7 @@
251 251  a. **Pattern based dates** – a string which can be described using a notation like dd/mm/yyyy or is represented as the number of periods since a point in time, for example: 2010M001 (first month in 2010), or 2014D123 (123^^rd^^ day in 2014); and
252 252  b. **Numerical based datetime** – a number specifying the elapsed periods since a fixed point in time, for example Unix Time is measured by the number of milliseconds since 1970.
253 253  
254 -The output of a time-based mapping is derived from the output Frequency, which is either explicitly stated in the mapping or defined as the value output by a specific [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] or [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in the output mapping. If the output frequency is unknown or if the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] format is not desired, then additional rules can be provided to specify the output date format for the given frequency Id. The default rules are:
254 +The output of a time-based mapping is derived from the output Frequency, which is either explicitly stated in the mapping or defined as the value output by a specific [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] or [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] in the output mapping. If the output frequency is unknown or if the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] format is not desired, then additional rules can be provided to specify the output date format for the given frequency Id. The default rules are:
255 255  
256 256  |Frequency|Format|Example
257 257  |A|YYYY|2010
... ... @@ -271,14 +271,14 @@
271 271  
272 272  There are two important points to note:
273 273  
274 -1. The output frequency determines the output date format, but the default output can be redefined using a Frequency Format mapping to force explicit rules on how the output [[time period>>doc:sdmx:Glossary.Time period.WebHome]] is formatted.
275 -1. To support the use case of changing frequency the structure (% style="color:#e74c3c" %)map(%%) can optionally provide a start of year [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]], which defines the year start date in MM-DD format. For example: YearStart=04-01.
274 +1. The output frequency determines the output date format, but the default output can be redefined using a Frequency Format mapping to force explicit rules on how the output [[time period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]] is formatted.
275 +1. To support the use case of changing frequency the structure map can optionally provide a start of year [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]], which defines the year start date in MM-DD format. For example: YearStart=04-01.
276 276  
277 277  === 13.7.1 Pattern based dates ===
278 278  
279 -Date and [[time formats>>doc:sdmx:Glossary.Time format.WebHome]] are specified by date and time pattern strings based on Java's Simple Date Format. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the [[components>>doc:sdmx:Glossary.Component.WebHome]] of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.
279 +Date and [[time formats>>doc:sdmx:Glossary 2\.1.Time format.WebHome]] are specified by date and time pattern strings based on Java's Simple Date Format. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.
280 280  
281 -Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale{{footnote}} A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}. An indicative list of examples is presented in the following table:
281 +Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale{{footnote}}A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}^^{{footnote}}A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}^^. An indicative list of examples is presented in the following table:
282 282  
283 283  (% style="width:604.294px" %)
284 284  |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU
... ... @@ -311,58 +311,55 @@
311 311  Examples
312 312  
313 313  22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
314 -
315 315  2008-mars-12 would be described as YYYY-MMM-DD, with locale fr-FR
316 -
317 317  22 July 1981 would be described as dd MMMM YYYY, with locale en-US
318 -
319 319  22 Jul 1981 would be described as dd MMM YYYY
320 -
321 321  2010 D62 would be described as YYYYDnn (day 62 of the year 2010)
322 322  
323 323  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
324 324  
325 -|Letter|Date or Time Component|Presentation|Examples
326 -|G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
327 -|yy|Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
328 -|yyyy|Year Full (upper case is Year of Week)|Year|1996
329 -|MM|Month number in year starting with 1|Month|07
330 -|MMM|Month name short|Month|Jul
331 -|MMMM|Month name full|Month|July
332 -|ww|Week in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|27
333 -|W|Week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
334 -|DD|Day in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|189
335 -|dd|Day in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|10
336 -|F|Day of week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
337 -|E|Day name in week|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|Tuesday; Tue
338 -|U|Day number of week (1 = Monday, ..., 7 = Sunday)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|1
339 -|HH|Hour in day (0-23)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
340 -|kk|Hour in day (1-24)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|24
341 -|KK|Hour in am/pm (0-11)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
342 -|hh|Hour in am/pm (1-12)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
343 -|mm|Minute in hour|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|30
344 -|ss|Second in minute|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|55
345 -|S|Millisecond|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|978
346 -|n|(((
347 -Number of periods, used after a SDMX
348 -
321 +(% style="width:850.294px" %)
322 +|(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
323 +|(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
324 +|(% style="width:125px" %)yy|(% style="width:385px" %)Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}}^^{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}}^^)|(% style="width:180px" %)Year|(% style="width:157px" %)96
325 +|(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
326 +|(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
327 +|(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
328 +|(% style="width:125px" %)MMMM|(% style="width:385px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
329 +|(% style="width:125px" %)ww|(% style="width:385px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
330 +|(% style="width:125px" %)W|(% style="width:385px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
331 +|(% style="width:125px" %)DD|(% style="width:385px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
332 +|(% style="width:125px" %)dd|(% style="width:385px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
333 +|(% style="width:125px" %)F|(% style="width:385px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
334 +|(% style="width:125px" %)E|(% style="width:385px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
335 +|(% style="width:125px" %)U|(% style="width:385px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
336 +|(% style="width:125px" %)HH|(% style="width:385px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
337 +|(% style="width:125px" %)kk|(% style="width:385px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
338 +|(% style="width:125px" %)KK|(% style="width:385px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
339 +|(% style="width:125px" %)hh|(% style="width:385px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
340 +|(% style="width:125px" %)mm|(% style="width:385px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
341 +|(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
342 +|(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
343 +|(% style="width:125px" %)n|(% style="width:385px" %)(((
344 +Number of periods, used after a [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]
349 349  Frequency Identifier such as M, Q, D (month, quarter, day)
350 -)))|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
346 +)))|(% style="width:180px" %)Number|(% style="width:157px" %)12
351 351  
352 352  The model is illustrated below:
353 353  
350 +(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png]]
354 354  
355 -
356 356  **Figure 24 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD dimension with the additional information on the component map to describe the time format?**
357 357  
354 +(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png]]
358 358  
356 +(% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
357 +**Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
359 359  
360 -==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ====
359 +=== 13.7.2 Numerical based datetime ===
361 361  
362 -=== 13.3.6 Numerical based datetime ===
361 +Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[Time Period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]], and the **Period** which must take one of the following enumerated values:
363 363  
364 -Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid SDMX Time Period, and the **Period** which must take one of the following enumerated values:
365 -
366 366  * day
367 367  * second
368 368  * millisecond
... ... @@ -369,75 +369,63 @@
369 369  * microsecond
370 370  * nanosecond
371 371  
372 -|Numerical datetime systems|Base|Period
373 -|(((
369 +(% style="width:545.294px" %)
370 +|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
371 +|(% style="width:268px" %)(((
374 374  Epoch Time (UNIX)
375 -
376 376  Milliseconds since 01 Jan 1970
377 -)))|1970|millisecond
378 -|(((
374 +)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
375 +|(% style="width:268px" %)(((
379 379  Windows System Time
380 -
381 381  Milliseconds since 01 Jan 1601
382 -)))|1601|millisecond
378 +)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
383 383  
384 384  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
385 385  
386 386  The model is illustrated below:
387 387  
388 -[[image:1750072341491-790.jpeg]]
384 +(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png]]
389 389  
390 -**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
386 +**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use **
391 391  
392 -==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
388 +=== 13.7.3 Mapping more complex time inputs ===
393 393  
394 -=== Mapping more complex time inputs ===
390 +[[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
395 395  
396 -VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
392 +== 13.8 Using TIME_PERIOD in mapping rules ==
397 397  
398 -== Using TIME_PERIOD in mapping rules ==
394 +The source TIME_PERIOD [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] can be used in conjunction with other input [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] to create discrete mapping rules where the output is conditional on the [[time period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]] value.
399 399  
400 -The source TIME_PERIOD Dimension can be used in conjunction with other input Dimensions to create discrete mapping rules where the output is conditional on the time period value.
396 +The main use case is setting the value of Observation [[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] in the target [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]].
401 401  
402 -The main use case is setting the value of Observation Attributes in the target dataset.
403 -
404 -|Rule|Source|Target
405 -|1|(((
398 +(% style="width:709.294px" %)
399 +|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
400 +|(% style="width:103px" %)1|(% style="width:405px" %)(((
406 406  If
407 -
408 408  INDICATOR=XULADS; and TIME_PERIOD=2007.
409 -)))|(((
410 -Set
411 -
412 -OBS_CONF=F
403 +)))|(% style="width:198px" %)(((
404 +Set OBS_CONF=F
413 413  )))
414 -|2|(((
406 +|(% style="width:103px" %)2|(% style="width:405px" %)(((
415 415  If
416 -
417 417  INDICATOR=XULADS; and TIME_PERIOD=2008.
418 -)))|Set OBS_CONF=F
419 -|3|(((
409 +)))|(% style="width:198px" %)Set OBS_CONF=F
410 +|(% style="width:103px" %)3|(% style="width:405px" %)(((
420 420  If
421 -
422 422  INDICATOR=XULADS; and TIME_PERIOD=2009.
423 -)))|(((
424 -Set
425 -
426 -OBS_CONF=F
413 +)))|(% style="width:198px" %)(((
414 +Set OBS_CONF=F
427 427  )))
428 -|4|(((
416 +|(% style="width:103px" %)4|(% style="width:405px" %)(((
429 429  If
430 -
431 431  INDICATOR=XULADS; and TIME_PERIOD=2010.
432 -)))|(((
433 -Set
434 -
435 -OBS_CONF=**C**
419 +)))|(% style="width:198px" %)(((
420 +Set OBS_CONF=**C**
436 436  )))
437 437  
438 -In the example above, OBS_CONF is an Observation Attribute.
423 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]].
439 439  
440 -== 13. Time span mapping rules using validity periods ==
425 +== 13.9 Time span mapping rules using validity periods ==
441 441  
442 442  Creating discrete mapping rules for each TIME_PERIOD is impractical where rules need to cover a specific span of time regardless of frequency, and for high-frequency data.
443 443  
... ... @@ -445,158 +445,144 @@
445 445  
446 446  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
447 447  
448 -|Rule|Source|Target
449 -|1|(((
433 +(% style="width:516.294px" %)
434 +|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
435 +|(% style="width:74px" %)1|(% style="width:215px" %)(((
450 450  If
451 -
452 452  INDICATOR=XULADS.
453 -
454 -
455 -Validity Period start period=2007 end period=2009
456 -)))|Set OBS_CONF=F
457 -|2|(((
438 +Validity Period
439 +start period=2007
440 +end period=2009
441 +)))|(% style="width:223px" %)Set OBS_CONF=F
442 +|(% style="width:74px" %)2|(% style="width:215px" %)(((
458 458  If
459 -
460 460  INDICATOR=XULADS.
461 -
462 -
463 -Validity Period start period=2010
464 -)))|(((
445 +Validity Period
446 +start period=2010
447 +)))|(% style="width:223px" %)(((
465 465  Set
466 -
467 467  OBS_CONF=F
468 468  )))
469 469  
470 -In Rule 1, start period resolves to the start of the 2007 period (2007-01-01T00:00:00), and the end period resolves to the very end of 2009 (2009-12-31T23:59:59). The rule will hold true regardless of the input data frequency. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of F.
452 +In Rule 1, start period resolves to the start of the 2007 period (2007-01-01T00:00:00), and the end period resolves to the very end of 2009 (2009-12-31T23:59:59). The rule will hold true regardless of the input data frequency. Any observations reporting data for the [[Indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]] XULADS that fall into that time range will have an OBS_CONF value of F.
471 471  
472 -In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
454 +In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the [[Indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]] XULADS that fall into that time range will have an OBS_CONF value of C.
473 473  
474 -== 13. Mapping examples ==
456 +In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the [[Indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]] XULADS that fall into that time range will have an OBS_CONF value of C.
475 475  
476 -=== 13. Many to one mapping (N-1) ===
458 +== 13.10 Mapping examples ==
477 477  
478 -|Source|Map To
479 -|(((
480 -**FREQ**="A"
460 +=== 13.10.1 Many to one mapping (N3513 -1) ===
481 481  
482 -ADJUSTMENT="N"
483 -
462 +(% style="width:542.294px" %)
463 +|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
464 +|(% style="width:274px" %)(((
465 +(% style="color:#8e44ad" %)**FREQ**="A"
466 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]="N"
484 484  **REF_AREA**="PL"
485 -
486 486  **COUNTERPART_AREA**="W0"
487 -
488 488  REF_SECTOR="S1"
489 -
490 490  COUNTERPART_SECTOR="S1"
491 -
492 492  ACCOUNTING_ENTRY="B"
493 -
494 494  STO="B5G"
495 -)))|(((
496 -FREQ="A"
497 -
473 +)))|(% style="width:265px" %)(((
474 +(% style="color:#8e44ad" %)FREQ="A"
498 498  REF_AREA="PL"
499 -
500 500  COUNTERPART_AREA="W0"
501 -INDICATOR="IND_ABC"
477 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]="IND_ABC"(%%)
502 502  
503 503  )))
504 504  
505 -The bold Dimensions map from source to target verbatim. The mapping simply specifies:
481 +The bold [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] map from source to target verbatim. The mapping simply specifies:
506 506  
507 -FREQ => FREQ
483 +> FREQ => FREQ
484 +> REF_AREA=> REF_AREA
485 +> COUNTERPART_AREA=> COUNTERPART _AREA
508 508  
509 -REF_AREA=> REF_AREA
487 +No [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified.
510 510  
511 -COUNTERPART_AREA=> COUNTERPART _AREA
489 +The remaining [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] all map to the [[Indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]] [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]. This is an example of many [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] mapping to one [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target [[indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]:
512 512  
513 -No Representation Mapping is required. The source value simply copies across unmodified.
491 +> N:S1:S1:B:B5G => IND_ABC
514 514  
515 -The remaining Dimensions all map to the Indicator Dimension. This is an example of many Dimensions mapping to one Dimension. In this case a Representation Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target indicator:
493 +Where the key sequence is based on the order specified in the mapping (i.e [[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]], REF_SECTOR, etc will result in the first value N being taken from [[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]] as this was the first item in the source [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] list.
516 516  
517 -N:S1:S1:B:B5G => IND_ABC
495 +**Note**: The key order is NOT based on the [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] order of the [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], as the mapping needs to be resilient to the [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] changing.
518 518  
519 -Where the key sequence is based on the order specified in the mapping (i.e ADJUSTMENT, REF_SECTOR, etc will result in the first value N being taken from ADJUSTMENT as this was the first item in the source Dimension list.
497 +=== 13.10.2 Mapping other data types to Code Id ===
520 520  
521 -**Note**: The key order is NOT based on the Dimension order of the DSD, as the mapping needs to be resilient to the DSD changing.
499 +In the case where the incoming data type is not a string and not a [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] identifier i.e. the source [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] is of type Integer and the target is [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. This is supported by the RepresentationMap. The RepresentationMap source can reference a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], Valuelist, or be free text, the free text can include regular expressions.
522 522  
523 -1.
524 -11.
525 -111. Mapping other data types to Code Id
501 +The following [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] mapping can be used to explicitly map each [[age>>doc:sdmx:Glossary 2\.1.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
526 526  
527 -In the case where the incoming data type is not a string and not a code identifier i.e. the source Dimension is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
503 +(% style="width:402.294px" %)
504 +|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id**
505 +|(% style="width:197px" %)0|(% style="width:204px" %)A
506 +|(% style="width:197px" %)1|(% style="width:204px" %)A
507 +|(% style="width:197px" %)2|(% style="width:204px" %)A
508 +|(% style="width:197px" %)3|(% style="width:204px" %)B
509 +|(% style="width:197px" %)4|(% style="width:204px" %)B
528 528  
529 -The following representation mapping can be used to explicitly map each age to an output code.
530 -
531 -|Source Input Free Text|Desired Output Code Id
532 -|0|A
533 -|1|A
534 -|2|A
535 -|3|B
536 -|4|B
537 -
538 538  If this mapping takes advantage of regular expressions it can be expressed in two rules:
539 539  
513 +(% style="width:336.294px" %)
514 +|(% style="width:182px" %)**Regular Expression**|(% style="width:151px" %)**Desired Output**
515 +|(% style="width:182px" %)[0-2]|(% style="width:151px" %)A
516 +|(% style="width:182px" %)[3-4]|(% style="width:151px" %)B
540 540  
541 -Regular Expression Desired Output
518 +=== 13.10.3 Observation Attributes for Time Period ===
542 542  
543 -|[0-2]|A
544 -|[3-4]|B
520 +This use case is where a specific observation for a specific [[time period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]] has an [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] value.
545 545  
546 -=== 13. Observation Attributes for Time Period ===
522 +(% style="width:621.294px" %)
523 +|(% style="width:201px" %)Input [[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF
524 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C
525 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C
526 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C
547 547  
548 -This use case is where a specific observation for a specific time period has an attribute value.
528 +Or using a validity period on the [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping:
549 549  
550 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
551 -|XULADS|2008|C
552 -|XULADS|2009|C
553 -|XULADS|2010|C
530 +(% style="width:629.294px" %)
531 +|(% style="width:202px" %)Input [[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF
532 +|(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С
554 554  
555 -Or using a validity period on the Representation Mapping:
534 +=== 13.10.4 Time mapping ===
556 556  
557 -Input INDICATOR Valid From/ Valid To Output OBS_CONF
536 +This use case is to create a [[time period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]] from an input that does not respect [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[Time Formats>>doc:sdmx:Glossary 2\.1.Time format.WebHome]].
558 558  
559 -XULADS 2008/2010 C
538 +The [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
560 560  
561 -=== 13. Time mapping ===
540 +(% style="width:652.294px" %)
541 +|(% style="text-align:center; width:139px" %)Source Value|(% style="text-align:center; width:165px" %)Source Mapping|(% style="text-align:center; width:182px" %)Target Frequency|(% style="text-align:center; width:163px" %)Output
542 +|(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981
562 562  
563 -This use case is to create a time period from an input that does not respect SDMX Time Formats.
544 +When the target frequency is based on another target [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] value, in this example the value of the FREQ [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in the target [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].
564 564  
565 -The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
546 +(% style="width:658.294px" %)
547 +|(% style="text-align:center; width:143px" %)Source Value|(% style="text-align:center; width:163px" %) Source Mapping|(% style="text-align:center; width:176px" %)Target Dimension|(% style="text-align:center; width:173px" %)Frequency Output
548 +|(% style="width:143px" %)18/07/1981|(% style="width:163px" %)dd/MM/yyyy|(% style="width:176px" %)FREQ|(% style="width:173px" %)1981-07-18 (when FREQ=D)
566 566  
567 -|Source Value|Source Mapping|Target Frequency|Output
568 -|18/07/1981|dd/MM/yyyy|A|1981
550 + When the source is a numerical format.
569 569  
570 -When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD.
552 +(% style="width:658.294px" %)
553 +|(% style="width:143px" %)Source Value|(% style="width:163px" %) Start Period|(% style="width:176px" %)Interval|(% style="width:176px" %)Target FREQ|(% style="width:173px" %) Output
554 +|(% style="width:143px" %)1589808220|(% style="width:163px" %)1970|(% style="width:176px" %) millisecond|(% style="width:176px" %)M|(% style="width:173px" %)2020-05
571 571  
572 -Source Value Source Mapping Target Frequency Output
573 -
574 -Dimension
575 -
576 -|18/07/1981 dd/MM/yyyy FREQ| |1981-07-18 (when FREQ=D)
577 -| When the source is a numerical format| |
578 -|Source Value Start Period Interval|(((
579 -Target
580 -
581 -FREQ
582 -)))|Output
583 -|1589808220 1970 millisecond|M|2020-05
584 -
585 585  When the source frequency is lower than the target frequency additional information 3568 can be provided for resolve to start of period, end of period, or mid period, as shown 3569 in the following example:
586 586  
587 - Source Value Source Mapping Target Frequency Output
558 +(% style="width:666.294px" %)
559 +|(% style="text-align:center; width:131px" %)(% style="color:#000000" %) Source Value|(% style="text-align:center; width:143px" %)(% style="color:#000000" %)Source Mapping|(% style="text-align:center; width:149px" %)(% style="color:#000000" %)Target Dimension|(% style="text-align:center; width:114px" %)(% style="color:#000000" %)Frequency|(% style="text-align:center; width:126px" %)(% style="color:#000000" %)Output
560 +|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1981-12-31
588 588  
589 -Dimension
590 -
591 - 1981 yyyy D – End of Period 1981-12-31
592 -
593 -
594 594  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
595 595  
596 - Source Value Source Mapping Target Frequency Output
564 +(% style="width:666.294px" %)
565 +|(% style="text-align:center; width:131px" %) Source Value|(% style="text-align:center; width:143px" %)Source Mapping|(% style="text-align:center; width:149px" %)Target Dimension|(% style="text-align:center; width:114px" %)Frequency|(% style="text-align:center; width:126px" %)Output
566 +|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1982-03-31
597 597  
598 -Dimension
599 -
600 600  ----
601 601  
570 +(% contenteditable="false" tabindex="-1" %)
571 +(((
602 602  {{putFootnotes/}}
573 +)))
1750074822764-573.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,0 +1,1 @@
1 +25.1 KB
Content
1750074865924-797.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
1750074994887-415.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,0 +1,1 @@
1 +13
© Semantic R&D Group, 2026