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

Summary

Details

Page properties
Content
... ... @@ -206,12 +206,11 @@
206 206  
207 207  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:
208 208  
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
209 +|**SDMX**|**VTL**
210 +|Dimension|(Simple) Identifier
211 +|TimeDimension|(Time) Identifier
212 +|Measure|Measure
213 +|DataAttribute|Attribute
215 215  
216 216  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).
217 217