Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 5.2
edited by Helena
on 2025/06/16 14:04
Change comment: There is no comment for this version
To version 1.9
edited by Helena
on 2025/06/16 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
1 -Artefact|Attribute|Code|Code list|Component|Concept scheme|Currency|Data set|Data structure definition|Dataflow|Dimension|Facet|Maintainable artefact|Measure|Nameable artefact|Representation|SDMX Information Model|Statistical data and metadata exchange|Structural metadata|Validation and transformation language
Content
... ... @@ -2,551 +2,616 @@
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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]) 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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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 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 -* exchange of the definition of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations describing the calculation algorithms);
11 -* compilation and execution of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] algorithms, either interpreting the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations or translating them in whatever other computer language is deemed as appropriate.
11 +* 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 +* compilation and execution of VTL algorithms, either interpreting the VTL Transformations or translating them in whatever other computer language is deemed as appropriate.
12 12  
13 -It is important to note that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] has its own information model (IM), derived from the Generic Statistical Information Model (GSIM) and described in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] User Guide. The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] IM is designed to be compatible with more standards, like [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], DDI (Data Documentation Initiative) and GSIM, and includes the model [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that can be manipulated (inputs and/or outputs of Transformations, e.g. "[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]", "Data Structure") and the model [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that allow the definition of the transformation algorithms (e.g. "Transformation", "Transformation Scheme").
14 +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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] language can be applied to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] by (% style="color:#e74c3c" %)mapping(%%) the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] IM model [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] to the model [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] can be used in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] as inputs and/or outputs of Transformations. It is important to be aware that the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] do not always have the same names in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] IMs, nor do they always have the same meaning. The more evident example is given by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] and the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] "[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]", which do not correspond one another: as a matter of fact, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] "[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]" (% style="color:#e74c3c" %)maps(%%) to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] "[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]", while the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] "[[Dataset>>doc:sdmx:Glossary.Data set.WebHome]]" has no explicit (% style="color:#e74c3c" %)mapping(%%) to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (such an abstraction is not needed in the definition of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations). A [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] "[[Dataset>>doc:sdmx:Glossary.Data set.WebHome]]", however, is an instance of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] "[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]" and can be the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] on which the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] transformations are executed (i.e., the Transformations are defined on [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and are applied to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] 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 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 -The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] programs (Transformation Schemes) are represented in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] through the TransformationScheme maintainable class which is composed of Transformation ([[nameable artefact>>doc:sdmx:Glossary.Nameable artefact.WebHome]]). Each Transformation assigns the outcome of the evaluation of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] expression to a result.
18 +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 -This section does not explain the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] language or any of the content published in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] guides. Rather, this is a description of how the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can be used in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] context and applied to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].
20 +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 ===
26 +The VTL can manipulate SDMX artefacts (or objects) by referencing them through predefined conventional names (aliases).
24 24  
25 -The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can manipulate [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] (or objects) by referencing them through predefined conventional names (aliases).
28 +The alias of an SDMX artefact can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
26 26  
27 -The alias of an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
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 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 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.
28 28  
29 -In any case, the aliases used in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations have to be (% style="color:#e74c3c" %)mapped(%%) to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] through the VtlMappingScheme and VtlMapping classes (see the section of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] IM relevant to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]). A VtlMapping allows specifying the aliases to be used in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. A VtlMappingScheme is a container for zero or more VtlMapping.
32 +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.
30 30  
31 -The correspondence between an alias and a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] must be one-to-one, meaning that a generic alias identifies one and just one [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] while a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is identified by one and just one alias. In other words, within a VtlMappingScheme an [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] can have just one alias and different [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] cannot have the same alias.
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 -This approach has the advantage that in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] code the URN of the referenced [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] is directly intelligible by a human reader but has the drawback that the references are verbose.
40 +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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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 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 -* [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name
45 +* SDMX-IM-package-name
43 43  * class-name
44 44  * agency-id
45 45  * maintainedobject-id
46 -* maintainedobject-(% style="color:#e74c3c" %)version
47 -* container-object-id{{footnote}}The container-object-id can repeat and may not be present.{{/footnote}}
49 +* maintainedobject-version
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 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>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.class-name=agency-id:maintainedobject-id (maintainedobject-(% style="color:#e74c3c" %)version(%%)).*container-object-id.object-id
55 +SDMXprefix.SDMX-IM-package-name.class-name=agency-id:maintainedobject-id
53 53  
54 -The **SDMXprefix** is "urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org", always the same for all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].
57 +(maintainedobject-version).*container-object-id.object-id
55 55  
56 -The [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name** **is the concatenation of the string** **"[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel." with the package-name, which the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] belongs to. For example, for referencing a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name is "[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.datastructure", because the class [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] belongs to the package "datastructure".
59 +The **SDMXprefix** is "urn:sdmx:org", always the same for all SDMX artefacts.
57 57  
58 -The class-name is the name of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object class, which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object belongs to (e.g., for referencing a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] the class-name is "[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]"). The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can reference [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that belong to the classes [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], DataAttribute, (% style="color:#e74c3c" %)Concept(%%), Codelist.
61 +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 59  
60 -The agency-id is the acronym of the agency that owns the definition of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]], for example for the Eurostat [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] the agency-id is "ESTAT"). The agency-id can be composite (for example AgencyA.Dept1.Unit2).
63 +The class-name is the name of the SDMX object class, which the SDMX object belongs to (e.g., for referencing a Dataflow the class-name is "Dataflow"). The VTL can reference SDMX artefacts that belong to the classes Dataflow, Dimension, TimeDimension, Measure, DataAttribute, Concept, Codelist.
61 61  
62 -The maintainedobject-id is the name of the maintained object which the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] belongs to, and in case the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] itself is maintainable{{footnote}}i.e., the artefact belongs to a maintainable class{{/footnote}}, coincides with the name of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]]. Therefore the maintainedobject-id depends on the class of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]]:
65 +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).
63 63  
64 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], which is a maintainable class, the maintainedobject-id is the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] name ([[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]-id);
65 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], TimeDimension or DataAttribute, which are not maintainable and belong to the
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 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:
66 66  
67 -DataStructure maintainable class, the maintainedobject-id is the name of the DataStructure (dataStructure-id) which the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] belongs to;
69 +* if the artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the Dataflow name (dataflow-id);
70 +* if the artefact is a Dimension, Measure, TimeDimension or DataAttribute, which are not maintainable and belong to the
68 68  
69 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a (% style="color:#e74c3c" %)Concept(%%), which is not maintainable and belongs to the ConceptScheme maintainable class, the maintainedobject-id is the name of the ConceptScheme (conceptScheme-id) which the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] belongs to;
70 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a Codelist, which is a maintainable class, the maintainedobject-id is the Codelist name (codelist-id).
72 +DataStructure maintainable class, the maintainedobject-id is the name of the DataStructure (dataStructure-id) which the artefact belongs to;
71 71  
72 -The maintainedobject-(% style="color:#e74c3c" %)version(%%) is the (% style="color:#e74c3c" %)version(%%), according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintained object which the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] belongs to (for example, possible (% style="color:#e74c3c" %)versions(%%) might be 1.0, 2.3, 1.0.0, 2.1.0 or 3.1.2).
74 +* if the artefact is a Concept, which is not maintainable and belongs to the ConceptScheme maintainable class, the maintainedobject-id is the name of the ConceptScheme (conceptScheme-id) which the artefact belongs to;
75 +* if the artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the Codelist name (codelist-id).
73 73  
74 -The container-object-id does not apply to the classes that can be referenced in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, therefore is not present in their URN.
77 +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).
75 75  
76 -The object-id is the name of the non-[[maintainable artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] (when the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is maintainable its name is already specified as the maintainedobject-id, see above), in particular it has to be specified:
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
77 77  
78 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] or DataAttribute (the object-id is the name of one of the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] above, which are data structure components)
79 -* if the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a (% style="color:#e74c3c" %)Concept(%%) (the object-id is the name of the (% style="color:#e74c3c" %)Concept(%%))
81 +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:
80 80  
81 -For example, by using the URN, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformation that sums two [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] DF1 and DF2 and assigns the result to a third persistent [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], that their (% style="color:#e74c3c" %)version(%%) is 1.0.0 and their Agency is AG, would be written as
83 +* if the artefact is a Dimension, TimeDimension, Measure or
82 82  
83 -{{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}}:
85 +DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
84 84  
85 -> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
86 -> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
87 -> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
87 +* if the artefact is a Concept (the object-id is the name of the Concept)
88 88  
89 -=== 12.2.3 Abbreviation of the URN ===
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 wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[8~]^^>>path:#_ftn8]](%%):
90 90  
91 -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>>doc:sdmx:Glossary.Artefact.WebHome]] remain intelligible in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] code by a human reader.
91 +'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
92 92  
93 -The URN can be abbreviated by omitting the parts that are not essential for the identification of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] or that can be deduced from other available information, including the context in which the invocation is made. The possible abbreviations are described below.
93 +'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
94 94  
95 -* The SDMXprefix can be omitted for all the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] objects, because it is a prefixed string (urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org), always the same for [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] objects.
96 -* The [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-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>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] packages and classes that allows this deduction is in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Standards - Section 5 - Registry Specifications, paragraph 6.2.3). In particular, considering the object classes of the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can reference, the package is:
97 -** "datastructure" for the classes [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], DataAttribute,
98 -** "conceptscheme" for the class (% style="color:#e74c3c" %)Concept(%%),
99 -** "codelist" for the class Codelist.
100 -* The class-name can be omitted as it can be deduced from the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] invocation. In particular, starting from the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] class of the invoked [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] (e.g. [[dataset>>doc:sdmx:Glossary.Data set.WebHome]], [[component>>doc:sdmx:Glossary.Component.WebHome]], identifier, [[measure>>doc:sdmx:Glossary.Measure.WebHome]], [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]], variable, valuedomain), which is known given the syntax of the invoking [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operator{{footnote}}For the syntax of the VTL operators see the VTL Reference Manual{{/footnote}}, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] class can be deduced from the mapping rules between [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (see the section "Mapping between [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]" 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}}.
101 -* 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>>doc:sdmx:Glossary.Artefact.WebHome]] 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>>doc:sdmx:Glossary.Artefact.WebHome]] 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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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).
102 -* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted:
103 -** if the referenced [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], which is a maintainable class, the maintainedobject-id is the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]-id and obviously cannot be omitted;
104 -** if the referenced [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], 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>>doc:sdmx:Glossary.Component.WebHome]] are always invoked within the invocation of a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], whose dataStructure-id can be deduced from the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural definitions;
105 -** if the referenced [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a (% style="color:#e74c3c" %)Concept(%%), which is not maintainable and belong to the ConceptScheme maintainable class, the maintained object is the conceptScheme-id and cannot be omitted;
106 -** if the referenced [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
107 -* When the maintainedobject-id is omitted, the maintainedobject-(% style="color:#e74c3c" %)version(%%) is omitted too. When the maintainedobject-id is not omitted and the maintainedobject-(% style="color:#e74c3c" %)version(%%) is omitted, the (% style="color:#e74c3c" %)version(%%) 1.0 is assumed by default.
108 -* As said, the container-object-id does not apply to the classes that can be referenced in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, therefore is not present in their URN
109 -* The object-id does not exist for the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] belonging to the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], and Codelist classes, while it exists and cannot be omitted for the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] belonging to the classes [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], DataAttribute and (% style="color:#e74c3c" %)Concept(%%), as for them the object-id is the main identifier of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]]
95 +'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
110 110  
97 +1.
98 +11.
99 +111. Abbreviation of the URN
100 +
101 +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.
102 +
103 +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.
104 +
105 +* 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.
106 +* 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:
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 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){{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}}.
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{{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).
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 +*
116 +** 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;
117 +** if the referenced artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
118 +* 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.
119 +* As said, the container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
120 +* The object-id does not exist for the artefacts belonging to the Dataflow, and Codelist classes, while it exists and cannot be omitted for the artefacts belonging to the classes Dimension, TimeDimension, Measure, DataAttribute and Concept, as for them the object-id is the main identifier of the artefact
121 +
111 111  The simplified object identifier is obtained by omitting all the first part of the URN, including the special characters, till the first part not omitted.
112 112  
113 113  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
114 114  
115 -> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
116 -> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
117 -> '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)' :=
118 118  
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 +
119 119  by omitting all the non-essential parts would become simply:
120 120  
121 -> DFR : = DF1 + DF2
134 +DFR := DF1 + DF2
122 122  
123 123  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}}:
124 124  
125 -> '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)'
126 126  
127 127  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^^:
128 128  
129 -> CL_FREQ
142 +CL_FREQ
130 130  
131 -As for the references to the [[components>>doc:sdmx:Glossary.Component.WebHome]], 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>>doc:sdmx:Glossary.Component.WebHome]] is SECTOR, is the following:
144 +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:
132 132  
133 -> '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
134 134  
148 +ECTOR'
149 +
135 135  The corresponding fully abbreviated reference, if made from a TransformationScheme belonging to AG, would become simply:
136 136  
137 -> SECTOR
152 +SECTOR
138 138  
139 -For example, the Transformation for renaming the [[component>>doc:sdmx:Glossary.Component.WebHome]] SECTOR of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] 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{{footnote}}The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC{{/footnote}}:
140 140  
141 -> '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]
142 142  
143 -In the references to the (% style="color:#e74c3c" %)Concepts(%%), which can exist for example in the definition of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Rulesets, at least the conceptScheme-id and the (% style="color:#e74c3c" %)concept(%%)-id must be specified.
158 +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.
144 144  
145 -An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the (% style="color:#e74c3c" %)concept(%%)-id is SECTOR, is the following:
160 +An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
146 146  
147 -> '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'
148 148  
149 149  The corresponding fully abbreviated reference, if made from a RulesetScheme belonging to AG, would become simply:
150 150  
151 -> CS1(1.0.0).SECTOR
166 +CS1(1.0.0).SECTOR
152 152  
153 -The [[Codes>>doc:sdmx:Glossary.Code.WebHome]] 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>>doc:sdmx:Glossary.Measure.WebHome]] of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF1 are between 0 and 25000 can be written like follows:
168 +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:
154 154  
155 -> 'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
170 +'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
156 156  
157 -The [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] ([[Component>>doc:sdmx:Glossary.Component.WebHome]], (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] syntax. In the Transformation above, for example, the values 0 and 2500 are compared to the values of the [[measures>>doc:sdmx:Glossary.Measure.WebHome]] of DF1(1.0.0).
172 +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).
158 158  
159 -=== 12.2.4 User-defined alias ===
174 +1.
175 +11.
176 +111. User-defined alias
160 160  
161 -The third possibility for referencing [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] statements is to use user-defined aliases not related to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] URN of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]].
178 +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.
162 162  
163 -This approach gives preference to the use of symbolic names for the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. As a consequence, in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[code>>doc:sdmx:Glossary.Code.WebHome]] the referenced [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] may become not directly intelligible by a human reader. In any case, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] aliases are associated to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] URN through the VtlMappingScheme and VtlMapping classes. These classes provide for structured references to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] whatever kind of reference is used in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] statements (URN, abbreviated URN or user-defined aliases).
180 +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).
164 164  
165 -=== 12.2.5 References to SDMX artefacts from VTL Rulesets ===
182 +1.
183 +11.
184 +111. References to SDMX artefacts from VTL Rulesets
166 166  
167 -The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Rulesets allow defining sets of reusable Rules that can be applied by some [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: when the Country is USA then the [[Currency>>doc:sdmx:Glossary.Currency.WebHome]] is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
186 +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.
168 168  
169 -The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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.
188 +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.
170 170  
171 -In the signature, given the mapping between [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] better described in the following paragraphs, a reference to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Value Domain becomes a reference to a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Codelist, while a reference to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Represented Variable becomes a reference to a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concept(%%), assuming for it a definite [[representation>>doc:sdmx:Glossary.Representation.WebHome]]{{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{{footnote}}Rulesets of this kind cannot be reused when the referenced Concept has a different representation.{{/footnote}}.
172 172  
173 -In general, for referencing [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Codelists and (% style="color:#e74c3c" %)Concepts(%%), the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] 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 (% style="color:#e74c3c" %)mapped(%%) to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].{{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.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
174 174  
175 -In the body of the Rulesets, the [[Codes>>doc:sdmx:Glossary.Code.WebHome]] and in general all the Values can be written without any other specification, because the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]], which the Values are referred (Codelist, (% style="color:#e74c3c" %)Concept(%%)) to can be deduced from the Ruleset signature.
194 +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.
176 176  
177 -== 12.3 Mapping between SDMX and VTL artefacts ==
196 +1.
197 +11. Mapping between SDMX and VTL artefacts
198 +111. When the mapping occurs
178 178  
179 -=== 12.3.1. When the mapping occurs ===
200 +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 -The mapping methods between the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object classes allow transforming a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition in a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] one and vice-versa for the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] to be manipulated. It should be remembered that [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] programs (i.e. Transformation Schemes) are represented in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] through the TransformationScheme maintainable class which is composed of Transformations ([[nameable artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]]). Each Transformation assigns the outcome of the evaluation of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] expression to a result: the input operands of the expression and the result can be [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. Every time a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object is referenced in a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformation as an input operand, there is the need to generate a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] definition of the object, so that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operations can take place. This can be made starting from the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition and applying a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping method in the direction from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]. The possible mapping methods from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] are described in the following paragraphs and are conceived to allow the automatic deduction of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] definition of the object from the knowledge of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition.
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{{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}}.
182 182  
183 -In the opposite direction, every time an object calculated by means of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] must be treated as a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object (for example for exchanging it through [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]), there is the need of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition of the object, so that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] operations can take place. The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition is needed for the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] objects for which a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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}}.
204 +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 -The mapping methods from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] are described in the following paragraphs as well, however they do not allow the complete [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition to be automatically deduced from the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] definition, more than all because the former typically contains additional information in respect to the latter. For example, the definition of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] includes also some mandatory information not available in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (like the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] to which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:sdmx:Glossary.Component.WebHome]] refer, the ‘usage’ and ‘attributeRelationship’ for the DataAttributes and so on). Therefore the mapping methods from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provide only a general guidance for generating [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definitions properly starting from the information available in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], independently of how the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definition it is actually generated (manually, automatically or part and part).
206 +1.
207 +11.
208 +111. General mapping of VTL and SDMX data structures
186 186  
187 -=== 12.3.2 General mapping of VTL and SDMX data structures ===
210 +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}}.
188 188  
189 -This section makes reference to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] "Model for data and their structure"{{footnote}}See the VTL 2.0 User Manual{{/footnote}} and the correspondent [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] "Data Structure Definition"{{footnote}}See the SDMX Standards Section 2 – Information Model{{/footnote}}.
212 +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  
191 -The main type of [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can manipulate is the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]], which in general is (% style="color:#e74c3c" %)mapped(%%) to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. This means that a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformation, in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] context, expresses the algorithm for calculating a derived [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] starting from some already existing [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] (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}}
214 +While the VTL Transformations are defined in term of Dataflow definitions, they are assumed to be executed on instances of such Dataflows, provided at runtime to the VTL engine (the mechanism for identifying the instances to be processed are not part of the VTL specifications and depend on the implementation of the VTL-based systems). As already said, the SDMX Datasets are instances of SDMX Dataflows, therefore a VTL Transformation defined on some SDMX Dataflows can be applied on some corresponding SDMX Datasets.
192 192  
193 -While the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations are defined in term of [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] definitions, they are assumed to be executed on instances of such [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], provided at runtime to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] engine (the mechanism for identifying the instances to be processed are not part of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] specifications and depend on the implementation of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]-based systems). As already said, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Datasets>>doc:sdmx:Glossary.Data set.WebHome]] are instances of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], therefore a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformation defined on some [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] can be applied on some corresponding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Datasets>>doc:sdmx:Glossary.Data set.WebHome]].
216 +A VTL Data Set is structured by one and just one Data Structure and a VTL Data Structure can structure any number of Data Sets. Correspondingly, in the SDMX context a SDMX Dataflow is structured by one and just one DataStructureDefinition and one DataStructureDefinition can structure any number of Dataflows.
194 194  
195 -A [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] is structured by one and just one Data Structure and a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Structure can structure any number of [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]]. Correspondingly, in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] context a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] is structured by one and just one DataStructureDefinition and one DataStructureDefinition can structure any number of [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]].
218 +A VTL Data Set has a Data Structure made of Components, which in turn can be Identifiers, Measures and Attributes. Similarly, a SDMX DataflowDefinition has a DataStructureDefinition made of components that can be DimensionComponents, Measure and DataAttributes. In turn, a SDMX DimensionComponent can be a Dimension or a TimeDimension.
196 196  
197 -A [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] has a Data Structure made of [[Components>>doc:sdmx:Glossary.Component.WebHome]], which in turn can be Identifiers, [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] and [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. Similarly, a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataflowDefinition has a DataStructureDefinition made of [[components>>doc:sdmx:Glossary.Component.WebHome]] that can be DimensionComponents, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] and DataAttributes. In turn, a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponent can be a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] or a TimeDimension.
220 +Correspondingly, in the SDMX implementation of the VTL, the VTL Identifiers can be (optionally) distinguished in similar sub-classes (Simple Identifier, Time Identifier) even if such a distinction is not evidenced in the VTL IM.
198 198  
199 -Correspondingly, in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] implementation of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Identifiers can be (optionally) distinguished in similar sub-classes (Simple Identifier, Time Identifier) even if such a distinction is not evidenced in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] IM.
200 -
201 201  The possible mapping options are described in more detail in the following sections.
202 202  
203 -=== 12.3.3 Mapping from SDMX to VTL data structures ===
224 +1.
225 +11.
226 +111. Mapping from SDMX to VTL data structures
204 204  
205 -==== 12.3.3.1 Basic Mapping ====
228 +**12.3.3.1 Basic Mapping**
206 206  
207 -The main mapping method from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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.
230 +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.
208 208  
209 -When transforming **from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]**, this method consists in leaving the [[components>>doc:sdmx:Glossary.Component.WebHome]] unchanged and maintaining their names and roles, according to the following table:
232 +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:
210 210  
211 -(% style="width:468.294px" %)
212 -|(% style="width:196px" %)**[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]**|(% style="width:269px" %)**[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]**
213 -|(% style="width:196px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]|(% style="width:269px" %)(Simple) Identifier
214 -|(% style="width:196px" %)TimeDimension|(% style="width:269px" %)(Time) Identifier
215 -|(% style="width:196px" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]|(% style="width:269px" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]
216 -|(% style="width:196px" %)DataAttribute|(% style="width:269px" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
234 +|**SDMX**|**VTL**
235 +|Dimension|(Simple) Identifier
236 +|TimeDimension|(Time) Identifier
237 +|Measure|Measure
238 +|DataAttribute|Attribute
217 217  
218 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes, in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] they are all considered "at data point / observation (% style="color:#e74c3c" %)level(%%)" (i.e. dependent on all the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Identifiers), because [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] does not have the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] or set or group of [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], whole [[data set>>doc:sdmx:Glossary.Data set.WebHome]]).
240 +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).
219 219  
220 -With the Basic mapping, one [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observation^^27^^ generates one [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data point.
242 +With the Basic mapping, one SDMX observation^^27^^ generates one VTL data point.
221 221  
222 -==== 12.3.3.2 Pivot Mapping ====
244 +**12.3.3.2 Pivot Mapping**
223 223  
224 -An alternative mapping method from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] is the **Pivot **mapping, which makes sense and is different from the Basic method only for the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data structures that contain a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] that plays the role of [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (like in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1) and just one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]. Through this method, these structures can be (% style="color:#e74c3c" %)mapped(%%) to multimeasure [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structures. Besides that, a user may choose to use any [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] acting as a list of [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] (e.g., a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] with indicators), either by considering the “[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]” role of a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], or at will using any coded [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Of course, in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, this can only work when only one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] is defined in the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
246 +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.
225 225  
226 -In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 the MeasureDimension was a subclass of DimensionComponent like [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] and TimeDimension. In the current [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%), this subclass does not exist anymore, however a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can have the role of [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (i.e. a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] that contributes to the identification of the [[measures>>doc:sdmx:Glossary.Measure.WebHome]]). In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 a DataStructure could have zero or one MeasureDimensions, in the current (% style="color:#e74c3c" %)version(%%) of the standard, from zero to many [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] may have the role of [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Hereinafter a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] that plays the role of [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 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>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] of the current [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%). For the sake of simplicity, the description below considers just one [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 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>>doc:sdmx:Glossary.Dimension.WebHome]] 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
227 227  
228 -Among other things, the Pivot method provides also backward compatibility with the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 data structures that contained a MeasureDimension.
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}}.
229 229  
230 -If applied to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structures that do not contain any MeasureDimension, this method behaves like the Basic mapping (see the previous paragraph).
252 +Among other things, the Pivot method provides also backward compatibility with the SDMX 2.1 data structures that contained a MeasureDimension.
231 231  
232 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structures that contain a MeasureDimension are (% style="color:#e74c3c" %)mapped(%%) as described below (this mapping is equivalent to a pivoting operation):
254 +If applied to SDMX structures that do not contain any MeasureDimension, this method behaves like the Basic mapping (see the previous paragraph).
233 233  
234 -* A [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] simple [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] becomes a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (simple) identifier and a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] TimeDimension becomes a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (time) identifier;
235 -* Each possible [[Code>>doc:sdmx:Glossary.Code.WebHome]] Cj of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension is (% style="color:#e74c3c" %)mapped(%%) to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], having the same name as the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Code>>doc:sdmx:Glossary.Code.WebHome]] (i.e. Cj); the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Cj is a new [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[component>>doc:sdmx:Glossary.Component.WebHome]] even if the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data structure has not such a [[Component>>doc:sdmx:Glossary.Component.WebHome]];
236 -* The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension is not (% style="color:#e74c3c" %)mapped(%%) to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (it disappears in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Structure);
237 -* The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] is not (% style="color:#e74c3c" %)mapped(%%) to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] as well (it disappears in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Structure);
238 -* An [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is (% style="color:#e74c3c" %)mapped(%%) in different ways according to its AttributeRelationship:
239 -** If, according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute becomes a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] 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>>doc:sdmx:Glossary.Data set.WebHome]] (% style="color:#e74c3c" %)level(%%)), or if it refers to a set (or a group) of [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] which does not include the MeasureDimension;
240 -** Otherwise, if, according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is (% style="color:#e74c3c" %)mapped(%%) to one [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] for each possible [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension. By default, the names of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are obtained by concatenating the name of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute and the names of the correspondent [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the MeasureDimension separated by underscore. For example, if the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is named DA and the possible [[Codes>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension are named C1, C2, …, Cn, then the corresponding [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] through [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operators).
241 -** Like in the Basic mapping, the resulting [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are considered as dependent on all the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] identifiers (i.e. "at data point / observation (% style="color:#e74c3c" %)level(%%)"), because [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] does not have the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] notion of [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Relationship.
256 +The SDMX structures that contain a MeasureDimension are mapped as described below (this mapping is equivalent to a pivoting operation):
242 242  
243 -The summary mapping table of the "pivot" mapping from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] for the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data structures that contain a MeasureDimension is the following:
258 +* A SDMX simple dimension becomes a VTL (simple) identifier and a SDMX TimeDimension becomes a VTL (time) identifier;
259 +* Each possible Code Cj of the SDMX MeasureDimension is mapped to a VTL Measure, having the same name as the SDMX Code (i.e. Cj); the VTL Measure Cj is a new VTL component even if the SDMX data structure has not such a Component;
260 +* The SDMX MeasureDimension is not mapped to VTL (it disappears in the VTL Data Structure);
261 +* The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
262 +* An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
263 +** 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;
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.
244 244  
245 -(% style="width:739.294px" %)
246 -|(% style="width:335px" %)**[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]**|(% style="width:400px" %)**[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]**
247 -|(% style="width:335px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]|(% style="width:400px" %)(Simple) Identifier
248 -|(% style="width:335px" %)TimeDimension|(% style="width:400px" %)(Time) Identifier
249 -|(% style="width:335px" %)MeasureDimension & one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]|(% style="width:400px" %)One [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] for each [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension
250 -|(% style="width:335px" %)DataAttribute not depending on the MeasureDimension|(% style="width:400px" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
251 -|(% style="width:335px" %)DataAttribute depending on the MeasureDimension|(% style="width:400px" %)(((
252 -One [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] for each [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the
253 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension
266 +The summary mapping table of the "pivot" mapping from SDMX to VTL for the SDMX data structures that contain a MeasureDimension is the following:
267 +
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|(((
274 +One Attribute for each Code of the
275 +
276 +SDMX MeasureDimension
254 254  )))
255 255  
256 -Using this mapping method, the [[components>>doc:sdmx:Glossary.Component.WebHome]] of the data structure can change in the conversion from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and it must be taken into account that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] statements can reference only the [[components>>doc:sdmx:Glossary.Component.WebHome]] of the resulting [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure.
279 +Using this mapping method, the components of the data structure can change in the conversion from SDMX to VTL and it must be taken into account that the VTL statements can reference only the components of the resulting VTL data structure.
257 257  
258 -At observation / data point (% style="color:#e74c3c" %)level(%%), calling Cj (j=1, … n) the j^^th^^ [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the MeasureDimension:
281 +At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
259 259  
260 -* The set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observations having the same values for all the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] except than the MeasureDimension become one multi-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Point, having one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] for each [[Code>>doc:sdmx:Glossary.Code.WebHome]] Cj of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension;
261 -* The values of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] simple [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], TimeDimension and DataAttributes not depending on the MeasureDimension (these [[components>>doc:sdmx:Glossary.Component.WebHome]] by definition have always the same values for all the observations of the set above) become the values of the corresponding [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (simple) Identifiers, (time) Identifier and [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]].
262 -* The value of the [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observation belonging to the set above and having MeasureDimension=Cj becomes the value of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Cj
263 -* For the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observation belonging to the set above and having MeasureDimension=Cj becomes the value of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] DA_Cj
283 +* 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;
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)
264 264  
265 -==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
286 +Identifiers, (time) Identifier and Attributes.
266 266  
267 -* In some cases, it may happen that the DataAttributes of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure need to be managed as [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]. Therefore, a variant of both the methods above consists in transforming all the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]]. When DataAttributes are converted to [[Measures>>doc:sdmx:Glossary.Measure.WebHome]], the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to [[Measures>>doc:sdmx:Glossary.Measure.WebHome]]). Obviously, the resulting [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure is, in general, multi-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] and does not contain [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]].
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
268 268  
269 -The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[components>>doc:sdmx:Glossary.Component.WebHome]], which according to the Basic and Pivot methods would have had the role of [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]], assume instead the role of [[Measure>>doc:sdmx:Glossary.Measure.WebHome]].
290 +Cj
270 270  
271 -Proper [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] features allow changing the role of specific [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] even after the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping: they can be useful when only some of the DataAttributes need to be managed as [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]].
292 +* 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
272 272  
273 -=== 12.3.4 Mapping from VTL to SDMX data structures ===
294 +**12.3.3.3 From SDMX DataAttributes to VTL Measures**
274 274  
275 -==== 12.3.4.1 Basic Mapping ====
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
276 276  
277 -The main mapping method **from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]** is called **Basic **mapping as well.
298 +Attributes.
278 278  
300 +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.
301 +
302 +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.
303 +
304 +1.
305 +11.
306 +111. Mapping from VTL to SDMX data structures
307 +
308 +**12.3.4.1 Basic Mapping**
309 +
310 +The main mapping method **from VTL to SDMX** is called **Basic **mapping as well.
311 +
279 279  This is considered as the default mapping method and is applied unless a different method is specified through the VtlMappingScheme and VtlDataflowMapping classes.
280 280  
281 -The method consists in leaving the [[components>>doc:sdmx:Glossary.Component.WebHome]] unchanged and maintaining their names and roles in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], according to the following mapping table, which is the same as the basic mapping from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], only seen in the opposite direction.
314 +The method consists in leaving the components unchanged and maintaining their names and roles in SDMX, according to the following mapping table, which is the same as the basic mapping from SDMX to VTL, only seen in the opposite direction.
282 282  
283 283  Mapping table:
284 284  
285 -(% style="width:470.294px" %)
286 -|(% style="width:262px" %)**[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]**|(% style="width:205px" %)**[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]**
287 -|(% style="width:262px" %)(Simple) Identifier|(% style="width:205px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
288 -|(% style="width:262px" %)(Time) Identifier|(% style="width:205px" %)TimeDimension
289 -|(% style="width:262px" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]|(% style="width:205px" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]
290 -|(% style="width:262px" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]|(% style="width:205px" %)DataAttribute
318 +|**VTL**|**SDMX**
319 +|(Simple) Identifier|Dimension
320 +|(Time) Identifier|TimeDimension
321 +|Measure|Measure
322 +|Attribute|DataAttribute
291 291  
292 -If the distinction between simple identifier and time identifier is not maintained in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] environment, the classification between [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] and TimeDimension exists only in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], as declared in the relevant DataStructureDefinition.
324 +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.
293 293  
294 -Regarding the [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]], because [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] considers all of them "at observation (% style="color:#e74c3c" %)level(%%)", the corresponding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes should be put "at observation (% style="color:#e74c3c" %)level(%%)" as well, unless some different information about their AttributeRelationship is otherwise available.
326 +Regarding the Attributes, because VTL considers all of them "at observation level", the corresponding SDMX DataAttributes should be put "at observation level" as well, unless some different information about their AttributeRelationship is otherwise available.
295 295  
296 -Note that the basic mappings in the two directions (from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and vice-versa) are (almost completely) reversible. In fact, if a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure is (% style="color:#e74c3c" %)mapped(%%) to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structure and then the latter is (% style="color:#e74c3c" %)mapped(%%) back to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], the resulting data structure is like the original one (apart for the AttributeRelationship, that can be different if the original [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure contains DataAttributes that are not at observation (% style="color:#e74c3c" %)level(%%)). In reverse order, if a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structure is (% style="color:#e74c3c" %)mapped(%%) to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and then the latter is (% style="color:#e74c3c" %)mapped(%%) back to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], the original data structure is obtained.
328 +Note that the basic mappings in the two directions (from SDMX to VTL and vice-versa) are (almost completely) reversible. In fact, if a SDMX structure is mapped to a VTL structure and then the latter is mapped back to SDMX, the resulting data structure is like the original one (apart for the AttributeRelationship, that can be different if the original SDMX structure contains DataAttributes that are not at observation level). In reverse order, if a VTL structure is mapped to SDMX and then the latter is mapped back to VTL, the original data structure is obtained.
297 297  
298 -As said, the resulting [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] must have the AttributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]].
330 +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.
299 299  
300 -==== 12.3.4.2 Unpivot Mapping ====
332 +**12.3.4.2 Unpivot Mapping**
301 301  
302 -An alternative mapping method from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is the **Unpivot **mapping.
334 +An alternative mapping method from VTL to SDMX is the **Unpivot **mapping.
303 303  
304 -Although this mapping method can be used in any case, it makes major sense in case the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure has more than one [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[component>>doc:sdmx:Glossary.Component.WebHome]] (multi-[[measures>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structure). This is used to support the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 case of a MeasureDimension or any other [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] acting as a list of [[Measures>>doc:sdmx:Glossary.Measure.WebHome]], under the assumptions explained in section “Pivot Mapping”.
336 +Although this mapping method can be used in any case, it makes major sense in case the VTL data structure has more than one measure component (multi-measures VTL structure). This is used to support the SDMX 2.1 case of a MeasureDimension or any other Dimension acting as a list of Measures, under the assumptions explained in section “Pivot Mapping”.
305 305  
306 -The multi-[[measures>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structures are converted to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] having an added MeasureDimension, which disambiguates the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] multiple [[Measures>>doc:sdmx:Glossary.Measure.WebHome]], and a new [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] in place of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ones, containing the values of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]].
338 +The multi-measures VTL structures are converted to SDMX Dataflows having an added MeasureDimension, which disambiguates the VTL multiple Measures, and a new Measure in place of the VTL ones, containing the values of the VTL Measures.
307 307  
308 308  The **unpivot** mapping behaves like follows:
309 309  
310 -* like in the basic mapping, a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (simple) identifier becomes a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] and a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (time) identifier becomes a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] TimeDimension (as said, a [[measure>>doc:sdmx:Glossary.Measure.WebHome]] identifier cannot exist in multi-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structures);
311 -* a MeasureDimension [[component>>doc:sdmx:Glossary.Component.WebHome]] called "measure_name" is added to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure;
312 -* a [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[component>>doc:sdmx:Glossary.Component.WebHome]] called "obs_value" is added to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure;
313 -* each [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] is (% style="color:#e74c3c" %)mapped(%%) to a [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension having the same name as the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] (therefore all the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] do not originate [[Components>>doc:sdmx:Glossary.Component.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure);
314 -* a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] becomes a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute having AttributeRelationship referred to all the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents including the TimeDimension and except the MeasureDimension.
342 +* like in the basic mapping, a VTL (simple) identifier becomes a SDMX Dimension and a VTL (time) identifier becomes a SDMX TimeDimension (as said, a measure identifier cannot exist in multi-measure VTL structures);
343 +* a MeasureDimension component called "measure_name" is added to the SDMX DataStructure;
344 +* a Measure component called "obs_value" is added to the SDMX DataStructure;
345 +* each VTL Measure is mapped to a Code of the SDMX MeasureDimension having the same name as the VTL Measure (therefore all the VTL Measure Components do not originate Components in the SDMX DataStructure);
346 +* a VTL Attribute becomes a SDMX DataAttribute having AttributeRelationship referred to all the SDMX DimensionComponents including the TimeDimension and except the MeasureDimension.
315 315  
316 316  The summary mapping table of the **unpivot** mapping method is the following:
317 317  
318 -(% style="width:638.294px" %)
319 -|(% style="width:200px" %)**[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]**|(% style="width:435px" %)**[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]**
320 -|(% style="width:200px" %)(Simple) Identifier|(% style="width:435px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
321 -|(% style="width:200px" %)(Time) Identifier|(% style="width:435px" %)TimeDimension
322 -|(% style="width:200px" %)All [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]]|(% style="width:435px" %)MeasureDimension (having one [[Code>>doc:sdmx:Glossary.Code.WebHome]] for each [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[component>>doc:sdmx:Glossary.Component.WebHome]]) & one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]
323 -|(% style="width:200px" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]|(% style="width:435px" %)DataAttribute depending on all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] 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
324 324  
325 -At observation / data point (% style="color:#e74c3c" %)level(%%):
356 +At observation / data point level:
326 326  
327 -* a multi-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Point becomes a set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observations, one for each [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]];
328 -* the values of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Identifiers become the values of the corresponding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents, for all the observations of the set above;
329 -* the name of the j^^th^^ [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] (e.g. “Cj”) becomes the [[Code>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension of the j^^th^^ observation of the set;
330 -* the value of the j^^th^^ [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] becomes the value of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] of the j^^th^^ observation of the set;
331 -* the values of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] become the values of the corresponding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes (in principle for all the observations of the set above).
358 +* a multi-measure VTL Data Point becomes a set of SDMX observations, one for each VTL Measure;
359 +* the values of the VTL Identifiers become the values of the corresponding SDMX DimensionComponents, for all the observations of the set above;
360 +* the name of the j^^th^^ VTL Measure (e.g. “Cj”) becomes the Code of the SDMX MeasureDimension of the j^^th^^ observation of the set;
361 +* the value of the j^^th^^ VTL Measure becomes the value of the SDMX Measure of the j^^th^^ observation of the set;
362 +* the values of the VTL Attributes become the values of the corresponding SDMX DataAttributes (in principle for all the observations of the set above).
332 332  
333 -If desired, this method can be applied also to mono-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structures, provided that none of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] has already the role of [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Identifier. Like in the general case, a MeasureDimension [[component>>doc:sdmx:Glossary.Component.WebHome]] called “measure_name” is added to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure, in this case it has just one possible [[Code>>doc:sdmx:Glossary.Code.WebHome]], corresponding to the name of the unique [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]. The original [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] would not become a [[Component>>doc:sdmx:Glossary.Component.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data structure. The value of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] would be assigned to the unique [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] called “obs_value”.
364 +If desired, this method can be applied also to mono-measure VTL structures, provided that none of the VTL Components has already the role of Measure Identifier. Like in the general case, a MeasureDimension component called “measure_name” is added to the SDMX DataStructure, in this case it has just one possible Code, corresponding to the name of the unique VTL Measure. The original VTL Measure would not become a Component in the SDMX data structure. The value of the VTL Measure would be assigned to the unique SDMX Measure called “obs_value”.
334 334  
335 -In any case, the resulting [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the possible [[Codes>>doc:sdmx:Glossary.Code.WebHome]] of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension need to be listed in a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Codelist, with proper id, agency and (% style="color:#e74c3c" %)version(%%); moreover, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] must have the AttributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]].
366 +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.
336 336  
337 -==== 12.3.4.3 From VTL Measures to SDMX Data Attributes ====
368 +**12.3.4.3 From VTL Measures to SDMX Data Attributes**
338 338  
339 -More than all for the multi-[[measure>>doc:sdmx:Glossary.Measure.WebHome]] [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] structures (having more than one [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Component>>doc:sdmx:Glossary.Component.WebHome]]), it may happen that the [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Data Structure need to be managed as DataAttributes in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Therefore, a third mapping method consists in transforming some [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[measures>>doc:sdmx:Glossary.Measure.WebHome]] in a corresponding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] and all the other [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes. This method is called M2A (“M2A” stands for “[[Measures>>doc:sdmx:Glossary.Measure.WebHome]] to DataAttributes”).
370 +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”).
340 340  
341 -All [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:sdmx:Glossary.Measure.WebHome]] maintain their names in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] that become [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes are the ones declared as DataAttributes in the target [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data structure definition.
372 +All VTL Measures maintain their names in SDMX. The VTL Measure Components that become SDMX DataAttributes are the ones declared as DataAttributes in the target SDMX data structure definition.
342 342  
343 343  The mapping table is the following:
344 344  
345 -(% style="width:467.294px" %)
346 -|(% style="width:214px" %)[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]|(% style="width:250px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
347 -|(% style="width:214px" %)(Simple) Identifier|(% style="width:250px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
348 -|(% style="width:214px" %)(Time) Identifier|(% style="width:250px" %)TimeDimension
349 -|(% style="width:214px" %)Some [[Measures>>doc:sdmx:Glossary.Measure.WebHome]]|(% style="width:250px" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]
350 -|(% style="width:214px" %)Other [[Measures>>doc:sdmx:Glossary.Measure.WebHome]]|(% style="width:250px" %)DataAttribute
351 -|(% style="width:214px" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]|(% 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
352 352  
353 -Even in this case, the resulting [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] must have the attributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]].
383 +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.
354 354  
355 -=== 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
356 356  
357 -In order to define and understand properly [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, the applied mapping methods must be specified in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. If the default mapping method (Basic) is applied, no specification is needed.
389 +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.
358 358  
359 -A customized mapping can be defined through the VtlMappingScheme and VtlDataflowMapping classes (see the section of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] IM relevant to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]). A VtlDataflowMapping allows specifying the mapping methods to be used for a specific [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], both in the direction from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (toVtlMappingMethod) and from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (fromVtlMappingMethod); in fact a VtlDataflowMapping associates the structured URN that identifies a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to its [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] alias and its mapping methods.
391 +A customized mapping can be defined through the VtlMappingScheme and VtlDataflowMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlDataflowMapping allows specifying the mapping methods to be used for a specific dataflow, both in the direction from SDMX to VTL (toVtlMappingMethod) and from VTL to SDMX (fromVtlMappingMethod); in fact a VtlDataflowMapping associates the structured URN that identifies a SDMX Dataflow to its VTL alias and its mapping methods.
360 360  
361 -It is possible to specify the toVtlMappingMethod and fromVtlMappingMethod also for the conventional [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] called "generic_dataflow": in this case the specified mapping methods are intended to become the default ones, overriding the "Basic" methods. In turn, the toVtlMappingMethod and fromVtlMappingMethod declared for a specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] are intended to override the default ones for such a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
393 +It is possible to specify the toVtlMappingMethod and fromVtlMappingMethod also for the conventional dataflow called "generic_dataflow": in this case the specified mapping methods are intended to become the default ones, overriding the "Basic" methods. In turn, the toVtlMappingMethod and fromVtlMappingMethod declared for a specific Dataflow are intended to override the default ones for such a Dataflow.
362 362  
363 -The VtlMappingScheme is a container for zero or more VtlDataflowMapping (it may contain also mappings towards [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] other than [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]]).
395 +The VtlMappingScheme is a container for zero or more VtlDataflowMapping (it may contain also mappings towards artefacts other than dataflows).
364 364  
365 -=== 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
366 366  
367 -Until now it has been assumed to (% style="color:#e74c3c" %)map(%%) one SMDX [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to one [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] and vice-versa. This mapping one-to-one is not mandatory according to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] because a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] 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>>doc:sdmx:Glossary.Representation.WebHome]] or storage (see [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 2.0 User Manual page 24), therefore a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] can be seen either as a unique set of data observations (corresponding to one [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]) or as the union of many sets of data observations (each one corresponding to a distinct [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]).
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
368 368  
369 -As a matter of fact, in some cases it can be useful to define [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operations involving definite parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] 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}}
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).
370 370  
371 -Therefore, in order to make the coding of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operations simpler when applied on parts of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], it is allowed to (% style="color:#e74c3c" %)map(%%) distinct parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to distinct [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] according to the following rules and conventions. This kind of mapping is possible both from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], 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}}
405 +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}}
372 372  
373 -Given a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and some predefined [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of its DataStructure, it is allowed to (% style="color:#e74c3c" %)map(%%) the subsets of observations that have the same combination of values for such [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to correspondent [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]].
407 +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}}
374 374  
375 -For example, assuming that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF1(1.0.0) has the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] INDICATOR, TIME_PERIOD and COUNTRY, and that the user declares the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY as basis for the mapping (i.e. the mapping [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]): the observations that have the same values for INDICATOR and COUNTRY would be (% style="color:#e74c3c" %)mapped(%%) to the same [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] (and vice-versa). In practice, this kind mapping is obtained like follows:
409 +Given a SDMX Dataflow and some predefined Dimensions of its DataStructure, it is allowed to map the subsets of observations that have the same combination of values for such Dimensions to correspondent VTL datasets.
376 376  
377 -* For a given [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], the user ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] definer) declares the DimensionComponents on which the mapping will be based, in a given order.{{footnote}}This definition is made through the ToVtlSubspace and ToVtlSpaceKey classes and/or the FromVtlSuperspace and FromVtlSpaceKey classes, depending on the direction of the mapping (“key” means “dimension”). The mapping of Dataflow subsets can be applied independently in the two directions, also according to different Dimensions. When no Dimension is declared for a given direction, it is assumed that the option of mapping different parts of a SDMX Dataflow to different VTL Data Sets is not used.{{/footnote}} Following the example above, imagine that the user declares the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY.
378 -* The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] is given a name using a special notation also called “ordered concatenation” and composed of the following parts:
379 -** The reference to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (expressed according to the rules described in the previous paragraphs, i.e. URN, abbreviated URN or another alias); for example DF(1.0.0);
411 +For example, assuming that the SDMX Dataflow DF1(1.0.0) has the Dimensions INDICATOR, TIME_PERIOD and COUNTRY, and that the user declares the Dimensions INDICATOR and COUNTRY as basis for the mapping (i.e. the mapping dimensions): the observations that have the same values for INDICATOR and COUNTRY would be mapped to the same VTL dataset (and vice-versa). In practice, this kind mapping is obtained like follows:
412 +
413 +* For a given SDMX Dataflow, the user (VTL definer) declares the DimensionComponents on which the mapping will be based, in a given order.{{footnote}}This definition is made through the ToVtlSubspace and ToVtlSpaceKey classes and/or the FromVtlSuperspace and FromVtlSpaceKey classes, depending on the direction of the mapping (“key” means “dimension”). The mapping of Dataflow subsets can be applied independently in the two directions, also according to different Dimensions. When no Dimension is declared for a given direction, it is assumed that the option of mapping different parts of a SDMX Dataflow to different VTL Data Sets is not used.{{/footnote}} Following the example above, imagine that the user declares the Dimensions INDICATOR and COUNTRY.
414 +* The VTL Data Set is given a name using a special notation also called “ordered concatenation” and composed of the following parts:
415 +** The reference to the SDMX Dataflow (expressed according to the rules described in the previous paragraphs, i.e. URN, abbreviated URN or another alias); for example DF(1.0.0);
380 380  ** a slash (“/”) as a separator;{{footnote}}As a consequence of this formalism, a slash in the name of the VTL Data Set assumes the specific meaning of separator between the name of the Dataflow and the values of some of its Dimensions.{{/footnote}}
381 -** The reference to a specific part of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] above, expressed as the concatenation of the values that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents declared above must have, separated by dots (“.”) and written in the order in which these DimensionComponents are defined{{footnote}}This is the order in which the dimensions are defined in the ToVtlSpaceKey class or in the FromVtlSpaceKey class, depending on the direction of the mapping.{{/footnote}}. For example
417 +** The reference to a specific part of the SDMX Dataflow above, expressed as the concatenation of the values that the SDMX DimensionComponents declared above must have, separated by dots (“.”) and written in the order in which these DimensionComponents are defined{{footnote}}This is the order in which the dimensions are defined in the ToVtlSpaceKey class or in the FromVtlSpaceKey class, depending on the direction of the mapping.{{/footnote}}. For example
382 382  
383 -POPULATION.USA would mean that such a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] is (% style="color:#e74c3c" %)mapped(%%) to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] observations for which the [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] //INDICATOR// is equal to POPULATION and the [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] //COUNTRY// is equal to USA.
419 +POPULATION.USA would mean that such a VTL Data Set is mapped to the SDMX observations for which the dimension //INDICATOR// is equal to POPULATION and the dimension //COUNTRY// is equal to USA.
384 384  
385 -In the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, this kind of [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] name must be referenced between single quotes because the slash (“/”) is not a regular character according to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] rules.
421 +In the VTL Transformations, this kind of dataset name must be referenced between single quotes because the slash (“/”) is not a regular character according to the VTL rules.
386 386  
387 -Therefore, the generic name of this kind of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] would be:
423 +Therefore, the generic name of this kind of VTL datasets would be:
388 388  
389 -> 'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
425 +'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
390 390  
391 -Where DF(1.0.0) is the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and //INDICATORvalue// and //COUNTRYvalue //are placeholders for one value of the INDICATOR and COUNTRY [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. Instead the specific name of one of these [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] would be:
427 +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:
392 392  
393 -> ‘DF(1.0.0)/POPULATION.USA’
429 +‘DF(1.0.0)/POPULATION.USA’
394 394  
395 -In particular, this is the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and //COUNTRY// = USA.
431 +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.
396 396  
397 -Let us now analyse the different meaning of this kind of mapping in the two mapping directions, i.e. from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
433 +Let us now analyse the different meaning of this kind of mapping in the two mapping directions, i.e. from SDMX to VTL and from VTL to SDMX.
398 398  
399 -As already said, the mapping from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] happens when the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] are operand of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, instead the mapping from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] happens when the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] that is result of Transformations{{footnote}}It should be remembered that, according to the VTL consistency rules, a given VTL dataset cannot be the result of more than one VTL Transformation.{{/footnote}} need to be treated as [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] objects. This kind of mapping can be applied independently in the two directions and the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] on which the mapping is based can be different in the two directions: these [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] are defined in the ToVtlSpaceKey and in the FromVtlSpaceKey classes respectively.
435 +As already said, the mapping from SDMX to VTL happens when the SDMX dataflows are operand of VTL Transformations, instead the mapping from VTL to SDMX happens when the VTL Data Sets that is result of Transformations{{footnote}}It should be remembered that, according to the VTL consistency rules, a given VTL dataset cannot be the result of more than one VTL Transformation.{{/footnote}} need to be treated as SDMX objects. This kind of mapping can be applied independently in the two directions and the Dimensions on which the mapping is based can be different in the two directions: these Dimensions are defined in the ToVtlSpaceKey and in the FromVtlSpaceKey classes respectively.
400 400  
401 -First, let us see what happens in the mapping direction from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], i.e. when parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (e.g. DF1(1.0.0)) need to be (% style="color:#e74c3c" %)mapped(%%) to distinct [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] that are operand of some [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations.
437 +First, let us see what happens in the mapping direction from SDMX to VTL, i.e. when parts of a SDMX Dataflow (e.g. DF1(1.0.0)) need to be mapped to distinct VTL Data Sets that are operand of some VTL Transformations.
402 402  
403 -As already said, each [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] is assumed to contain all the observations of the
439 +As already said, each VTL Data Set is assumed to contain all the observations of the
404 404  
405 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] having INDICATOR=//INDICATORvalue //and COUNTRY=// COUNTRYvalue//. For example, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] ‘DF1(1.0.0)/POPULATION.USA’ would contain all the observations of DF1(1.0.0) having INDICATOR = POPULATION and COUNTRY = USA.
441 +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.
406 406  
407 -In order to obtain the data structure of these [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] from the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] one, it is assumed that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure; this is possible because their values are fixed for each one of the invoked [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]]{{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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] specified for the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] 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.
408 408  
409 -In the example above, for all the [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] of the kind
445 +basic, pivot …).
410 410  
411 -> ‘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.
447 +In the example above, for all the datasets of the kind
412 412  
413 -It should be noted that the desired [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] (i.e. of the kind ‘DF1(1.0.0)/// INDICATORvalue//.//COUNTRYvalue//’) can be obtained also by applying the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operator “**sub**” (subspace) to the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF1(1.0.0), like in the following [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] expression:
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.
414 414  
415 -> ‘DF1(1.0.0)/POPULATION.USA’ :=
416 -> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
417 ->
418 -> ‘DF1(1.0.0)/POPULATION.CANADA’ :=
419 -> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
420 ->
421 -> … … …
451 +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:
422 422  
423 -In fact the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operator “sub” has exactly the same behaviour. Therefore, (% style="color:#e74c3c" %)mapping(%%) different parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to different [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] in the direction from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] through the ordered concatenation notation is equivalent to a proper use of the operator “**sub**” on such a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].{{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}}
453 +‘DF1(1.0.0)/POPULATION.USA’ :=
424 424  
425 -In the direction from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] it is allowed to omit the value of one or more DimensionComponents on which the (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Dimension.WebHome]] all the values are kept and the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is not dropped.
455 +DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
426 426  
427 -For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
457 +‘DF1(1.0.0)/POPULATION.CANADA’ :=
428 428  
429 -This is equivalent to the application of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] “sub” operator only to the identifier //INDICATOR//:
459 +DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
430 430  
431 -> ‘DF1(1.0.0)/POPULATION.’ :=
432 -> DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
461 +… … …
433 433  
434 -Therefore the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
463 +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}}
435 435  
436 -Heterogeneous invocations of the same [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] are allowed, i.e. omitting different [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] in different invocations.
465 +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.
437 437  
438 -Let us now analyse the (% style="color:#e74c3c" %)mapping(%%) direction from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
467 +For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
439 439  
440 -In this situation, distinct parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] are calculated as distinct [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]], under the (% style="color:#e74c3c" %)constraint(%%) that they must have the same [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure.
469 +This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
441 441  
442 -For example, let us assume that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] programmer wants to calculate the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] DF2(1.0.0) having the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] TIME_PERIOD, INDICATOR, and COUNTRY and that such a programmer finds it convenient to calculate separately the parts of DF2(1.0.0) that have different combinations of values for INDICATOR and COUNTRY:
471 +‘DF1(1.0.0)/POPULATION.’ :=
443 443  
444 -* each part is calculated as a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] derived [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]], result of a dedicated [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformation;{{footnote}}If the whole DF2(1.0) is calculated by means of just one VTL Transformation, then the mapping between the SDMX Dataflow and the corresponding VTL dataset is one-to-one and this kind of mapping (one SDMX Dataflow to many VTL datasets) does not apply.{{/footnote}}
445 -* the data structure of all these [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.{{footnote}}This is possible as each VTL dataset corresponds to one particular combination of values of INDICATOR and COUNTRY.{{/footnote}}
473 +DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
446 446  
447 -Under these hypothesis, such derived [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] can be (% style="color:#e74c3c" %)mapped(%%) to DF2(1.0.0) by declaring the DimensionComponents INDICATOR and COUNTRY as (% style="color:#e74c3c" %)mapping(%%) [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]{{footnote}}The mapping dimensions are defined as FromVtlSpaceKeys of the FromVtlSuperSpace of the VtlDataflowMapping relevant to DF2(1.0).{{/footnote}}.
475 +Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
448 448  
449 -The corresponding [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, assuming that the result needs to be persistent, would be of this kind
477 +Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different Dimensions in different invocations.
450 450  
451 -:{{footnote}}the symbol of the VTL persistent assignment is used (<-){{/footnote}}
479 +Let us now analyse the mapping direction from VTL to SDMX.
452 452  
453 -> ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
481 +In this situation, distinct parts of a SDMX Dataflow are calculated as distinct VTL datasets, under the constraint that they must have the same VTL data structure.
454 454  
483 +For example, let us assume that the VTL programmer wants to calculate the SDMX Dataflow DF2(1.0.0) having the Dimensions TIME_PERIOD, INDICATOR, and COUNTRY and that such a programmer finds it convenient to calculate separately the parts of DF2(1.0.0) that have different combinations of values for INDICATOR and COUNTRY:
484 +
485 +* each part is calculated as a VTL derived Data Set, result of a dedicated VTL Transformation;{{footnote}}If the whole DF2(1.0) is calculated by means of just one VTL Transformation, then the mapping between the SDMX Dataflow and the corresponding VTL dataset is one-to-one and this kind of mapping (one SDMX Dataflow to many VTL datasets) does not apply.{{/footnote}}
486 +* the data structure of all these VTL Data Sets has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.{{footnote}}This is possible as each VTL dataset corresponds to one particular combination of values of INDICATOR and COUNTRY.{{/footnote}}
487 +
488 +Under these hypothesis, such derived VTL Data Sets can be mapped to DF2(1.0.0) by declaring the DimensionComponents INDICATOR and COUNTRY as mapping dimensions{{footnote}}The mapping dimensions are defined as FromVtlSpaceKeys of the FromVtlSuperSpace of the VtlDataflowMapping relevant to DF2(1.0).{{/footnote}}.
489 +
490 +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}}
491 +
492 +‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
493 +
455 455  Some examples follow, for some specific values of INDICATOR and COUNTRY:
456 456  
457 -> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
458 -> … … …
459 -> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
460 -> ‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
461 -> … … …
496 +‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
462 462  
463 -As said, it is assumed that these [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] derived [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] have the TIME_PERIOD as the only identifier. In the mapping from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to SMDX, the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY are added to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data structure on order to obtain the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] one, with the following values respectively:
498 +… … …
464 464  
465 -> VTL dataset INDICATOR value COUNTRY value
466 ->
467 -> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
468 -> ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
469 ->
470 -> ‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
471 -> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
472 -> … … …
500 +‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
473 473  
474 -It should be noted that the application of this many-to-one mapping from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is equivalent to an appropriate sequence of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations. These use the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operator “calc” to add the proper [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] (in the example DF2(1.0.0)), that can be (% style="color:#e74c3c" %)mapped(%%) oneto-one to the homonymous [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. Following the same example, these [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations would be:
502 +‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
475 475  
476 -> 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’,
477 -> … ,
478 -> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
479 -> …);
504 +… … …
480 480  
481 -In other words, starting from the [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] explicitly calculated through [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (in the example ‘DF2(1.0)/GDPPERCAPITA.USA’ and so on), the first step consists in calculating other (non-persistent) [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] (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>>doc:sdmx:Glossary.Data set.WebHome]] 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 (% style="color:#e74c3c" %)mapped(%%) one-to-one to the homonymous [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] having the [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[components>>doc:sdmx:Glossary.Component.WebHome]] TIME_PERIOD, INDICATOR and COUNTRY.
506 +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:
482 482  
483 -Therefore, (% style="color:#e74c3c" %)mapping(%%) different [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] having the same data structure to different parts of a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], i.e. in the direction from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], through the ordered concatenation notation is equivalent to a proper use of the operators “calc” and “union” on such [[datasets>>doc:sdmx:Glossary.Data set.WebHome]].{{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}}
508 +VTL dataset   INDICATOR value COUNTRY value
484 484  
485 -It is worth noting that in the direction from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] it is mandatory to specify the value for every [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] on which the (% style="color:#e74c3c" %)mapping(%%) is based (in other word, in the name of the calculated [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is not possible to omit the value of some of the Dimensions).
486 486  
487 -=== 12.3.7 Mapping variables and value domains between VTL and SDMX ===
511 +‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
488 488  
489 -With reference to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] “model for Variables and Value domains”, the following additional mappings have to be considered:
513 +‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
490 490  
491 -(% style="width:706.294px" %)
492 -|(% style="width:257px" %)[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]|(% style="width:446px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
493 -|(% style="width:257px" %)**[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] [[Component>>doc:sdmx:Glossary.Component.WebHome]]**|(% style="width:446px" %)Although this abstraction exists in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a [[Component>>doc:sdmx:Glossary.Component.WebHome]] (either a DimensionComponent or a [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] or a DataAttribute) belonging to one specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]^^43^^
494 -|(% style="width:257px" %)**Represented Variable**|(% style="width:446px" %)(% style="color:#e74c3c" %)**Concept**(%%) with a definite [[Representation>>doc:sdmx:Glossary.Representation.WebHome]]
495 -|(% style="width:257px" %)**Value Domain**|(% style="width:446px" %)(((
496 -**[[Representation>>doc:sdmx:Glossary.Representation.WebHome]]** (see the Structure
515 +‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
516 +
517 +‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
518 +
519 +… … …
520 +
521 +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:
522 +
523 +DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
524 +
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 +
545 +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.
546 +
547 +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}}
548 +
549 +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).
550 +
551 +1.
552 +11.
553 +111. Mapping variables and value domains between VTL and SDMX
554 +
555 +With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
556 +
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**|(((
561 +**Representation** (see the Structure
562 +
497 497  Pattern in the Base Package)
498 498  )))
499 -|(% style="width:257px" %)**Enumerated Value Domain / [[Code List>>doc:sdmx:Glossary.Code list.WebHome]]**|(% style="width:446px" %)**Codelist**
500 -|(% style="width:257px" %)**[[Code>>doc:sdmx:Glossary.Code.WebHome]]**|(% style="width:446px" %)**[[Code>>doc:sdmx:Glossary.Code.WebHome]]** (for enumerated DimensionComponent, [[Measure>>doc:sdmx:Glossary.Measure.WebHome]], DataAttribute)
501 -|(% style="width:257px" %)**Described Value Domain**|(% style="width:446px" %)(((
502 -non-enumerated** [[Representation>>doc:sdmx:Glossary.Representation.WebHome]]**
503 -(having [[Facets>>doc:sdmx:Glossary.Facet.WebHome]] / ExtendedFacets, see the Structure Pattern in the Base Package)
565 +|**Enumerated Value Domain / Code List**|**Codelist**
566 +|**Code**|**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
567 +|**Described Value Domain**|(((
568 +non-enumerated** Representation**
569 +
570 +(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
504 504  )))
505 -|(% style="width:257px" %)**Value**|(% style="width:446px" %)Although this abstraction exists in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a **[[Code>>doc:sdmx:Glossary.Code.WebHome]]** of a Codelist (for enumerated [[Representations>>doc:sdmx:Glossary.Representation.WebHome]]) or
506 -|(% style="width:257px" %) |(% style="width:446px" %)to a valid **value **(for non-enumerated** **[[Representations>>doc:sdmx:Glossary.Representation.WebHome]])
507 -|(% style="width:257px" %)**Value Domain Subset / Set**|(% style="width:446px" %)This abstraction does not exist in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
508 -|(% style="width:257px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:446px" %)This abstraction does not exist in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
509 -|(% style="width:257px" %)**Described Value Domain Subset / Described Set**|(% style="width:446px" %)This abstraction does not exist in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
510 -|(% style="width:257px" %)**Set list**|(% style="width:446px" %)This abstraction does not exist in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]
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
511 511  
512 -The main difference between [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] relies on the fact that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] for defining subsets of Value Domains do not exist in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], therefore the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] features for referring to predefined subsets are not available in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. These [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] 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>>doc:sdmx:Glossary.Data set.WebHome]] [[Component>>doc:sdmx:Glossary.Component.WebHome]] (aimed at defining the set of values that the [[Component>>doc:sdmx:Glossary.Component.WebHome]] of a [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] can take, possibly a subset of the [[codes>>doc:sdmx:Glossary.Code.WebHome]] of Value Domain).
579 +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).
513 513  
514 -Another difference consists in the fact that all Value Domains are considered as identifiable objects in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] either if enumerated or not, while in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] the Codelist (corresponding to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] enumerated Value Domain) is identifiable, while the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] non-enumerated [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (corresponding to a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] non-enumerated Value Domain) is not identifiable. As a consequence, the definition of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Rulesets, which in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] can refer either to enumerated or non-enumerated value domains, in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] can refer only to enumerated Value Domains (i.e. to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Codelists). As for the (% style="color:#e74c3c" %)mapping(%%) between [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] variables and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concepts(%%), it should be noted that these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] do not coincide perfectly. In fact, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] variables are represented variables, defined always on the same Value Domain (“[[Representation>>doc:sdmx:Glossary.Representation.WebHome]]” in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]) independently of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] / data structure in which they appear{{footnote}}By using represented variables, VTL can assume that data structures having the same variables as identifiers can be composed one another because the correspondent values can match.{{/footnote}}, while the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concepts(%%) can have different [[Representations>>doc:sdmx:Glossary.Representation.WebHome]] in different DataStructures.{{footnote}}A Concept becomes a Component in a DataStructureDefinition, and Components can have different LocalRepresentations in different DataStructureDefinitions, also overriding the (possible) base representation of the Concept.{{/footnote}} This means that one [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concept(%%) can correspond to many [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Variables, one for each [[representation>>doc:sdmx:Glossary.Representation.WebHome]] the (% style="color:#e74c3c" %)Concept(%%) has.
581 +Another difference consists in the fact that all Value Domains are considered as identifiable objects in VTL either if enumerated or not, while in SDMX the Codelist (corresponding to a VTL enumerated Value Domain) is identifiable, while the SDMX non-enumerated Representation (corresponding to a VTL non-enumerated Value Domain) is not identifiable. As a consequence, the definition of the VTL Rulesets, which in VTL can refer either to enumerated or non-enumerated value domains, in SDMX can refer only to enumerated Value Domains (i.e. to SDMX Codelists). As for the mapping between VTL variables and SDMX Concepts, it should be noted that these artefacts do not coincide perfectly. In fact, the VTL variables are represented variables, defined always on the same Value Domain (“Representation” in SDMX) independently of the data set / data structure in which they appear{{footnote}}By using represented variables, VTL can assume that data structures having the same variables as identifiers can be composed one another because the correspondent values can match.{{/footnote}}, while the SDMX Concepts can have different Representations in different DataStructures.{{footnote}}A Concept becomes a Component in a DataStructureDefinition, and Components can have different LocalRepresentations in different DataStructureDefinitions, also overriding the (possible) base representation of the Concept.{{/footnote}} This means that one SDMX Concept can correspond to many VTL Variables, one for each representation the Concept has.
515 515  
516 -Therefore, it is important to be aware that some [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] operations (for example the binary operations at [[data set>>doc:sdmx:Glossary.Data set.WebHome]] (% style="color:#e74c3c" %)level(%%)) are consistent only if the [[components>>doc:sdmx:Glossary.Component.WebHome]] having the same names in the operated [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:sdmx:Glossary.Data set.WebHome]] have also the same [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (i.e. the same Value Domain as for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]). For example, it is possible to obtain correct results from the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] expression
583 +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
517 517  
518 -> 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.
519 519  
520 -if the matching [[components>>doc:sdmx:Glossary.Component.WebHome]] in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general [[representation>>doc:sdmx:Glossary.Representation.WebHome]]. In simpler words, DS_a and DS_b must use the same values/[[codes>>doc:sdmx:Glossary.Code.WebHome]] (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
587 +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
521 521  
522 -As mentioned, the property above is not enforced by construction in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], and different [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the same (% style="color:#e74c3c" %)Concept(%%) can be not compatible one another (for example, it may happen that geo_area is represented by ISO-alpha-3 [[codes>>doc:sdmx:Glossary.Code.WebHome]] in DS_a and by ISO alpha-2 [[codes>>doc:sdmx:Glossary.Code.WebHome]] in DS_b). Therefore, it will be up to the definer of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]
589 +Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
523 523  
524 -Transformations to ensure that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] expressions are consistent with the actual [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the correspondent [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concepts(%%).
591 +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.
525 525  
526 -It remains up to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] definer also the assurance of the consistency between a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Ruleset defined on Variables and the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] on which the Ruleset is applied. In fact, a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Ruleset is expressed by means of the values of the Variables (i.e. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concepts(%%)), i.e. assuming definite [[representations>>doc:sdmx:Glossary.Representation.WebHome]] for them (e.g. ISOalpha-3 for country). If the Ruleset is applied to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] that have the same name of the (% style="color:#e74c3c" %)Concept(%%) they refer to but different [[representations>>doc:sdmx:Glossary.Representation.WebHome]] (e.g. ISO-alpha-2 for country), the Ruleset cannot work properly.
593 +1.
594 +11. Mapping between SDMX and VTL Data Types
595 +111. VTL Data types
527 527  
528 -== 12.4 Mapping between SDMX and VTL Data Types ==
597 +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 -=== 12.4.1 VTL Data types ===
599 +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  
532 -According to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] User Guide the possible operations in [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] depend on the data types of the [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. For example, numbers can be multiplied but text strings cannot. In the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
601 +[[image:1750067055028-964.png]]
533 533  
534 -The [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 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>>doc:sdmx:Glossary.Data set.WebHome]], [[Components>>doc:sdmx:Glossary.Component.WebHome]], Rulesets, etc.), which are the types of the compound structures. See below the diagram of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] data types, taken from the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] User Manual:
603 +==== Figure 22 – VTL Data Types ====
535 535  
536 -[[image:1750070288958-132.png]]
537 -
538 -**Figure 22 – VTL Data Types**
539 -
540 540  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.
541 541  
542 542  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):
543 543  
544 -[[image:1750070310572-584.png]]
609 +==== Figure 23 – VTL Basic Scalar Types ====
545 545  
546 -**Figure 23 – VTL Basic Scalar Types**
611 +1.
612 +11.
613 +111. VTL basic scalar types and SDMX data types
547 547  
548 -=== 12.4.2 VTL basic scalar types and SDMX data types ===
549 -
550 550  The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
551 551  
552 552  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).
... ... @@ -563,256 +563,309 @@
563 563  
564 564  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.
565 565  
566 -=== 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
567 567  
568 568  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
569 569  
570 -(% style="width:583.294px" %)
571 -|(% style="width:360px" %)SDMX data type (BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
572 -|(% style="width:360px" %)(((
637 +|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
638 +|(((
573 573  String
640 +
574 574  (string allowing any character)
575 -)))|(% style="width:221px" %)string
576 -|(% style="width:360px" %)(((
577 -Alpha
642 +)))|string
643 +|(((
644 +Alpha 
645 +
578 578  (string which only allows A-z)
579 -)))|(% style="width:221px" %)string
580 -|(% style="width:360px" %)(((
647 +)))|string
648 +|(((
581 581  AlphaNumeric
650 +
582 582  (string which only allows A-z and 0-9)
583 -)))|(% style="width:221px" %)string
584 -|(% style="width:360px" %)(((
652 +)))|string
653 +|(((
585 585  Numeric
655 +
586 586  (string which only allows 0-9, but is not numeric so that is can having leading zeros)
587 -)))|(% style="width:221px" %)string
588 -|(% style="width:360px" %)(((
657 +)))|string
658 +|(((
589 589  BigInteger
660 +
590 590  (corresponds to XML Schema xs:integer datatype; infinite set of integer values)
591 -)))|(% style="width:221px" %)integer
592 -|(% style="width:360px" %)(((
662 +)))|integer
663 +|(((
593 593  Integer
665 +
594 594  (corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
667 +
595 595  (inclusive))
596 -)))|(% style="width:221px" %)integer
597 -|(% style="width:360px" %)(((
669 +)))|integer
670 +|(((
598 598  Long
672 +
599 599  (corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
674 +
600 600  +9223372036854775807 (inclusive))
601 -)))|(% style="width:221px" %)integer
602 -|(% style="width:360px" %)(((
676 +)))|integer
677 +|(((
603 603  Short
679 +
604 604  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
605 -)))|(% style="width:221px" %)integer
606 -|(% 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
607 -|(% 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 +|(((
608 608  Float
685 +
609 609  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
610 -)))|(% style="width:221px" %)number
611 -|(% style="width:360px" %)(((
687 +)))|number
688 +|(((
612 612  Double
690 +
613 613  (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
614 -)))|(% style="width:221px" %)number
615 -|(% style="width:360px" %)(((
692 +)))|number
693 +|(((
616 616  Boolean
695 +
617 617  (corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
697 +
618 618  binary-valued logic: {true, false})
619 -)))|(% style="width:221px" %)boolean
620 -|(% style="width:360px" %)(((
699 +)))|boolean
700 +|(((
621 621  URI
702 +
622 622  (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
623 -)))|(% style="width:221px" %)string
624 -|(% style="width:360px" %)(((
704 +)))|string
705 +|(((
625 625  Count
707 +
626 626  (an integer following a sequential pattern, increasing by 1 for each occurrence)
627 -)))|(% style="width:221px" %)integer
628 -|(% style="width:360px" %)(((
709 +)))|integer
710 +|(((
629 629  InclusiveValueRange
712 +
630 630  (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
631 -)))|(% style="width:221px" %)number
632 -|(% style="width:360px" %)(((
714 +)))|number
715 +|(((
633 633  ExclusiveValueRange
717 +
634 634  (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
635 -)))|(% style="width:221px" %)number
636 -|(% style="width:360px" %)(((
719 +)))|number
720 +|(((
637 637  Incremental
722 +
638 638  (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
639 -)))|(% style="width:221px" %)number
640 -|(% style="width:360px" %)(((
724 +)))|number
725 +|(((
641 641  ObservationalTimePeriod
727 +
642 642  (superset of StandardTimePeriod and TimeRange)
643 -)))|(% style="width:221px" %)time
644 -|(% style="width:360px" %)(((
729 +)))|time
730 +|(((
645 645  StandardTimePeriod
732 +
646 646  (superset of BasicTimePeriod and ReportingTimePeriod)
647 -)))|(% style="width:221px" %)time
648 -|(% style="width:360px" %)(((
734 +)))|time
735 +|(((
649 649  BasicTimePeriod
737 +
650 650  (superset of GregorianTimePeriod and DateTime)
651 -)))|(% style="width:221px" %)date
652 -|(% style="width:360px" %)(((
739 +)))|date
740 +|(((
653 653  GregorianTimePeriod
742 +
654 654  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
655 -)))|(% style="width:221px" %)date
656 -|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
657 -|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
658 -|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
659 -|(% style="width:360px" %)(((
744 +)))|date
745 +|GregorianYear (YYYY)|date
746 +|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
747 +|GregorianDay (YYYY-MM-DD)|date
748 +|(((
660 660  ReportingTimePeriod
750 +
661 661  (superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
662 -)))|(% style="width:221px" %)time_period
663 -|(% style="width:360px" %)(((
752 +)))|time_period
753 +|(((
664 664  ReportingYear
755 +
665 665  (YYYY-A1 – 1 year period)
666 -)))|(% style="width:221px" %)time_period
667 -|(% style="width:360px" %)(((
757 +)))|time_period
758 +|(((
668 668  ReportingSemester
760 +
669 669  (YYYY-Ss – 6 month period)
670 -)))|(% style="width:221px" %)time_period
671 -|(% style="width:360px" %)(((
762 +)))|time_period
763 +|(((
672 672  ReportingTrimester
765 +
673 673  (YYYY-Tt – 4 month period)
674 -)))|(% style="width:221px" %)time_period
675 -|(% style="width:360px" %)(((
767 +)))|time_period
768 +|(((
676 676  ReportingQuarter
770 +
677 677  (YYYY-Qq – 3 month period)
678 -)))|(% style="width:221px" %)time_period
679 -|(% style="width:360px" %)(((
772 +)))|time_period
773 +|(((
680 680  ReportingMonth
775 +
681 681  (YYYY-Mmm – 1 month period)
682 -)))|(% style="width:221px" %)time_period
683 -|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
684 -|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
685 -|(% 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 +|(((
686 686  ReportingDay
782 +
687 687  (YYYY-Dddd – 1 day period)
688 -)))|(% style="width:221px" %)time_period
689 -|(% style="width:360px" %)(((
784 +)))|time_period
785 +|(((
690 690  DateTime
787 +
691 691  (YYYY-MM-DDThh:mm:ss)
692 -)))|(% style="width:221px" %)date
693 -|(% style="width:360px" %)(((
789 +)))|date
790 +|(((
694 694  TimeRange
792 +
695 695  (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
696 -)))|(% style="width:221px" %)time
697 -|(% style="width:360px" %)(((
794 +)))|time
795 +|(((
698 698  Month
797 +
699 699  (~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
700 -)))|(% style="width:221px" %)string
701 -|(% style="width:360px" %)(((
799 +)))|string
800 +|(((
702 702  MonthDay
802 +
703 703  (~-~-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)
704 -)))|(% style="width:221px" %)string
705 -|(% style="width:360px" %)(((
804 +)))|string
805 +|(((
706 706  Day
807 +
707 707  (~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
708 -)))|(% style="width:221px" %)string
709 -|(% style="width:360px" %)(((
809 +)))|string
810 +|(((
710 710  Time
812 +
711 711  (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
712 -)))|(% style="width:221px" %)string
713 -|(% style="width:360px" %)(((
814 +)))|string
815 +|(((
714 714  Duration
817 +
715 715  (corresponds to XML Schema xs:duration datatype)
716 -)))|(% style="width:221px" %)duration
717 -|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
718 -|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
719 -|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
720 -|(% 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
721 721  
722 -**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
825 +додол
723 723  
827 +==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
828 +
724 724  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).
725 725  
726 -=== 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
727 727  
728 728  The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
729 729  
730 -(% style="width:748.294px" %)
731 -|(% style="width:164px" %)(((
732 -VTL basic scalar type
733 -)))|(% style="width:304px" %)(((
837 +|(((
838 +VTL basic
839 +
840 +scalar type
841 +)))|(((
734 734  Default SDMX data type
735 -(BasicComponentDataType)
736 -)))|(% style="width:277px" %)Default output format
737 -|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
738 -|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
739 -|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
740 -|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
741 -|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
742 -|(% 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|(((
743 743  ReportingTimePeriod
855 +
744 744  (StandardReportingPeriod)
745 -)))|(% style="width:277px" %)(((
857 +)))|(((
746 746   YYYY-Pppp
859 +
747 747  (according to SDMX )
748 748  )))
749 -|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
750 -|(% 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"
751 751  
752 -**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 ====
753 753  
754 -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
755 755  
869 +Transformations and Expressions of the SDMX information model).
870 +
756 756  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.
757 757  
758 -(% style="width:717.294px" %)
759 -|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
760 -|(% colspan="2" style="width:714px" %)
761 -|(% colspan="2" style="width:714px" %)Number
762 -|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
763 -|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
764 -|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
765 -|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
766 -|(% style="width:122px" %) |(% style="width:591px" %)
767 -|(% colspan="2" style="width:714px" %)Time and duration
768 -|(% style="width:122px" %)C|(% style="width:591px" %)century
769 -|(% style="width:122px" %)Y|(% style="width:591px" %)year
770 -|(% style="width:122px" %)S|(% style="width:591px" %)semester
771 -|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
772 -|(% style="width:122px" %)M|(% style="width:591px" %)month
773 -|(% style="width:122px" %)W|(% style="width:591px" %)week
774 -|(% style="width:122px" %)D|(% style="width:591px" %)day
775 -|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
776 -|(% style="width:122px" %)M|(% style="width:591px" %)minute
777 -|(% style="width:122px" %)S|(% style="width:591px" %)second
778 -|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
779 -|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
780 -|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
781 -|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
782 -|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
783 -|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
784 -|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
785 -|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
786 -|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
787 -|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
788 -|(% style="width:122px" %) |(% style="width:591px" %)
789 -|(% colspan="2" style="width:714px" %)String
790 -|(% style="width:122px" %)X|(% style="width:591px" %)any string character
791 -|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
792 -|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
793 -|(% style="width:122px" %) |(% style="width:591px" %)
794 -|(% colspan="2" style="width:714px" %)Boolean
795 -|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
796 -|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
797 -|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
798 -|(% style="width:122px" %) |(% style="width:591px" %)
799 -|(% colspan="2" style="width:714px" %)Other qualifiers
800 -|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
801 -|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
802 -|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
803 -|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
804 -|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
805 -|(% 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 +| |
806 806  
807 807  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}}.
808 808  
809 -=== 12.4.3 Null Values ===
923 +1.
924 +11.
925 +111. Null Values
810 810  
811 811  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.
812 812  
813 813  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.
814 814  
815 -=== 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
816 816  
817 817  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.
818 818  
... ... @@ -826,6 +826,26 @@
826 826  
827 827  In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
828 828  
947 +
829 829  ----
830 830  
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 +
831 831  {{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
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,0 @@
1 -12