Changes for page 12 Validation and Transformation Language (VTL)

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 2 removed)
  • 1750070288958-132.png
  • 1750070310572-584.png
  • 1750067055028-964.png

Details

Page properties

Content

...	...	@@ -2,9 +2,10 @@
2	2	{{toc/}}
3	3	{{/box}}
4	4
5		-== 12.1 Introduction ==
	5	+1.
	6	+11. Introduction
6	6
7		-The Validation and Transformation Language (VTL) supports the definition of Transformations, which are algorithms to calculate new data starting from already existing ones{{footnote}}The Validation and Transformation Language is a standard language designed and published under the SDMX initiative. VTL is described in the VTL User and Reference Guides available on the SDMX website https://sdmx.org.{{/footnote}}. The purpose of the VTL in the SDMX context is to enable the:
	8	+The Validation and Transformation Language (VTL) supports the definition of Transformations, which are algorithms to calculate new data starting from already existing ones[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%). The purpose of the VTL in the SDMX context is to enable the:
8	8
9	9	* definition of validation and transformation algorithms, in order to specify how to calculate new data from existing ones;
10	10	* exchange of the definition of VTL algorithms, also together the definition of the data structures of the involved data (for example, exchange the data structures of a reporting framework together with the validation rules to be applied, exchange the input and output data structures of a calculation task together with the VTL Transformations describing the calculation algorithms);
...	...	@@ -12,31 +12,33 @@
12	12
13	13	It is important to note that the VTL has its own information model (IM), derived from the Generic Statistical Information Model (GSIM) and described in the VTL User Guide. The VTL IM is designed to be compatible with more standards, like SDMX, DDI (Data Documentation Initiative) and GSIM, and includes the model artefacts that can be manipulated (inputs and/or outputs of Transformations, e.g. "Data Set", "Data Structure") and the model artefacts that allow the definition of the transformation algorithms (e.g. "Transformation", "Transformation Scheme").
14	14
15		-The VTL language can be applied to SDMX artefacts by mapping the SDMX IM model artefacts to the model artefacts that VTL can manipulate{{footnote}}In this chapter, in order to distinguish VTL and SDMX model artefacts, the VTL ones are written in the Arial font while the SDMX ones in Courier New.{{/footnote}}. Thus, the SDMX artefacts can be used in VTL as inputs and/or outputs of Transformations. It is important to be aware that the artefacts do not always have the same names in the SDMX and VTL IMs, nor do they always have the same meaning. The more evident example is given by the SDMX Dataset and the VTL "Data Set", which do not correspond one another: as a matter of fact, the VTL "Data Set" maps to the SDMX "Dataflow", while the SDMX "Dataset" has no explicit mapping to VTL (such an abstraction is not needed in the definition of VTL Transformations). A SDMX "Dataset", however, is an instance of a SDMX "Dataflow" and can be the artefact on which the VTL transformations are executed (i.e., the Transformations are defined on Dataflows and are applied to Dataflow instances that can be Datasets).
	16	+The VTL language can be applied to SDMX artefacts by mapping the SDMX IM model artefacts to the model artefacts that VTL can manipulate[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]](%%). Thus, the SDMX artefacts can be used in VTL as inputs and/or outputs of Transformations. It is important to be aware that the artefacts do not always have the same names in the SDMX and VTL IMs, nor do they always have the same meaning. The more evident example is given by the SDMX Dataset and the VTL "Data Set", which do not correspond one another: as a matter of fact, the VTL "Data Set" maps to the SDMX "Dataflow", while the SDMX "Dataset" has no explicit mapping to VTL (such an abstraction is not needed in the definition of VTL Transformations). A SDMX "Dataset", however, is an instance of a SDMX "Dataflow" and can be the artefact on which the VTL transformations are executed (i.e., the Transformations are defined on Dataflows and are applied to Dataflow instances that can be Datasets).
16	16
17	17	The VTL programs (Transformation Schemes) are represented in SDMX through the TransformationScheme maintainable class which is composed of Transformation (nameable artefact). Each Transformation assigns the outcome of the evaluation of a VTL expression to a result.
18	18
19	19	This section does not explain the VTL language or any of the content published in the VTL guides. Rather, this is a description of how the VTL can be used in the SDMX context and applied to SDMX artefacts.
20	20
21		-== 12.2 References to SDMX artefacts from VTL statements ==
	22	+1.
	23	+11. References to SDMX artefacts from VTL statements
	24	+111. Introduction
