Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena K. on 2026/06/10 10:18
From version 13.3
edited by Helena K.
on 2026/06/10 10:16
Change comment: There is no comment for this version
To version 7.1
edited by Helena K.
on 2025/06/16 15:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,31 +1,76 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 +(% contenteditable="false" tabindex="-1" %)
2 +(((
3 +(% class="macro" data-macro="startmacro:box|-|title=~"**Contents**~"|-|\{\{toc/}}" data-widget="xwiki-macro" %)
4 +(((
5 +(% class="macro-placeholder hidden" %)
6 +(((
7 +macro:box
8 +)))
4 4  
10 +(% class="box" %)
11 +(((
12 +(% class="box-title" %)
13 +(((
14 +**Contents**
15 +)))
16 +
17 +(% class="macro" data-macro="startmacro:toc|-|" %)
18 +(((
19 +(% class="macro-placeholder hidden" %)
20 +(((
21 +macro:toc
22 +)))
23 +
24 +(% class="wikitoc" %)
25 +*
26 +** [[13.1 Introduction>>doc:null||anchor="H13.1Introduction"]]
27 +** [[13.2 1-1 structure maps>>doc:null||anchor="H13.21-1structuremaps"]]
28 +** [[13.3 N-n structure maps>>doc:null||anchor="H13.3N-nstructuremaps"]]
29 +** [[13.4 Ambiguous mapping rules>>doc:null||anchor="H13.4Ambiguousmappingrules"]]
30 +** [[13.5 Representation maps>>doc:null||anchor="H13.5Representationmaps"]]
31 +** [[13.6 Regular expression and substring rules>>doc:null||anchor="H13.6Regularexpressionandsubstringrules"]]
32 +*** [[13.6.1 Regular expressions>>doc:null||anchor="H13.6.1Regularexpressions"]]
33 +*** [[13.6.2 Substrings>>doc:null||anchor="H13.6.2Substrings"]]
34 +** [[13.7 Mapping non-SDMX time formats to SDMX formats>>doc:null||anchor="H13.7Mappingnon-SDMXtimeformatstoSDMXformats"]]
35 +*** [[13.7.1 Pattern based dates>>doc:null||anchor="H13.7.1Patternbaseddates"]]
36 +*** [[13.7.2 Numerical based datetime>>doc:null||anchor="H13.7.2Numericalbaseddatetime"]]
37 +*** [[13.7.3 Mapping more complex time inputs>>doc:null||anchor="H13.7.3Mappingmorecomplextimeinputs"]]
38 +** [[13.8 Using TIME_PERIOD in mapping rules>>doc:null||anchor="H13.8UsingTIME_PERIODinmappingrules"]]
39 +** [[13.9 Time span mapping rules using validity periods>>doc:null||anchor="H13.9Timespanmappingrulesusingvalidityperiods"]]
40 +** [[13.10 Mapping examples>>doc:null||anchor="H13.10Mappingexamples"]]
41 +*** [[13.10.1 Many to one mapping (N3513 -1)>>doc:null||anchor="H13.10.1A0Manytoonemapping28N3513-129"]]
42 +*** [[13.10.2 Mapping other data types to Code Id>>doc:null||anchor="H13.10.2MappingotherdatatypestoCodeId"]]
43 +*** [[13.10.3 Observation Attributes for Time Period>>doc:null||anchor="H13.10.3ObservationAttributesforTimePeriod"]]
44 +*** [[13.10.4 Time mapping>>doc:null||anchor="H13.10.4Timemapping"]]
45 +)))
46 +)))
47 +)))
48 +)))
49 +
5 5  == 13.1 Introduction ==
6 6  
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]].
52 +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.
8 8  
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.
54 +Structure mapping does not alter the [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
10 10  
11 -An input [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] maps to:
56 +An input series (% style="color:#e74c3c" %)maps(%%) to:
12 12  
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.
58 +1. Exactly one output series; or
59 +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
60 +1. Zero output series where no source rule matches the input [[Component>>doc:sdmx:Glossary.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 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.
66 +* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]](% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_1" %)^^[[1>>doc:null||anchor="x_footnote_1"]]^^(%%) to multi-dimensional; and
67 +* 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.
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 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.
71 +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.
27 27  
28 -In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] are mapped to their ISO 3character equivalent.
73 +In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary.Code.WebHome]] are (% style="color:#e74c3c" %)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 map to the same target value, for example when deriving regions from country [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
84 +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]].
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 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.
96 +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.
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>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and
105 +ADJUSTMENT=N; and
61 61  MATURITY=L.
62 62  )))|(% style="width:378px" %)(((
63 63  Set
64 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L
109 +INDICATOR=A_N_L
65 65  )))
66 66  |(% style="width:65px" %)2|(% style="width:519px" %)(((
67 67  If
68 68  FREQUENCY=M; and
69 -[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=S_A1; and
114 +ADJUSTMENT=S_A1; and
70 70  MATURITY=TY12.
71 71  )))|(% style="width:378px" %)(((
72 72  Set
73 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12
118 +INDICATOR=MON_SAX_12
74 74  )))
75 75  
76 -N-n rules can also set values for multiple source [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
121 +N-n rules can also set values for multiple source Components.
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>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and MATURITY=L.
127 +FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
83 83  )))|(% style="width:383px" %)(((
84 84  Set
85 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L, STATUS=QXR15,
130 +INDICATOR=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>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=S_A1; and MATURITY=TY12.
135 +FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
91 91  )))|(% style="width:383px" %)(((
92 92  Set
93 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12,
138 +INDICATOR=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>>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]].
145 +A structure map is ambiguous if the rules result in a dataset containing multiple series with the same Series Key.
101 101  
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:
147 +A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
103 103  
104 104  (% style="width:972.294px" %)
105 -|(% style="text-align:center; width:257px" %)**Source**|(% style="text-align:center; width:315px" %)**Target**|(% style="text-align:center; width:397px" %)**Output Series Key**
150 +|(% style="width:257px" %)Source|(% style="width:315px" %)Target|(% style="width:397px" %)Output Series Key
106 106  |(% style="width:257px" %)SERIES_CODE=XMAN_Z_21|(% style="width:315px" %)(((
107 -[[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]
108 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM
152 +Dimensions
153 +INDICATOR=XM
109 109  FREQ=A
110 -[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N
111 -[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]
155 +ADJUSTMENT=N
156 +Attributes
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>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]
121 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM
165 +Dimensions
166 +INDICATOR=XM
122 122  FREQ=A
123 -[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N
124 -[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]
168 +ADJUSTMENT=N
169 +Attributes
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>>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.
174 +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.
130 130  
131 131  == 13.5 Representation maps ==
132 132  
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.
178 +[[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.
134 134  
135 -The source and target of a [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map can reference any of the following:
180 +The source and target of a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) can reference any of the following:
136 136  
137 -1. [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
182 +1. Codelist
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 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:
186 +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:
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 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:
197 +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:
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 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.
209 +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.
165 165  
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.
211 +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.
167 167  
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:
213 +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:
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 2\.1.Representation.WebHome]] Maps:
221 +Other characteristics of [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Maps(%%):
177 177  
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.
223 +* 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;
224 +* 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
225 +* 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.
181 181  
182 182  == 13.6 Regular expression and substring rules ==
183 183  
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.
229 +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.
185 185  
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:
231 +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:
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 2\.1.Representation.WebHome]] Map.
239 +Regular expression mapping rules are defined in the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Map.
195 195  
196 -Below is an example set of regular expression rules for a particular [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
241 +Below is an example set of regular expression rules for a particular [[component>>doc:sdmx:Glossary.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 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]].
249 +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]].
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  
... ... @@ -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' map to Y// as shown in the following example:
284 +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:
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 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]].
292 +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.
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 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:
299 +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:
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 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.
319 +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.
320 +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.
276 276  
277 277  === 13.7.1 Pattern based dates ===
278 278  
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.
324 +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.
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}}^^{{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:
326 +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(% contenteditable="false" tabindex="-1" data-macro="startmacro: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" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro: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" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_2" %)^^[[2>>doc:null||anchor="x_footnote_2"]]^^(%%). 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
... ... @@ -321,7 +321,7 @@
321 321  (% style="width:850.294px" %)
322 322  |(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
323 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
369 +|(% style="width:125px" %)yy|(% style="width:385px" %)Year short (upper case is Year of Week(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_3" %)^^[[3>>doc:null||anchor="x_footnote_3"]]^^(%%))|(% style="width:180px" %)Year|(% style="width:157px" %)96
325 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 326  |(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
327 327  |(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
... ... @@ -341,17 +341,17 @@
341 341  |(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
342 342  |(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
343 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]]
389 +Number of periods, used after a SDMX
345 345  Frequency Identifier such as M, Q, D (month, quarter, day)
346 346  )))|(% style="width:180px" %)Number|(% style="width:157px" %)12
347 347  
348 348  The model is illustrated below:
349 349  
350 -(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png]]
395 +(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png||data-widget="image"]]
351 351  
352 352  **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?**
353 353  
354 -(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png]]
399 +(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png||data-widget="image"]]
355 355  
356 356  (% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
357 357  **Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
... ... @@ -358,7 +358,7 @@
358 358  
359 359  === 13.7.2 Numerical based datetime ===
360 360  
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:
406 +Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Time Period>>doc:sdmx:Glossary.Time period.WebHome]], and the **Period** which must take one of the following enumerated values:
362 362  
363 363  * day
364 364  * second
... ... @@ -381,19 +381,19 @@
381 381  
382 382  The model is illustrated below:
383 383  
384 -(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png]]
429 +(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png||data-widget="image"]]
385 385  
386 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 **
387 387  
388 388  === 13.7.3 Mapping more complex time inputs ===
389 389  
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.
435 +[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
391 391  
392 392  == 13.8 Using TIME_PERIOD in mapping rules ==
393 393  
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.
439 +The source TIME_PERIOD [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can be used in conjunction with other input [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to create discrete mapping rules where the output is conditional on the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] value.
395 395  
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]].
441 +The main use case is setting the value of Observation [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the target [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
397 397  
398 398  (% style="width:709.294px" %)
399 399  |(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
... ... @@ -420,13 +420,13 @@
420 420  Set OBS_CONF=**C**
421 421  )))
422 422  
423 -In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]].
468 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
424 424  
425 425  == 13.9 Time span mapping rules using validity periods ==
426 426  
427 -Creating discrete (% style="color:#e74c3c" %)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.
472 +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.
428 428  
429 -Instead, an optional validity period can be set for each (% style="color:#e74c3c" %)mapping(%%).
474 +Instead, an optional validity period can be set for each mapping.
430 430  
431 431  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
432 432  
... ... @@ -434,7 +434,7 @@
434 434  |(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
435 435  |(% style="width:74px" %)1|(% style="width:215px" %)(((
436 436  If
437 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XULADS.
482 +INDICATOR=XULADS.
438 438  Validity Period
439 439  start period=2007
440 440  end period=2009
... ... @@ -441,7 +441,7 @@
441 441  )))|(% style="width:223px" %)Set OBS_CONF=F
442 442  |(% style="width:74px" %)2|(% style="width:215px" %)(((
443 443  If
444 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XULADS.
489 +INDICATOR=XULADS.
445 445  Validity Period
446 446  start period=2010
447 447  )))|(% style="width:223px" %)(((
... ... @@ -449,11 +449,11 @@
449 449  OBS_CONF=F
450 450  )))
451 451  
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.
497 +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.
453 453  
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.
499 +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.
455 455  
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.
501 +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.
457 457  
458 458  == 13.10 Mapping examples ==
459 459  
... ... @@ -460,10 +460,10 @@
460 460  === 13.10.1 Many to one mapping (N3513 -1) ===
461 461  
462 462  (% style="width:542.294px" %)
463 -|(% style="width:274px" %)**Source**|(% style="width:265px" %)(% style="color:#e74c3c" %)**Map**(%%)** To**
508 +|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
464 464  |(% style="width:274px" %)(((
465 465  (% style="color:#8e44ad" %)**FREQ**="A"
466 -[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]="N"
511 +ADJUSTMENT="N"
467 467  **REF_AREA**="PL"
468 468  **COUNTERPART_AREA**="W0"
469 469  REF_SECTOR="S1"
... ... @@ -474,34 +474,34 @@
474 474  (% style="color:#8e44ad" %)FREQ="A"
475 475  REF_AREA="PL"
476 476  COUNTERPART_AREA="W0"
477 -[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]="IND_ABC"(%%)
522 +INDICATOR="IND_ABC"(%%)
478 478  
479 479  )))
480 480  
481 -The bold [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The (% style="color:#e74c3c" %)mapping(%%) simply specifies:
526 +The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The mapping simply specifies:
482 482  
483 483  > FREQ => FREQ
484 484  > REF_AREA=> REF_AREA
485 485  > COUNTERPART_AREA=> COUNTERPART _AREA
486 486  
487 -No [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)Mapping(%%) is required. The source value simply copies across unmodified.
532 +No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified.
488 488  
489 -The remaining [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] all (% style="color:#e74c3c" %)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]] (% style="color:#e74c3c" %)mapping(%%) to one [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)Mapping(%%) is required, and the (% style="color:#e74c3c" %)mapping(%%) first describes the input 'partial key' and how this (% style="color:#e74c3c" %)maps(%%) to the target [[indicator>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]:
534 +The remaining [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] all (% style="color:#e74c3c" %)map(%%) to the Indicator [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. This is an example of many [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] mapping to one [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required, and the mapping first describes the input 'partial key' and how this (% style="color:#e74c3c" %)maps(%%) to the target indicator:
490 490  
491 491  > N:S1:S1:B:B5G => IND_ABC
492 492  
493 -Where the key sequence is based on the order specified in the (% style="color:#e74c3c" %)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.
538 +Where the key sequence is based on the order specified in the (% style="color:#e74c3c" %)mapping(%%) (i.e [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]], REF_SECTOR, etc will result in the first value N being taken from [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]] as this was the first item in the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] list.
494 494  
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 (% style="color:#e74c3c" %)mapping(%%) needs to be resilient to the [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] changing.
540 +**Note**: The key order is NOT based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] order of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], as the (% style="color:#e74c3c" %)mapping(%%) needs to be resilient to the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] changing.
496 496  
497 497  === 13.10.2 Mapping other data types to Code Id ===
498 498  
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.
544 +In the case where the incoming data type is not a string and not a [[code>>doc:sdmx:Glossary.Code.WebHome]] identifier i.e. the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 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.
500 500  
501 -The following [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)mapping(%%) can be used to explicitly (% style="color:#e74c3c" %)map(%%) each [[age>>doc:sdmx:Glossary 2\.1.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
546 +The following [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)mapping(%%) can be used to explicitly (% style="color:#e74c3c" %)map(%%) each [[age>>doc:sdmx:Glossary.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary.Code.WebHome]].
502 502  
503 503  (% style="width:402.294px" %)
504 -|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] Id**
549 +|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id**
505 505  |(% style="width:197px" %)0|(% style="width:204px" %)A
506 506  |(% style="width:197px" %)1|(% style="width:204px" %)A
507 507  |(% style="width:197px" %)2|(% style="width:204px" %)A
... ... @@ -508,7 +508,7 @@
508 508  |(% style="width:197px" %)3|(% style="width:204px" %)B
509 509  |(% style="width:197px" %)4|(% style="width:204px" %)B
510 510  
511 -If this (% style="color:#e74c3c" %)mapping(%%) takes advantage of regular expressions it can be expressed in two rules:
556 +If this mapping takes advantage of regular expressions it can be expressed in two rules:
512 512  
513 513  (% style="width:336.294px" %)
514 514  |(% style="width:182px" %)**Regular Expression**|(% style="width:151px" %)**Desired Output**
... ... @@ -517,34 +517,34 @@
517 517  
518 518  === 13.10.3 Observation Attributes for Time Period ===
519 519  
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.
565 +This use case is where a specific observation for a specific [[time period>>doc:sdmx:Glossary.Time period.WebHome]] has an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] value.
521 521  
522 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
568 +|(% style="width:201px" %)Input INDICATOR|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF
524 524  |(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C
525 525  |(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C
526 526  |(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C
527 527  
528 -Or using a validity period on the [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)Mapping(%%):
573 +Or using a validity period on the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping:
529 529  
530 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
576 +|(% style="width:202px" %)Input INDICATOR|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF
532 532  |(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С
533 533  
534 534  === 13.10.4 Time mapping ===
535 535  
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]].
581 +This use case is to create a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] from an input that does not respect [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Time Formats.
537 537  
538 -The [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] (% style="color:#e74c3c" %)Mapping(%%) from SYS_TIME to TIME_PERIOD specifies itself as a time (% style="color:#e74c3c" %)mapping(%%) with the following details:
583 +The [[Component>>doc:sdmx:Glossary.Component.WebHome]] Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
539 539  
540 540  (% style="width:652.294px" %)
541 -|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source (% style="color:#e74c3c" %)Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output
586 +|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output
542 542  |(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981
543 543  
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]].
589 +When the target frequency is based on another target [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] value, in this example the value of the FREQ [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the target [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
545 545  
546 546  (% style="width:658.294px" %)
547 -|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source (% style="color:#e74c3c" %)Mapping|(% style="width:176px" %)Target [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]|(% style="width:173px" %)Frequency Output
592 +|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source Mapping|(% style="width:176px" %)Target Dimension|(% style="width:173px" %)Frequency Output
548 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)
549 549  
550 550   When the source is a numerical format.
... ... @@ -556,7 +556,7 @@
556 556  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:
557 557  
558 558  (% style="width:666.294px" %)
559 -|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source (% style="color:#e74c3c" %)Mapping|(% style="width:149px" %)Target [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
604 +|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
560 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
561 561  
562 562  When the start of year is April 1^^st^^ the Structure (% style="color:#e74c3c" %)Map(%%) has YearStart=04-01:
... ... @@ -569,5 +569,16 @@
569 569  
570 570  (% contenteditable="false" tabindex="-1" %)
571 571  (((
572 -{{putFootnotes/}}
617 +(% class="macro" data-macro="startmacro:putFootnotes|-|" data-widget="xwiki-macro" %)
618 +(((
619 +(% class="macro-placeholder hidden" %)
620 +(((
621 +macro:putFootnotes
573 573  )))
623 +
624 +(% class="footnotes" %)
625 +1. [[^>>doc:null||anchor="x_footnote_ref_1" id="x_footnote_1" class="footnoteBackRef"]] Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.
626 +1. [[^>>doc:null||anchor="x_footnote_ref_2" id="x_footnote_2" class="footnoteBackRef"]] 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//
627 +1. [[^>>doc:null||anchor="x_footnote_ref_3" id="x_footnote_3" class="footnoteBackRef"]] yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years
628 +)))
629 +)))
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -13
SUZ.Methodology.Code.MethodologyClass[0]
© Semantic R&D Group, 2026