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
-
... ... @@ -477,31 +477,30 @@ 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: 1170.29px" %)481 -|(% style="width: 392px" %)**VTL**|(% style="width:776px" %)**SDMX**482 -|(% style="width: 392px" %)**Data Set Component**|(% style="width:776px" %)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: 392px" %)**Represented Variable**|(% style="width:776px" %)(((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" %)((( 484 484 **Concept** with a definite 485 485 486 486 Representation 487 487 ))) 488 -|(% style="width: 392px" %)**Value Domain**|(% style="width:776px" %)(((488 +|(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)((( 489 489 **Representation** (see the Structure Pattern in the Base Package) 490 490 ))) 491 -|(% style="width:392px" %)**Enumerated Value Domain / Code List**|(% style="width:776px" %)**Codelist** 492 -|(% style="width:392px" %)**Code**|(% style="width:776px" %)((( 493 -**Code** (for enumerated 494 - 495 -DimensionComponent, Measure, DataAttribute) 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) 496 496 ))) 497 -|(% style="width: 392px" %)**Described Value Domain**|(% style="width:776px" %)(((496 +|(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)((( 498 498 non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package) 499 499 ))) 500 -|(% style="width: 392px" %)**Value**|(% style="width:776px" %)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)501 -|(% style="width: 392px" %)**Value Domain Subset / Set**|(% style="width:776px" %)This abstraction does not exist in SDMX502 -|(% style="width: 392px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:776px" %)This abstraction does not exist in SDMX503 -|(% style="width: 392px" %)**Described Value Domain Subset / Described Set**|(% style="width:776px" %)This abstraction does not exist in SDMX504 -|(% style="width: 392px" %)**Set list**|(% style="width:776px" %)This abstraction does not exist in SDMX499 +|(% 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 505 505 506 506 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). 507 507