22	22
23		-=== 12.2.1 Introduction ===
24		-
25	25	The VTL can manipulate SDMX artefacts (or objects) by referencing them through predefined conventional names (aliases).
26	26
27	27	The alias of an SDMX artefact can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
28	28
29		-In any case, the aliases used in the VTL Transformations have to be mapped to the SDMX artefacts through the VtlMappingScheme and VtlMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlMapping allows specifying the aliases to be used in the VTL Transformations, Rulesets{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}} or User Defined Operators{{footnote}}The VTLMappings are used also for User Defined Operators (UDO). Although UDOs are envisaged to be defined on generic operands, so that the specific artefacts to be manipulated are passed as parameters at their invocation, it is also possible that an UDO invokes directly some specific SDMX artefacts. These SDMX artefacts have to be mapped to the corresponding aliases used in the definition of the UDO through the VtlMappingScheme and VtlMapping classes as well.{{/footnote}} to reference SDMX artefacts. A VtlMappingScheme is a container for zero or more VtlMapping.
	30	+In any case, the aliases used in the VTL Transformations have to be mapped to the SDMX artefacts through the VtlMappingScheme and VtlMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlMapping allows specifying the aliases to be used in the VTL Transformations, Rulesets[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[3~]^^>>path:#_ftn3]](%%) or User Defined Operators[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[4~]^^>>path:#_ftn4]](%%) to reference SDMX artefacts. A VtlMappingScheme is a container for zero or more VtlMapping.
30	30
31	31	The correspondence between an alias and a SDMX artefact must be one-to-one, meaning that a generic alias identifies one and just one SDMX artefact while a SDMX artefact is identified by one and just one alias. In other words, within a VtlMappingScheme an artefact can have just one alias and different artefacts cannot have the same alias.
32	32
33	33	The references through the URN and the abbreviated URN are described in the following paragraphs.
34	34
35		-=== 12.2.2 References through the URN ===
	36	+1.
	37	+11.
	38	+111. References through the URN
36	36
37	37	This approach has the advantage that in the VTL code the URN of the referenced artefacts is directly intelligible by a human reader but has the drawback that the references are verbose.
38	38
39		-The SDMX URN{{footnote}}For a complete description of the structure of the URN see the SDMX 2.1 Standards - Section 5 - Registry Specifications, paragraph 6.2.2 ("Universal Resource Name (URN)").{{/footnote}}(% style="font-size:12px" %) (%%)is the concatenation of the following parts, separated by special symbols like dot, equal, asterisk, comma, and parenthesis:
	42	+The SDMX URN[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[5~]^^>>path:#_ftn5]](%%) is the concatenation of the following parts, separated by special symbols like dot, equal, asterisk, comma, and parenthesis:
40	40
41	41	* SDMXprefix
42	42	* SDMX-IM-package-name
...	...	@@ -44,13 +44,15 @@
44	44	* agency-id
45	45	* maintainedobject-id
46	46	* maintainedobject-version
47		-* container-object-id{{footnote}}The container-object-id can repeat and may not be present.{{/footnote}}
	50	+* container-object-id [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[6~]^^>>path:#_ftn6]]
48	48	* object-id
49	49
50	50	The generic structure of the URN is the following:
51	51
52		-SDMXprefix.SDMX-IM-package-name.class-name=agency-id:maintainedobject-id (maintainedobject-version).*container-object-id.object-id
	55	+SDMXprefix.SDMX-IM-package-name.class-name=agency-id:maintainedobject-id
53	53
	57	+(maintainedobject-version).*container-object-id.object-id
	58	+
54	54	The **SDMXprefix** is "urn:sdmx:org", always the same for all SDMX artefacts.
55	55
56	56	The SDMX-IM-package-name** **is the concatenation of the string** **"sdmx.infomodel." with the package-name, which the artefact belongs to. For example, for referencing a Dataflow the SDMX-IM-package-name is "sdmx.infomodel.datastructure", because the class Dataflow belongs to the package "datastructure".
...	...	@@ -59,7 +59,7 @@
59	59
60	60	The agency-id is the acronym of the agency that owns the definition of the artefact, for example for the Eurostat artefacts the agency-id is "ESTAT"). The agency-id can be composite (for example AgencyA.Dept1.Unit2).
61	61
62		-The maintainedobject-id is the name of the maintained object which the artefact belongs to, and in case the artefact itself is maintainable{{footnote}}i.e., the artefact belongs to a maintainable class{{/footnote}}, coincides with the name of the artefact. Therefore the maintainedobject-id depends on the class of the artefact:
	67	+The maintainedobject-id is the name of the maintained object which the artefact belongs to, and in case the artefact itself is maintainable[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[7~]^^>>path:#_ftn7]](%%), coincides with the name of the artefact. Therefore the maintainedobject-id depends on the class of the artefact:
63	63
64	64	* if the artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the Dataflow name (dataflow-id);
65	65	* if the artefact is a Dimension, Measure, TimeDimension or DataAttribute, which are not maintainable and belong to the
...	...	@@ -71,21 +71,28 @@
71	71
72	72	The maintainedobject-version is the version, according to the SDMX versioning rules, of the maintained object which the artefact belongs to (for example, possible versions might be 1.0, 2.3, 1.0.0, 2.1.0 or 3.1.2).
73	73
74		-The container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN.
	79	+The container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
75	75
76	76	The object-id is the name of the non-maintainable artefact (when the artefact is maintainable its name is already specified as the maintainedobject-id, see above), in particular it has to be specified:
77	77
78		-* 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)
	83	+* if the artefact is a Dimension, TimeDimension, Measure or
	84	+
	85	+DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
	86	+
79	79	* if the artefact is a Concept (the object-id is the name of the Concept)
80	80
81		-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}}:
	89	+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[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[8~]^^>>path:#_ftn8]](%%):
82	82
83		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	91	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
86	86
87		-=== 12.2.3 Abbreviation of the URN ===
	93	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
88	88
	95	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	96	+
	97	+1.
	98	+11.
	99	+111. Abbreviation of the URN
	100	+
89	89	The complete formulation of the URN described above is exhaustive but verbose, even for very simple statements. In order to reduce the verbosity through a simplified identifier and make the work of transformation definers easier, proper abbreviations of the URN are possible. Using this approach, the referenced artefacts remain intelligible in the VTL code by a human reader.
90	90
91	91	The URN can be abbreviated by omitting the parts that are not essential for the identification of the artefact or that can be deduced from other available information, including the context in which the invocation is made. The possible abbreviations are described below.
...	...	@@ -92,14 +92,15 @@
92	92
93	93	* The SDMXprefix can be omitted for all the SDMX objects, because it is a prefixed string (urn:sdmx:org), always the same for SDMX objects.
94	94	* The SDMX-IM-package-name** **can be omitted as well because it can be deduced from the class-name that follows it (the table of the SDMX-IM packages and classes that allows this deduction is in the SDMX 2.1 Standards - Section 5 - Registry Specifications, paragraph 6.2.3). In particular, considering the object classes of the artefacts that VTL can reference, the package is:
95		-** "datastructure" for the classes Dataflow, Dimension, TimeDimension, Measure, DataAttribute,
96		-** "conceptscheme" for the class Concept,
97		-** "codelist" for the class Codelist.
98		-* The class-name can be omitted as it can be deduced from the VTL invocation. In particular, starting from the VTL class of the invoked artefact (e.g. dataset, component, identifier, measure, attribute, variable, valuedomain), which is known given the syntax of the invoking VTL operator{{footnote}}For the syntax of the VTL operators see the VTL Reference Manual{{/footnote}}, the SDMX class can be deduced from the mapping rules between VTL and SDMX (see the section "Mapping between VTL and SDMX" hereinafter){{footnote}}In case the invoked artefact is a VTL component, which can be invoked only within the invocation of a VTL data set (SDMX Dataflow), the specific SDMX class-name (e.g. Dimension, TimeDimension, Measure or DataAttribute) can be deduced from the data structure of the SDMX Dataflow, which the component belongs to.{{/footnote}}.
99		-* If the agency-id is not specified, it is assumed by default equal to the agency-id of the TransformationScheme, UserDefinedOperatorScheme or RulesetScheme from which the artefact is invoked. For example, the agencyid can be omitted if it is the same as the invoking TransformationScheme and cannot be omitted if the artefact comes from another agency{{footnote}}If the Agency is composite (for example AgencyA.Dept1.Unit2), the agency is considered different even if only part of the composite name is different (for example AgencyA.Dept1.Unit3 is a different Agency than the previous one). Moreover the agency-id cannot be omitted in part (i.e., if a TransformationScheme owned by AgencyA.Dept1.Unit2 references an artefact coming from AgencyA.Dept1.Unit3, the specification of the agency-id becomes mandatory and must be complete, without omitting the possibly equal parts like AgencyA.Dept1){{/footnote}}. Take also into account that, according to the VTL consistency rules, the agency of the result of a Transformation must be the same as its TransformationScheme, therefore the agency-id can be omitted for all the results (left part of Transformation statements).
100		-* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted:
101		-** if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
102		-** if the referenced artefact is a Dimension, TimeDimension, Measure, DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the dataStructure-id and can be omitted, given that these components are always invoked within the invocation of a Dataflow, whose dataStructure-id can be deduced from the SDMX structural definitions;
	107	+** "datastructure" for the classes Dataflow, Dimension, TimeDimension, Measure, DataAttribute, o "conceptscheme" for the class Concept, o "codelist" for the class Codelist.
	108	+* The class-name can be omitted as it can be deduced from the VTL invocation. In particular, starting from the VTL class of the invoked artefact (e.g. dataset, component, identifier, measure, attribute, variable, valuedomain), which is known given the syntax of the invoking VTL operator[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[9~]^^>>path:#_ftn9]](%%), the SDMX class can be deduced from the mapping rules between VTL and SDMX (see the section "Mapping between VTL and SDMX" hereinafter)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[10~]^^>>path:#_ftn10]](%%).
	109	+* If the agency-id is not specified, it is assumed by default equal to the agency-id of the TransformationScheme, UserDefinedOperatorScheme or RulesetScheme from which the artefact is invoked. For example, the agencyid can be omitted if it is the same as the invoking TransformationScheme and cannot be omitted if the artefact comes from another agency[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[11~]^^>>path:#_ftn11]](%%). Take also into account that, according to the VTL consistency rules, the agency of the result of a Transformation must be the same as its TransformationScheme, therefore the agency-id can be omitted for all the results (left part of Transformation statements).
	110	+* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted: o if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
	111	+** if the referenced artefact is a Dimension, TimeDimension, Measure,
	112	+
	113	+DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the dataStructure-id and can be omitted, given that these components are always invoked within the invocation of a Dataflow, whose dataStructure-id can be deduced from the SDMX structural definitions;
	114	+
	115	+*
103	103	** if the referenced artefact is a Concept, which is not maintainable and belong to the ConceptScheme maintainable class, the maintained object is the conceptScheme-id and cannot be omitted;
104	104	** if the referenced artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
105	105	* When the maintainedobject-id is omitted, the maintainedobject-version is omitted too. When the maintainedobject-id is not omitted and the maintainedobject-version is omitted, the version 1.0 is assumed by default.
...	...	@@ -110,81 +110,91 @@
110	110
111	111	For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
112	112
113		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
114		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
115		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	126	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
116	116
	128	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
	129	+
	130	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	131	+
117	117	by omitting all the non-essential parts would become simply:
118	118
119		-> DFR  : = DF1 + DF2
	134	+DFR := DF1 + DF2
120	120
121		-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}}:
	136	+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[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[12~]^^>>path:#_ftn12]](%%):
122	122
123		-> 'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
	138	+'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
124	124
125	125	if the Codelist is referenced from a RulesetScheme belonging to the agency AG, omitting all the optional parts, the abbreviated reference would become simply^^19^^:
126	126
127		-> CL_FREQ
	142	+CL_FREQ
128	128
129	129	As for the references to the components, it can be enough to specify the componentId, given that the dataStructure-Id can be omitted. An example of non-abbreviated reference, if the data structure is DST1 and the component is SECTOR, is the following:
130	130
131		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S ECTOR'
	146	+'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S
132	132
	148	+ECTOR'
	149	+
133	133	The corresponding fully abbreviated reference, if made from a TransformationScheme belonging to AG, would become simply:
134	134
135		-> SECTOR
	152	+SECTOR
136	136
137		-For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as{{footnote}}The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC{{/footnote}}:
	154	+For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[13~]^^>>path:#_ftn13]](%%):
138	138
139		-> 'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
	156	+'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
140	140
141	141	In the references to the Concepts, which can exist for example in the definition of the VTL Rulesets, at least the conceptScheme-id and the concept-id must be specified.
142	142
143	143	An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
144	144
145		-> 'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
	162	+'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
146	146
147	147	The corresponding fully abbreviated reference, if made from a RulesetScheme belonging to AG, would become simply:
148	148
149		-> CS1(1.0.0).SECTOR
	166	+CS1(1.0.0).SECTOR
150	150
151	151	The Codes and in general all the Values can be written without any other specification, for example, the transformation to check if the values of the measures of the Dataflow DF1 are between 0 and 25000 can be written like follows:
152	152
153		-> 'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
	170	+'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
154	154
155	155	The artefact (Component, Concept, Codelist …) which the Values are referred to can be deduced from the context in which the reference is made, taking also into account the VTL syntax. In the Transformation above, for example, the values 0 and 2500 are compared to the values of the measures of DF1(1.0.0).
156	156
157		-=== 12.2.4 User-defined alias ===
	174	+1.
	175	+11.
	176	+111. User-defined alias
158	158
159	159	The third possibility for referencing SDMX artefacts from VTL statements is to use user-defined aliases not related to the SDMX URN of the artefact.
160	160
161	161	This approach gives preference to the use of symbolic names for the SDMX artefacts. As a consequence, in the VTL code the referenced artefacts may become not directly intelligible by a human reader. In any case, the VTL aliases are associated to the SDMX URN through the VtlMappingScheme and VtlMapping classes. These classes provide for structured references to SDMX artefacts whatever kind of reference is used in VTL statements (URN, abbreviated URN or user-defined aliases).
162	162
163		-=== 12.2.5 References to SDMX artefacts from VTL Rulesets ===
	182	+1.
	183	+11.
	184	+111. References to SDMX artefacts from VTL Rulesets
164	164
165	165	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.
166	166
167	167	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.
168	168
169		-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}}.
	190	+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[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[14~]^^>>path:#_ftn14]](%%).
170	170
171		-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}}
	192	+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.[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[15~]^^>>path:#_ftn15]]
172	172
173	173	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.
174	174
175		-== 12.3 Mapping between SDMX and VTL artefacts ==
	196	+1.
	197	+11. Mapping between SDMX and VTL artefacts
	198	+111. When the mapping occurs
176	176
177		-=== 12.3.1. When the mapping occurs ===
178		-
179	179	The mapping methods between the VTL and SDMX object classes allow transforming a SDMX definition in a VTL one and vice-versa for the artefacts to be manipulated. It should be remembered that VTL programs (i.e. Transformation Schemes) are represented in SDMX through the TransformationScheme maintainable class which is composed of Transformations (nameable artefacts). Each Transformation assigns the outcome of the evaluation of a VTL expression to a result: the input operands of the expression and the result can be SDMX artefacts. Every time a SDMX object is referenced in a VTL Transformation as an input operand, there is the need to generate a VTL definition of the object, so that the VTL operations can take place. This can be made starting from the SDMX definition and applying a SDMX-VTL mapping method in the direction from SDMX to VTL. The possible mapping methods from SDMX to VTL are described in the following paragraphs and are conceived to allow the automatic deduction of the VTL definition of the object from the knowledge of the SDMX definition.
180	180
181		-In the opposite direction, every time an object calculated by means of VTL must be treated as a SDMX object (for example for exchanging it through SDMX), there is the need of a SDMX definition of the object, so that the SDMX operations can take place. The SDMX definition is needed for the VTL objects for which a SDMX use is envisaged{{footnote}}If a calculated artefact is persistent, it needs a persistent definition, i.e. a SDMX definition in a SDMX environment. In addition, possible calculated artefact that are not persistent may require a SDMX definition, for example when the result of a nonpersistent calculation is disseminated through SDMX tools (like an inquiry tool).{{/footnote}}.
	202	+In the opposite direction, every time an object calculated by means of VTL must be treated as a SDMX object (for example for exchanging it through SDMX), there is the need of a SDMX definition of the object, so that the SDMX operations can take place. The SDMX definition is needed for the VTL objects for which a SDMX use is envisaged[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[16~]^^>>path:#_ftn16]](%%).
182	182
183	183	The mapping methods from VTL to SDMX are described in the following paragraphs as well, however they do not allow the complete SDMX definition to be automatically deduced from the VTL definition, more than all because the former typically contains additional information in respect to the latter. For example, the definition of a SDMX DSD includes also some mandatory information not available in VTL (like the concept scheme to which the SDMX components refer, the ‘usage’ and ‘attributeRelationship’ for the DataAttributes and so on). Therefore the mapping methods from VTL to SDMX provide only a general guidance for generating SDMX definitions properly starting from the information available in VTL, independently of how the SDMX definition it is actually generated (manually, automatically or part and part).
184	184
185		-=== 12.3.2 General mapping of VTL and SDMX data structures ===
	206	+1.
	207	+11.
	208	+111. General mapping of VTL and SDMX data structures
186	186
187		-This section makes reference to the VTL "Model for data and their structure"{{footnote}}See the VTL 2.0 User Manual{{/footnote}} and the correspondent SDMX "Data Structure Definition"{{footnote}}See the SDMX Standards Section 2 – Information Model{{/footnote}}.
	210	+This section makes reference to the VTL "Model for data and their structure"[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[17~]^^>>path:#_ftn17]](%%) and the correspondent SDMX "Data Structure Definition"{{footnote}}See the SDMX Standards Section 2 – Information Model{{/footnote}}.
188	188
189	189	The main type of artefact that the VTL can manipulate is the VTL Data Set, which in general is mapped to the SDMX Dataflow. This means that a VTL Transformation, in the SDMX context, expresses the algorithm for calculating a derived Dataflow starting from some already existing Dataflows (either collected or derived).{{footnote}}Besides the mapping between one SDMX Dataflow and one VTL Data Set, it is also possible to map distinct parts of a SDMX Dataflow to different VTL Data Set, as explained in a following paragraph.{{/footnote}}
190	190
...	...	@@ -198,31 +198,34 @@
198	198
199	199	The possible mapping options are described in more detail in the following sections.
200	200
201		-=== 12.3.3 Mapping from SDMX to VTL data structures ===
	224	+1.
	225	+11.
	226	+111. Mapping from SDMX to VTL data structures
202	202
203		-==== 12.3.3.1 Basic Mapping ====
	228	+**12.3.3.1 Basic Mapping**
204	204
205	205	The main mapping method from SDMX to VTL is called **Basic **mapping. This is considered as the default mapping method and is applied unless a different method is specified through the VtlMappingScheme and VtlDataflowMapping classes.
206	206
207	207	When transforming **from SDMX to VTL**, this method consists in leaving the components unchanged and maintaining their names and roles, according to the following table:
208	208
209		-(% style="width:468.294px" %)
210		-|(% style="width:196px" %)**SDMX**|(% style="width:269px" %)**VTL**
211		-|(% style="width:196px" %)Dimension|(% style="width:269px" %)(Simple) Identifier
212		-|(% style="width:196px" %)TimeDimension|(% style="width:269px" %)(Time) Identifier
213		-|(% style="width:196px" %)Measure|(% style="width:269px" %)Measure
214		-|(% style="width:196px" %)DataAttribute|(% style="width:269px" %)Attribute
	234	+|**SDMX**|**VTL**
	235	+|Dimension|(Simple) Identifier
	236	+|TimeDimension|(Time) Identifier
	237	+|Measure|Measure
	238	+|DataAttribute|Attribute
215	215
216	216	The SDMX DataAttributes, in VTL they are all considered "at data point / observation level" (i.e. dependent on all the VTL Identifiers), because VTL does not have the SDMX AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, dimension or set or group of dimensions, whole data set).
217	217
218	218	With the Basic mapping, one SDMX observation^^27^^ generates one VTL data point.
219	219
220		-==== 12.3.3.2 Pivot Mapping ====
	244	+**12.3.3.2 Pivot Mapping**
221	221
222	222	An alternative mapping method from SDMX to VTL is the **Pivot **mapping, which makes sense and is different from the Basic method only for the SDMX data structures that contain a Dimension that plays the role of measure dimension (like in SDMX 2.1) and just one Measure. Through this method, these structures can be mapped to multimeasure VTL data structures. Besides that, a user may choose to use any Dimension acting as a list of Measures (e.g., a Dimension with indicators), either by considering the “Measure” role of a Dimension, or at will using any coded Dimension. Of course, in SDMX 3.0, this can only work when only one Measure is defined in the DSD.
223	223
224		-In SDMX 2.1 the MeasureDimension was a subclass of DimensionComponent like Dimension and TimeDimension. In the current SDMX version, this subclass does not exist anymore, however a Dimension can have the role of measure dimension (i.e. a Dimension that contributes to the identification of the measures). In SDMX 2.1 a DataStructure could have zero or one MeasureDimensions, in the current version of the standard, from zero to many Dimension may have the role of measure dimension. Hereinafter a Dimension that plays the role of measure dimension is referenced for simplicity as “MeasureDimension“, i.e. maintaining the capital letters and the courier font even if the MeasureDimension is not anymore a class in the SDMX Information Model of the current SDMX version. For the sake of simplicity, the description below considers just one Dimension having the role of MeasureDimension (i.e., the more simple and common case). Nevertheless, it maintains its validity also if in the DataStructure there are more dimension with the role of MeasureDimensions: in this case what is said about the MeasureDimension must be applied to the combination of all the MeasureDimensions considered as a joint variable{{footnote}}E.g., if in the data structure there exist 3 Dimensions C,D,E having the role of MeasureDimension, they should be considered as a joint MeasureDimension Z=(C,D,E); therefore when the description says “each possible value Cj of the MeasureDimension …” it means “each possible combination of values (Cj, Dk, Ew) of the joint MeasureDimension Z=(C,D,E)”.{{/footnote}}.
	248	+In SDMX 2.1 the MeasureDimension was a subclass of DimensionComponent like Dimension and TimeDimension. In the current SDMX version, this subclass does not exist anymore, however a Dimension can have the role of measure dimension (i.e. a Dimension that contributes to the identification of the measures). In SDMX 2.1 a DataStructure could have zero or one MeasureDimensions, in the current version of the standard, from zero to many Dimension may have the role of measure dimension. Hereinafter a Dimension that plays the role of measure dimension is referenced for simplicity as “MeasureDimension“, i.e. maintaining the capital letters and the courier font even if the MeasureDimension is not anymore a class in the SDMX Information Model of the current SDMX version. For the sake of simplicity, the description below considers just one Dimension having the role of MeasureDimension (i.e., the more simple and common case). Nevertheless, it maintains its validity also if in the DataStructure there are more dimension with the role of MeasureDimensions: in this case what is said about the MeasureDimension must be applied to the combination of all the
225	225
	250	+MeasureDimensions considered as a joint variable{{footnote}}E.g., if in the data structure there exist 3 Dimensions C,D,E having the role of MeasureDimension, they should be considered as a joint MeasureDimension Z=(C,D,E); therefore when the description says “each possible value Cj of the MeasureDimension …” it means “each possible combination of values (Cj, Dk, Ew) of the joint MeasureDimension Z=(C,D,E)”.{{/footnote}}.
	251	+
226	226	Among other things, the Pivot method provides also backward compatibility with the SDMX 2.1 data structures that contained a MeasureDimension.
227	227
228	228	If applied to SDMX structures that do not contain any MeasureDimension, this method behaves like the Basic mapping (see the previous paragraph).
...	...	@@ -235,19 +235,18 @@
235	235	* The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
236	236	* An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
237	237	** If, according to the SDMX AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the SDMX DataAttribute becomes a VTL Attribute having the same name. This happens if the AttributeRelationship is not specified (i.e. the DataAttribute does not depend on any DimensionComponent and therefore is at data set level), or if it refers to a set (or a group) of dimensions which does not include the MeasureDimension;
238		-** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators).
239		-** Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
	264	+** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators). o Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
