Skip to Content

Changes for page 9 Structure Map

Last modified by Artur on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/06/08 11:48
Change comment: There is no comment for this version
To version 3.3
edited by Helena
on 2025/06/08 11:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -34,9 +34,9 @@
34 34  
35 35  **Figure 38: Relationship Class diagram of the EpochMap and DatePatternMap**
36 36  
37 -=== 9.1.4 Explanation of the Diagram ===
37 +==== 9.1.4 Explanation of the Diagram ====
38 38  
39 -==== 9.1.4.1 Narrative ====
39 +===== 9.1.4.1 Narrative =====
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  
... ... @@ -44,7 +44,7 @@
44 44  
45 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 -==== 9.1.4.2 Definitions ====
47 +===== 9.1.4.2 Definitions =====
48 48  
49 49  (% style="width:974.835px" %)
50 50  |**Class**|(% style="width:197px" %)**Feature**|(% style="width:568px" %)**Description**