Changes for page 12 Validation and Transformation Language (VTL)

Last modified by Helena K. on 2026/06/10 10:09

From 3.2 to 3.3 From 10.1 to 10.2

From version 3.3

edited by Helena K.
on 2025/06/16 13:43

Change comment: There is no comment for this version

To version 10.1

edited by Helena K.
on 2026/06/09 20:15

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 1 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]
- SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Tags

...	...	@@ -1,0 +1,1 @@
	1	+Artefact\|Attribute\|Code\|Code list\|Component\|Concept scheme\|Currency\|Data set\|Data structure definition\|Dataflow\|Dimension\|Facet\|Maintainable artefact\|Measure\|Nameable artefact\|Representation\|SDMX Information Model\|Statistical data and metadata exchange\|Structural metadata\|Validation and transformation language

Content

@@ -78,8 +78,12 @@
  * if the artefact is a Dimension, TimeDimension, Measure or DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
  * if the artefact is a Concept (the object-id is the name of the Concept)
--For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
++
++For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as
++
++{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
++
  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
@@ -106,6 +106,8 @@
  * As said, the container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
  * The object-id does not exist for the artefacts belonging to the Dataflow, and Codelist classes, while it exists and cannot be omitted for the artefacts belonging to the classes Dimension, TimeDimension, Measure, DataAttribute and Concept, as for them the object-id is the main identifier of the artefact
++
++
  The simplified object identifier is obtained by omitting all the first part of the URN, including the special characters, till the first part not omitted.
  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
@@ -116,7 +116,7 @@
  by omitting all the non-essential parts would become simply:
--> DFR  : = DF1 + DF2
++> DFR : = DF1 + DF2
  The references to the Codelists can be simplified similarly. For example, given the non-abbreviated reference to the Codelist AG:CL_FREQ(1.0.0), which is{{footnote}}Single quotes are needed because this reference is not a VTL regular name. 19 Single quotes are not needed in this case because CL_FREQ is a VTL regular name.{{/footnote}}:
@@ -162,14 +162,16 @@
  === 12.2.5 References to SDMX artefacts from VTL Rulesets ===
--The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: (i) when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
++The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
  The VTL Rulesets have a signature, in which the Value Domains or the Variables on which the Ruleset is defined are declared, and a body, which contains the Rules.
  In the signature, given the mapping between VTL and SDMX better described in the following paragraphs, a reference to a VTL Value Domain becomes a reference to a SDMX Codelist, while a reference to a VTL Represented Variable becomes a reference to a SDMX Concept, assuming for it a definite representation{{footnote}}Rulesets of this kind cannot be reused when the referenced Concept has a different representation.{{/footnote}}.
--In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets). The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
++In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets).
++The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
++
  In the body of the Rulesets, the Codes and in general all the Values can be written without any other specification, because the artefact, which the Values are referred (Codelist, Concept) to can be deduced from the Ruleset signature.
  == 12.3 Mapping between SDMX and VTL artefacts ==
@@ -458,26 +458,20 @@
  As said, it is assumed that these VTL derived Data Sets have the TIME_PERIOD as the only identifier. In the mapping from VTL to SMDX, the Dimensions INDICATOR and COUNTRY are added to the VTL data structure on order to obtain the SDMX one, with the following values respectively:
--> VTL dataset  INDICATOR value COUNTRY value
++> VTL dataset INDICATOR value COUNTRY value
  >
--> ‘DF2(1.0.0)/GDPPERCAPITA.USA’  GDPPERCAPITA USA
++> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
  > ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
  >
--> ‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
--> ‘DF2(1.0.0)/POPGROWTH.CANADA’  POPGROWTH CANADA
++> ‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
++> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
  > … … …
  It should be noted that the application of this many-to-one mapping from VTL to SDMX is equivalent to an appropriate sequence of VTL Transformations. These use the VTL operator “calc” to add the proper VTL identifiers (in the example, INDICATOR and COUNTRY) and to assign to them the proper values and the operator “union” in order to obtain the final VTL dataset (in the example DF2(1.0.0)), that can be mapped oneto-one to the homonymous SDMX Dataflow. Following the same example, these VTL Transformations would be:
--> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
--> DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
--> DF2bis_POPGROWTH_USA  := ‘DF2(1.0.0)/POPGROWTH.USA’  [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
--> DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
--> DF2(1.0) <- UNION   (DF2bis_GDPPERCAPITA_USA’,
--> DF2bis_GDPPERCAPITA_CANADA’,
++> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”]; DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”];… … … DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”]; DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”];… … … DF2(1.0) <- UNION (DF2bis_GDPPERCAPITA_USA’, DF2bis_GDPPERCAPITA_CANADA’,
  > … ,
--> DF2bis_POPGROWTH_USA’,
--> DF2bis_POPGROWTH_CANADA’
++> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
  > …);
  In other words, starting from the datasets explicitly calculated through VTL (in the example ‘DF2(1.0)/GDPPERCAPITA.USA’ and so on), the first step consists in calculating other (non-persistent) VTL datasets (in the example DF2bis_GDPPERCAPITA_USA and so on) by adding the identifiers INDICATOR and COUNTRY with the desired values (//INDICATORvalue// and //COUNTRYvalue)//. Finally, all these non-persistent Data Sets are united and give the final result DF2(1.0){{footnote}}The result is persistent in this example but it can be also non persistent if needed.{{/footnote}}, which can be mapped one-to-one to the homonymous SDMX Dataflow having the dimension components TIME_PERIOD, INDICATOR and COUNTRY.
@@ -535,7 +535,6 @@
  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:1750070288958-132.png]]
  **Figure 22 – VTL Data Types**
@@ -571,7 +571,8 @@
  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
  (% style="width:583.294px" %)
--|(% style="width:360px" %)SDMX data type (BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
++|(% style="width:360px" %)SDMX data type
++(BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
  |(% style="width:360px" %)(((
  String
  (string allowing any character)
@@ -606,7 +606,8 @@
  Short
  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
  )))|(% style="width:221px" %)integer
--|(% style="width:360px" %)Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:221px" %)number
++|(% style="width:360px" %)Decimal
++(corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:221px" %)number
  |(% style="width:360px" %)(((
  Float
  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
@@ -656,7 +656,7 @@
  GregorianTimePeriod
  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
  )))|(% style="width:221px" %)date
--|(% style="width:360px" %)GregorianYear  (YYYY)|(% style="width:221px" %)date
++|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
  |(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
  |(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
  |(% style="width:360px" %)(((
@@ -695,19 +695,19 @@
  )))|(% style="width:221px" %)date
  |(% style="width:360px" %)(((
  TimeRange
--(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
++(YYYY-MM-DD(Thh:mm:ss)?/)
  )))|(% style="width:221px" %)time
  |(% style="width:360px" %)(((
  Month
--(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
++(MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
  )))|(% style="width:221px" %)string
  |(% style="width:360px" %)(((
  MonthDay
--(~-~-MM-DD; specifies a day within a month independent of a year; e.g. Christmas is December 25^^th^^; used to specify reporting year start day)
++(MM-DD; specifies a day within a month independent of a year; e.g. Christmas is December 25^^th^^; used to specify reporting year start day)
  )))|(% style="width:221px" %)string
  |(% style="width:360px" %)(((
  Day
--(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
++(-DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
  )))|(% style="width:221px" %)string
  |(% style="width:360px" %)(((
  Time

SUZ.Methodology.Code.MethodologyClass[0]

SKMS.Methodology.Code.MethodologyClass[0]

Index

...	...	@@ -1,0 +1,1 @@
	1	+12