240	240
241	241	The summary mapping table of the "pivot" mapping from SDMX to VTL for the SDMX data structures that contain a MeasureDimension is the following:
242	242
243		-(% style="width:739.294px" %)
244		-|(% style="width:335px" %)**SDMX**|(% style="width:400px" %)**VTL**
245		-|(% style="width:335px" %)Dimension|(% style="width:400px" %)(Simple) Identifier
246		-|(% style="width:335px" %)TimeDimension|(% style="width:400px" %)(Time) Identifier
247		-|(% style="width:335px" %)MeasureDimension & one Measure|(% style="width:400px" %)One Measure for each Code of the SDMX MeasureDimension
248		-|(% style="width:335px" %)DataAttribute not depending on the MeasureDimension|(% style="width:400px" %)Attribute
249		-|(% style="width:335px" %)DataAttribute depending on the MeasureDimension|(% style="width:400px" %)(((
	268	+|**SDMX**|**VTL**
	269	+|Dimension|(Simple) Identifier
	270	+|TimeDimension|(Time) Identifier
	271	+|MeasureDimension & one Measure|One Measure for each Code of the SDMX MeasureDimension
	272	+|DataAttribute not depending on the MeasureDimension|Attribute
	273	+|DataAttribute depending on the MeasureDimension|(((
250	250	One Attribute for each Code of the
	275	+
251	251	SDMX MeasureDimension
252	252	)))
253	253
...	...	@@ -256,21 +256,31 @@
256	256	At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
257	257
258	258	* The set of SDMX observations having the same values for all the Dimensions except than the MeasureDimension become one multi-measure VTL Data Point, having one Measure for each Code Cj of the SDMX MeasureDimension;
259		-* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple) Identifiers, (time) Identifier and Attributes.
260		-* The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
	284	+* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple)
	285	+
	286	+Identifiers, (time) Identifier and Attributes.
	287	+
	288	+* The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure
	289	+
	290	+Cj
	291	+
261	261	* For the SDMX DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Attribute DA_Cj
262	262
263		-==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
	294	+**12.3.3.3 From SDMX DataAttributes to VTL Measures**
264	264
265		-* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain Attributes.
	296	+* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain
266	266
	298	+Attributes.
	299	+
267	267	The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final VTL components, which according to the Basic and Pivot methods would have had the role of Attribute, assume instead the role of Measure.
268	268
269	269	Proper VTL features allow changing the role of specific attributes even after the SDMX to VTL mapping: they can be useful when only some of the DataAttributes need to be managed as VTL Measures.
270	270
271		-=== 12.3.4 Mapping from VTL to SDMX data structures ===
	304	+1.
	305	+11.
	306	+111. Mapping from VTL to SDMX data structures
272	272
273		-==== 12.3.4.1 Basic Mapping ====
	308	+**12.3.4.1 Basic Mapping**
274	274
275	275	The main mapping method **from VTL to SDMX** is called **Basic **mapping as well.
276	276
...	...	@@ -280,12 +280,11 @@
280	280
281	281	Mapping table:
282	282
283		-(% style="width:470.294px" %)
284		-|(% style="width:262px" %)**VTL**|(% style="width:205px" %)**SDMX**
285		-|(% style="width:262px" %)(Simple) Identifier|(% style="width:205px" %)Dimension
286		-|(% style="width:262px" %)(Time) Identifier|(% style="width:205px" %)TimeDimension
287		-|(% style="width:262px" %)Measure|(% style="width:205px" %)Measure
288		-|(% style="width:262px" %)Attribute|(% style="width:205px" %)DataAttribute
	318	+|**VTL**|**SDMX**
	319	+|(Simple) Identifier|Dimension
	320	+|(Time) Identifier|TimeDimension
	321	+|Measure|Measure
	322	+|Attribute|DataAttribute
289	289
290	290	If the distinction between simple identifier and time identifier is not maintained in the VTL environment, the classification between Dimension and TimeDimension exists only in SDMX, as declared in the relevant DataStructureDefinition.
291	291
...	...	@@ -295,7 +295,7 @@
295	295
296	296	As said, the resulting SDMX definitions must be compliant with the SDMX consistency rules. For example, the SDMX DSD must have the AttributeRelationship for the DataAttributes, which does not exist in VTL.
297	297
298		-==== 12.3.4.2 Unpivot Mapping ====
	332	+**12.3.4.2 Unpivot Mapping**
299	299
300	300	An alternative mapping method from VTL to SDMX is the **Unpivot **mapping.
301	301
...	...	@@ -313,12 +313,11 @@
313	313
314	314	The summary mapping table of the **unpivot** mapping method is the following:
315	315
316		-(% style="width:638.294px" %)
317		-|(% style="width:200px" %)**VTL**|(% style="width:435px" %)**SDMX**
318		-|(% style="width:200px" %)(Simple) Identifier|(% style="width:435px" %)Dimension
319		-|(% style="width:200px" %)(Time) Identifier|(% style="width:435px" %)TimeDimension
320		-|(% style="width:200px" %)All Measure Components|(% style="width:435px" %)MeasureDimension (having one Code for each VTL measure component) & one Measure
321		-|(% style="width:200px" %)Attribute|(% style="width:435px" %)DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
	350	+|**VTL**|**SDMX**
	351	+|(Simple) Identifier|Dimension
	352	+|(Time) Identifier|TimeDimension
	353	+|All Measure Components|MeasureDimension (having one Code for each VTL measure component) & one Measure
	354	+|Attribute|DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
322	322
323	323	At observation / data point level:
324	324
...	...	@@ -332,7 +332,7 @@
332	332
333	333	In any case, the resulting SDMX definitions must be compliant with the SDMX consistency rules. For example, the possible Codes of the SDMX MeasureDimension need to be listed in a SDMX Codelist, with proper id, agency and version; moreover, the SDMX DSD must have the AttributeRelationship for the DataAttributes, which does not exist in VTL.
334	334
335		-==== 12.3.4.3 From VTL Measures to SDMX Data Attributes ====
	368	+**12.3.4.3 From VTL Measures to SDMX Data Attributes**
336	336
337	337	More than all for the multi-measure VTL structures (having more than one Measure Component), it may happen that the Measures of the VTL Data Structure need to be managed as DataAttributes in SDMX. Therefore, a third mapping method consists in transforming some VTL measures in a corresponding SDMX Measures and all the other VTL Measures in SDMX DataAttributes. This method is called M2A (“M2A” stands for “Measures to DataAttributes”).
338	338
...	...	@@ -340,17 +340,18 @@
340	340
341	341	The mapping table is the following:
342	342
343		-(% style="width:467.294px" %)
344		-|(% style="width:214px" %)VTL|(% style="width:250px" %)SDMX
345		-|(% style="width:214px" %)(Simple) Identifier|(% style="width:250px" %)Dimension
346		-|(% style="width:214px" %)(Time) Identifier|(% style="width:250px" %)TimeDimension
347		-|(% style="width:214px" %)Some Measures|(% style="width:250px" %)Measure
348		-|(% style="width:214px" %)Other Measures|(% style="width:250px" %)DataAttribute
349		-|(% style="width:214px" %)Attribute|(% style="width:250px" %)DataAttribute
	376	+|VTL|SDMX
	377	+|(Simple) Identifier|Dimension
	378	+|(Time) Identifier|TimeDimension
	379	+|Some Measures|Measure
	380	+|Other Measures|DataAttribute
	381	+|Attribute|DataAttribute
350	350
351	351	Even in this case, the resulting SDMX definitions must be compliant with the SDMX consistency rules. For example, the SDMX DSD must have the attributeRelationship for the DataAttributes, which does not exist in VTL.
352	352
353		-=== 12.3.5 Declaration of the mapping methods between data structures ===
	385	+1.
	386	+11.
	387	+111. Declaration of the mapping methods between data structures
354	354
355	355	In order to define and understand properly VTL Transformations, the applied mapping methods must be specified in the SDMX structural metadata. If the default mapping method (Basic) is applied, no specification is needed.
356	356
...	...	@@ -360,10 +360,14 @@
360	360
361	361	The VtlMappingScheme is a container for zero or more VtlDataflowMapping (it may contain also mappings towards artefacts other than dataflows).
362	362
363		-=== 12.3.6 Mapping dataflow subsets to distinct VTL Data Sets ===
	397	+1.
	398	+11.
	399	+111. Mapping dataflow subsets to distinct VTL Data Sets
364	364
365		-Until now it has been assumed to map one SMDX Dataflow to one VTL Data Set and vice-versa. This mapping one-to-one is not mandatory according to VTL because a VTL Data Set is meant to be a set of observations (data points) on a logical plane, having the same logical data structure and the same general meaning, independently of the possible physical representation or storage (see VTL 2.0 User Manual page 24), therefore a SDMX Dataflow can be seen either as a unique set of data observations (corresponding to one VTL Data Set) or as the union of many sets of data observations (each one corresponding to a distinct VTL Data Set).
	401	+Until now it has been assumed to map one SMDX Dataflow to one VTL Data Set and vice-versa. This mapping one-to-one is not mandatory according to VTL because a VTL Data Set is meant to be a set of observations (data points) on a logical plane, having the same logical data structure and the same general meaning, independently of the possible physical representation or storage (see VTL 2.0 User Manual page 24), therefore a SDMX Dataflow can be seen either as a unique set of data observations
366	366
	403	+(corresponding to one VTL Data Set) or as the union of many sets of data observations (each one corresponding to a distinct VTL Data Set).
	404	+
367	367	As a matter of fact, in some cases it can be useful to define VTL operations involving definite parts of a SDMX Dataflow instead than the whole.{{footnote}}A typical example of this kind is the validation, and more in general the manipulation, of individual time series belonging to the same Dataflow, identifiable through the DimensionComponents of the Dataflow except the TimeDimension. The coding of these kind of operations might be simplified by mapping distinct time series (i.e. different parts of a SDMX Dataflow) to distinct VTL Data Sets.{{/footnote}}
368	368
369	369	Therefore, in order to make the coding of VTL operations simpler when applied on parts of SDMX Dataflows, it is allowed to map distinct parts of a SDMX Dataflow to distinct VTL Data Sets according to the following rules and conventions. This kind of mapping is possible both from SDMX to VTL and from VTL to SDMX, as better explained below.{{footnote}}Please note that this kind of mapping is only an option at disposal of the definer of VTL Transformations; in fact it remains always possible to manipulate the needed parts of SDMX Dataflows by means of VTL operators (e.g. “sub”, “filter”, “calc”, “union” …), maintaining a mapping one-to-one between SDMX Dataflows and VTL Data Sets.{{/footnote}}
...	...	@@ -384,11 +384,11 @@
384	384
385	385	Therefore, the generic name of this kind of VTL datasets would be:
386	386
387		-> 'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
	425	+'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
388	388
389	389	Where DF(1.0.0) is the Dataflow and //INDICATORvalue// and //COUNTRYvalue //are placeholders for one value of the INDICATOR and COUNTRY dimensions. Instead the specific name of one of these VTL datasets would be:
390	390
391		-> ‘DF(1.0.0)/POPULATION.USA’
	429	+‘DF(1.0.0)/POPULATION.USA’
392	392
393	393	In particular, this is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and //COUNTRY// = USA.
394	394
...	...	@@ -402,22 +402,26 @@
402	402
403	403	SDMX Dataflow having INDICATOR=//INDICATORvalue //and COUNTRY=// COUNTRYvalue//. For example, the VTL dataset ‘DF1(1.0.0)/POPULATION.USA’ would contain all the observations of DF1(1.0.0) having INDICATOR = POPULATION and COUNTRY = USA.
404	404
405		-In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e. basic, pivot …).
	443	+In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e.
