Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 6.9
edited by Helena
on 2025/05/16 12:37
Change comment: There is no comment for this version
To version 6.8
edited by Helena
on 2025/05/16 12:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -414,8 +414,13 @@
414 414  
415 415  It should be noted that the desired VTL Data Sets (i.e. of the kind ‘DF1(1.0.0)/// INDICATORvalue//.//COUNTRYvalue//’) can be obtained also by applying the VTL operator “**sub**” (subspace) to the Dataflow DF1(1.0.0), like in the following VTL expression:
416 416  
417 -[[image:1747388275998-621.png]]
417 +‘DF1(1.0.0)/POPULATION.USA’ :=
418 +DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
418 418  
420 +‘DF1(1.0.0)/POPULATION.CANADA’ :=
421 +DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
422 +… … …
423 +
419 419  In fact the VTL operator “sub” has exactly the same behaviour. Therefore, mapping different parts of a SDMX Dataflow to different VTL Data Sets in the direction from SDMX to VTL through the ordered concatenation notation is equivalent to a proper use of the operator “**sub**” on such a Dataflow.{{footnote}}In case the ordered concatenation notation is used, the VTL Transformation described above, e.g. ‘DF1(1.0)/POPULATION.USA’ := DF1(1.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA”], is implicitly executed. In order to test the overall compliance of the VTL program to the VTL consistency rules, it has to be considered as part of the VTL program even if it is not explicitly coded.{{/footnote}}
420 420  
421 421  In the direction from SDMX to VTL it is allowed to omit the value of one or more
1747388275998-621.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content