Changes for page 9 Structure Map

Last modified by Helena K. on 2026/06/08 17:16

From version 18.7
edited by Helena K.
on 2026/06/08 17:15
Change comment: There is no comment for this version
To version 18.6
edited by Helena K.
on 2026/06/08 17:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -40,9 +40,9 @@
40 40  
41 41  The EpochMap and DatePatternMap are both //IdentifiableArtefact//. An EpochMap and DatePatternMap both provide the ability to map source to target date formats. The EpochMap describes the source date as the number of epochs since a point in time, where the duration of each epoch is defined, e.g., number of milliseconds since 1970. The DatePatternMap describes the source date as a pattern for example MM-YYYY, accompanied by the appropriate locale.
42 42  
43 -Both mappings describe the target date as a frequency Identifier. The frequency identifier is given either a fixed value, e.g., ‘A’ or a reference to a [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] or [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] in the target DataStructureDefinition of the StructureMap, e.g. ‘FREQ’. In the latter case, the frequency id is derived at run time when the output [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] and observations are generated. Dates mapped using the frequency lookup can therefore be mapped using different frequencies depending on the [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] or observation being converted.
43 +Both mappings describe the target date as a frequency Identifier. The frequency identifier is given either a fixed value, e.g., ‘A’ or a reference to a Dimension or Attribute in the target DataStructureDefinition of the StructureMap, e.g. ‘FREQ’. In the latter case, the frequency id is derived at run time when the output series and observations are generated. Dates mapped using the frequency lookup can therefore be mapped using different frequencies depending on the series or observation being converted.
44 44  
45 -If the Frequency Identifier aligns with standard [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] frequencies the output date format can be derived using standard [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] date formatting (e.g., A=YYYY, Q=YYYY-Qn). If the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] standard formatting is not desired or if the frequency Id is not a standard [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] frequency [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], the FrequencyFormatMapping can be used to describe the relationship between the frequency Id and the output date format, e.g., A01=YYYY.
45 +If the Frequency Identifier aligns with standard SDMX frequencies the output date format can be derived using standard SDMX date formatting (e.g., A=YYYY, Q=YYYY-Qn). If the SDMX standard formatting is not desired or if the frequency Id is not a standard SDMX frequency Code, the FrequencyFormatMapping can be used to describe the relationship between the frequency Id and the output date format, e.g., A01=YYYY.
46 46  
47 47  ==== 9.1.4.2 Definitions ====
48 48  
© Semantic R&D Group, 2026