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)
Details
- Page properties
-
- Content
-
... ... @@ -541,38 +541,39 @@ 541 541 542 542 With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered: 543 543 544 -(% style="width:1170.29px" %) 545 -|**VTL**|(% style="width:754px" %)**SDMX** 546 -|**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 547 -|**Represented Variable**|(% style="width:754px" %)((( 544 +|VTL|SDMX 545 +|**Data Set Component**|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^^43^^ 546 +|**Represented Variable**|((( 548 548 **Concept** with a definite 549 549 550 550 Representation 551 551 ))) 552 -|**Value Domain**|( % style="width:754px" %)(((551 +|**Value Domain**|((( 553 553 **Representation** (see the Structure 554 554 555 555 Pattern in the Base Package) 556 556 ))) 557 -|**Enumerated Value Domain / Code List**| (% style="width:754px" %)**Codelist**558 -|**Code**|( % style="width:754px" %)(((556 +|**Enumerated Value Domain / Code List**|**Codelist** 557 +|**Code**|((( 559 559 **Code** (for enumerated 560 560 561 561 DimensionComponent, Measure, DataAttribute) 562 562 ))) 563 -|**Described Value Domain**|( % style="width:754px" %)(((564 -non-enumerated** Representation** 562 +|**Described Value Domain**|((( 563 +non-enumerated** Representation** 565 565 566 566 (having Facets / ExtendedFacets, see the Structure Pattern in the Base Package) 567 567 ))) 568 -|**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 569 -| |(% style="width:754px" %)((( 570 -to a valid **value **(for non-enumerated** **Representations) 567 +|**Value**|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 568 +| |((( 569 +to a valid **value **(for non-enumerated** ** 570 + 571 +Representations) 571 571 ))) 572 -|**Value Domain Subset / Set**| (% style="width:754px" %)This abstraction does not exist in SDMX573 -|**Enumerated Value Domain Subset / Enumerated Set**| (% style="width:754px" %)This abstraction does not exist in SDMX574 -|**Described Value Domain Subset / Described Set**| (% style="width:754px" %)This abstraction does not exist in SDMX575 -|**Set list**| (% style="width:754px" %)This abstraction does not exist in SDMX573 +|**Value Domain Subset / Set**|This abstraction does not exist in SDMX 574 +|**Enumerated Value Domain Subset / Enumerated Set**|This abstraction does not exist in SDMX 575 +|**Described Value Domain Subset / Described Set**|This abstraction does not exist in SDMX 576 +|**Set list**|This abstraction does not exist in SDMX 576 576 577 577 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). 578 578