Changes for page 13 Structure Mapping
Last modified by Helena K. on 2026/06/10 10:18
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
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
-
... ... @@ -1,76 +1,31 @@ 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 -))) 1 +{{box title="**Contents**"}} 2 +{{toc/}} 3 +{{/box}} 9 9 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 - 50 50 == 13.1 Introduction == 51 51 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. 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]]. 53 53 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. 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. 55 55 56 -An input series (%style="color:#e74c3c"%)maps(%%)to:11 +An input [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] maps to: 57 57 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. 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. 61 61 62 62 Typical use cases include: 63 63 64 64 * Transforming received data into a common internal structure; 65 65 * Transforming reported data into the data collector's preferred structure; 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="macrofootnoteRef" id="x_footnote_ref_1" %)^^[[1>>doc:null||anchor="x_footnote_1"]]^^(%%)to multi-dimensional; and67 -* 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. 68 68 69 69 == 13.2 1-1 structure maps == 70 70 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. 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. 72 72 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.28 +In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] are mapped to their ISO 3character equivalent. 74 74 75 75 (% style="width:585.294px" %) 76 76 |(% style="width:173px" %)**Country**|(% style="width:180px" %)**Alpha-2 code**|(% style="width:229px" %)**Alpha-3 code** ... ... @@ -81,7 +81,7 @@ 81 81 |(% style="width:173px" %)Andorra|(% style="width:180px" %)AD|(% style="width:229px" %)AND 82 82 |(% style="width:173px" %)etc…|(% style="width:180px" %) |(% style="width:229px" %) 83 83 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]].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]]. 85 85 86 86 (% style="width:490.294px" %) 87 87 |(% style="width:260px" %)Source Component: REF_AREA|(% style="width:227px" %)Target Component: REGION ... ... @@ -93,7 +93,7 @@ 93 93 94 94 == 13.3 N-n structure maps == 95 95 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.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. 97 97 98 98 Example: 99 99 ... ... @@ -102,40 +102,40 @@ 102 102 |(% style="width:65px" %)1|(% style="width:519px" %)((( 103 103 If 104 104 FREQUENCY=A; and 105 -ADJUSTMENT=N; and 60 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and 106 106 MATURITY=L. 107 107 )))|(% style="width:378px" %)((( 108 108 Set 109 -INDICATOR=A_N_L 64 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L 110 110 ))) 111 111 |(% style="width:65px" %)2|(% style="width:519px" %)((( 112 112 If 113 113 FREQUENCY=M; and 114 -ADJUSTMENT=S_A1; and 69 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=S_A1; and 115 115 MATURITY=TY12. 116 116 )))|(% style="width:378px" %)((( 117 117 Set 118 -INDICATOR=MON_SAX_12 73 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12 119 119 ))) 120 120 121 -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]]. 122 122 123 123 (% style="width:965.294px" %) 124 124 |(% style="width:73px" %)Rule|(% style="width:506px" %)Source|(% style="width:383px" %)Target 125 125 |(% style="width:73px" %)1|(% style="width:506px" %)((( 126 126 If 127 -FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 82 +FREQUENCY=A; and [[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N; and MATURITY=L. 128 128 )))|(% style="width:383px" %)((( 129 129 Set 130 -INDICATOR=A_N_L, STATUS=QXR15, 85 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=A_N_L, STATUS=QXR15, 131 131 NOTE="Unadjusted". 132 132 ))) 133 133 |(% style="width:73px" %)2|(% style="width:506px" %)((( 134 134 If 135 -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. 136 136 )))|(% style="width:383px" %)((( 137 137 Set 138 -INDICATOR=MON_SAX_12, 93 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=MON_SAX_12, 139 139 STATUS=MPM12, 140 140 NOTE="Seasonally Adjusted" 141 141 ))) ... ... @@ -142,18 +142,18 @@ 142 142 143 143 == 13.4 Ambiguous mapping rules == 144 144 145 -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]]. 146 146 147 -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: 148 148 149 149 (% style="width:972.294px" %) 150 -|(% 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** 151 151 |(% style="width:257px" %)SERIES_CODE=XMAN_Z_21|(% style="width:315px" %)((( 152 -Dimensions 153 -INDICATOR=XM 107 +[[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] 108 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM 154 154 FREQ=A 155 -ADJUSTMENT=N 156 -Attributes 110 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N 111 +[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] 157 157 UNIT_MEASURE=_Z 158 158 COMP_ORG=21 159 159 )))|(% style="width:397px" %)XM:A:N ... ... @@ -162,28 +162,28 @@ 162 162 163 163 164 164 )))|(% style="width:315px" %)((( 165 -Dimensions 166 -INDICATOR=XM 120 +[[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] 121 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]=XM 167 167 FREQ=A 168 -ADJUSTMENT=N 169 -Attributes 123 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]=N 124 +[[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] 170 170 UNIT_MEASURE=_Z 171 171 COMP_ORG=34 172 172 )))|(% style="width:397px" %)XM:A:N 173 173 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. 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. 175 175 176 176 == 13.5 Representation maps == 177 177 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.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. 179 179 180 -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: 181 181 182 -1. Codelist 137 +1. [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] 183 183 1. Free Text (restricted by type, e.g String, Integer, Boolean) 184 184 1. Valuelist 185 185 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: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: 187 187 188 188 (% style="width:356.294px" %) 189 189 |(% style="width:167px" %)CL_ISO_ALPHA2|(% style="width:186px" %)CL_ISO_ALPHA3 ... ... @@ -194,7 +194,7 @@ 194 194 |(% style="width:167px" %)AD|(% style="width:186px" %)AND 195 195 |(% style="width:167px" %)etc…|(% style="width:186px" %) 196 196 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: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: 198 198 199 199 (% style="width:364.294px" %) 200 200 |(% style="width:169px" %)Text|(% style="width:192px" %)CL_ISO_ALPHA2 ... ... @@ -206,11 +206,11 @@ 206 206 |(% style="width:169px" %)"Eire"|(% style="width:192px" %)IE 207 207 |(% style="width:169px" %)etc…|(% style="width:192px" %) 208 208 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. 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. 210 210 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.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. 212 212 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: 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: 214 214 215 215 (% style="width:435.294px" %) 216 216 |(% style="width:126px" %)Value|(% style="width:133px" %)Locale|(% style="width:173px" %)Name ... ... @@ -218,17 +218,17 @@ 218 218 |(% style="width:126px" %)%|(% style="width:133px" %)En|(% style="width:173px" %)Percentage 219 219 |(% style="width:126px" %) |(% style="width:133px" %)fr|(% style="width:173px" %)Pourcentage 220 220 221 -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: 222 222 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'; and225 -* 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. 226 226 227 227 == 13.6 Regular expression and substring rules == 228 228 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. 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. 230 230 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: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: 232 232 233 233 //If starts with 'XU' map to 'Y'// 234 234 ... ... @@ -236,9 +236,9 @@ 236 236 237 237 === 13.6.1 Regular expressions === 238 238 239 -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. 240 240 241 -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]]. 242 242 243 243 (% style="width:664.294px" %) 244 244 |(% style="width:141px" %)**Regex**|(% style="width:362px" %)**Description**|(% style="width:158px" %)**Output** ... ... @@ -246,7 +246,7 @@ 246 246 |(% style="width:141px" %)^[A-G]|(% style="width:362px" %)Rule match if the input starts with letters A to G|(% style="width:158px" %)OUT_B 247 247 |(% style="width:141px" %)A~|B|(% style="width:362px" %)Rule match if input is either 'A' or 'B'|(% style="width:158px" %)OUT_C 248 248 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]]. 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]]. 250 250 251 251 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 252 252 ... ... @@ -281,7 +281,7 @@ 281 281 |(% style="width:169px" %)ABC_DEF_XYZ|(% style="width:147px" %)5|(% style="width:133px" %)3|(% style="width:171px" %)DEF 282 282 |(% style="width:169px" %)XULADS|(% style="width:147px" %)1|(% style="width:133px" %)2|(% style="width:171px" %)XU 283 283 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:239 +Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example: 285 285 286 286 (% style="width:628.294px" %) 287 287 |(% style="width:163px" %)Start|(% style="width:158px" %)Length|(% style="width:128px" %)Source|(% style="width:176px" %)Target ... ... @@ -289,7 +289,7 @@ 289 289 290 290 == 13.7 Mapping non-SDMX time formats to SDMX formats == 291 291 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.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]]. 293 293 294 294 Two types of time input are defined: 295 295 ... ... @@ -296,7 +296,7 @@ 296 296 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 297 297 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. 298 298 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: 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: 300 300 301 301 |Frequency|Format|Example 302 302 |A|YYYY|2010 ... ... @@ -316,14 +316,14 @@ 316 316 317 317 There are two important points to note: 318 318 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.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. 321 321 322 322 === 13.7.1 Pattern based dates === 323 323 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. 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. 325 325 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="macrofootnoteRef" id="x_footnote_ref_2" %)^^[[2>>doc:null||anchor="x_footnote_2"]]^^(%%). 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: 327 327 328 328 (% style="width:604.294px" %) 329 329 |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU ... ... @@ -366,7 +366,7 @@ 366 366 (% style="width:850.294px" %) 367 367 |(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples** 368 368 |(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD 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="macrofootnoteRef" id="x_footnote_ref_3" %)^^[[3>>doc:null||anchor="x_footnote_3"]]^^(%%))|(% style="width:180px" %)Year|(% style="width:157px" %)96324 +|(% 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 370 370 |(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996 371 371 |(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07 372 372 |(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul ... ... @@ -386,17 +386,17 @@ 386 386 |(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55 387 387 |(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978 388 388 |(% style="width:125px" %)n|(% style="width:385px" %)((( 389 -Number of periods, used after a SDMX 344 +Number of periods, used after a [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 390 390 Frequency Identifier such as M, Q, D (month, quarter, day) 391 391 )))|(% style="width:180px" %)Number|(% style="width:157px" %)12 392 392 393 393 The model is illustrated below: 394 394 395 -(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png ||data-widget="image"]]350 +(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png]] 396 396 397 397 **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?** 398 398 399 -(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png ||data-widget="image"]]354 +(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png]] 400 400 401 401 (% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %) 402 402 **Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension** ... ... @@ -403,7 +403,7 @@ 403 403 404 404 === 13.7.2 Numerical based datetime === 405 405 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: 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: 407 407 408 408 * day 409 409 * second ... ... @@ -426,19 +426,19 @@ 426 426 427 427 The model is illustrated below: 428 428 429 -(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png ||data-widget="image"]]384 +(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png]] 430 430 431 431 **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 ** 432 432 433 433 === 13.7.3 Mapping more complex time inputs === 434 434 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. 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. 436 436 437 437 == 13.8 Using TIME_PERIOD in mapping rules == 438 438 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. 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. 440 440 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]]. 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]]. 442 442 443 443 (% style="width:709.294px" %) 444 444 |(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target** ... ... @@ -465,7 +465,7 @@ 465 465 Set OBS_CONF=**C** 466 466 ))) 467 467 468 -In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. 423 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]. 469 469 470 470 == 13.9 Time span mapping rules using validity periods == 471 471 ... ... @@ -494,11 +494,11 @@ 494 494 OBS_CONF=F 495 495 ))) 496 496 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. 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. 498 498 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. 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. 500 500 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. 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. 502 502 503 503 == 13.10 Mapping examples == 504 504 ... ... @@ -508,7 +508,7 @@ 508 508 |(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To** 509 509 |(% style="width:274px" %)((( 510 510 (% style="color:#8e44ad" %)**FREQ**="A" 511 -ADJUSTMENT="N" 466 +[[ADJUSTMENT>>doc:sdmx:Glossary 2\.1.Adjustment.WebHome]]="N" 512 512 **REF_AREA**="PL" 513 513 **COUNTERPART_AREA**="W0" 514 514 REF_SECTOR="S1" ... ... @@ -519,31 +519,31 @@ 519 519 (% style="color:#8e44ad" %)FREQ="A" 520 520 REF_AREA="PL" 521 521 COUNTERPART_AREA="W0" 522 -INDICATOR="IND_ABC"(%%) 477 +[[INDICATOR>>doc:sdmx:Glossary 2\.1.Statistical indicator.WebHome]]="IND_ABC"(%%) 523 523 524 524 ))) 525 525 526 -The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)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: 527 527 528 528 > FREQ => FREQ 529 529 > REF_AREA=> REF_AREA 530 530 > COUNTERPART_AREA=> COUNTERPART _AREA 531 531 532 -No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified. 487 +No [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified. 533 533 534 -The remaining [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] all (%style="color:#e74c3c" %)map(%%)totheIndicator [[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: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]]: 535 535 536 536 > N:S1:S1:B:B5G => IND_ABC 537 537 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.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. 539 539 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.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. 541 541 542 542 === 13.10.2 Mapping other data types to Code Id === 543 543 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. 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. 545 545 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]].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]]. 547 547 548 548 (% style="width:402.294px" %) 549 549 |(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id** ... ... @@ -562,34 +562,34 @@ 562 562 563 563 === 13.10.3 Observation Attributes for Time Period === 564 564 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. 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. 566 566 567 567 (% style="width:621.294px" %) 568 -|(% style="width:201px" %)Input INDICATOR|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF 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 569 569 |(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C 570 570 |(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C 571 571 |(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C 572 572 573 -Or using a validity period on the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping: 528 +Or using a validity period on the [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping: 574 574 575 575 (% style="width:629.294px" %) 576 -|(% style="width:202px" %)Input INDICATOR|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF 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 577 577 |(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С 578 578 579 579 === 13.10.4 Time mapping === 580 580 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. 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]]. 582 582 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: 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: 584 584 585 585 (% style="width:652.294px" %) 586 -|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output 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 587 587 |(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981 588 588 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]]. 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]]. 590 590 591 591 (% style="width:658.294px" %) 592 -|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source Mapping|(% style="width:176px" %)Target Dimension|(% style="width:173px" %)Frequency Output 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 593 593 |(% 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) 594 594 595 595 When the source is a numerical format. ... ... @@ -601,13 +601,13 @@ 601 601 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: 602 602 603 603 (% style="width:666.294px" %) 604 -|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output 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 605 605 |(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1981-12-31 606 606 607 -When the start of year is April 1^^st^^ the Structure (% style="color:#e74c3c" %)Map(%%)has YearStart=04-01:562 +When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01: 608 608 609 609 (% style="width:666.294px" %) 610 -|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output 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 611 611 |(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1982-03-31 612 612 613 613 ---- ... ... @@ -614,16 +614,5 @@ 614 614 615 615 (% contenteditable="false" tabindex="-1" %) 616 616 ((( 617 -(% class="macro" data-macro="startmacro:putFootnotes|-|" data-widget="xwiki-macro" %) 618 -((( 619 -(% class="macro-placeholder hidden" %) 620 -((( 621 -macro:putFootnotes 572 +{{putFootnotes/}} 622 622 ))) 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 -)))
- SUZ.Methodology.Code.MethodologyClass[0]
-
- SKMS.Methodology.Code.MethodologyClass[0]
-
- Index
-
... ... @@ -1,0 +1,1 @@ 1 +13