Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.21
edited by Helena
on 2025/06/16 13:26
Change comment: There is no comment for this version
To version 1.23
edited by Helena
on 2025/06/16 13:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -256,19 +256,14 @@
256 256  At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
257 257  
258 258  * The set of SDMX observations having the same values for all the Dimensions except than the MeasureDimension become one multi-measure VTL Data Point, having one Measure for each Code Cj of the SDMX MeasureDimension;
259 -* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple)
260 -
261 -Identifiers, (time) Identifier and Attributes.
262 -
259 +* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple) Identifiers, (time) Identifier and Attributes.
263 263  * The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
264 264  * For the SDMX DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Attribute DA_Cj
265 265  
266 266  ==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
267 267  
268 -* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain
265 +* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain Attributes.
269 269  
270 -Attributes.
271 -
272 272  The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final VTL components, which according to the Basic and Pivot methods would have had the role of Attribute, assume instead the role of Measure.
273 273  
274 274  Proper VTL features allow changing the role of specific attributes even after the SDMX to VTL mapping: they can be useful when only some of the DataAttributes need to be managed as VTL Measures.
... ... @@ -285,11 +285,12 @@
285 285  
286 286  Mapping table:
287 287  
288 -|**VTL**|**SDMX**
289 -|(Simple) Identifier|Dimension
290 -|(Time) Identifier|TimeDimension
291 -|Measure|Measure
292 -|Attribute|DataAttribute
283 +(% style="width:470.294px" %)
284 +|(% style="width:262px" %)**VTL**|(% style="width:205px" %)**SDMX**
285 +|(% style="width:262px" %)(Simple) Identifier|(% style="width:205px" %)Dimension
286 +|(% style="width:262px" %)(Time) Identifier|(% style="width:205px" %)TimeDimension
287 +|(% style="width:262px" %)Measure|(% style="width:205px" %)Measure
288 +|(% style="width:262px" %)Attribute|(% style="width:205px" %)DataAttribute
293 293  
294 294  If the distinction between simple identifier and time identifier is not maintained in the VTL environment, the classification between Dimension and TimeDimension exists only in SDMX, as declared in the relevant DataStructureDefinition.
295 295