Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version
To version 7.2
edited by Helena
on 2025/05/17 00:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,111 +1,102 @@
1 -= 12 Validation and Transformation Language (VTL) =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 12.1 Introduction ==
4 4  
5 -The Validation and Transformation Language (VTL) supports the definition of Transformations, which are algorithms to calculate new data starting from already existing ones^^[[^^5^^>>path:#sdfootnote5sym||name="sdfootnote5anc"]]^^. The purpose of the VTL in the SDMX context is to enable the:
7 +The [[Validation and Transformation Language>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:xwiki: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:xwiki:Glossary.Validation and transformation language.WebHome]] in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] context is to enable the:
6 6  
7 7  * definition of validation and transformation algorithms, in order to specify how to calculate new data from existing ones;
8 -* 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);
9 -* compilation and execution of VTL algorithms, either interpreting the VTL Transformations or translating them in whatever other computer language is deemed as appropriate.
10 +* exchange of the definition of [[VTL>>doc:xwiki: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:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations describing the calculation algorithms);
11 +* compilation and execution of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] algorithms, either interpreting the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations or translating them in whatever other computer language is deemed as appropriate.
10 10  
11 -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").
13 +It is important to note that the [[VTL>>doc:xwiki: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:xwiki:Glossary.Validation and transformation language.WebHome]] User Guide. The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] IM is designed to be compatible with more standards, like [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], DDI (Data Documentation Initiative) and GSIM, and includes the model [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] that can be manipulated (inputs and/or outputs of Transformations, e.g. [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]]", "Data Structure") and the model [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] that allow the definition of the transformation algorithms (e.g. "Transformation", "Transformation Scheme").
12 12  
13 -The VTL language can be applied to SDMX artefacts by mapping the SDMX IM model artefacts to the model artefacts that VTL can manipulate^^[[^^6^^>>path:#sdfootnote6sym||name="sdfootnote6anc"]]^^. 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).
15 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] language can be applied to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] by (% style="color:#2ecc71" %)mapping(%%) the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] IM model [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] to the model [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] that [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] can be used in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] as inputs and/or outputs of Transformations. It is important to be aware that the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] do not always have the same names in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] and [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataset>>doc:xwiki:Glossary.Data set.WebHome]] and the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]]", which do not correspond one another: as a matter of fact, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] (% style="color:#2ecc71" %)maps(%%) to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]", while the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataset>>doc:xwiki:Glossary.Data set.WebHome]] has no explicit (% style="color:#2ecc71" %)mapping(%%) to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (such an abstraction is not needed in the definition of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations). A [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataset>>doc:xwiki:Glossary.Data set.WebHome]]", however, is an instance of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] and can be the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] on which the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] transformations are executed (i.e., the Transformations are defined on [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] and are applied to [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] instances that can be Datasets).
14 14  
15 -The VTL programs (Transformation Schemes) are represented in SDMX through the TransformationScheme maintainable class which is composed of
17 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs (Transformation Schemes) are represented in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] through the TransformationScheme maintainable class which is composed of Transformation ([[nameable artefact>>doc:xwiki:Glossary.Nameable artefact.WebHome]]). Each Transformation assigns the outcome of the evaluation of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expression to a result.
16 16  
17 -Transformation (nameable artefact). Each Transformation assigns the outcome of the evaluation of a VTL expression to a result.
19 +This section does not explain the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] language or any of the content published in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] guides. Rather, this is a description of how the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can be used in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] context and applied to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]].
18 18  
19 -This section does not explain the VTL language or any of the content published in the VTL guides. Rather, this is a description of how the VTL can be used in the SDMX context and applied to SDMX artefacts.
20 -
21 21  == 12.2 References to SDMX artefacts from VTL statements ==
22 22  
23 23  === 12.2.1 Introduction ===
24 24  
25 -The VTL can manipulate SDMX artefacts (or objects) by referencing them through predefined conventional names (aliases).
25 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can manipulate [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] (or objects) by referencing them through predefined conventional names (aliases).
26 26  
27 -The alias of an SDMX artefact can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
27 +The alias of an [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
28 28  
29 -In any case, the aliases used in the VTL Transformations have to be mapped to the
29 +In any case, the aliases used in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations have to be (% style="color:#2ecc71" %)mapped(%%) to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] through the VtlMappingScheme and VtlMapping classes (see the section of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] IM relevant to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]). A VtlMapping allows specifying the aliases to be used in the [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]]. A VtlMappingScheme is a container for zero or more VtlMapping.
30 30  
31 -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^^[[^^7^^>>path:#sdfootnote7sym||name="sdfootnote7anc"]]^^ or User Defined Operators^^[[^^8^^>>path:#sdfootnote8sym||name="sdfootnote8anc"]]^^ to reference SDMX artefacts. A VtlMappingScheme is a container for zero or more VtlMapping.
31 +The correspondence between an alias and a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] must be one-to-one, meaning that a generic alias identifies one and just one [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] while a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is identified by one and just one alias. In other words, within a VtlMappingScheme an [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] can have just one alias and different [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] cannot have the same alias.
32 32  
33 -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.
34 -
35 35  The references through the URN and the abbreviated URN are described in the following paragraphs.
36 36  
37 37  === 12.2.2 References through the URN ===
38 38  
39 -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.
37 +This approach has the advantage that in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] code the URN of the referenced [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] is directly intelligible by a human reader but has the drawback that the references are verbose.
40 40  
41 -The SDMX URN^^[[^^9^^>>path:#sdfootnote9sym||name="sdfootnote9anc"]]^^ is the concatenation of the following parts, separated by special symbols like dot, equal, asterisk, comma, and parenthesis:
39 +The [[SDMX>>doc:xwiki: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}} is the concatenation of the following parts, separated by special symbols like dot, equal, asterisk, comma, and parenthesis:
42 42  
43 43  * SDMXprefix
44 -* SDMX-IM-package-name
42 +* [[SDMX-IM>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]-package-name
45 45  * class-name
46 46  * agency-id
47 47  * maintainedobject-id
48 -* maintainedobject-version
49 -* container-object-id ^^[[^^10^^>>path:#sdfootnote10sym||name="sdfootnote10anc"]]^^
46 +* maintainedobject-(% style="color:#2ecc71" %)version
47 +* container-object-id{{footnote}}The container-object-id can repeat and may not be present.{{/footnote}}
50 50  * object-id
51 51  
52 52  The generic structure of the URN is the following:
53 53  
54 -SDMXprefix.SDMX-IM-package-name.class-name=agency-id:maintainedobject-id
52 +SDMXprefix.[[SDMX-IM>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]-package-name.class-name=agency-id:maintainedobject-id (maintainedobject-(% style="color:#2ecc71" %)version(%%)).*container-object-id.object-id
55 55  
56 -(maintainedobject-version).*container-object-id.object-id
54 +The **SDMXprefix** is "urn:[[sdmx>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]:org", always the same for all [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]].
57 57  
58 -The **SDMXprefix** is "urn:sdmx:org", always the same for all SDMX artefacts.
56 +The [[SDMX-IM>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]-package-name** **is the concatenation of the string** **[[sdmx>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]].infomodel." with the package-name, which the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] belongs to. For example, for referencing a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] the [[SDMX-IM>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]-package-name is [[sdmx>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.datastructure", because the class [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] belongs to the package "datastructure".
59 59  
60 -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".
58 +The class-name is the name of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] object class, which the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] object belongs to (e.g., for referencing a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] the class-name is [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]"). The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can reference [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] that belong to the classes [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], DataAttribute, (% style="color:#2ecc71" %)Concept(%%), Codelist.
61 61  
62 -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.
60 +The agency-id is the acronym of the agency that owns the definition of the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]], for example for the Eurostat [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] the agency-id is "ESTAT"). The agency-id can be composite (for example AgencyA.Dept1.Unit2).
63 63  
64 -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).
62 +The maintainedobject-id is the name of the maintained object which the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] belongs to, and in case the [[artefact>>doc:xwiki: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:xwiki:Glossary.Artefact.WebHome]]. Therefore the maintainedobject-id depends on the class of the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]]:
65 65  
66 -The maintainedobject-id is the name of the maintained object which the artefact belongs to, and in case the artefact itself is maintainable^^[[^^11^^>>path:#sdfootnote11sym||name="sdfootnote11anc"]]^^, coincides with the name of the artefact. Therefore the maintainedobject-id depends on the class of the artefact:
64 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], which is a maintainable class, the maintainedobject-id is the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] name ([[dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]-id);
65 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], TimeDimension or DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the name of the DataStructure (dataStructure-id) which the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] belongs to;
66 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a (% style="color:#2ecc71" %)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:xwiki:Glossary.Artefact.WebHome]] belongs to;
67 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a Codelist, which is a maintainable class, the maintainedobject-id is the Codelist name (codelist-id).
67 67  
68 -* if the artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the Dataflow name (dataflow-id);
69 -* if the artefact is a Dimension, Measure, TimeDimension or DataAttribute, which are not maintainable and belong to the
69 +The maintainedobject-(% style="color:#2ecc71" %)version(%%) is the (% style="color:#2ecc71" %)version(%%), according to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintained object which the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] belongs to (for example, possible (% style="color:#2ecc71" %)versions(%%) might be 1.0, 2.3, 1.0.0, 2.1.0 or 3.1.2).
70 70  
71 -DataStructure maintainable class, the maintainedobject-id is the name of the DataStructure (dataStructure-id) which the artefact belongs to;
71 +The container-object-id does not apply to the classes that can be referenced in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, therefore is not present in their URN
72 72  
73 -* 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;
74 -* if the artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the Codelist name (codelist-id).
73 +The object-id is the name of the non-[[maintainable artefact>>doc:xwiki:Glossary.Maintainable artefact.WebHome]] (when the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is maintainable its name is already specified as the maintainedobject-id, see above), in particular it has to be specified:
75 75  
76 -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 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] or DataAttribute (the object-id is the name of one of the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] above, which are data structure [[components>>doc:xwiki:Glossary.Component.WebHome]])
76 +* if the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a (% style="color:#2ecc71" %)Concept(%%) (the object-id is the name of the (% style="color:#2ecc71" %)Concept(%%))
77 77  
78 -The container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
78 +For example, by using the URN, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation that sums two [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] DF1 and DF2 and assigns the result to a third persistent [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]], that their (% style="color:#2ecc71" %)version(%%) is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
79 79  
80 -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:
81 -
82 -* if the artefact is a Dimension, TimeDimension, Measure or DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
83 -* if the artefact is a Concept (the object-id is the name of the Concept)
84 -
85 -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^^[[^^12^^>>path:#sdfootnote12sym||name="sdfootnote12anc"]]^^:
86 -
87 87  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
88 -
89 89  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
90 -
91 91  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
92 92  
93 93  === 12.2.3 Abbreviation of the URN ===
94 94  
95 -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.
86 +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:xwiki:Glossary.Artefact.WebHome]] remain intelligible in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] code by a human reader.
96 96  
97 -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.
88 +The URN can be abbreviated by omitting the parts that are not essential for the identification of the [[artefact>>doc:xwiki: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.
98 98  
99 -* 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. • The SDMX-IM-package-name** &nbsp;**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:
100 -** "datastructure" for the classes Dataflow, Dimension, TimeDimension, Measure, DataAttribute, o "conceptscheme" for the class Concept, o "codelist" for the class Codelist.
101 -* 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^^[[^^13^^>>path:#sdfootnote13sym||name="sdfootnote13anc"]]^^, the SDMX class can be deduced from the mapping rules between VTL and SDMX (see the section "Mapping between VTL and SDMX" hereinafter)^^[[^^14^^>>path:#sdfootnote14sym||name="sdfootnote14anc"]]^^.
102 -* 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^^[[^^15^^>>path:#sdfootnote15sym||name="sdfootnote15anc"]]^^. 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).
103 -* 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;
104 -** if the referenced artefact is a Dimension, TimeDimension, Measure, DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the dataStructure-id and can be omitted, given that these components are always invoked within the invocation of a Dataflow, whose dataStructure-id can be deduced from the SDMX structural definitions;
105 -** 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;
106 -** if the referenced artefact 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-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. • 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
108 -* 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
90 +* The SDMXprefix can be omitted for all the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] objects, because it is a prefixed string (urn:[[sdmx>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]:org), always the same for [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] objects. • The [[SDMX-IM>>doc:xwiki: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:xwiki:Glossary.SDMX Information Model.WebHome]] packages and classes that allows this deduction is in the [[SDMX>>doc:xwiki: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:xwiki:Glossary.Artefact.WebHome]] that [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can reference, the package is:
91 +** "datastructure" for the classes [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], DataAttribute, o "conceptscheme" for the class (% style="color:#2ecc71" %)Concept(%%), o "codelist" for the class Codelist.
92 +* The class-name can be omitted as it can be deduced from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] invocation. In particular, starting from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] class of the invoked [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (e.g. [[dataset>>doc:xwiki:Glossary.Data set.WebHome]], [[component>>doc:xwiki:Glossary.Component.WebHome]], identifier, [[measure>>doc:xwiki:Glossary.Measure.WebHome]], [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]], variable, valuedomain), which is known given the syntax of the invoking [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator{{footnote}}For the syntax of the VTL operators see the VTL Reference Manual{{/footnote}}, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] class can be deduced from the (% style="color:#2ecc71" %)mapping(%%) rules between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (see the section (% style="color:#2ecc71" %)Mapping(%%) between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki: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}}.
93 +* 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:xwiki: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:xwiki: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:xwiki: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).
94 +* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted: o if the referenced [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], which is a maintainable class, the maintainedobject-id is the [[dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]-id and obviously cannot be omitted;
95 +** if the referenced [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:xwiki: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:xwiki:Glossary.Component.WebHome]] are always invoked within the invocation of a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], whose dataStructure-id can be deduced from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] structural definitions;
96 +** if the referenced [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a (% style="color:#2ecc71" %)Concept(%%), which is not maintainable and belong to the ConceptScheme maintainable class, the maintained object is the conceptScheme-id and cannot be omitted;
97 +** if the referenced [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
98 +* When the maintainedobject-id is omitted, the maintainedobject-(% style="color:#2ecc71" %)version(%%) is omitted too. When the maintainedobject-id is not omitted and the maintainedobject-(% style="color:#2ecc71" %)version(%%) is omitted, the (% style="color:#2ecc71" %)version(%%) 1.0 is assumed by default. • As said, the container-object-id does not apply to the classes that can be referenced in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, therefore is not present in their URN
99 +* The object-id does not exist for the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] belonging to the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], and Codelist classes, while it exists and cannot be omitted for the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] belonging to the classes [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], DataAttribute and (% style="color:#2ecc71" %)Concept(%%), as for them the object-id is the main identifier of the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]]
109 109  
110 110  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.
111 111  
... ... @@ -112,9 +112,7 @@
112 112  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
113 113  
114 114  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
115 -
116 116  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
117 -
118 118  'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
119 119  
120 120  by omitting all the non-essential parts would become simply:
... ... @@ -121,15 +121,15 @@
121 121  
122 122  DFR := DF1 + DF2
123 123  
124 -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^^[[^^16^^>>path:#sdfootnote16sym||name="sdfootnote16anc"]]^^:
113 +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.{{/footnote}}:
125 125  
126 126  'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
127 127  
128 -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^^:
117 +if the Codelist is referenced from a RulesetScheme belonging to the agency AG, omitting all the optional parts, the abbreviated reference would become simply{{footnote}}Single quotes are not needed in this case because CL_FREQ is a VTL regular name.{{/footnote}}:
129 129  
130 130  CL_FREQ
131 131  
132 -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:
121 +As for the references to the [[components>>doc:xwiki: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:xwiki:Glossary.Component.WebHome]] is SECTOR, is the following:
133 133  
134 134  'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S
135 135  
... ... @@ -139,13 +139,13 @@
139 139  
140 140  SECTOR
141 141  
142 -For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as^^[[^^17^^>>path:#sdfootnote17sym||name="sdfootnote17anc"]]^^:
131 +For example, the Transformation for renaming the [[component>>doc:xwiki:Glossary.Component.WebHome]] SECTOR of the [[Dataflow>>doc:xwiki: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}}:
143 143  
144 144  'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
145 145  
146 -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.
135 +In the references to the (% style="color:#2ecc71" %)Concepts(%%), which can exist for example in the definition of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Rulesets, at least the conceptScheme-id and the (% style="color:#2ecc71" %)concept(%%)-id must be specified.
147 147  
148 -An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
137 +An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the (% style="color:#2ecc71" %)concept(%%)-id is SECTOR, is the following:
149 149  
150 150  'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
151 151  
... ... @@ -153,167 +153,149 @@
153 153  
154 154  CS1(1.0.0).SECTOR
155 155  
156 -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:
145 +The [[Codes>>doc:xwiki: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:xwiki:Glossary.Measure.WebHome]] of the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF1 are between 0 and 25000 can be written like follows:
157 157  
158 158  'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
159 159  
160 -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).
149 +The [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] ([[Component>>doc:xwiki:Glossary.Component.WebHome]], (% style="color:#2ecc71" %)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:xwiki: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:xwiki:Glossary.Measure.WebHome]] of DF1(1.0.0).
161 161  
162 162  === 12.2.4 User-defined alias ===
163 163  
164 -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.
153 +The third possibility for referencing [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] statements is to use user-defined aliases not related to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] URN of the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]].
165 165  
166 -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).
155 +This approach gives preference to the use of symbolic names for the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]]. As a consequence, in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] code the referenced [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] may become not directly intelligible by a human reader. In any case, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] aliases are associated to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] URN through the VtlMappingScheme and VtlMapping classes. These classes provide for structured references to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] whatever kind of reference is used in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] statements (URN, abbreviated URN or user-defined aliases).
167 167  
168 168  === 12.2.5 References to SDMX artefacts from VTL Rulesets ===
169 169  
170 -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.
159 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Rulesets allow defining sets of reusable Rules that can be applied by some [[VTL>>doc:xwiki: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:xwiki:Glossary.Currency.WebHome]] is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
171 171  
172 -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.
161 +The [[VTL>>doc:xwiki: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.
173 173  
174 -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^^[[^^18^^>>path:#sdfootnote18sym||name="sdfootnote18anc"]]^^.
163 +In the signature, given the mapping between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] better described in the following paragraphs, a reference to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Value Domain becomes a reference to a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Codelist, while a reference to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Represented Variable becomes a reference to a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concept(%%), assuming for it a definite representation{{footnote}}Rulesets of this kind cannot be reused when the referenced Concept has a different representation.{{/footnote}}.
175 175  
176 -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.^^[[^^19^^>>path:#sdfootnote19sym||name="sdfootnote19anc"]]^^
165 +In general, for referencing [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Codelists and (% style="color:#2ecc71" %)Concepts(%%), the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki: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:#2ecc71" %)mapped(%%) to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]].{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
177 177  
178 -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.
167 +In the body of the Rulesets, the [[Codes>>doc:xwiki:Glossary.Code.WebHome]] and in general all the Values can be written without any other specification, because the [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]], which the Values are referred (Codelist, (% style="color:#2ecc71" %)Concept(%%)) to can be deduced from the Ruleset signature.
179 179  
180 180  == 12.3 Mapping between SDMX and VTL artefacts ==
181 181  
182 182  === 12.3.1 When the mapping occurs ===
183 183  
184 -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.
173 +The mapping methods between the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] object classes allow transforming a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition in a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] one and vice-versa for the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] to be manipulated. It should be remembered that [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs (i.e. Transformation Schemes) are represented in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] through the TransformationScheme maintainable class which is composed of Transformations ([[nameable artefacts>>doc:xwiki:Glossary.Nameable artefact.WebHome]]). Each Transformation assigns the outcome of the evaluation of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expression to a result: the input operands of the expression and the result can be [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]].
185 185  
186 -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.
175 +Every time a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] object is referenced in a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation as an input operand, there is the need to generate a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definition of the object, so that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operations can take place. This can be made starting from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition and applying a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-[[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] mapping method in the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]. The possible mapping methods from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] are described in the following paragraphs and are conceived to allow the automatic deduction of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definition of the object from the knowledge of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition.
187 187  
188 -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^^[[^^20^^>>path:#sdfootnote20sym||name="sdfootnote20anc"]]^^.
177 +In the opposite direction, every time an object calculated by means of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] must be treated as a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] object (for example for exchanging it through [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]), there is the need of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition of the object, so that the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] operations can take place. The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition is needed for the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] objects for which a [[SDMX>>doc:xwiki: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 non-persistent calculation is disseminated through SDMX tools (like an inquiry tool).{{/footnote}}.
189 189  
190 -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).
179 +The mapping methods from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] are described in the following paragraphs as well, however they do not allow the complete [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition to be automatically deduced from the [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] includes also some mandatory information not available in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (like the [[concept scheme>>doc:xwiki:Glossary.Concept scheme.WebHome]] to which the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:xwiki:Glossary.Component.WebHome]] refer, the ‘usage’ and ‘attributeRelationship’ for the DataAttributes and so on). Therefore the mapping methods from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] provide only a general guidance for generating [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definitions properly starting from the information available in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], independently of how the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definition it is actually generated (manually, automatically or part and part).
191 191  
192 192  === 12.3.2 General mapping of VTL and SDMX data structures ===
193 193  
194 -This section makes reference to the VTL "Model for data and their structure"^^[[^^21^^>>path:#sdfootnote21sym||name="sdfootnote21anc"]]^^ and the correspondent SDMX "Data Structure Definition"^^[[^^22^^>>path:#sdfootnote22sym||name="sdfootnote22anc"]]^^.
183 +This section makes reference to the [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] "Data Structure Definition"{{footnote}}See the SDMX Standards Section 2 – Information Model{{/footnote}}.
195 195  
196 -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).^^[[^^23^^>>path:#sdfootnote23sym||name="sdfootnote23anc"]]^^
185 +The main type of [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can manipulate is the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]], which in general is (% style="color:#2ecc71" %)mapped(%%) to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]. This means that a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation, in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] context, expresses the algorithm for calculating a derived [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] starting from some already existing [[Dataflows>>doc:xwiki: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}}
197 197  
198 -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.
187 +While the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations are defined in term of [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] definitions, they are assumed to be executed on instances of such [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]], provided at runtime to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] engine (the mechanism for identifying the instances to be processed are not part of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] specifications and depend on the implementation of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]-based systems). As already said, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Datasets>>doc:xwiki:Glossary.Data set.WebHome]] are instances of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]], therefore a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation defined on some [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] can be applied on some corresponding [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Datasets>>doc:xwiki:Glossary.Data set.WebHome]].
199 199  
200 -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.
189 +A [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] is structured by one and just one Data Structure and a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Structure can structure any number of [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]]. Correspondingly, in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] context a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] is structured by one and just one DataStructureDefinition and one DataStructureDefinition can structure any number of [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]].
201 201  
202 -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
191 +A [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] has a Data Structure made of [[Components>>doc:xwiki:Glossary.Component.WebHome]], which in turn can be Identifiers, [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] and [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]]. Similarly, a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataflowDefinition has a DataStructureDefinition made of [[components>>doc:xwiki:Glossary.Component.WebHome]] that can be DimensionComponents, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] and DataAttributes. In turn, a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
203 203  
204 -DimensionComponent can be a Dimension or a TimeDimension.
193 +DimensionComponent can be a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] or a TimeDimension.
205 205  
206 -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.
195 +Correspondingly, in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] implementation of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], the [[VTL>>doc:xwiki: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:xwiki:Glossary.Validation and transformation language.WebHome]] IM.
207 207  
208 208  The possible mapping options are described in more detail in the following sections.
209 209  
210 210  === 12.3.3 Mapping from SDMX to VTL data structures ===
211 211  
212 -**12.3.3.1 Basic Mapping**
201 +==== 12.3.3.1 Basic Mapping ====
213 213  
214 -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. 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:
203 +The main mapping method from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki: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. When transforming **from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]**, this method consists in leaving the [[components>>doc:xwiki:Glossary.Component.WebHome]] unchanged and maintaining their names and roles, according to the following table:
215 215  
216 -|**SDMX**|**VTL**
217 -|Dimension|(Simple) Identifier
218 -|TimeDimension|(Time) Identifier
205 +(% style="width:529.294px" %)
206 +|(% style="width:151px" %)**SDMX**|(% style="width:375px" %)**VTL**
207 +|(% style="width:151px" %)Dimension|(% style="width:375px" %)(Simple) Identifier
208 +|(% style="width:151px" %)TimeDimension|(% style="width:375px" %)(Time) Identifier
209 +|(% style="width:151px" %)Measure|(% style="width:375px" %)Measure
210 +|(% style="width:151px" %)DataAttribute|(% style="width:375px" %)Attribute
219 219  
220 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape4" height="1" width="192"]]
212 +The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes, in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] they are all considered "at data point / observation (% style="color:#2ecc71" %)level(%%) (i.e. dependent on all the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Identifiers), because [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] does not have the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] or set or group of [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]], whole [[data set>>doc:xwiki:Glossary.Data set.WebHome]]).
221 221  
222 -|Measure|Measure
223 -|DataAttribute|Attribute
214 +With the Basic mapping, one [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observation{{footnote}}Here an SDMX observation is meant to correspond to one combination of values of the DimensionComponents.{{/footnote}} generates one [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data point.
224 224  
225 -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).
216 +==== 12.3.3.2 Pivot Mapping ====
226 226  
227 -With the Basic mapping, one SDMX observation^^27^^ generates one VTL data point.
218 +An alternative mapping method from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data structures that contain a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] that plays the role of [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] (like in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1) and just one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]. Through this method, these structures can be (% style="color:#2ecc71" %)mapped(%%) to multimeasure [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structures. Besides that, a user may choose to use any [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] acting as a list of [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] (e.g., a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] with indicators), either by considering the “[[Measure>>doc:xwiki:Glossary.Measure.WebHome]]” role of a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], or at will using any coded [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]. Of course, in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, this can only work when only one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] is defined in the DSD.
228 228  
229 -**12.3.3.2 Pivot Mapping**
220 +In [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 the MeasureDimension was a subclass of DimensionComponent like [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] and TimeDimension. In the current [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)version(%%), this subclass does not exist anymore, however a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] can have the role of [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] (i.e. a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] that contributes to the identification of the [[measures>>doc:xwiki:Glossary.Measure.WebHome]]). In [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 a DataStructure could have zero or one MeasureDimensions, in the current (% style="color:#2ecc71" %)version(%%) of the standard, from zero to many [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] may have the role of [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]]. Hereinafter a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] that plays the role of [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[dimension>>doc:xwiki: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:xwiki:Glossary.SDMX Information Model.WebHome]] of the current [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)version(%%). For the sake of simplicity, the description below considers just one [[Dimension>>doc:xwiki: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:xwiki: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}}.
230 230  
231 -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.
222 +Among other things, the Pivot method provides also backward compatibility with the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 data structures that contained a MeasureDimension.
232 232  
233 -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
224 +If applied to [[SDMX>>doc:xwiki: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).
234 234  
235 -MeasureDimensions considered as a joint variable^^[[^^24^^>>path:#sdfootnote24sym||name="sdfootnote24anc"]]^^.
226 +Here an [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observation is meant to correspond to one combination of values of the DimensionComponents.
236 236  
237 -Among other things, the Pivot method provides also backward compatibility with the SDMX 2.1 data structures that contained a MeasureDimension.
228 +The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] structures that contain a MeasureDimension are (% style="color:#2ecc71" %)mapped(%%) as described below (this mapping is equivalent to a pivoting operation):
238 238  
239 -If applied to SDMX structures that do not contain any MeasureDimension, this method behaves like the Basic mapping (see the previous paragraph).
230 +* A [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] simple [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] becomes a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (simple) identifier and a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] TimeDimension becomes a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (time) identifier;
231 +* Each possible [[Code>>doc:xwiki:Glossary.Code.WebHome]] Cj of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension is (% style="color:#2ecc71" %)mapped(%%) to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], having the same name as the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Code>>doc:xwiki:Glossary.Code.WebHome]] (i.e. Cj); the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] Cj is a new [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[component>>doc:xwiki:Glossary.Component.WebHome]] even if the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data structure has not such a [[Component>>doc:xwiki:Glossary.Component.WebHome]];
232 +* The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension is not (% style="color:#2ecc71" %)mapped(%%) to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (it disappears in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Structure);
233 +* The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] is not (% style="color:#2ecc71" %)mapped(%%) to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] as well (it disappears in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Structure);
234 +* An [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is (% style="color:#2ecc71" %)mapped(%%) in different ways according to its AttributeRelationship:
235 +** If, according to the [[SDMX>>doc:xwiki: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:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute becomes a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:xwiki: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:xwiki:Glossary.Data set.WebHome]] (% style="color:#2ecc71" %)level(%%)), or if it refers to a set (or a group) of [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] which does not include the MeasureDimension;
236 +** Otherwise, if, according to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is (% style="color:#2ecc71" %)mapped(%%) to one [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] for each possible [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension. By default, the names of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] are obtained by concatenating the name of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute and the names of the correspondent [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the MeasureDimension separated by underscore. For example, if the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute is named DA and the possible [[Codes>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension are named C1, C2, …, Cn, then the corresponding [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:xwiki: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:xwiki:Glossary.Attribute.WebHome]] through [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operators).
237 +** Like in the Basic mapping, the resulting [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] are considered as dependent on all the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] identifiers (i.e. "at data point / observation (% style="color:#2ecc71" %)level(%%)"), because [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] does not have the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] notion of [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] Relationship.
240 240  
241 -^^27^^ Here an SDMX observation is meant to correspond to one combination of values of the DimensionComponents.
239 +The summary mapping table of the "pivot" mapping from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] for the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data structures that contain a MeasureDimension is the following:
242 242  
243 -The SDMX structures that contain a MeasureDimension are mapped as described below (this mapping is equivalent to a pivoting operation):
244 -
245 -* A SDMX simple dimension becomes a VTL (simple) identifier and a SDMX TimeDimension becomes a VTL (time) identifier;
246 -* 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
247 -
248 -Component;
249 -
250 -* The SDMX MeasureDimension is not mapped to VTL (it disappears in the VTL Data Structure);
251 -* The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
252 -* An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
253 -** 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
254 -
255 -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;
256 -
257 -*
258 -** 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).
259 -** 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.
260 -
261 -The summary mapping table of the "pivot" mapping from SDMX to VTL for the SDMX data structures that contain a MeasureDimension is the following:
262 -
263 -|**SDMX**|**VTL**
264 -|Dimension|(Simple) Identifier
265 -|TimeDimension|(Time) Identifier
266 -|MeasureDimension & one Measure|(((
267 -One Measure for each Code of the
268 -
269 -SDMX MeasureDimension
241 +(% style="width:769.294px" %)
242 +|(% style="width:401px" %)**[[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]**|(% style="width:366px" %)**[[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]**
243 +|(% style="width:401px" %)[[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]|(% style="width:366px" %)(Simple) Identifier
244 +|(% style="width:401px" %)TimeDimension|(% style="width:366px" %)(Time) Identifier
245 +|(% style="width:401px" %)MeasureDimension & one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]|(% style="width:366px" %)(((
246 +One [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] for each [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension
270 270  )))
271 -|DataAttribute not depending on the MeasureDimension|Attribute
272 -|DataAttribute depending on the MeasureDimension|(((
273 -One Attribute for each Code of the
274 -
275 -SDMX MeasureDimension
248 +|(% style="width:401px" %)DataAttribute not depending on the MeasureDimension|(% style="width:366px" %)[[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
249 +|(% style="width:401px" %)DataAttribute depending on the MeasureDimension|(% style="width:366px" %)(((
250 +One [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] for each [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension
276 276  )))
277 277  
278 -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.
253 +Using this mapping method, the [[components>>doc:xwiki:Glossary.Component.WebHome]] of the data structure can change in the conversion from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and it must be taken into account that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] statements can reference only the [[components>>doc:xwiki:Glossary.Component.WebHome]] of the resulting [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure.
279 279  
280 -At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
255 +At observation / data point (% style="color:#2ecc71" %)level(%%), calling Cj (j=1, … n) the j^^th^^ [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the MeasureDimension:
281 281  
282 -* 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;
283 -* 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)
257 +* The set of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observations having the same values for all the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] except than the MeasureDimension become one multi-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Point, having one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] for each [[Code>>doc:xwiki:Glossary.Code.WebHome]] Cj of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension;
258 +* The values of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] simple [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension and DataAttributes not depending on the MeasureDimension (these [[components>>doc:xwiki: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:xwiki:Glossary.Validation and transformation language.WebHome]] (simple) Identifiers, (time) Identifier and [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]].
259 +* The value of the [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observation belonging to the set above and having MeasureDimension=Cj becomes the value of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] Cj
260 +* For the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observation belonging to the set above and having MeasureDimension=Cj becomes the value of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] DA_Cj
284 284  
285 -Identifiers, (time) Identifier and Attributes.
262 +==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
286 286  
287 -* The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
288 -* 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
264 +* In some cases, it may happen that the DataAttributes of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure need to be managed as [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]. Therefore, a variant of both the methods above consists in transforming all the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]]. When DataAttributes are converted to [[Measures>>doc:xwiki:Glossary.Measure.WebHome]], the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] to [[Measures>>doc:xwiki:Glossary.Measure.WebHome]]). Obviously, the resulting [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure is, in general, multi-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] and does not contain [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]].
289 289  
290 -**12.3.3.3 From SDMX DataAttributes to VTL Measures**
266 +The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[components>>doc:xwiki:Glossary.Component.WebHome]], which according to the Basic and Pivot methods would have had the role of [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]], assume instead the role of [[Measure>>doc:xwiki:Glossary.Measure.WebHome]].
291 291  
292 -* 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
268 +Proper [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] features allow changing the role of specific [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] even after the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] mapping: they can be useful when only some of the DataAttributes need to be managed as [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]].
293 293  
294 -Attributes.
295 -
296 -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.
297 -
298 -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.
299 -
300 300  === 12.3.4 Mapping from VTL to SDMX data structures ===
301 301  
302 -**12.3.4.1 Basic Mapping**
272 +==== 12.3.4.1 Basic Mapping ====
303 303  
304 -The main mapping method **from VTL to SDMX** is called **Basic **mapping as well.
274 +The main mapping method **from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]** is called **Basic **mapping as well.
305 305  
306 306  This is considered as the default mapping method and is applied unless a different method is specified through the VtlMappingScheme and VtlDataflowMapping classes.
307 307  
308 -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.
278 +The method consists in leaving the [[components>>doc:xwiki:Glossary.Component.WebHome]] unchanged and maintaining their names and roles in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], according to the following mapping table, which is the same as the basic mapping from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], only seen in the opposite direction.
309 309  
310 310  Mapping table:
311 311  
312 -|**VTL**|**SDMX**
313 -|(Simple) Identifier|Dimension
314 -|(Time) Identifier|TimeDimension
315 -|Measure|Measure
316 -|Attribute|DataAttribute
282 +(% style="width:667.294px" %)
283 +|(% style="width:272px" %)**VTL**|(% style="width:392px" %)**SDMX**
284 +|(% style="width:272px" %)(Simple) Identifier|(% style="width:392px" %)Dimension
285 +|(% style="width:272px" %)(Time) Identifier|(% style="width:392px" %)TimeDimension
286 +|(% style="width:272px" %)Measure|(% style="width:392px" %)Measure
287 +|(% style="width:272px" %)Attribute|(% style="width:392px" %)DataAttribute
317 317  
318 318  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.
319 319  
... ... @@ -323,7 +323,7 @@
323 323  
324 324  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.
325 325  
326 -**12.3.4.2 Unpivot Mapping**
297 +==== 12.3.4.2 Unpivot Mapping ====
327 327  
328 328  An alternative mapping method from VTL to SDMX is the **Unpivot **mapping.
329 329  
... ... @@ -347,11 +347,12 @@
347 347  
348 348  The summary mapping table of the **unpivot** mapping method is the following:
349 349  
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
321 +(% style="width:994.294px" %)
322 +|(% style="width:306px" %)**VTL**|(% style="width:684px" %)**SDMX**
323 +|(% style="width:306px" %)(Simple) Identifier|(% style="width:684px" %)Dimension
324 +|(% style="width:306px" %)(Time) Identifier|(% style="width:684px" %)TimeDimension
325 +|(% style="width:306px" %)All Measure Components|(% style="width:684px" %)MeasureDimension (having one Code for each VTL measure component) & one Measure
326 +|(% style="width:306px" %)Attribute|(% style="width:684px" %)DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
355 355  
356 356  At observation / data point level:
357 357  
... ... @@ -365,7 +365,7 @@
365 365  
366 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.
367 367  
368 -**12.3.4.3 From VTL Measures to SDMX Data Attributes**
340 +==== 12.3.4.3 From VTL Measures to SDMX Data Attributes ====
369 369  
370 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”).
371 371  
... ... @@ -373,12 +373,13 @@
373 373  
374 374  The mapping table is the following:
375 375  
376 -|VTL|SDMX
377 -|(Simple) Identifier|Dimension
378 -|(Time) Identifier|TimeDimension
379 -|Some Measures|Measure
380 -|Other Measures|DataAttribute
381 -|Attribute|DataAttribute
348 +(% style="width:689.294px" %)
349 +|(% style="width:344px" %)**VTL**|(% style="width:341px" %)**SDMX**
350 +|(% style="width:344px" %)(Simple) Identifier|(% style="width:341px" %)Dimension
351 +|(% style="width:344px" %)(Time) Identifier|(% style="width:341px" %)TimeDimension
352 +|(% style="width:344px" %)Some Measures|(% style="width:341px" %)Measure
353 +|(% style="width:344px" %)Other Measures|(% style="width:341px" %)DataAttribute
354 +|(% style="width:344px" %)Attribute|(% style="width:341px" %)DataAttribute
382 382  
383 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.
384 384  
... ... @@ -396,20 +396,20 @@
396 396  
397 397  Until now it has been assumed to map one SMDX Dataflow to one VTL Data Set and vice-versa. This mapping one-to-one is not mandatory according to VTL because a VTL Data Set is meant to be a set of observations (data points) on a logical plane, having the same logical data structure and the same general meaning, independently of the possible physical representation or storage (see VTL 2.0 User Manual page 24), therefore a SDMX Dataflow can be seen either as a unique set of data observations (corresponding to one VTL Data Set) or as the union of many sets of data observations (each one corresponding to a distinct VTL Data Set).
398 398  
399 -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.^^[[^^25^^>>path:#sdfootnote25sym||name="sdfootnote25anc"]]^^
372 +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}}
400 400  
401 -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.^^[[^^26^^>>path:#sdfootnote26sym||name="sdfootnote26anc"]]^^
374 +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}}
402 402  
403 403  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.
404 404  
405 405  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:
406 406  
407 -* For a given SDMX Dataflow, the user (VTL definer) declares the DimensionComponents on which the mapping will be based, in a given order.^^[[^^27^^>>path:#sdfootnote27sym||name="sdfootnote27anc"]]^^ Following the example above, imagine that the user declares the Dimensions INDICATOR and COUNTRY.
380 +* 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.
408 408  * The VTL Data Set is given a name using a special notation also called “ordered concatenation” and composed of the following parts:
409 409  ** 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);
410 -** a slash (“/”) as a separator; ^^[[^^28^^>>path:#sdfootnote28sym||name="sdfootnote28anc"]]^^
383 +** 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}}
411 411  
412 -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^^[[^^29^^>>path:#sdfootnote29sym||name="sdfootnote29anc"]]^^. For example 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.
385 +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 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.
413 413  
414 414  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.
415 415  
... ... @@ -425,36 +425,24 @@
425 425  
426 426  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.
427 427  
428 -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^^[[^^30^^>>path:#sdfootnote30sym||name="sdfootnote30anc"]]^^ 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.
401 +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.
429 429  
430 430  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.
431 431  
432 432  As already said, each VTL Data Set is assumed to contain all the observations of the
433 433  
434 -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.
407 +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.
435 435  
436 -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^^[[^^31^^>>path:#sdfootnote31sym||name="sdfootnote31anc"]]^^. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e.
409 +In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e. basic, pivot …).
437 437  
438 -basic, pivot …).
411 +In the example above, for all the datasets of the kind ‘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.
439 439  
440 -In the example above, for all the datasets of the kind
441 -
442 -‘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.
443 -
444 444  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:
445 445  
446 -‘DF1(1.0.0)/POPULATION.USA’ :=
415 +[[image:1747388275998-621.png]]
447 447  
448 -DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
417 +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}}
449 449  
450 -‘DF1(1.0.0)/POPULATION.CANADA’ :=
451 -
452 -DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
453 -
454 -… … …
455 -
456 -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. ^^[[^^32^^>>path:#sdfootnote32sym||name="sdfootnote32anc"]]^^
457 -
458 458  In the direction from SDMX to VTL it is allowed to omit the value of one or more
459 459  
460 460  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.
... ... @@ -463,10 +463,8 @@
463 463  
464 464  This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
465 465  
466 -‘DF1(1.0.0)/POPULATION.’ :=
427 +[[image:1747388244829-693.png]]
467 467  
468 -DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
469 -
470 470  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
471 471  
472 472  Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different
... ... @@ -481,70 +481,34 @@
481 481  
482 482  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:
483 483  
484 -* each part is calculated as a VTL derived Data Set, result of a dedicated VTL Transformation; ^^[[^^33^^>>path:#sdfootnote33sym||name="sdfootnote33anc"]]^^
485 -* the data structure of all these VTL Data Sets has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.^^[[^^34^^>>path:#sdfootnote34sym||name="sdfootnote34anc"]]^^
443 +* 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}}
444 +* 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}}
486 486  
487 -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^^[[^^35^^>>path:#sdfootnote35sym||name="sdfootnote35anc"]]^^.
446 +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}}.
488 488  
489 -The corresponding VTL Transformations, assuming that the result needs to be persistent, would be of this kind:^^ [[^^36^^>>path:#sdfootnote36sym||name="sdfootnote36anc"]]^^
448 +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}}
490 490  
491 491  ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
492 492  
493 493  Some examples follow, for some specific values of INDICATOR and COUNTRY:
494 494  
495 -‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
454 +[[image:1747388222879-916.png]]
496 496  
497 -… … …
456 +[[image:1747388206717-256.png]]
498 498  
499 -‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
500 -
501 -‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
502 -
503 -… … …
504 -
505 505  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:
506 506  
507 -VTL dataset INDICATOR value COUNTRY value
460 +[[image:1747388148322-387.png]]
508 508  
509 -‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
510 -
511 -‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
512 -
513 -‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
514 -
515 -‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
516 -
517 -… … …
518 -
519 519  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:
520 520  
521 -DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
464 +[[image:1747388179021-814.png]]
522 522  
523 -DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
524 -
525 -DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’
526 -
527 -[calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
528 -
529 -DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
530 -
531 -DF2(1.0) <- UNION (DF2bis_GDPPERCAPITA_USA’,
532 -
533 -DF2bis_GDPPERCAPITA_CANADA’,
534 -
535 -… ,
536 -
537 -DF2bis_POPGROWTH_USA’,
538 -
539 -DF2bis_POPGROWTH_CANADA’
540 -
541 -…);
542 -
543 543  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
544 544  
545 -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)^^[[^^37^^>>path:#sdfootnote37sym||name="sdfootnote37anc"]]^^, which can be mapped one-to-one to the homonymous SDMX Dataflow having the dimension components TIME_PERIOD, INDICATOR and COUNTRY.
468 +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 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. ^^[[^^38^^>>path:#sdfootnote38sym||name="sdfootnote38anc"]][[^^39^^>>path:#sdfootnote39sym||name="sdfootnote39anc"]]^^
470 +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}}
548 548  
549 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 550  
... ... @@ -552,52 +552,43 @@
552 552  
553 553  With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
554 554  
555 -|VTL|SDMX
556 -|**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^^
557 -|**Represented Variable**|(((
478 +(% style="width:895.294px" %)
479 +|(% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**
480 +|(% style="width:278px" %)**Data Set Component**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
481 +|(% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((
558 558  **Concept** with a definite
559 559  
560 560  Representation
561 561  )))
562 -|**Value Domain**|(((
563 -**Representation** (see the Structure
564 -
565 -Pattern in the Base Package)
486 +|(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)(((
487 +**Representation** (see the Structure Pattern in the Base Package)
566 566  )))
567 -|**Enumerated Value Domain / Code List**|**Codelist**
568 -|**Code**|(((
569 -**Code** (for enumerated
570 -
571 -DimensionComponent, Measure, DataAttribute)
489 +|(% style="width:278px" %)**Enumerated Value Domain /
490 +Code List**|(% style="width:613px" %)**Codelist**
491 +|(% style="width:278px" %)**Code**|(% style="width:613px" %)(((
492 +**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
572 572  )))
573 -|**Described Value Domain**|(((
574 -non-enumerated** &nbsp;&nbsp;&nbsp;Representation**
575 -
576 -(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
494 +|(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)(((
495 +non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
577 577  )))
578 -|**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
579 -||(((
580 -to a valid **value &nbsp;&nbsp;&nbsp;**(for non-enumerated** &nbsp;&nbsp;&nbsp;**
497 +|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations)
498 +|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
499 +|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
500 +|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
501 +|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX
581 581  
582 -Representations)
583 -)))
584 -|**Value Domain Subset / Set**|This abstraction does not exist in SDMX
585 -|**Enumerated Value Domain Subset / Enumerated Set**|This abstraction does not exist in SDMX
586 -|**Described Value Domain Subset / Described Set**|This abstraction does not exist in SDMX
587 -|**Set list**|This abstraction does not exist in SDMX
588 -
589 589  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).
590 590  
591 -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^^[[^^40^^>>path:#sdfootnote40sym||name="sdfootnote40anc"]]^^, while the SDMX Concepts can have different Representations in different DataStructures.^^[[^^41^^>>path:#sdfootnote41sym||name="sdfootnote41anc"]]^^ This means that one SDMX Concept can correspond to many VTL Variables, one for each representation the Concept has.
505 +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.
592 592  
593 593  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
594 594  
595 -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.
509 +DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
596 596  
511 +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.
512 +
597 597  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
598 598  
599 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape5" height="1" width="192"]]
600 -
601 601  Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
602 602  
603 603  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.
... ... @@ -610,140 +610,19 @@
610 610  
611 611  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:
612 612  
613 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]]
527 +[[image:1747388434672-948.png]]
614 614  
615 -==== Figure 22 – VTL Data Types ====
529 +(% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
530 +**Figure 22 – VTL Data Types**
616 616  
617 617  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.
618 618  
619 619  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):
620 620  
536 +[[image:1747388465321-274.png]]
621 621  
538 +**Figure 23 – VTL Basic Scalar Types**
622 622  
623 -(((
624 -//n//
625 -
626 -//a//
627 -
628 -//e//
629 -
630 -//l//
631 -
632 -//o//
633 -
634 -//o//
635 -
636 -//B//
637 -
638 -//n//
639 -
640 -//o//
641 -
642 -//i//
643 -
644 -//t//
645 -
646 -//a//
647 -
648 -//r//
649 -
650 -//u//
651 -
652 -//D//
653 -
654 -//d//
655 -
656 -//o//
657 -
658 -//i//
659 -
660 -//r//
661 -
662 -//e//
663 -
664 -//p//
665 -
666 -//_//
667 -
668 -//e//
669 -
670 -//m//
671 -
672 -//i//
673 -
674 -//T//
675 -
676 -//e//
677 -
678 -//t//
679 -
680 -//a//
681 -
682 -//D//
683 -
684 -//e//
685 -
686 -//m//
687 -
688 -//i//
689 -
690 -//T//
691 -
692 -//r//
693 -
694 -//e//
695 -
696 -//g//
697 -
698 -//e//
699 -
700 -//t//
701 -
702 -//n//
703 -
704 -//I//
705 -
706 -//r//
707 -
708 -//e//
709 -
710 -//b//
711 -
712 -//m//
713 -
714 -//u//
715 -
716 -//N//
717 -
718 -//g//
719 -
720 -//n//
721 -
722 -//i//
723 -
724 -//r//
725 -
726 -//t//
727 -
728 -//S//
729 -
730 -//r//
731 -
732 -//a//
733 -
734 -//l//
735 -
736 -//a//
737 -
738 -//c//
739 -
740 -//S//
741 -
742 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_82d45833.gif||alt="Shape6" height="231" width="184"]]
743 -)))
744 -
745 -==== Figure 23 – VTL Basic Scalar Types ====
746 -
747 747  === 12.4.2 VTL basic scalar types and SDMX data types ===
748 748  
749 749  The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
... ... @@ -766,204 +766,159 @@
766 766  
767 767  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
768 768  
769 -|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
770 -|(((
562 +(% style="width:823.294px" %)
563 +|(% style="width:509px" %)**SDMX data type (BasicComponentDataType)**|(% style="width:312px" %)**Default VTL basic scalar type**
564 +|(% style="width:509px" %)(((
771 771  String
772 -
773 773  (string allowing any character)
774 -)))|string
775 -|(((
567 +)))|(% style="width:312px" %)string
568 +|(% style="width:509px" %)(((
776 776  Alpha
777 -
778 778  (string which only allows A-z)
779 -)))|string
780 -|(((
571 +)))|(% style="width:312px" %)string
572 +|(% style="width:509px" %)(((
781 781  AlphaNumeric
782 -
783 783  (string which only allows A-z and 0-9)
784 -)))|string
785 -|(((
575 +)))|(% style="width:312px" %)string
576 +|(% style="width:509px" %)(((
786 786  Numeric
787 -
788 788  (string which only allows 0-9, but is not numeric so that is can having leading zeros)
789 -)))|string
790 -|(((
579 +)))|(% style="width:312px" %)string
580 +|(% style="width:509px" %)(((
791 791  BigInteger
792 -
793 793  (corresponds to XML Schema xs:integer datatype; infinite set of integer values)
794 -)))|integer
795 -|(((
583 +)))|(% style="width:312px" %)integer
584 +|(% style="width:509px" %)(((
796 796  Integer
797 -
798 -(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
799 -
800 -(inclusive))
801 -)))|integer
802 -|(((
586 +(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647 (inclusive))
587 +)))|(% style="width:312px" %)integer
588 +|(% style="width:509px" %)(((
803 803  Long
804 -
805 -(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
806 -
807 -+9223372036854775807 (inclusive))
808 -)))|integer
809 -|(((
590 +(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and +9223372036854775807 (inclusive))
591 +)))|(% style="width:312px" %)integer
592 +|(% style="width:509px" %)(((
810 810  Short
811 -
812 812  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
813 -)))|integer
814 -|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
815 -|(((
595 +)))|(% style="width:312px" %)integer
596 +|(% style="width:509px" %)Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:312px" %)number
597 +|(% style="width:509px" %)(((
816 816  Float
817 -
818 818  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
819 -)))|number
820 -|(((
600 +)))|(% style="width:312px" %)number
601 +|(% style="width:509px" %)(((
821 821  Double
822 -
823 823  (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
824 -)))|number
825 -|(((
604 +)))|(% style="width:312px" %)number
605 +|(% style="width:509px" %)(((
826 826  Boolean
607 +(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of binary-valued logic: {true, false})
608 +)))|(% style="width:312px" %)boolean
827 827  
828 -(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
829 -
830 -binary-valued logic: {true, false})
831 -)))|boolean
832 -
833 -||(% colspan="2" %)(((
610 +(% style="width:822.294px" %)
611 +|(% colspan="2" style="width:507px" %)(((
834 834  URI
835 -
836 836  (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
837 -)))|(% colspan="2" %)string
838 -||(% colspan="2" %)(((
614 +)))|(% colspan="1" style="width:311px" %)string
615 +|(% colspan="2" style="width:507px" %)(((
839 839  Count
840 -
841 841  (an integer following a sequential pattern, increasing by 1 for each occurrence)
842 -)))|(% colspan="2" %)integer
843 -||(% colspan="2" %)(((
618 +)))|(% colspan="1" style="width:311px" %)integer
619 +|(% colspan="2" style="width:507px" %)(((
844 844  InclusiveValueRange
845 -
846 846  (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
847 -)))|(% colspan="2" %)number
848 -||(% colspan="2" %)(((
622 +)))|(% colspan="1" style="width:311px" %)number
623 +|(% colspan="2" style="width:507px" %)(((
849 849  ExclusiveValueRange
850 -
851 851  (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
852 -)))|(% colspan="2" %)number
853 -||(% colspan="2" %)(((
626 +)))|(% colspan="1" style="width:311px" %)number
627 +|(% colspan="2" style="width:507px" %)(((
854 854  Incremental
855 -
856 856  (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
857 -)))|(% colspan="2" %)number
858 -||(% colspan="2" %)(((
630 +)))|(% colspan="1" style="width:311px" %)number
631 +|(% colspan="2" style="width:507px" %)(((
859 859  ObservationalTimePeriod
860 -
861 861  (superset of StandardTimePeriod and TimeRange)
862 -)))|(% colspan="2" %)time
863 -||(% colspan="2" %)(((
634 +)))|(% colspan="1" style="width:311px" %)time
635 +|(% colspan="2" style="width:507px" %)(((
864 864  StandardTimePeriod
865 -
866 -(superset of BasicTimePeriod and
867 -
868 -ReportingTimePeriod)
869 -)))|(% colspan="2" %)time
870 -||(% colspan="2" %)(((
637 +(superset of BasicTimePeriod and ReportingTimePeriod)
638 +)))|(% colspan="1" style="width:311px" %)time
639 +|(% colspan="2" style="width:507px" %)(((
871 871  BasicTimePeriod
872 -
873 873  (superset of GregorianTimePeriod and DateTime)
874 -)))|(% colspan="2" %)date
875 -||(% colspan="2" %)(((
642 +)))|(% colspan="1" style="width:311px" %)date
643 +|(% colspan="2" style="width:507px" %)(((
876 876  GregorianTimePeriod
877 -
878 878  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
879 -)))|(% colspan="2" %)date
880 -||(% colspan="2" %)GregorianYear (YYYY)|(% colspan="2" %)date
881 -||(% colspan="2" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% colspan="2" %)date
882 -||(% colspan="2" %)GregorianDay (YYYY-MM-DD)|(% colspan="2" %)date
883 -||(% colspan="2" %)(((
646 +)))|(% colspan="1" style="width:311px" %)date
647 +|(% colspan="2" style="width:507px" %)GregorianYear (YYYY)|(% colspan="1" style="width:311px" %)date
648 +|(% colspan="2" style="width:507px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% colspan="1" style="width:311px" %)date
649 +|(% colspan="2" style="width:507px" %)GregorianDay (YYYY-MM-DD)|(% colspan="1" style="width:311px" %)date
650 +|(% colspan="2" style="width:507px" %)(((
884 884  ReportingTimePeriod
885 -
886 -(superset of RepostingYear, ReportingSemester,
887 -
888 -ReportingTrimester, ReportingQuarter,
889 -
890 -ReportingMonth, ReportingWeek, ReportingDay)
891 -)))|(% colspan="2" %)time_period
892 -||(% colspan="2" %)(((
652 +(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
653 +)))|(% colspan="1" style="width:311px" %)time_period
654 +|(% colspan="2" style="width:507px" %)(((
893 893  ReportingYear
894 -
895 895  (YYYY-A1 – 1 year period)
896 -)))|(% colspan="2" %)time_period
897 -||(% colspan="2" %)(((
657 +)))|(% colspan="1" style="width:311px" %)time_period
658 +|(% colspan="2" style="width:507px" %)(((
898 898  ReportingSemester
899 -
900 900  (YYYY-Ss – 6 month period)
901 -)))|(% colspan="2" %)time_period
902 -||(% colspan="2" %)(((
661 +)))|(% colspan="1" style="width:311px" %)time_period
662 +|(% colspan="2" style="width:507px" %)(((
903 903  ReportingTrimester
904 -
905 905  (YYYY-Tt – 4 month period)
906 -)))|(% colspan="2" %)time_period
907 -||(% colspan="2" %)(((
665 +)))|(% colspan="1" style="width:311px" %)time_period
666 +|(% colspan="2" style="width:507px" %)(((
908 908  ReportingQuarter
909 -
910 910  (YYYY-Qq – 3 month period)
911 -)))|(% colspan="2" %)time_period
912 -||(% colspan="2" %)(((
669 +)))|(% colspan="1" style="width:311px" %)time_period
670 +|(% colspan="2" style="width:507px" %)(((
913 913  ReportingMonth
914 -
915 915  (YYYY-Mmm – 1 month period)
916 -)))|(% colspan="2" %)time_period
917 -||(% colspan="2" %)ReportingWeek|(% colspan="2" %)time_period
918 -||(% colspan="2" %)|(% colspan="2" %)
919 -||(% colspan="2" %)|(% colspan="2" %)
920 -|(% colspan="2" %)(YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% colspan="2" %)|
921 -|(% colspan="2" %)(((
673 +)))|(% colspan="1" style="width:311px" %)time_period
674 +|(% colspan="2" style="width:507px" %)ReportingWeek|(% colspan="1" style="width:311px" %)time_period
675 +|(% colspan="1" style="width:507px" %)(YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% colspan="2" style="width:312px" %)
676 +|(% colspan="1" style="width:507px" %)(((
922 922  ReportingDay
923 -
924 924  (YYYY-Dddd – 1 day period)
925 -)))|(% colspan="2" %)time_period|
926 -|(% colspan="2" %)(((
679 +)))|(% colspan="2" style="width:312px" %)time_period
680 +|(% colspan="1" style="width:507px" %)(((
927 927  DateTime
928 -
929 929  (YYYY-MM-DDThh:mm:ss)
930 -)))|(% colspan="2" %)date|
931 -|(% colspan="2" %)(((
683 +)))|(% colspan="2" style="width:312px" %)date
684 +|(% colspan="1" style="width:507px" %)(((
932 932  TimeRange
933 -
934 934  (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
935 -)))|(% colspan="2" %)time|
936 -|(% colspan="2" %)(((
687 +)))|(% colspan="2" style="width:312px" %)time
688 +|(% colspan="1" style="width:507px" %)(((
937 937  Month
938 -
939 939  (~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
940 -)))|(% colspan="2" %)string|
941 -|(% colspan="2" %)(((
691 +)))|(% colspan="2" style="width:312px" %)string
692 +|(% colspan="1" style="width:507px" %)(((
942 942  MonthDay
943 -
944 944  (~-~-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)
945 -)))|(% colspan="2" %)string|
946 -|(% colspan="2" %)(((
695 +)))|(% colspan="2" style="width:312px" %)string
696 +|(% colspan="1" style="width:507px" %)(((
947 947  Day
948 -
949 949  (~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
950 -)))|(% colspan="2" %)string|
951 -|(% colspan="2" %)(((
699 +)))|(% colspan="2" style="width:312px" %)string
700 +|(% colspan="1" style="width:507px" %)(((
952 952  Time
953 -
954 954  (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
955 -)))|(% colspan="2" %)string|
956 -|(% colspan="2" %)(((
703 +)))|(% colspan="2" style="width:312px" %)string
704 +|(% colspan="1" style="width:507px" %)(((
957 957  Duration
958 -
959 959  (corresponds to XML Schema xs:duration datatype)
960 -)))|(% colspan="2" %)duration|
961 -|(% colspan="2" %)XHTML|(% colspan="2" %)Metadata type – not applicable|
962 -|(% colspan="2" %)KeyValues|(% colspan="2" %)Metadata type – not applicable|
963 -|(% colspan="2" %)IdentifiableReference|(% colspan="2" %)Metadata type – not applicable|
964 -|(% colspan="2" %)DataSetReference|(% colspan="2" %)Metadata type – not applicable|
707 +)))|(% colspan="2" style="width:312px" %)duration
708 +|(% colspan="1" style="width:507px" %)XHTML|(% colspan="2" style="width:312px" %)Metadata type – not applicable
709 +|(% colspan="1" style="width:507px" %)KeyValues|(% colspan="2" style="width:312px" %)Metadata type – not applicable
710 +|(% colspan="1" style="width:507px" %)IdentifiableReference|(% colspan="2" style="width:312px" %)Metadata type – not applicable
711 +|(% colspan="1" style="width:507px" %)DataSetReference|(% colspan="2" style="width:312px" %)Metadata type – not applicable
965 965  
966 -==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
713 +(% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes" %)
714 +**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
967 967  
968 968  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).
969 969  
... ... @@ -971,93 +971,86 @@
971 971  
972 972  The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
973 973  
974 -|(((
975 -VTL basic
976 -
977 -scalar type
978 -)))|(((
979 -Default SDMX data type
980 -
981 -(BasicComponentDataType
982 -
983 -)
984 -)))|Default output format
985 -|String|String|Like XML (xs:string)
986 -|Number|Float|Like XML (xs:float)
987 -|Integer|Integer|Like XML (xs:int)
988 -|Date|DateTime|YYYY-MM-DDT00:00:00Z
989 -|Time|StandardTimePeriod|<date>/<date> (as defined above)
990 -|time_period|(((
722 +(% style="width:1073.29px" %)
723 +|(% style="width:207px" %)(((
724 +**VTL basic scalar type**
725 +)))|(% style="width:462px" %)(((
726 +**Default SDMX data type (BasicComponentDataType)**
727 +)))|(% style="width:402px" %)**Default output format**
728 +|(% style="width:207px" %)String|(% style="width:462px" %)String|(% style="width:402px" %)Like XML (xs:string)
729 +|(% style="width:207px" %)Number|(% style="width:462px" %)Float|(% style="width:402px" %)Like XML (xs:float)
730 +|(% style="width:207px" %)Integer|(% style="width:462px" %)Integer|(% style="width:402px" %)Like XML (xs:int)
731 +|(% style="width:207px" %)Date|(% style="width:462px" %)DateTime|(% style="width:402px" %)YYYY-MM-DDT00:00:00Z
732 +|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)<date>/<date> (as defined above)
733 +|(% style="width:207px" %)time_period|(% style="width:462px" %)(((
991 991  ReportingTimePeriod
992 -
993 993  (StandardReportingPeriod)
994 -)))|(((
736 +)))|(% style="width:402px" %)(((
995 995  YYYY-Pppp
996 -
997 997  (according to SDMX )
998 998  )))
999 -|Duration|Duration|(((
740 +|(% style="width:207px" %)Duration|(% style="width:462px" %)Duration|(% style="width:402px" %)(((
1000 1000  Like XML (xs:duration)
1001 -
1002 1002  PnYnMnDTnHnMnS
1003 1003  )))
1004 -|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
744 +|(% style="width:207px" %)Boolean|(% style="width:462px" %)Boolean|(% style="width:402px" %)Like XML (xs:boolean) with the values "true" or "false"
1005 1005  
1006 -==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
746 +(% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes-1" %)
747 +**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
1007 1007  
1008 1008  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).
1009 1009  
1010 1010  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.
1011 1011  
1012 -|(% colspan="2" %)VTL special characters for the formatting masks
1013 -|(% colspan="2" %)
1014 -|(% colspan="2" %)Number
1015 -|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
1016 -|E|one numeric digit (for the exponent of the scientific notation)
1017 -|. (dot)|possible separator between the integer and the decimal parts.
1018 -|, (comma)|possible separator between the integer and the decimal parts.
1019 -||
1020 -|(% colspan="2" %)Time and duration
1021 -|C|century
1022 -|Y|year
1023 -|S|semester
1024 -|Q|quarter
1025 -|M|month
1026 -|W|week
1027 -|D|day
1028 -|h|hour digit (by default on 24 hours)
1029 -|M|minute
1030 -|S|second
1031 -|D|decimal of second
1032 -|P|period indicator (representation in one digit for the duration)
1033 -|P|number of the periods specified in the period indicator
1034 -|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
1035 -|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
1036 -|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
1037 -|Month|lowercase textual representation of the month (e.g., january)
1038 -|Day|lowercase textual representation of the month (e.g., monday)
1039 -|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
1040 -|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
1041 -||
1042 -|(% colspan="2" %)String
1043 -|X|any string character
1044 -|Z|any string character from "A" to "z"
1045 -|9|any string character from "0" to "9"
1046 -||
1047 -|(% colspan="2" %)Boolean
1048 -|B|Boolean using "true" for True and "false" for False
1049 -|1|Boolean using "1" for True and "0" for False
1050 -|0|Boolean using "0" for True and "1" for False
1051 -||
1052 -|(% colspan="2" %)Other qualifiers
1053 -|*|an arbitrary number of digits (of the preceding type)
1054 -|+|at least one digit (of the preceding type)
1055 -|( )|optional digits (specified within the brackets)
1056 -|\|prefix for the special characters that must appear in the mask
1057 -|N|fixed number of digits used in the preceding textual representation of the month or the day
1058 -||
753 +(% style="width:713.294px" %)
754 +|(% colspan="2" style="width:710px" %)VTL special characters for the formatting masks
755 +|(% colspan="2" style="width:710px" %)
756 +|(% colspan="2" style="width:710px" %)Number
757 +|D|(% style="width:486px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
758 +|E|(% style="width:486px" %)one numeric digit (for the exponent of the scientific notation)
759 +|. (dot)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
760 +|, (comma)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
761 +| |(% style="width:486px" %)
762 +|(% colspan="2" style="width:710px" %)Time and duration
763 +|C|(% style="width:486px" %)century
764 +|Y|(% style="width:486px" %)year
765 +|S|(% style="width:486px" %)semester
766 +|Q|(% style="width:486px" %)quarter
767 +|M|(% style="width:486px" %)month
768 +|W|(% style="width:486px" %)week
769 +|D|(% style="width:486px" %)day
770 +|h|(% style="width:486px" %)hour digit (by default on 24 hours)
771 +|M|(% style="width:486px" %)minute
772 +|S|(% style="width:486px" %)second
773 +|D|(% style="width:486px" %)decimal of second
774 +|P|(% style="width:486px" %)period indicator (representation in one digit for the duration)
775 +|P|(% style="width:486px" %)number of the periods specified in the period indicator
776 +|AM/PM|(% style="width:486px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
777 +|MONTH|(% style="width:486px" %)uppercase textual representation of the month (e.g., JANUARY for January)
778 +|DAY|(% style="width:486px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
779 +|Month|(% style="width:486px" %)lowercase textual representation of the month (e.g., january)
780 +|Day|(% style="width:486px" %)lowercase textual representation of the month (e.g., monday)
781 +|Month|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
782 +|Day|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
783 +| |(% style="width:486px" %)
784 +|(% colspan="2" style="width:710px" %)String
785 +|X|(% style="width:486px" %)any string character
786 +|Z|(% style="width:486px" %)any string character from "A" to "z"
787 +|9|(% style="width:486px" %)any string character from "0" to "9"
788 +| |(% style="width:486px" %)
789 +|(% colspan="2" style="width:710px" %)Boolean
790 +|B|(% style="width:486px" %)Boolean using "true" for True and "false" for False
791 +|1|(% style="width:486px" %)Boolean using "1" for True and "0" for False
792 +|0|(% style="width:486px" %)Boolean using "0" for True and "1" for False
793 +| |(% style="width:486px" %)
794 +|(% colspan="2" style="width:710px" %)Other qualifiers
795 +|*|(% style="width:486px" %)an arbitrary number of digits (of the preceding type)
796 +|+|(% style="width:486px" %)at least one digit (of the preceding type)
797 +|( )|(% style="width:486px" %)optional digits (specified within the brackets)
798 +|\|(% style="width:486px" %)prefix for the special characters that must appear in the mask
799 +|N|(% style="width:486px" %)fixed number of digits used in the preceding textual representation of the month or the day
1059 1059  
1060 -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^^[[^^42^^>>path:#sdfootnote42sym||name="sdfootnote42anc"]]^^.
801 +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}}.
1061 1061  
1062 1062  === 12.4.5 Null Values ===
1063 1063  
... ... @@ -1075,8 +1075,8 @@
1075 1075  
1076 1076  A different format can be specified in the attribute "vtlLiteralFormat" of the CustomType artefact (see also the section Transformations and Expressions of the SDMX information model).
1077 1077  
1078 -Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain VTL basic scalar type, if a value is found for the vtlLiteralFormat attribute of the CustomType of such VTL basic scalar type. The overriding assumption is applied for all the literals of a related VTL
819 +Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain VTL basic scalar type, if a value is found for the vtlLiteralFormat attribute of the CustomType of such VTL basic scalar type. The overriding assumption is applied for all the literals of a related VTL TransformationScheme.
1079 1079  
1080 -TransformationScheme.
1081 -
1082 1082  In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
822 +
823 +{{putFootnotes/}}
1747388148322-387.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
1747388179021-814.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +66.2 KB
Content
1747388206717-256.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +10.3 KB
Content
1747388222879-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +9.9 KB
Content
1747388244829-693.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +7.4 KB
Content
1747388275998-621.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +19.2 KB
Content
1747388434672-948.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
1747388465321-274.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_82d45833.gif
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +70.5 KB
Content