Changes for page 13 Structure Mapping

Last modified by Helena K. on 2026/06/10 10:18

From 4.8 to 4.9 From 13.1 to 13.2

From version 4.9

edited by Helena K.
on 2025/06/16 14:50

Change comment: There is no comment for this version

To version 13.1

edited by Helena K.
on 2026/06/09 20:16

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 3 added, 0 removed)
Objects (0 modified, 1 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]
- SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

@@ -4,28 +4,28 @@
  == 13.1 Introduction ==
--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.
++The purpose of SDMX structure mapping is to transform datasets from one dimensionality to another. In practice, this means that the input and output datasets conform to different Data Structure Definition.
--Structure mapping does not alter the [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
++Structure mapping does not alter the observation values and is not intended to perform any aggregations or calculations.
--An input series (% style="color:#e74c3c" %)maps(%%) to:
++An input series maps to:
 . Exactly one output series; or
--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
--1. Zero output series where no source rule matches the input [[Component>>doc:sdmx:Glossary.Component.WebHome]] values.
++1. Multiple output series with different Series Keys, but the same observation values; or
++1. Zero output series where no source rule matches the input Component values.
  Typical use cases include:
  * Transforming received data into a common internal structure;
  * Transforming reported data into the data collector's preferred structure;
--* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
--* 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.
++* Transforming unidimensional datasets{{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
++* Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
  == 13.2 1-1 structure maps ==
--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.
++1-1 (pronounced 'one to one') mappings support the simple use case where the value of a Component in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept.
--In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary.Code.WebHome]] are (% style="color:#e74c3c" %)mapped(%%) to their ISO 3character equivalent.
++In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
  (% style="width:585.294px" %)
  |(% style="width:173px" %)**Country**|(% style="width:180px" %)**Alpha-2 code**|(% style="width:229px" %)**Alpha-3 code**
@@ -36,7 +36,7 @@
  |(% style="width:173px" %)Andorra|(% style="width:180px" %)AD|(% style="width:229px" %)AND
  |(% style="width:173px" %)etc…|(% style="width:180px" %) |(% style="width:229px" %)
--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]].
++Different source values can also map to the same target value, for example when deriving regions from country codes.
  (% style="width:490.294px" %)
  |(% style="width:260px" %)Source Component: REF_AREA|(% style="width:227px" %)Target Component: REGION
@@ -48,7 +48,7 @@
  == 13.3 N-n structure maps ==
--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.
++N-n (pronounced 'N to N') mappings describe rules where a specified combination of values in multiple source Components map to specified values in one or more target Components. For example, when mapping a partial Series Key from a highly multidimensional cube (like Balance of Payments) to a single 'Indicator' Dimension in a target Data Structure.
  Example:
@@ -126,19 +126,19 @@
  COMP_ORG=34
  )))|(% style="width:397px" %)XM:A:N
--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.
++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, for the same period in time.
  == 13.5 Representation maps ==
