Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 2.4
edited by Helena K.
on 2026/01/27 13:39
Change comment: There is no comment for this version
To version 2.2
edited by Helena K.
on 2026/01/27 13:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,7 @@
17 17  |Contribution to growth over 1 year (quarterly data)|Contribution to growth|4|Q
18 18  |Contribution to growth over 1 year (annual data)|Contribution to growth|1|A
19 19  |3 months moving average|Moving average|3|M
20 -|Annual index (reference year=100){{footnote}}Note that for the case of an index, it is useful to specify the reference base period in an additional attribute (see concept BASE_PER specified in the SDMX Glossary).{{/footnote}}|Index|1|A
20 +|Annual index (reference year=100)[[~[1~]>>path:#_ftn1]]|Index|1|A
21 21  
22 22  This guideline describes two methods that may be used to code a time transformation:
23 23  
... ... @@ -26,7 +26,7 @@
26 26  
27 27  Both of these methods are included as separate use cases as served by each method. The aim of this document is to demonstrate that guidance and a standard approach is available and promoted for each use case. The use cases are described in the related sections.
28 28  
29 -Further recommended code values for expressing general statistical concepts such as "not applicable", etc., can be found in section “Generic codes” of the "Guidelines for the creation and management of SDMX Cross-Domain Code Lists" (to be found under “Guidelines” on the official SDMX website{{footnote}}http://sdmx.org/{{/footnote}}).
29 +Further recommended code values for expressing general statistical concepts such as "not applicable", etc., can be found in section “Generic codes” of the "Guidelines for the creation and management of SDMX Cross-Domain Code Lists" (to be found under “Guidelines” on the official SDMX website[[~[2~]>>path:#_ftn2]]).
30 30  
31 31  = 2. SDMX Concepts for Time Transformations =
32 32  
... ... @@ -104,7 +104,7 @@
104 104  
105 105  **Example:**
106 106  
107 -The formula for a simple annual growth rate can be expressed as follows:{{footnote}}Note: often growth rates are expressed as percentage growth, in which case the value is multiplied with 100%. This is however not relevant for this guideline and is left out for simplicity.{{/footnote}}
107 +The formula for a simple annual growth rate can be expressed as follows:[[~[3~]>>path:#_ftn3]]
108 108  
109 109  //GT= VT-VT-PVT-P//[[image:file:///C:/Users/axyli/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
110 110  
... ... @@ -165,8 +165,7 @@
165 165  
166 166  In case the mixed frequencies or complex transformations as outlined above are needed in a simpler way and normalisation does not need to be strictly enforced, a composite code list CL_TIMETRANS may be created.
167 167  
168 -The number of periods in the code follows the frequency of the series unless stated otherwise. Example: code G3Y refers to a three-year growth rate, irrespective of the series frequency. For complex transformations, the codes that would be used for the respective transformations can be concatenated and separated by an underscore{{footnote}}Example:
169 -G1_C4 Growth rate, period on period, over 4-period cumulated sum{{/footnote}}.
168 +The number of periods in the code follows the frequency of the series unless stated otherwise. Example: code G3Y refers to a three-year growth rate, irrespective of the series frequency. For complex transformations, the codes that would be used for the respective transformations can be concatenated and separated by an underscore[[~[4~]>>path:#_ftn4]].
170 170  
171 171  Example for composite CL_TIMETRANS:
172 172  
... ... @@ -226,7 +226,7 @@
226 226  
227 227  The table below shows coding example using all 3 options lined out above.
228 228  
229 -|Statement|Normalised{{footnote}}For sake of readability the prefix TIMETRANS_ was not put in the table. The concepts are in fact called TIMETRANS_TYPE and TIMETRANS_PER.{{/footnote}}|Type+Period|Type+Period+Freq
228 +|Statement|Normalised[[(% class="wikiinternallink wikiinternallink" %)**~[5~]**>>path:#_ftn5]]|Type+Period|Type+Period+Freq
230 230  |Level series (non transformed data)|(((
231 231  FREQ=A or Q or M …
232 232  
... ... @@ -322,4 +322,16 @@
322 322  
323 323  ----
324 324  
325 -{{putFootnotes/}}
324 +[[~[1~]>>path:#_ftnref1]] Note that for the case of an index, it is useful to specify the reference base period in an additional attribute (see concept BASE_PER specified in the SDMX Glossary).
325 +
326 +[[~[2~]>>path:#_ftnref2]] [[http:~~/~~/sdmx.org/>>url:http://sdmx.org/]]
327 +
328 +[[~[3~]>>path:#_ftnref3]] Note: often growth rates are expressed as percentage growth, in which case the value is multiplied with 100%. This is however not relevant for this guideline and is left out for simplicity.
329 +
330 +[[~[4~]>>path:#_ftnref4]] Example:
331 +
332 +|**G1_C4**|Growth rate, period on period, over 4-period cumulated sum
333 +
334 +
335 +
336 +[[~[5~]>>path:#_ftnref5]] For sake of readability the prefix **TIMETRANS_ **was not put in the table. The concepts are in fact called **TIMETRANS_TYPE** and **TIMETRANS_PER**.
© Semantic R&D Group, 2026