Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.3
edited by Helena
on 2025/05/17 00:31
Change comment: There is no comment for this version
To version 7.5
edited by Helena
on 2025/05/17 00:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -412,29 +412,27 @@
412 412  
413 413  [[image:1747388275998-621.png]]
414 414  
415 -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}}
415 +In fact the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “sub” has exactly the same behaviour. Therefore, (% style="color:#2ecc71" %)mapping(%%) different parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] in the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] through the ordered concatenation notation is equivalent to a proper use of the operator “**sub**” on such a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]].{{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}}
416 416  
417 -In the direction from SDMX to VTL it is allowed to omit the value of one or more
417 +In the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] it is allowed to omit the value of one or more DimensionComponents on which the (% style="color:#2ecc71" %)mapping(%%) is based, but maintaining all the separating dots (therefore it may happen to find two or more consecutive dots and dots in the beginning or in the end). The absence of value means that for the corresponding [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] all the values are kept and the [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] is not dropped.
418 418  
419 -DimensionComponents on which the mapping is based, but maintaining all the separating dots (therefore it may happen to find two or more consecutive dots and dots in the beginning or in the end). The absence of value means that for the corresponding Dimension all the values are kept and the Dimension is not dropped.
419 +For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
420 420  
421 -For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
421 +This is equivalent to the application of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] “sub” operator only to the identifier //INDICATOR//:
422 422  
423 -This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
424 -
425 425  [[image:1747388244829-693.png]]
426 426  
427 427  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
428 428  
429 -Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different
427 +Heterogeneous invocations of the same [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are allowed, i.e. omitting different
430 430  
431 431  Dimensions in different invocations.
432 432  
433 -Let us now analyse __the mapping direction from VTL to SDMX__.
431 +Let us now analyse __the mapping direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]__.
434 434  
435 -In this situation, distinct parts of a SDMX Dataflow are calculated as distinct VTL datasets, under the constraint that they must have the same VTL data structure.
433 +In this situation, distinct parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are calculated as distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]], under the (% style="color:#2ecc71" %)constraint(%%) that they must have the same [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure.
436 436  
437 -For example, let us assume that the VTL programmer wants to calculate the SDMX
435 +For example, let us assume that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programmer wants to calculate the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
438 438  
439 439  Dataflow DF2(1.0.0) having the Dimensions TIME_PERIOD, INDICATOR, and COUNTRY and that such a programmer finds it convenient to calculate separately the parts of DF2(1.0.0) that have different combinations of values for INDICATOR and COUNTRY:
440 440