--[[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.
++Representation Maps replace the SDMX 2.1 Codelist Maps and are used describe explicit mappings between source and target Component values.
--The source and target of a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%) can reference any of the following:
++The source and target of a Representation Map can reference any of the following:
 . Codelist
 . Free Text (restricted by type, e.g String, Integer, Boolean)
 . Valuelist
--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:
++A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form:
  (% style="width:356.294px" %)
  |(% style="width:167px" %)CL_ISO_ALPHA2|(% style="width:186px" %)CL_ISO_ALPHA3
@@ -149,7 +149,7 @@
  |(% style="width:167px" %)AD|(% style="width:186px" %)AND
  |(% style="width:167px" %)etc…|(% style="width:186px" %)
--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:
++A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
  (% style="width:364.294px" %)
  |(% style="width:169px" %)Text|(% style="width:192px" %)CL_ISO_ALPHA2
@@ -161,9 +161,9 @@
  |(% style="width:169px" %)"Eire"|(% style="width:192px" %)IE
  |(% style="width:169px" %)etc…|(% style="width:192px" %)
--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.
++Valuelists, introduced in SDMX 3.0, are equivalent to Codelists but allow the maintenance of non-SDMX identifiers. Importantly, their IDs do not need to conform to IDType, but as a consequence are not Identifiable.
--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.
++When used in Representation Maps, Valuelists allow Non-SDMX identifiers containing characters like £, $, % to be mapped to Code IDs, or Codes mapped to non-SDMX identifiers.
  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:
@@ -173,17 +173,17 @@
  |(% style="width:126px" %)%|(% style="width:133px" %)En|(% style="width:173px" %)Percentage
  |(% style="width:126px" %) |(% style="width:133px" %)fr|(% style="width:173px" %)Pourcentage
--Other characteristics of [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Maps(%%):
++Other characteristics of Representation Maps:
--* 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;
--* 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
--* 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.
++* Support the mapping of multiple source Component values to multiple Target Component values as described in section 13.3 on n-to-n mappings; this covers also the case of mapping an Attribute with an array representation to map combinations of values to a single target value;
++* 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
++* Support for mapping rules where regular expressions or substrings are used to match source Component values. Refer to section 13.6 for more on this topic.
  == 13.6 Regular expression and substring rules ==
--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.
++It is common for classifications to contain meanings within the identifier, for example the code Id 'XULADS' may refer to a particular seasonality because it starts with the letters XU.
--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:
++With SDMX 2.1 each code that starts with XU had to be individually mapped to the same seasonality, and additional mappings added when new Codes 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:
  //If starts with 'XU' map to 'Y'//
@@ -191,9 +191,9 @@
  === 13.6.1 Regular expressions ===
--Regular expression mapping rules are defined in the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Map.
++Regular expression mapping rules are defined in the Representation Map.
--Below is an example set of regular expression rules for a particular [[component>>doc:sdmx:Glossary.Component.WebHome]].
++Below is an example set of regular expression rules for a particular component.
  (% style="width:664.294px" %)
  |(% style="width:141px" %)**Regex**|(% style="width:362px" %)**Description**|(% style="width:158px" %)**Output**
@@ -201,7 +201,7 @@
  |(% style="width:141px" %)^[A-G]|(% style="width:362px" %)Rule match if the input starts with letters A to G|(% style="width:158px" %)OUT_B
  |(% style="width:141px" %)A~|B|(% style="width:362px" %)Rule match if input is either 'A' or 'B'|(% style="width:158px" %)OUT_C
--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]].
++Like all mapping rules, the output is either a Code, a Value or free text depending on the representation of the Component in the target Data Structure Definition.
  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
@@ -225,7 +225,7 @@
  The input 'G' matches on the last rule which is used as a catch-all or default in this example.
--=== 13. Substrings ===
++=== 13.6.2 Substrings ===
  Substrings provide an alternative to regular expressions where the required section of an input value can be described using the number of the starting character, and the length of the substring in characters. The first character is at position 1.
@@ -236,7 +236,7 @@
  |(% style="width:169px" %)ABC_DEF_XYZ|(% style="width:147px" %)5|(% style="width:133px" %)3|(% style="width:171px" %)DEF
  |(% style="width:169px" %)XULADS|(% style="width:147px" %)1|(% style="width:133px" %)2|(% style="width:171px" %)XU
--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:
++Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example:
  (% style="width:628.294px" %)
  |(% style="width:163px" %)Start|(% style="width:158px" %)Length|(% style="width:128px" %)Source|(% style="width:176px" %)Target
@@ -244,7 +244,7 @@
  == 13.7 Mapping non-SDMX time formats to SDMX formats ==
--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.
++Structure mapping allows non-SDMX compliant time values in source datasets to be mapped to an SDMX compliant time format.
  Two types of time input are defined:
@@ -251,7 +251,7 @@
  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
  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.
--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:
++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 or Attribute in the output mapping. If the output frequency is unknown or if the SDMX 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:
  |Frequency|Format|Example
  |A|YYYY|2010
@@ -271,14 +271,14 @@
  There are two important points to note:
--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.
--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.
++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 is formatted.
++1. To support the use case of changing frequency the structure map can optionally provide a start of year attribute, which defines the year start date in MM-DD format. For example: YearStart=04-01.
  === 13.7.1 Pattern based dates ===
--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.
++Date and time formats 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 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.
--Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale{{footnote}} A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}. An indicative list of examples is presented in the following table:
++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:
  (% style="width:604.294px" %)
  |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU
@@ -311,56 +311,53 @@
  Examples
 /06/1981 would be described as dd/MM/YYYY, with locale en-GB