406	406
	445	+basic, pivot …).
	446	+
407	407	In the example above, for all the datasets of the kind
408	408
409		-> ‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
	449	+‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
410	410
411	411	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:
412	412
413		-> ‘DF1(1.0.0)/POPULATION.USA’ :=
414		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
415		->
416		-> ‘DF1(1.0.0)/POPULATION.CANADA’ :=
417		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
418		->
419		-> … … …
	453	+‘DF1(1.0.0)/POPULATION.USA’ :=
420	420
	455	+DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
	456	+
	457	+‘DF1(1.0.0)/POPULATION.CANADA’ :=
	458	+
	459	+DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
	460	+
	461	+… … …
	462	+
421	421	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}}
422	422
423	423	In the direction from SDMX to VTL it is allowed to omit the value of one or more DimensionComponents on which the mapping is based, but maintaining all the separating dots (therefore it may happen to find two or more consecutive dots and dots in the beginning or in the end). The absence of value means that for the corresponding Dimension all the values are kept and the Dimension is not dropped.
...	...	@@ -426,9 +426,10 @@
426	426
427	427	This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
428	428
429		-> ‘DF1(1.0.0)/POPULATION.’ :=
430		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
	471	+‘DF1(1.0.0)/POPULATION.’ :=
431	431
	473	+DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
	474	+
