Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.23
edited by Helena
on 2025/05/16 09:00
Change comment: There is no comment for this version
To version 5.22
edited by Helena
on 2025/05/16 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -580,10 +580,8 @@
580 580  
581 581  Therefore, it is important to be aware that some VTL operations (for example the binary operations at data set level) are consistent only if the components having the same names in the operated VTL Data Sets have also the same representation (i.e. the same Value Domain as for VTL). For example, it is possible to obtain correct results from the VTL expression
582 582  
583 -DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
583 +DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets) if the matching components in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general representation. In simpler words, DS_a and DS_b must use the same values/codes (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
584 584  
585 -if the matching components in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general representation. In simpler words, DS_a and DS_b must use the same values/codes (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
586 -
587 587  As mentioned, the property above is not enforced by construction in SDMX, and different representations of the same Concept can be not compatible one another (for example, it may happen that geo_area is represented by ISO-alpha-3 codes in DS_a and by ISO alpha-2 codes in DS_b). Therefore, it will be up to the definer of VTL
588 588  
589 589  Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.