--
 -mars-12 would be described as YYYY-MMM-DD, with locale fr-FR
--
 July 1981 would be described as dd MMMM YYYY, with locale en-US
--
 Jul 1981 would be described as dd MMM YYYY
--
 D62 would be described as YYYYDnn (day 62 of the year 2010)
  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
--|Letter|Date or Time Component|Presentation|Examples
--|G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
--|yy|Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
--|yyyy|Year Full (upper case is Year of Week)|Year|1996
--|MM|Month number in year starting with 1|Month|07
--|MMM|Month name short|Month|Jul
--|MMMM|Month name full|Month|July
--|ww|Week in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|27
--|W|Week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
--|DD|Day in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|189
--|dd|Day in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|10
--|F|Day of week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
--|E|Day name in week|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|Tuesday; Tue
--|U|Day number of week (1 = Monday, ..., 7 = Sunday)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|1
--|HH|Hour in day (0-23)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
--|kk|Hour in day (1-24)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|24
--|KK|Hour in am/pm (0-11)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
--|hh|Hour in am/pm (1-12)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
--|mm|Minute in hour|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|30
--|ss|Second in minute|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|55
--|S|Millisecond|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|978
--|n|(((
++(% style="width:850.294px" %)
++|(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
++|(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
++|(% 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
++|(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
++|(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
++|(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
++|(% style="width:125px" %)MMMM|(% style="width:385px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
++|(% style="width:125px" %)ww|(% style="width:385px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
++|(% style="width:125px" %)W|(% style="width:385px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
++|(% style="width:125px" %)DD|(% style="width:385px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
++|(% style="width:125px" %)dd|(% style="width:385px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
++|(% style="width:125px" %)F|(% style="width:385px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
++|(% style="width:125px" %)E|(% style="width:385px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
++|(% style="width:125px" %)U|(% style="width:385px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
++|(% style="width:125px" %)HH|(% style="width:385px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
++|(% style="width:125px" %)kk|(% style="width:385px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
++|(% style="width:125px" %)KK|(% style="width:385px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
++|(% style="width:125px" %)hh|(% style="width:385px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
++|(% style="width:125px" %)mm|(% style="width:385px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
++|(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
++|(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
++|(% style="width:125px" %)n|(% style="width:385px" %)(((
  Number of periods, used after a SDMX
--
  Frequency Identifier such as M, Q, D (month, quarter, day)
--)))|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
++)))|(% style="width:180px" %)Number|(% style="width:157px" %)12
  The model is illustrated below:
++(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png]]
--
  **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?**
++(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png]]
++(% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
++**Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
--==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ====
++=== 13.7.2 Numerical based datetime ===
--=== 13.3.6 Numerical based datetime ===
--
  Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid SDMX Time Period, and the **Period** which must take one of the following enumerated values:
  * day
@@ -369,75 +369,63 @@
  * microsecond
  * nanosecond
--|Numerical datetime systems|Base|Period
--|(((
++(% style="width:545.294px" %)
++|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
++|(% style="width:268px" %)(((
  Epoch Time (UNIX)
--
  Milliseconds since 01 Jan 1970
--)))|1970|millisecond
--|(((
++)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
++|(% style="width:268px" %)(((
  Windows System Time
--
  Milliseconds since 01 Jan 1601
--)))|1601|millisecond
++)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
  The model is illustrated below:
--[[image:1750072341491-790.jpeg]]
++(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png]]
--**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
++**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 **
--==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
++=== 13.7.3 Mapping more complex time inputs ===
--=== Mapping more complex time inputs ===
--
  VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
--== Using TIME_PERIOD in mapping rules ==
++== 13.8 Using TIME_PERIOD in mapping rules ==
  The source TIME_PERIOD Dimension can be used in conjunction with other input Dimensions to create discrete mapping rules where the output is conditional on the time period value.
  The main use case is setting the value of Observation Attributes in the target dataset.
--|Rule|Source|Target
--|1|(((
++(% style="width:709.294px" %)
++|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
++|(% style="width:103px" %)1|(% style="width:405px" %)(((
  If
--
  INDICATOR=XULADS; and TIME_PERIOD=2007.
--)))|(((
--Set
--
--OBS_CONF=F
++)))|(% style="width:198px" %)(((
++Set OBS_CONF=F
  )))
--|2|(((
++|(% style="width:103px" %)2|(% style="width:405px" %)(((
  If
--
  INDICATOR=XULADS; and TIME_PERIOD=2008.
--)))|Set OBS_CONF=F
--|3|(((
++)))|(% style="width:198px" %)Set OBS_CONF=F
++|(% style="width:103px" %)3|(% style="width:405px" %)(((
  If
--
  INDICATOR=XULADS; and TIME_PERIOD=2009.
--)))|(((
--Set
--
--OBS_CONF=F
++)))|(% style="width:198px" %)(((
++Set OBS_CONF=F
  )))
--|4|(((
++|(% style="width:103px" %)4|(% style="width:405px" %)(((
  If
--
  INDICATOR=XULADS; and TIME_PERIOD=2010.
--)))|(((
--Set
--
--OBS_CONF=**C**
++)))|(% style="width:198px" %)(((
++Set OBS_CONF=**C**
  )))
  In the example above, OBS_CONF is an Observation Attribute.
--== 13. Time span mapping rules using validity periods ==
++== 13.9 Time span mapping rules using validity periods ==
  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.
@@ -445,25 +445,22 @@
  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
--|Rule|Source|Target
--|1|(((
++(% style="width:516.294px" %)
++|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
++|(% style="width:74px" %)1|(% style="width:215px" %)(((
  If
--
  INDICATOR=XULADS.
--
--
--Validity Period start period=2007 end period=2009
--)))|Set OBS_CONF=F
--|2|(((
++Validity Period
++start period=2007
++end period=2009
++)))|(% style="width:223px" %)Set OBS_CONF=F
++|(% style="width:74px" %)2|(% style="width:215px" %)(((
  If
--
  INDICATOR=XULADS.
--
--
--Validity Period start period=2010
--)))|(((
++Validity Period
++start period=2010
++)))|(% style="width:223px" %)(((
  Set
--
  OBS_CONF=F
  )))
@@ -471,132 +471,121 @@
  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.
--== 13. Mapping examples ==
++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.
--=== 13. Many to one mapping (N-1) ===
++== 13.10 Mapping examples ==
--|Source|Map To
--|(((
--**FREQ**="A"
++=== 13.10.1 Many to one mapping (N3513 -1) ===
++(% style="width:542.294px" %)
++|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
++|(% style="width:274px" %)(((
++(% style="color:#8e44ad" %)**FREQ**="A"
  ADJUSTMENT="N"
--
  **REF_AREA**="PL"
--
  **COUNTERPART_AREA**="W0"
--
  REF_SECTOR="S1"
--
  COUNTERPART_SECTOR="S1"
--
  ACCOUNTING_ENTRY="B"
--
  STO="B5G"
--)))|(((
--FREQ="A"
--
++)))|(% style="width:265px" %)(((
++(% style="color:#8e44ad" %)FREQ="A"
  REF_AREA="PL"
--
  COUNTERPART_AREA="W0"
--INDICATOR="IND_ABC"
++INDICATOR="IND_ABC"(%%)
  )))
  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
--FREQ => FREQ
++> FREQ => FREQ
++> REF_AREA=> REF_AREA
++> COUNTERPART_AREA=> COUNTERPART _AREA
--REF_AREA=> REF_AREA
--
--COUNTERPART_AREA=> COUNTERPART _AREA
--
  No Representation Mapping is required. The source value simply copies across unmodified.
  The remaining Dimensions all map to the Indicator Dimension. This is an example of many Dimensions mapping to one Dimension. In this case a Representation Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target indicator:
--N:S1:S1:B:B5G => IND_ABC
++> N:S1:S1:B:B5G => IND_ABC
  Where the key sequence is based on the order specified in the mapping (i.e ADJUSTMENT, REF_SECTOR, etc will result in the first value N being taken from ADJUSTMENT as this was the first item in the source Dimension list.
  **Note**: The key order is NOT based on the Dimension order of the DSD, as the mapping needs to be resilient to the DSD changing.
--1.
--11.
--111. Mapping other data types to Code Id
++=== 13.10.2 Mapping other data types to Code Id ===
  In the case where the incoming data type is not a string and not a code identifier i.e. the source Dimension is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
  The following representation mapping can be used to explicitly map each age to an output code.
--|Source Input Free Text|Desired Output Code Id
--|0|A
--|1|A
--|2|A
--|3|B
--|4|B
++(% style="width:402.294px" %)
++|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id**
++|(% style="width:197px" %)0|(% style="width:204px" %)A
++|(% style="width:197px" %)1|(% style="width:204px" %)A
++|(% style="width:197px" %)2|(% style="width:204px" %)A
++|(% style="width:197px" %)3|(% style="width:204px" %)B
++|(% style="width:197px" %)4|(% style="width:204px" %)B
  If this mapping takes advantage of regular expressions it can be expressed in two rules:
++(% style="width:336.294px" %)
++|(% style="width:182px" %)**Regular Expression**|(% style="width:151px" %)**Desired Output**
++|(% style="width:182px" %)[0-2]|(% style="width:151px" %)A
++|(% style="width:182px" %)[3-4]|(% style="width:151px" %)B
--Regular Expression        Desired Output
++=== 13.10.3 Observation Attributes for Time Period ===
--|[0-2]|A
--|[3-4]|B
--
--=== 13. Observation Attributes for Time Period ===
--
  This use case is where a specific observation for a specific time period has an attribute value.
--|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
--|XULADS|2008|C
--|XULADS|2009|C
--|XULADS|2010|C
++(% style="width:621.294px" %)
++|(% style="width:201px" %)Input INDICATOR|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF
++|(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C
++|(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C
++|(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C
  Or using a validity period on the Representation Mapping:
--Input INDICATOR                    Valid From/ Valid To             Output OBS_CONF
++(% style="width:629.294px" %)
++|(% style="width:202px" %)Input INDICATOR|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF
++|(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С
--XULADS                                  2008/2010                             C
++=== 13.10.4 Time mapping ===
--=== 13.  Time mapping ===
--
  This use case is to create a time period from an input that does not respect SDMX Time Formats.
  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
--|Source Value|Source Mapping|Target Frequency|Output
--|18/07/1981|dd/MM/yyyy|A|1981
++(% style="width:652.294px" %)
++|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output
++|(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981
  When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD.
--Source Value             Source Mapping           Target       Frequency Output
++(% style="width:658.294px" %)
++|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source Mapping|(% style="width:176px" %)Target Dimension|(% style="width:173px" %)Frequency Output
++|(% 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)
--Dimension
++ When the source is a numerical format.
--|18/07/1981                dd/MM/yyyy                  FREQ| |1981-07-18 (when FREQ=D)
--| When the source is a numerical format| |
--|Source Value              Start Period        Interval|(((
--Target
++(% style="width:658.294px" %)
++|(% style="width:143px" %)Source Value|(% style="width:163px" %) Start Period|(% style="width:176px" %)Interval|(% style="width:176px" %)Target FREQ|(% style="width:173px" %) Output
++|(% style="width:143px" %)1589808220|(% style="width:163px" %)1970|(% style="width:176px" %) millisecond|(% style="width:176px" %)M|(% style="width:173px" %)2020-05
--FREQ
--)))|Output
--|1589808220               1970                   millisecond|M|2020-05
--
  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:
--                      Source Value          Source Mapping           Target       Frequency Output
++(% style="width:666.294px" %)
++|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
++|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1981-12-31
--Dimension
--
--                      1981                       yyyy                               D – End of Period        1981-12-31
--
--
  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
--                      Source Value          Source Mapping           Target       Frequency Output
++(% style="width:666.294px" %)
++|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
++|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1982-03-31
--Dimension
--
  ----
++(% contenteditable="false" tabindex="-1" %)
++(((
  {{putFootnotes/}}
++)))

1750074822764-573.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.arturkryazhev

Size

...	...	@@ -1,0 +1,1 @@
	1	+25.1 KB

Content

1750074865924-797.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.arturkryazhev

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.8 KB

Content

1750074994887-415.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.arturkryazhev

Size

...	...	@@ -1,0 +1,1 @@
	1	+12.4 KB

Content

SUZ.Methodology.Code.MethodologyClass[0]

SKMS.Methodology.Code.MethodologyClass[0]

Index

...	...	@@ -1,0 +1,1 @@
	1	+13