Changes for page 12 Validation and Transformation Language (VTL)

Last modified by Helena on 2025/09/10 11:19

From 6.8 to 6.9 From 6.13 to 7.1

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.13

edited by Helena
on 2025/05/16 12:42

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 2 added, 0 removed)
- 1747388434672-948.png
- 1747388465321-274.png

Details

Page properties

Content

@@ -477,38 +477,30 @@
  With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
--(% style="width:1170.29px" %)
--|**VTL**|(% style="width:754px" %)**SDMX**
--|**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}}
--|**Represented Variable**|(% style="width:754px" %)(((
++(% style="width:895.294px" %)
++|(% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**
++|(% 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}}
++|(% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((
  **Concept** with a definite
  Representation
  )))
--|**Value Domain**|(% style="width:754px" %)(((
--**Representation** (see the Structure
--
--Pattern in the Base Package)
++|(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)(((
++**Representation** (see the Structure Pattern in the Base Package)
  )))
--|**Enumerated Value Domain / Code List**|(% style="width:754px" %)**Codelist**
--|**Code**|(% style="width:754px" %)(((
--**Code** (for enumerated
--
--DimensionComponent, Measure, DataAttribute)
++|(% style="width:278px" %)**Enumerated Value Domain /
++Code List**|(% style="width:613px" %)**Codelist**
++|(% style="width:278px" %)**Code**|(% style="width:613px" %)(((
++**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
  )))
--|**Described Value Domain**|(% style="width:754px" %)(((
--non-enumerated** Representation**
--
--(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
++|(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)(((
++non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
  )))
--|**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
--| |(% style="width:754px" %)(((
--to a valid **value **(for non-enumerated** **Representations)
--)))
--|**Value Domain Subset / Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
--|**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
--|**Described Value Domain Subset / Described Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
--|**Set list**|(% style="width:754px" %)This abstraction does not exist in SDMX
++|(% 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)
++|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
++|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
++|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
++|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX
  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).
@@ -534,7 +534,7 @@
  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:
--[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]]
++[[image:1747388434672-948.png]]
  (% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
  **Figure 22 – VTL Data Types**
@@ -543,13 +543,10 @@
  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):
++[[image:1747388465321-274.png]]
  **Figure 23 – VTL Basic Scalar Types**
--(((
--
--)))
--
  === 12.4.2 VTL basic scalar types and SDMX data types ===
  The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
@@ -763,53 +763,53 @@
  The custom output formats can be specified by means of the VTL formatting mask described in the section "Type Conversion and Formatting Mask" of the VTL Reference Manual. Such a section describes the masks for the VTL basic scalar types "number", "integer", "date", "time", "time_period" and "duration" and gives examples. As for the types "string" and "boolean" the VTL conventions are extended with some other special characters as described in the following table.
--|(% colspan="2" %)VTL special characters for the formatting masks
--|(% colspan="2" %)
--|(% colspan="2" %)Number
--|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
--|E|one numeric digit (for the exponent of the scientific notation)
--|. (dot)|possible separator between the integer and the decimal parts.
--|, (comma)|possible separator between the integer and the decimal parts.
--| |
--|(% colspan="2" %)Time and duration
--|C|century
--|Y|year
--|S|semester
--|Q|quarter
--|M|month
--|W|week
--|D|day
--|h|hour digit (by default on 24 hours)
--|M|minute
--|S|second
--|D|decimal of second
--|P|period indicator (representation in one digit for the duration)
--|P|number of the periods specified in the period indicator
--|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
--|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
--|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
--|Month|lowercase textual representation of the month (e.g., january)
--|Day|lowercase textual representation of the month (e.g., monday)
--|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
--|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
--| |
--|(% colspan="2" %)String
--|X|any string character
--|Z|any string character from "A" to "z"
--|9|any string character from "0" to "9"
--| |
--|(% colspan="2" %)Boolean
--|B|Boolean using "true" for True and "false" for False
--|1|Boolean using "1" for True and "0" for False
--|0|Boolean using "0" for True and "1" for False
--| |
--|(% colspan="2" %)Other qualifiers
--|*|an arbitrary number of digits (of the preceding type)
--|+|at least one digit (of the preceding type)
--|( )|optional digits (specified within the brackets)
--|\|prefix for the special characters that must appear in the mask
--|N|fixed number of digits used in the preceding textual representation of the month or the day
--| |
++(% style="width:713.294px" %)
++|(% colspan="2" style="width:710px" %)VTL special characters for the formatting masks
++|(% colspan="2" style="width:710px" %)
++|(% colspan="2" style="width:710px" %)Number
++|D|(% style="width:486px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
++|E|(% style="width:486px" %)one numeric digit (for the exponent of the scientific notation)
++|. (dot)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
++|, (comma)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
++| |(% style="width:486px" %)
++|(% colspan="2" style="width:710px" %)Time and duration
++|C|(% style="width:486px" %)century
++|Y|(% style="width:486px" %)year
++|S|(% style="width:486px" %)semester
++|Q|(% style="width:486px" %)quarter
++|M|(% style="width:486px" %)month
++|W|(% style="width:486px" %)week
++|D|(% style="width:486px" %)day
++|h|(% style="width:486px" %)hour digit (by default on 24 hours)
++|M|(% style="width:486px" %)minute
++|S|(% style="width:486px" %)second
++|D|(% style="width:486px" %)decimal of second
++|P|(% style="width:486px" %)period indicator (representation in one digit for the duration)
++|P|(% style="width:486px" %)number of the periods specified in the period indicator
++|AM/PM|(% style="width:486px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
++|MONTH|(% style="width:486px" %)uppercase textual representation of the month (e.g., JANUARY for January)
++|DAY|(% style="width:486px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
++|Month|(% style="width:486px" %)lowercase textual representation of the month (e.g., january)
++|Day|(% style="width:486px" %)lowercase textual representation of the month (e.g., monday)
++|Month|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
++|Day|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
++| |(% style="width:486px" %)
++|(% colspan="2" style="width:710px" %)String
++|X|(% style="width:486px" %)any string character
++|Z|(% style="width:486px" %)any string character from "A" to "z"
++|9|(% style="width:486px" %)any string character from "0" to "9"
++| |(% style="width:486px" %)
++|(% colspan="2" style="width:710px" %)Boolean
++|B|(% style="width:486px" %)Boolean using "true" for True and "false" for False
++|1|(% style="width:486px" %)Boolean using "1" for True and "0" for False
++|0|(% style="width:486px" %)Boolean using "0" for True and "1" for False
++| |(% style="width:486px" %)
++|(% colspan="2" style="width:710px" %)Other qualifiers
++|*|(% style="width:486px" %)an arbitrary number of digits (of the preceding type)
++|+|(% style="width:486px" %)at least one digit (of the preceding type)
++|( )|(% style="width:486px" %)optional digits (specified within the brackets)
++|\|(% style="width:486px" %)prefix for the special characters that must appear in the mask
++|N|(% style="width:486px" %)fixed number of digits used in the preceding textual representation of the month or the day
  The default conversion, either standard or customized, can be used to deduce automatically the representation of the components of the result of a VTL Transformation. In alternative, the representation of the resulting SDMX Dataflow can be given explicitly by providing its DataStructureDefinition. In other words, the representation specified in the DSD, if available, overrides any default conversion{{footnote}}The representation given in the DSD should obviously be compatible with the VTL data type.{{/footnote}}.

1747388434672-948.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+43.2 KB

Content

1747388465321-274.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+17.9 KB

Content