432	432	Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
433	433
434	434	Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different Dimensions in different invocations.
...	...	@@ -446,34 +446,59 @@
446	446
447	447	The corresponding VTL Transformations, assuming that the result needs to be persistent, would be of this kind:{{footnote}}the symbol of the VTL persistent assignment is used (<-){{/footnote}}
448	448
449		-> ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
	492	+‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
450	450
451	451	Some examples follow, for some specific values of INDICATOR and COUNTRY:
452	452
453		-> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
454		-> … … …
455		-> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
456		-> ‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
457		-> … … …
	496	+‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
458	458
	498	+… … …
	499	+
	500	+‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
	501	+
	502	+‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
	503	+
	504	+… … …
	505	+
459	459	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:
460	460
461		-> VTL dataset  INDICATOR value COUNTRY value
462		->
463		-> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
464		-> ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
465		->
466		-> ‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
467		-> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
468		-> … … …
	508	+VTL dataset   INDICATOR value COUNTRY value
469	469
	510	+
	511	+‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
	512	+
	513	+‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
	514	+
	515	+‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
	516	+
	517	+‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
	518	+
	519	+… … …
	520	+
470	470	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:
471	471
472		-> 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’,
473		-> … ,
474		-> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
475		-> …);
	523	+DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
476	476
	525	+DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
	526	+
	527	+DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’
	528	+
	529	+[calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
	530	+
	531	+DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
	532	+
	533	+DF2(1.0) <- UNION  (DF2bis_GDPPERCAPITA_USA’,
	534	+
	535	+DF2bis_GDPPERCAPITA_CANADA’,
	536	+
	537	+… ,
	538	+
	539	+DF2bis_POPGROWTH_USA’,
	540	+
	541	+DF2bis_POPGROWTH_CANADA’
	542	+
	543	+…);
	544	+
477	477	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.
478	478
479	479	Therefore, mapping different VTL datasets having the same data structure to different parts of a SDMX Dataflow, i.e. in the direction from VTL to SDMX, through the ordered concatenation notation is equivalent to a proper use of the operators “calc” and “union” on such datasets.{{footnote}}In case the ordered concatenation notation from VTL to SDMX is used, the set of Transformations described above is implicitly performed; therefore, in order to test the overall compliance of the VTL program to the VTL consistency rules, these implicit Transformations have to be considered as part of the VTL program even if they are not explicitly coded.{{/footnote}}{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
...	...	@@ -480,30 +480,33 @@
480	480
481	481	It is worth noting that in the direction from VTL to SDMX it is mandatory to specify the value for every Dimension on which the mapping is based (in other word, in the name of the calculated VTL dataset is not possible to omit the value of some of the Dimensions).
482	482
483		-=== 12.3.7 Mapping variables and value domains between VTL and SDMX ===
	551	+1.
	552	+11.
	553	+111. Mapping variables and value domains between VTL and SDMX
484	484
485	485	With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
486	486
487		-(% style="width:706.294px" %)
488		-|(% style="width:257px" %)VTL|(% style="width:446px" %)SDMX
489		-|(% style="width:257px" %)**Data Set Component**|(% style="width:446px" %)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^^
490		-|(% style="width:257px" %)**Represented Variable**|(% style="width:446px" %)**Concept** with a definite Representation
491		-|(% style="width:257px" %)**Value Domain**|(% style="width:446px" %)(((
	557	+|VTL|SDMX
	558	+|**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^^
	559	+|**Represented Variable**|**Concept** with a definite Representation
	560	+|**Value Domain**|(((
492	492	**Representation** (see the Structure
	562	+
493	493	Pattern in the Base Package)
494	494	)))
495		-|(% style="width:257px" %)**Enumerated Value Domain / Code List**|(% style="width:446px" %)**Codelist**
496		-|(% style="width:257px" %)**Code**|(% style="width:446px" %)**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
497		-|(% style="width:257px" %)**Described Value Domain**|(% style="width:446px" %)(((
	565	+|**Enumerated Value Domain / Code List**|**Codelist**
	566	+|**Code**|**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
	567	+|**Described Value Domain**|(((
498	498	non-enumerated** Representation**
	569	+
499	499	(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
500	500	)))
501		-|(% style="width:257px" %)**Value**|(% style="width:446px" %)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
502		-|(% style="width:257px" %) |(% style="width:446px" %)to a valid **value **(for non-enumerated** **Representations)
503		-|(% style="width:257px" %)**Value Domain Subset / Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
504		-|(% style="width:257px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
505		-|(% style="width:257px" %)**Described Value Domain Subset / Described Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
506		-|(% style="width:257px" %)**Set list**|(% style="width:446px" %)This abstraction does not exist in SDMX
	572	+|**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
	573	+| |to a valid **value **(for non-enumerated** **Representations)
	574	+|**Value Domain Subset / Set**|This abstraction does not exist in SDMX
	575	+|**Enumerated Value Domain Subset / Enumerated Set**|This abstraction does not exist in SDMX
	576	+|**Described Value Domain Subset / Described Set**|This abstraction does not exist in SDMX
	577	+|**Set list**|This abstraction does not exist in SDMX
507	507
508	508	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).
509	509
...	...	@@ -511,10 +511,8 @@
511	511
512	512	Therefore, it is important to be aware that some VTL operations (for example the binary operations at data set level) are consistent only if the components having the same names in the operated VTL Data Sets have also the same representation (i.e. the same Value Domain as for VTL). For example, it is possible to obtain correct results from the VTL expression
513	513
514		-> DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
	585	+DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets) if the matching components in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general representation. In simpler words, DS_a and DS_b must use the same values/codes (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
515	515
516		-if the matching components in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general representation. In simpler words, DS_a and DS_b must use the same values/codes (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
517		-
518	518	As mentioned, the property above is not enforced by construction in SDMX, and different representations of the same Concept can be not compatible one another (for example, it may happen that geo_area is represented by ISO-alpha-3 codes in DS_a and by ISO alpha-2 codes in DS_b). Therefore, it will be up to the definer of VTL
519	519
520	520	Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
...	...	@@ -521,29 +521,28 @@
521	521
522	522	It remains up to the SDMX-VTL definer also the assurance of the consistency between a VTL Ruleset defined on Variables and the SDMX Components on which the Ruleset is applied. In fact, a VTL Ruleset is expressed by means of the values of the Variables (i.e. SDMX Concepts), i.e. assuming definite representations for them (e.g. ISOalpha-3 for country). If the Ruleset is applied to SDMX Components that have the same name of the Concept they refer to but different representations (e.g. ISO-alpha-2 for country), the Ruleset cannot work properly.
523	523
524		-== 12.4 Mapping between SDMX and VTL Data Types ==
	593	+1.
	594	+11. Mapping between SDMX and VTL Data Types
	595	+111. VTL Data types
525	525
526		-=== 12.4.1 VTL Data types ===
527		-
528	528	According to the VTL User Guide the possible operations in VTL depend on the data types of the artefacts. For example, numbers can be multiplied but text strings cannot. In the VTL Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
529	529
530	530	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:
531	531
	601	+[[image:1750067055028-964.png]]
532	532
533		-[[image:1750070288958-132.png]]
	603	+==== Figure 22 – VTL Data Types ====
534	534
535		-**Figure 22 – VTL Data Types**
536		-
537	537	The VTL scalar types are in turn subdivided in basic scalar types, which are elementary (not defined in term of other data types) and Value Domain and Set scalar types, which are defined in terms of the basic scalar types.
538	538
539	539	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):
540	540
541		-[[image:1750070310572-584.png]]
	609	+==== Figure 23 – VTL Basic Scalar Types ====
542	542
543		-**Figure 23 – VTL Basic Scalar Types**
	611	+1.
	612	+11.
	613	+111. VTL basic scalar types and SDMX data types
544	544
545		-=== 12.4.2 VTL basic scalar types and SDMX data types ===
546		-
547	547	The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
548	548
549	549	The internal representation is the format used within a VTL system to represent (and process) all the scalar values of a certain type. In principle, this format is hidden and not necessarily known by users. The external representations are instead the external formats of the values of a certain basic scalar type, i.e. the formats known by the users. For example, the internal representation of the dates can be an integer counting the days since a predefined date (e.g. from 01/01/4713 BC up to 31/12/5874897 AD like in Postgres) while two possible external representations are the formats YYYY-MMGG and MM-GG-YYYY (e.g. respectively 2010-12-31 and 12-31-2010).
...	...	@@ -560,256 +560,309 @@
560	560
561	561	The opposite conversion, i.e. from VTL to SDMX, happens when a VTL result, i.e. a VTL Data Set output of a Transformation, must become a SDMX artefact (or part of it). The values of the VTL result must be converted into the desired (SDMX) external representations (data types) of the SDMX artefact.
562	562
563		-=== 12.4.3 Mapping SDMX data types to VTL basic scalar types ===
	631	+1.
	632	+11.
	633	+111. Mapping SDMX data types to VTL basic scalar types
564	564
565	565	The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
566	566
567		-(% style="width:583.294px" %)
568		-|(% style="width:360px" %)SDMX data type (BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
569		-|(% style="width:360px" %)(((
	637	+|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
	638	+|(((
570	570	String
	640	+
571	571	(string allowing any character)
572		-)))|(% style="width:221px" %)string
573		-|(% style="width:360px" %)(((
574		-Alpha
	642	+)))|string
	643	+|(((
	644	+Alpha
	645	+
575	575	(string which only allows A-z)
576		-)))|(% style="width:221px" %)string
577		-|(% style="width:360px" %)(((
	647	+)))|string
	648	+|(((
578	578	AlphaNumeric
	650	+
579	579	(string which only allows A-z and 0-9)
580		-)))|(% style="width:221px" %)string
581		-|(% style="width:360px" %)(((
	652	+)))|string
	653	+|(((
582	582	Numeric
	655	+
583	583	(string which only allows 0-9, but is not numeric so that is can having leading zeros)
584		-)))|(% style="width:221px" %)string
585		-|(% style="width:360px" %)(((
	657	+)))|string
	658	+|(((
586	586	BigInteger
	660	+
587	587	(corresponds to XML Schema xs:integer datatype; infinite set of integer values)
588		-)))|(% style="width:221px" %)integer
589		-|(% style="width:360px" %)(((
	662	+)))|integer
	663	+|(((
590	590	Integer
	665	+
591	591	(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
	667	+
592	592	(inclusive))
593		-)))|(% style="width:221px" %)integer
594		-|(% style="width:360px" %)(((
	669	+)))|integer
	670	+|(((
595	595	Long
	672	+
596	596	(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
	674	+
597	597	+9223372036854775807 (inclusive))
598		-)))|(% style="width:221px" %)integer
599		-|(% style="width:360px" %)(((
	676	+)))|integer
	677	+|(((
600	600	Short
	679	+
601	601	(corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
602		-)))|(% style="width:221px" %)integer
603		-|(% 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
604		-|(% style="width:360px" %)(((
	681	+)))|integer
	682	+|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
	683	+|(((
605	605	Float
	685	+
606	606	(corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
607		-)))|(% style="width:221px" %)number
608		-|(% style="width:360px" %)(((
	687	+)))|number
	688	+|(((
609	609	Double
	690	+
610	610	(corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
611		-)))|(% style="width:221px" %)number
612		-|(% style="width:360px" %)(((
	692	+)))|number
	693	+|(((
613	613	Boolean
	695	+
614	614	(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
	697	+
615	615	binary-valued logic: {true, false})
616		-)))|(% style="width:221px" %)boolean
617		-|(% style="width:360px" %)(((
	699	+)))|boolean
	700	+|(((
618	618	URI
	702	+
619	619	(corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
620		-)))|(% style="width:221px" %)string
621		-|(% style="width:360px" %)(((
	704	+)))|string
	705	+|(((
622	622	Count
	707	+
623	623	(an integer following a sequential pattern, increasing by 1 for each occurrence)
624		-)))|(% style="width:221px" %)integer
625		-|(% style="width:360px" %)(((
	709	+)))|integer
	710	+|(((
626	626	InclusiveValueRange
	712	+
627	627	(decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
628		-)))|(% style="width:221px" %)number
629		-|(% style="width:360px" %)(((
	714	+)))|number
	715	+|(((
630	630	ExclusiveValueRange
	717	+
631	631	(decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
632		-)))|(% style="width:221px" %)number
633		-|(% style="width:360px" %)(((
	719	+)))|number
	720	+|(((
634	634	Incremental
	722	+
635	635	(decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
636		-)))|(% style="width:221px" %)number
637		-|(% style="width:360px" %)(((
	724	+)))|number
	725	+|(((
638	638	ObservationalTimePeriod
	727	+
639	639	(superset of StandardTimePeriod and TimeRange)
640		-)))|(% style="width:221px" %)time
641		-|(% style="width:360px" %)(((
	729	+)))|time
	730	+|(((
642	642	StandardTimePeriod
	732	+
643	643	(superset of BasicTimePeriod and ReportingTimePeriod)
644		-)))|(% style="width:221px" %)time
645		-|(% style="width:360px" %)(((
	734	+)))|time
	735	+|(((
646	646	BasicTimePeriod
	737	+
647	647	(superset of GregorianTimePeriod and DateTime)
648		-)))|(% style="width:221px" %)date
649		-|(% style="width:360px" %)(((
	739	+)))|date
	740	+|(((
650	650	GregorianTimePeriod
	742	+
651	651	(superset of GregorianYear, GregorianYearMonth, and GregorianDay)
652		-)))|(% style="width:221px" %)date
653		-|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
654		-|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
655		-|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
656		-|(% style="width:360px" %)(((
	744	+)))|date
	745	+|GregorianYear (YYYY)|date
	746	+|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
	747	+|GregorianDay (YYYY-MM-DD)|date
	748	+|(((
657	657	ReportingTimePeriod
	750	+
658	658	(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
659		-)))|(% style="width:221px" %)time_period
660		-|(% style="width:360px" %)(((
	752	+)))|time_period
	753	+|(((
661	661	ReportingYear
	755	+
662	662	(YYYY-A1 – 1 year period)
663		-)))|(% style="width:221px" %)time_period
664		-|(% style="width:360px" %)(((
	757	+)))|time_period
	758	+|(((
665	665	ReportingSemester
	760	+
666	666	(YYYY-Ss – 6 month period)
667		-)))|(% style="width:221px" %)time_period
668		-|(% style="width:360px" %)(((
	762	+)))|time_period
	763	+|(((
669	669	ReportingTrimester
	765	+
670	670	(YYYY-Tt – 4 month period)
671		-)))|(% style="width:221px" %)time_period
672		-|(% style="width:360px" %)(((
	767	+)))|time_period
	768	+|(((
673	673	ReportingQuarter
	770	+
674	674	(YYYY-Qq – 3 month period)
675		-)))|(% style="width:221px" %)time_period
676		-|(% style="width:360px" %)(((
	772	+)))|time_period
	773	+|(((
677	677	ReportingMonth
	775	+
678	678	(YYYY-Mmm – 1 month period)
679		-)))|(% style="width:221px" %)time_period
680		-|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
681		-|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
682		-|(% style="width:360px" %)(((
	777	+)))|time_period
	778	+|ReportingWeek|time_period
	779	+| (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|
	780	+|(((
683	683	ReportingDay
	782	+
684	684	(YYYY-Dddd – 1 day period)
685		-)))|(% style="width:221px" %)time_period
686		-|(% style="width:360px" %)(((
	784	+)))|time_period
	785	+|(((
687	687	DateTime
	787	+
688	688	(YYYY-MM-DDThh:mm:ss)
689		-)))|(% style="width:221px" %)date
690		-|(% style="width:360px" %)(((
	789	+)))|date
	790	+|(((
691	691	TimeRange
	792	+
692	692	(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
693		-)))|(% style="width:221px" %)time
694		-|(% style="width:360px" %)(((
	794	+)))|time
	795	+|(((
695	695	Month
	797	+
696	696	(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
697		-)))|(% style="width:221px" %)string
698		-|(% style="width:360px" %)(((
	799	+)))|string
	800	+|(((
699	699	MonthDay
	802	+
700	700	(~-~-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)
701		-)))|(% style="width:221px" %)string
702		-|(% style="width:360px" %)(((
	804	+)))|string
	805	+|(((
703	703	Day
	807	+
704	704	(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
705		-)))|(% style="width:221px" %)string
706		-|(% style="width:360px" %)(((
	809	+)))|string
	810	+|(((
707	707	Time
	812	+
708	708	(hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
709		-)))|(% style="width:221px" %)string
710		-|(% style="width:360px" %)(((
	814	+)))|string
	815	+|(((
711	711	Duration
	817	+
712	712	(corresponds to XML Schema xs:duration datatype)
713		-)))|(% style="width:221px" %)duration
714		-|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
715		-|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
716		-|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
717		-|(% style="width:360px" %)DataSetReference|(% style="width:221px" %)Metadata type – not applicable
	819	+)))|duration
	820	+|XHTML|Metadata type – not applicable
	821	+|KeyValues|Metadata type – not applicable
	822	+|IdentifiableReference|Metadata type – not applicable
	823	+|DataSetReference|Metadata type – not applicable
718	718
719		-**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
	825	+додол
720	720
	827	+==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
	828	+
721	721	When VTL takes in input SDMX artefacts, it is assumed that a type conversion according to the table above always happens. In case a different VTL basic scalar type is desired, it can be achieved in the VTL program taking in input the default VTL basic scalar type above and applying to it the VTL type conversion features (see the implicit and explicit type conversion and the "cast" operator in the VTL Reference Manual).
722	722
723		-=== 12.4.4 Mapping VTL basic scalar types to SDMX data types ===
	831	+1.
	832	+11.
	833	+111. Mapping VTL basic scalar types to SDMX data types
724	724
725	725	The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
726	726
727		-(% style="width:748.294px" %)
728		-|(% style="width:164px" %)(((
729		-VTL basic scalar type
730		-)))|(% style="width:304px" %)(((
	837	+|(((
	838	+VTL basic
	839	+
	840	+scalar type
	841	+)))|(((
731	731	Default SDMX data type
732		-(BasicComponentDataType)
733		-)))|(% style="width:277px" %)Default output format
734		-|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
735		-|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
736		-|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
737		-|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
738		-|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
739		-|(% style="width:164px" %)time_period|(% style="width:304px" %)(((
	843	+
	844	+(BasicComponentDataType
	845	+
	846	+)
	847	+)))|Default output format
	848	+|String|String|Like XML (xs:string)
	849	+|Number|Float|Like XML (xs:float)
	850	+|Integer|Integer|Like XML (xs:int)
	851	+|Date|DateTime|YYYY-MM-DDT00:00:00Z
	852	+|Time|StandardTimePeriod|<date>/<date> (as defined above)
	853	+|time_period|(((
740	740	ReportingTimePeriod
	855	+
741	741	(StandardReportingPeriod)
742		-)))|(% style="width:277px" %)(((
	857	+)))|(((
743	743	YYYY-Pppp
	859	+
744	744	(according to SDMX )
745	745	)))
746		-|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
747		-|(% style="width:164px" %)Boolean|(% style="width:304px" %)Boolean|(% style="width:277px" %)Like XML (xs:boolean) with the values "true" or "false"
	862	+|Duration|Duration|Like XML (xs:duration) PnYnMnDTnHnMnS
	863	+|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
748	748
749		-**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
	865	+==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
750	750
751		-In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section Transformations and Expressions of the SDMX information model).
	867	+In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section
752	752
	869	+Transformations and Expressions of the SDMX information model).
	870	+
753	753	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.
754	754
755		-(% style="width:717.294px" %)
756		-|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
757		-|(% colspan="2" style="width:714px" %)
758		-|(% colspan="2" style="width:714px" %)Number
759		-|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
760		-|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
761		-|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
762		-|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
763		-|(% style="width:122px" %) |(% style="width:591px" %)
764		-|(% colspan="2" style="width:714px" %)Time and duration
765		-|(% style="width:122px" %)C|(% style="width:591px" %)century
766		-|(% style="width:122px" %)Y|(% style="width:591px" %)year
767		-|(% style="width:122px" %)S|(% style="width:591px" %)semester
768		-|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
769		-|(% style="width:122px" %)M|(% style="width:591px" %)month
770		-|(% style="width:122px" %)W|(% style="width:591px" %)week
771		-|(% style="width:122px" %)D|(% style="width:591px" %)day
772		-|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
773		-|(% style="width:122px" %)M|(% style="width:591px" %)minute
774		-|(% style="width:122px" %)S|(% style="width:591px" %)second
775		-|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
776		-|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
777		-|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
778		-|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
779		-|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
780		-|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
781		-|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
782		-|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
783		-|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
784		-|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
785		-|(% style="width:122px" %) |(% style="width:591px" %)
786		-|(% colspan="2" style="width:714px" %)String
787		-|(% style="width:122px" %)X|(% style="width:591px" %)any string character
788		-|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
789		-|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
790		-|(% style="width:122px" %) |(% style="width:591px" %)
791		-|(% colspan="2" style="width:714px" %)Boolean
792		-|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
793		-|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
794		-|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
795		-|(% style="width:122px" %) |(% style="width:591px" %)
796		-|(% colspan="2" style="width:714px" %)Other qualifiers
797		-|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
798		-|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
799		-|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
800		-|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
801		-|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
802		-|(% style="width:122px" %) |(% style="width:591px" %)
	873	+|(% colspan="2" %)VTL special characters for the formatting masks
	874	+|(% colspan="2" %)
	875	+|(% colspan="2" %)Number
	876	+|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
	877	+|E|one numeric digit (for the exponent of the scientific notation)
	878	+|. (dot)|possible separator between the integer and the decimal parts.
	879	+|, (comma)|possible separator between the integer and the decimal parts.
	880	+| |
	881	+|(% colspan="2" %)Time and duration
	882	+|C|century
	883	+|Y|year
	884	+|S|semester
	885	+|Q|quarter
	886	+|M|month
	887	+|W|week
	888	+|D|day
	889	+|h|hour digit (by default on 24 hours)
	890	+|M|minute
	891	+|S|second
	892	+|D|decimal of second
	893	+|P|period indicator (representation in one digit for the duration)
	894	+|P|number of the periods specified in the period indicator
	895	+|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
	896	+|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
	897	+|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
	898	+|Month|lowercase textual representation of the month (e.g., january)
	899	+|Day|lowercase textual representation of the month (e.g., monday)
	900	+|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
	901	+|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
	902	+| |
	903	+|(% colspan="2" %)String
	904	+|X|any string character
	905	+|Z|any string character from "A" to "z"
	906	+|9|any string character from "0" to "9"
	907	+| |
	908	+|(% colspan="2" %)Boolean
	909	+|B|Boolean using "true" for True and "false" for False
	910	+|1|Boolean using "1" for True and "0" for False
	911	+|0|Boolean using "0" for True and "1" for False
	912	+| |
	913	+|(% colspan="2" %)Other qualifiers
	914	+|*|an arbitrary number of digits (of the preceding type)
	915	+|+|at least one digit (of the preceding type)
	916	+|( )|optional digits (specified within the brackets)
	917	+|\|prefix for the special characters that must appear in the mask
	918	+|N|fixed number of digits used in the preceding textual representation of the month or the day
	919	+| |
803	803
804	804	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}}.
805	805
806		-=== 12.4.3 Null Values ===
	923	+1.
	924	+11.
	925	+111. Null Values
807	807
808	808	In the conversions from SDMX to VTL it is assumed by default that a missing value in SDMX becomes a NULL in VTL. After the conversion, the NULLs can be manipulated through the proper VTL operators.
809	809
810	810	On the other side, the VTL programs can produce in output NULL values for Measures and Attributes (Null values are not allowed in the Identifiers). In the conversion from VTL to SDMX, it is assumed that a NULL in VTL becomes a missing value in SDMX. In the conversion from VTL to SDMX, the default assumption can be overridden, separately for each VTL basic scalar type, by specifying which the value that represents the NULL in SDMX is. This can be specified in the attribute "nullValue" of the CustomType artefact (see also the section Transformations and Expressions of the SDMX information model). A CustomType belongs to a CustomTypeScheme, which can be referenced by one or more TransformationScheme (i.e. VTL programs). The overriding assumption is applied for all the SDMX Dataflows calculated in the TransformationScheme.
811	811
812		-=== 12.4.5 Format of the literals used in VTL Transformations ===
	931	+1.
	932	+11.
	933	+111. Format of the literals used in VTL Transformations
813	813
814	814	The VTL programs can contain literals, i.e. specific values of certain data types written directly in the VTL definitions or expressions. The VTL does not prescribe a specific format for the literals and leave the specific VTL systems and the definers of VTL Transformations free of using their preferred formats.
815	815
...	...	@@ -823,6 +823,42 @@
823	823
824	824	In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
825	825
	947	+
826	826	----
827	827
	950	+[[~[1~]>>path:#_ftnref1]] The Validation and Transformation Language is a standard language designed and published under the SDMX initiative. VTL is described in the VTL User and Reference Guides available on the SDMX website [[https:~~/~~/sdmx.org>>url:https://sdmx.org/]][[.>>url:https://sdmx.org/]]
	951	+
	952	+[[~[2~]>>path:#_ftnref2]] In this chapter, in order to distinguish VTL and SDMX model artefacts, the VTL ones are written in the Arial font while the SDMX ones in Courier New
	953	+
	954	+[[~[3~]>>path:#_ftnref3]] See also the section "VTL-DL Rulesets" in the VTL Reference Manual.
	955	+
	956	+[[~[4~]>>path:#_ftnref4]] The VTLMappings are used also for User Defined Operators (UDO). Although UDOs are envisaged to be defined on generic operands, so that the specific artefacts to be manipulated are passed as parameters at their invocation, it is also possible that an UDO invokes directly some specific SDMX artefacts. These SDMX artefacts have to be mapped to the corresponding aliases used in the definition of the UDO through the VtlMappingScheme and VtlMapping classes as well.
	957	+
	958	+[[~[5~]>>path:#_ftnref5]] For a complete description of the structure of the URN see the SDMX 2.1 Standards - Section 5 - Registry Specifications, paragraph 6.2.2 ("Universal Resource Name (URN)").
	959	+
	960	+[[~[6~]>>path:#_ftnref6]] The container-object-id can repeat and may not be present.
	961	+
	962	+[[~[7~]>>path:#_ftnref7]] i.e., the artefact belongs to a maintainable class
	963	+
	964	+[[~[8~]>>path:#_ftnref8]] 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.
	965	+
	966	+[[~[9~]>>path:#_ftnref9]] For the syntax of the VTL operators see the VTL Reference Manual
	967	+
	968	+[[~[10~]>>path:#_ftnref10]] In case the invoked artefact is a VTL component, which can be invoked only within the invocation of a VTL data set (SDMX Dataflow), the specific SDMX class-name (e.g. Dimension, TimeDimension, Measure or DataAttribute) can be deduced from the data structure of the SDMX Dataflow, which the component belongs to.
	969	+
	970	+[[~[11~]>>path:#_ftnref11]] If the Agency is composite (for example AgencyA.Dept1.Unit2), the agency is considered different even if only part of the composite name is different (for example AgencyA.Dept1.Unit3 is a different Agency than the previous one). Moreover the agency-id cannot be omitted in part (i.e., if a TransformationScheme owned by AgencyA.Dept1.Unit2 references an artefact coming from AgencyA.Dept1.Unit3, the specification of the agency-id becomes mandatory and must be complete, without omitting the possibly equal parts like AgencyA.Dept1)
	971	+
	972	+[[~[12~]>>path:#_ftnref12]] 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.
	973	+
	974	+[[~[13~]>>path:#_ftnref13]] The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC
	975	+
	976	+[[~[14~]>>path:#_ftnref14]] Rulesets of this kind cannot be reused when the referenced Concept has a different representation.
	977	+
	978	+[[~[15~]>>path:#_ftnref15]] See also the section "VTL-DL Rulesets" in the VTL Reference Manual.
	979	+
	980	+[[~[16~]>>path:#_ftnref16]] If a calculated artefact is persistent, it needs a persistent definition, i.e. a SDMX definition in a SDMX environment. In addition, possible calculated artefact that are not persistent may require a SDMX definition, for example when the result of a nonpersistent calculation is disseminated through SDMX tools (like an inquiry tool).
	981	+
	982	+[[~[17~]>>path:#_ftnref17]] See the VTL 2.0 User Manual
	983	+
	984	+
828	828	{{putFootnotes/}}

1750070288958-132.png

Author

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

Size

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

Content

1750070310572-584.png

Author

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

Size

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

Content

1750067055028-964.png

Author

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

Size

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

Content