Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.17
edited by Helena
on 2025/06/16 13:20
Change comment: There is no comment for this version
To version 1.19
edited by Helena
on 2025/06/16 13:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -80,9 +80,9 @@
80 80  
81 81  For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
82 82  
83 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
83 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
86 86  
87 87  === 12.2.3 Abbreviation of the URN ===
88 88  
... ... @@ -110,51 +110,47 @@
110 110  
111 111  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
112 112  
113 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
113 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
114 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
115 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
114 114  
115 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
116 -
117 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
118 -
119 119  by omitting all the non-essential parts would become simply:
120 120  
121 -DFR := DF1 + DF2
119 +> DFR  : =  DF1 + DF2
122 122  
123 123  The references to the Codelists can be simplified similarly. For example, given the non-abbreviated reference to the Codelist AG:CL_FREQ(1.0.0), which is{{footnote}}Single quotes are needed because this reference is not a VTL regular name. 19 Single quotes are not needed in this case because CL_FREQ is a VTL regular name.{{/footnote}}:
124 124  
125 -'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
123 +> 'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
126 126  
127 127  if the Codelist is referenced from a RulesetScheme belonging to the agency AG, omitting all the optional parts, the abbreviated reference would become simply^^19^^:
128 128  
129 -CL_FREQ
127 +> CL_FREQ
130 130  
131 131  As for the references to the components, it can be enough to specify the componentId, given that the dataStructure-Id can be omitted. An example of non-abbreviated reference, if the data structure is DST1 and the component is SECTOR, is the following:
132 132  
133 -'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S
131 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S ECTOR'
134 134  
135 -ECTOR'
136 -
137 137  The corresponding fully abbreviated reference, if made from a TransformationScheme belonging to AG, would become simply:
138 138  
139 -SECTOR
135 +> SECTOR
140 140  
141 141  For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as{{footnote}}The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC{{/footnote}}:
142 142  
143 -'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
139 +> 'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
144 144  
145 145  In the references to the Concepts, which can exist for example in the definition of the VTL Rulesets, at least the conceptScheme-id and the concept-id must be specified.
146 146  
147 147  An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
148 148  
149 -'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
145 +> 'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
150 150  
151 151  The corresponding fully abbreviated reference, if made from a RulesetScheme belonging to AG, would become simply:
152 152  
153 -CS1(1.0.0).SECTOR
149 +> CS1(1.0.0).SECTOR
154 154  
155 155  The Codes and in general all the Values can be written without any other specification, for example, the transformation to check if the values of the measures of the Dataflow DF1 are between 0 and 25000 can be written like follows:
156 156  
157 -'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
153 +> 'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
158 158  
159 159  The artefact (Component, Concept, Codelist …) which the Values are referred to can be deduced from the context in which the reference is made, taking also into account the VTL syntax. In the Transformation above, for example, the values 0 and 2500 are compared to the values of the measures of DF1(1.0.0).
160 160  
... ... @@ -210,11 +210,12 @@
210 210  
211 211  When transforming **from SDMX to VTL**, this method consists in leaving the components unchanged and maintaining their names and roles, according to the following table:
212 212  
213 -|**SDMX**|**VTL**
214 -|Dimension|(Simple) Identifier
215 -|TimeDimension|(Time) Identifier
216 -|Measure|Measure
217 -|DataAttribute|Attribute
209 +(% style="width:468.294px" %)
210 +|(% style="width:196px" %)**SDMX**|(% style="width:269px" %)**VTL**
211 +|(% style="width:196px" %)Dimension|(% style="width:269px" %)(Simple) Identifier
212 +|(% style="width:196px" %)TimeDimension|(% style="width:269px" %)(Time) Identifier
213 +|(% style="width:196px" %)Measure|(% style="width:269px" %)Measure
214 +|(% style="width:196px" %)DataAttribute|(% style="width:269px" %)Attribute
218 218  
219 219  The SDMX DataAttributes, in VTL they are all considered "at data point / observation level" (i.e. dependent on all the VTL Identifiers), because VTL does not have the SDMX AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, dimension or set or group of dimensions, whole data set).
220 220