Changes for page 12 Validation and Transformation Language (VTL)
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
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 ... ... @@ -477,30 +477,38 @@ 477 477 478 478 With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered: 479 479 480 -(% style="width: 895.294px" %)481 -| (% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**482 -| (% style="width:278px" %)**Data Set Component**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}483 -| (% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((485 +(% style="width:1170.29px" %) 486 +|**VTL**|(% style="width:754px" %)**SDMX** 487 +|**Data Set Component**|(% style="width:754px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}} 488 +|**Represented Variable**|(% style="width:754px" %)((( 484 484 **Concept** with a definite 485 485 486 486 Representation 487 487 ))) 488 -|(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)((( 489 -**Representation** (see the Structure Pattern in the Base Package) 493 +|**Value Domain**|(% style="width:754px" %)((( 494 +**Representation** (see the Structure 495 + 496 +Pattern in the Base Package) 490 490 ))) 491 -|(% style="width:278px" %)**Enumerated Value Domain / 492 -Code List**|(% style="width:613px" %)**Codelist** 493 -|(% style="width:278px" %)**Code**|(% style="width:613px" %)((( 494 -**Code** (for enumerated DimensionComponent, Measure, DataAttribute) 498 +|**Enumerated Value Domain / Code List**|(% style="width:754px" %)**Codelist** 499 +|**Code**|(% style="width:754px" %)((( 500 +**Code** (for enumerated 501 + 502 +DimensionComponent, Measure, DataAttribute) 495 495 ))) 496 -|(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)((( 497 -non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package) 504 +|**Described Value Domain**|(% style="width:754px" %)((( 505 +non-enumerated** Representation** 506 + 507 +(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package) 498 498 ))) 499 -|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations) 500 -|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX 501 -|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX 502 -|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX 503 -|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX 509 +|**Value**|(% style="width:754px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or 510 +| |(% style="width:754px" %)((( 511 +to a valid **value **(for non-enumerated** **Representations) 512 +))) 513 +|**Value Domain Subset / Set**|(% style="width:754px" %)This abstraction does not exist in SDMX 514 +|**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:754px" %)This abstraction does not exist in SDMX 515 +|**Described Value Domain Subset / Described Set**|(% style="width:754px" %)This abstraction does not exist in SDMX 516 +|**Set list**|(% style="width:754px" %)This abstraction does not exist in SDMX 504 504 505 505 The main difference between VTL and SDMX relies on the fact that the VTL artefacts for defining subsets of Value Domains do not exist in SDMX, therefore the VTL features for referring to predefined subsets are not available in SDMX. These artefacts are the Value Domain Subset (or Set), either enumerated or described, the Set List (list of values belonging to enumerated subsets) and the Data Set Component (aimed at defining the set of values that the Component of a Data Set can take, possibly a subset of the codes of Value Domain). 506 506 ... ... @@ -526,7 +526,7 @@ 526 526 527 527 The VTL data types are sub-divided in scalar types (like integers, strings, etc.), which are the types of the scalar values, and compound types (like Data Sets, Components, Rulesets, etc.), which are the types of the compound structures. See below the diagram of the VTL data types, taken from the VTL User Manual: 528 528 529 -[[image: 1747388434672-948.png]]542 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]] 530 530 531 531 (% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %) 532 532 **Figure 22 – VTL Data Types** ... ... @@ -535,10 +535,13 @@ 535 535 536 536 The VTL basic scalar types are listed below and follow a hierarchical structure in terms of supersets/subsets (e.g. "scalar" is the superset of all the basic scalar types): 537 537 538 -[[image:1747388465321-274.png]] 539 539 540 540 **Figure 23 – VTL Basic Scalar Types** 541 541 554 +((( 555 + 556 +))) 557 + 542 542 === 12.4.2 VTL basic scalar types and SDMX data types === 543 543 544 544 The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
- 1747388275998-621.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.2 KB - Content
- 1747388434672-948.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.2 KB - Content
- 1747388465321-274.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.9 KB - Content