Changes for page 12 Validation and Transformation Language (VTL)

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

From 7.1 to 7.2 From 9.2 to 9.3

From version 7.2

edited by Helena
on 2025/05/17 00:29

Change comment: There is no comment for this version

To version 9.2

edited by Helena
on 2025/05/19 13:52

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Methodology.SDMX STANDARDS\: SECTION 6\. TECHNICAL NOTES Version 3\.0.WebHome

Content

@@ -286,62 +286,62 @@
  |(% style="width:272px" %)Measure|(% style="width:392px" %)Measure
  |(% style="width:272px" %)Attribute|(% style="width:392px" %)DataAttribute
--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.
++If the distinction between simple identifier and time identifier is not maintained in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] environment, the classification between [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] and TimeDimension exists only in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], as declared in the relevant DataStructureDefinition.
--Regarding the Attributes, because VTL considers all of them "at observation level", the corresponding SDMX DataAttributes should be put "at observation level" as well, unless some different information about their AttributeRelationship is otherwise available.
++Regarding the [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]], because [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] considers all of them "at observation (% style="color:#2ecc71" %)level(%%)", the corresponding [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes should be put "at observation (% style="color:#2ecc71" %)level(%%) as well, unless some different information about their AttributeRelationship is otherwise available.
--Note that the basic mappings in the two directions (from SDMX to VTL and vice-versa) are (almost completely) reversible. In fact, if a SDMX structure is mapped to a VTL structure and then the latter is mapped back to SDMX, the resulting data structure is like the original one (apart for the AttributeRelationship, that can be different if the original SDMX structure contains DataAttributes that are not at observation level). In reverse order, if a VTL structure is mapped to SDMX and then the latter is mapped back to VTL, the original data structure is obtained.
++Note that the basic mappings in the two directions (from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and vice-versa) are (almost completely) reversible. In fact, if a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] structure is (% style="color:#2ecc71" %)mapped(%%) to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structure and then the latter is (% style="color:#2ecc71" %)mapped(%%) back to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], the resulting data structure is like the original one (apart for the AttributeRelationship, that can be different if the original [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] structure contains DataAttributes that are not at observation (% style="color:#2ecc71" %)level(%%)). In reverse order, if a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structure is (% style="color:#2ecc71" %)mapped(%%) to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] and then the latter is (% style="color:#2ecc71" %)mapped(%%) back to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], the original data structure is obtained.
--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.
++As said, the resulting [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] must have the AttributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]].
  ==== 12.3.4.2 Unpivot Mapping ====
--An alternative mapping method from VTL to SDMX is the **Unpivot **mapping.
++An alternative mapping method from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] is the **Unpivot **mapping.
--Although this mapping method can be used in any case, it makes major sense in case the VTL data structure has more than one measure component (multi-measures VTL structure). This is used to support the SDMX 2.1 case of a MeasureDimension or any other Dimension acting as a list of Measures, under the assumptions explained in section “Pivot Mapping”.
++Although this mapping method can be used in any case, it makes major sense in case the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure has more than one [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[component>>doc:xwiki:Glossary.Component.WebHome]] (multi-[[measures>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structure). This is used to support the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 case of a MeasureDimension or any other [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] acting as a list of [[Measures>>doc:xwiki:Glossary.Measure.WebHome]], under the assumptions explained in section “Pivot Mapping”.
--The multi-measures VTL structures are converted to SDMX Dataflows having an added MeasureDimension, which disambiguates the VTL multiple Measures, and a new Measure in place of the VTL ones, containing the values of the VTL Measures.
++The multi-[[measures>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structures are converted to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] having an added MeasureDimension, which disambiguates the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] multiple [[Measures>>doc:xwiki:Glossary.Measure.WebHome]], and a new [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] in place of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] ones, containing the values of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]].
  The **unpivot** mapping behaves like follows:
--* like in the basic mapping, a VTL (simple) identifier becomes a SDMX
++* like in the basic mapping, a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (simple) identifier becomes a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
--Dimension and a VTL (time) identifier becomes a SDMX TimeDimension (as said, a measure identifier cannot exist in multi-measure VTL structures);
++[[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] and a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (time) identifier becomes a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] TimeDimension (as said, a [[measure>>doc:xwiki:Glossary.Measure.WebHome]] identifier cannot exist in multi-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structures);
--* a MeasureDimension component called "measure_name" is added to the SDMX DataStructure;
--* a Measure component called "obs_value" is added to the SDMX
++* a MeasureDimension [[component>>doc:xwiki:Glossary.Component.WebHome]] called "measure_name" is added to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure;
++* a [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] [[component>>doc:xwiki:Glossary.Component.WebHome]] called "obs_value" is added to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
  DataStructure;
--* each VTL Measure is mapped to a Code of the SDMX MeasureDimension having the same name as the VTL Measure (therefore all the VTL Measure Components do not originate Components in the SDMX DataStructure);
--* a VTL Attribute becomes a SDMX DataAttribute having AttributeRelationship referred to all the SDMX DimensionComponents including the TimeDimension and except the MeasureDimension.
++* each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] is (% style="color:#2ecc71" %)mapped(%%) to a [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension having the same name as the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] (therefore all the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] do not originate [[Components>>doc:xwiki:Glossary.Component.WebHome]] in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure);
++* a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] becomes a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttribute having AttributeRelationship referred to all the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents including the TimeDimension and except the MeasureDimension.
  The summary mapping table of the **unpivot** mapping method is the following:
  (% style="width:994.294px" %)
  |(% style="width:306px" %)**VTL**|(% style="width:684px" %)**SDMX**
--|(% style="width:306px" %)(Simple) Identifier|(% style="width:684px" %)Dimension
++|(% style="width:306px" %)(Simple) Identifier|(% style="width:684px" %)[[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]
  |(% style="width:306px" %)(Time) Identifier|(% style="width:684px" %)TimeDimension
--|(% style="width:306px" %)All Measure Components|(% style="width:684px" %)MeasureDimension (having one Code for each VTL measure component) & one Measure
--|(% style="width:306px" %)Attribute|(% style="width:684px" %)DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
++|(% style="width:306px" %)All [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]]|(% style="width:684px" %)MeasureDimension (having one [[Code>>doc:xwiki:Glossary.Code.WebHome]] for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[component>>doc:xwiki:Glossary.Component.WebHome]]) & one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]
++|(% style="width:306px" %)[[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]|(% style="width:684px" %)DataAttribute depending on all [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] including the TimeDimension and except the MeasureDimension
--At observation / data point level:
++At observation / data point (% style="color:#2ecc71" %)level(%%):
--* a multi-measure VTL Data Point becomes a set of SDMX observations, one for each VTL Measure;
--* the values of the VTL Identifiers become the values of the corresponding SDMX DimensionComponents, for all the observations of the set above;
--* the name of the j^^th^^ VTL Measure (e.g. “Cj”) becomes the Code of the SDMX MeasureDimension of the j^^th^^ observation of the set;
--* the value of the j^^th^^ VTL Measure becomes the value of the SDMX Measure of the j^^th^^ observation of the set;
--* the values of the VTL Attributes become the values of the corresponding SDMX DataAttributes (in principle for all the observations of the set above).
++* a multi-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Point becomes a set of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observations, one for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]];
++* the values of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Identifiers become the values of the corresponding [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents, for all the observations of the set above;
++* the name of the j^^th^^ [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] (e.g. “Cj”) becomes the [[Code>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension of the j^^th^^ observation of the set;
++* the value of the j^^th^^ [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] becomes the value of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] of the j^^th^^ observation of the set;
++* the values of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] become the values of the corresponding [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes (in principle for all the observations of the set above).
--If desired, this method can be applied also to mono-measure VTL structures, provided that none of the VTL Components has already the role of Measure Identifier. Like in the general case, a MeasureDimension component called “measure_name” is added to the SDMX DataStructure, in this case it has just one possible Code, corresponding to the name of the unique VTL Measure. The original VTL Measure would not become a Component in the SDMX data structure. The value of the VTL Measure would be assigned to the unique SDMX Measure called “obs_value”.
++If desired, this method can be applied also to mono-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structures, provided that none of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] has already the role of [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] Identifier. Like in the general case, a MeasureDimension [[component>>doc:xwiki:Glossary.Component.WebHome]] called “measure_name” is added to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataStructure, in this case it has just one possible [[Code>>doc:xwiki:Glossary.Code.WebHome]], corresponding to the name of the unique [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]. The original [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] would not become a [[Component>>doc:xwiki:Glossary.Component.WebHome]] in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data structure. The value of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] would be assigned to the unique [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] called “obs_value”.
--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.
++In any case, the resulting [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the possible [[Codes>>doc:xwiki:Glossary.Code.WebHome]] of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] MeasureDimension need to be listed in a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Codelist, with proper id, agency and (% style="color:#2ecc71" %)version(%%); moreover, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] must have the AttributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]].
  ==== 12.3.4.3 From VTL Measures to SDMX Data Attributes ====
--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”).
++More than all for the multi-[[measure>>doc:xwiki:Glossary.Measure.WebHome]] [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] structures (having more than one [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] [[Component>>doc:xwiki:Glossary.Component.WebHome]]), it may happen that the [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Data Structure need to be managed as DataAttributes in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. Therefore, a third mapping method consists in transforming some [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[measures>>doc:xwiki:Glossary.Measure.WebHome]] in a corresponding [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] and all the other [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes. This method is called M2A (“M2A” stands for “[[Measures>>doc:xwiki:Glossary.Measure.WebHome]] to DataAttributes”).
--All VTL Measures maintain their names in SDMX. The VTL Measure Components that become SDMX DataAttributes are the ones declared as DataAttributes in the target SDMX data structure definition.
++All [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] maintain their names in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] that become [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DataAttributes are the ones declared as DataAttributes in the target [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data structure definition.
  The mapping table is the following:
@@ -353,99 +353,95 @@
  |(% style="width:344px" %)Other Measures|(% style="width:341px" %)DataAttribute
  |(% style="width:344px" %)Attribute|(% style="width:341px" %)DataAttribute
--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.
++Even in this case, the resulting [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] definitions must be compliant with the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] consistency rules. For example, the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] must have the attributeRelationship for the DataAttributes, which does not exist in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]].
  === 12.3.5 Declaration of the mapping methods between data structures ===
--In order to define and understand properly VTL Transformations, the applied mapping methods must be specified in the SDMX structural metadata. If the default mapping method (Basic) is applied, no specification is needed.
++In order to define and understand properly [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, the applied mapping methods must be specified in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:xwiki:Glossary.Structural metadata.WebHome]]. If the default mapping method (Basic) is applied, no specification is needed.
--A customized mapping can be defined through the VtlMappingScheme and VtlDataflowMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlDataflowMapping allows specifying the mapping methods to be used for a specific dataflow, both in the direction from SDMX to VTL (toVtlMappingMethod) and from VTL to SDMX (fromVtlMappingMethod); in fact a VtlDataflowMapping associates the structured URN that identifies a SDMX Dataflow to its VTL alias and its mapping methods.
++A customized mapping can be defined through the VtlMappingScheme and VtlDataflowMapping 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 VtlDataflowMapping allows specifying the mapping methods to be used for a specific [[dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], both in the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (toVtlMappingMethod) and from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (fromVtlMappingMethod); in fact a VtlDataflowMapping associates the structured URN that identifies a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to its [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] alias and its mapping methods.
--It is possible to specify the toVtlMappingMethod and fromVtlMappingMethod also for the conventional dataflow called "generic_dataflow": in this case the specified mapping methods are intended to become the default ones, overriding the "Basic" methods. In turn, the toVtlMappingMethod and fromVtlMappingMethod declared for a specific Dataflow are intended to override the default ones for such a Dataflow.
++It is possible to specify the toVtlMappingMethod and fromVtlMappingMethod also for the conventional [[dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] called "generic_dataflow": in this case the specified mapping methods are intended to become the default ones, overriding the "Basic" methods. In turn, the toVtlMappingMethod and fromVtlMappingMethod declared for a specific [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are intended to override the default ones for such a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]].
--The VtlMappingScheme is a container for zero or more VtlDataflowMapping (it may contain also mappings towards artefacts other than dataflows).
++The VtlMappingScheme is a container for zero or more VtlDataflowMapping (it may contain also mappings towards [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] other than [[dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]]).
  === 12.3.6 Mapping dataflow subsets to distinct VTL Data Sets ===
--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).
++Until now it has been assumed to (% style="color:#2ecc71" %)map(%%) one SMDX [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to one [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] and vice-versa. This mapping one-to-one is not mandatory according to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] because a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] is meant to be a set of observations (data points) on a logical plane, having the same logical data structure and the same general meaning, independently of the possible physical [[representation>>doc:xwiki:Glossary.Representation.WebHome]] or storage (see [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 2.0 User Manual page 24), therefore a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] can be seen either as a unique set of data observations (corresponding to one [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]]) or as the union of many sets of data observations (each one corresponding to a distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]]).
--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}}
++As a matter of fact, in some cases it can be useful to define [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operations involving definite parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] instead than the whole.{{footnote}}A typical example of this kind is the validation, and more in general the manipulation, of individual time series belonging to the same Dataflow, identifiable through the DimensionComponents of the Dataflow except the TimeDimension. The coding of these kind of operations might be simplified by mapping distinct time series (i.e. different parts of a SDMX Dataflow) to distinct VTL Data Sets.{{/footnote}}
--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}}
++Therefore, in order to make the coding of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operations simpler when applied on parts of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]], it is allowed to (% style="color:#2ecc71" %)map(%%) distinct parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] according to the following rules and conventions. This kind of mapping is possible both from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], as better explained below.{{footnote}}Please note that this kind of mapping is only an option at disposal of the definer of VTL Transformations; in fact it remains always possible to manipulate the needed parts of SDMX Dataflows by means of VTL operators (e.g. “sub”, “filter”, “calc”, “union” …), maintaining a mapping one-to-one between SDMX Dataflows and VTL Data Sets.{{/footnote}}
--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.
++Given a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] and some predefined [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] of its DataStructure, it is allowed to (% style="color:#2ecc71" %)map(%%) the subsets of observations that have the same combination of values for such [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] to correspondent [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]].
--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:
++For example, assuming that the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF1(1.0.0) has the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR, TIME_PERIOD and COUNTRY, and that the user declares the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY as basis for the mapping (i.e. the mapping [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]): the observations that have the same values for INDICATOR and COUNTRY would be (% style="color:#2ecc71" %)mapped(%%) to the same [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] (and vice-versa). In practice, this kind mapping is obtained like follows:
--* 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.
--* The VTL Data Set is given a name using a special notation also called “ordered concatenation” and composed of the following parts:
--** 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);
++* For a given [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], the user ([[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definer) declares the DimensionComponents on which the mapping will be based, in a given order.{{footnote}}This definition is made through the ToVtlSubspace and ToVtlSpaceKey classes and/or the FromVtlSuperspace and FromVtlSpaceKey classes, depending on the direction of the mapping (“key” means “dimension”). The mapping of Dataflow subsets can be applied independently in the two directions, also according to different Dimensions. When no Dimension is declared for a given direction, it is assumed that the option of mapping different parts of a SDMX Dataflow to different VTL Data Sets is not used.{{/footnote}} Following the example above, imagine that the user declares the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY.
++* The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] is given a name using a special notation also called “ordered concatenation” and composed of the following parts:
++** The reference to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] (expressed according to the rules described in the previous paragraphs, i.e. URN, abbreviated URN or another alias); for example DF(1.0.0);
  ** 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}}
--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.
++The reference to a specific part of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] above, expressed as the concatenation of the values that the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents declared above must have, separated by dots (“.”) and written in the order in which these DimensionComponents are defined{{footnote}}This is the order in which the dimensions are defined in the ToVtlSpaceKey class or in the FromVtlSpaceKey class, depending on the direction of the mapping.{{/footnote}}. For example POPULATION.USA would mean that such a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] is (% style="color:#2ecc71" %)mapped(%%) to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] observations for which the [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] //INDICATOR// is equal to POPULATION and the [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] //COUNTRY// is equal to USA.
--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.
++In the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, this kind of [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] name must be referenced between single quotes because the slash (“/”) is not a regular character according to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] rules.
--Therefore, the generic name of this kind of VTL datasets would be:
++Therefore, the generic name of this kind of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] would be:
  'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
--Where DF(1.0.0) is the Dataflow and //INDICATORvalue// and //COUNTRYvalue //are placeholders for one value of the INDICATOR and COUNTRY dimensions. Instead the specific name of one of these VTL datasets would be:
++Where DF(1.0.0) is the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] and //INDICATORvalue// and //COUNTRYvalue //are placeholders for one value of the INDICATOR and COUNTRY [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]. Instead the specific name of one of these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] would be:
  ‘DF(1.0.0)/POPULATION.USA’
--In particular, this is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and //COUNTRY// = USA.
++In particular, this is the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and //COUNTRY// = USA.
--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.
++Let us now analyse the different meaning of this kind of mapping in the two mapping directions, i.e. from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]].
--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.
++As already said, the mapping from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] happens when the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] are operand of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, instead the mapping from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] happens when the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] that is result of Transformations{{footnote}}It should be remembered that, according to the VTL consistency rules, a given VTL dataset cannot be the result of more than one VTL Transformation.{{/footnote}} need to be treated as [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] objects. This kind of mapping can be applied independently in the two directions and the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] on which the mapping is based can be different in the two directions: these [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] are defined in the ToVtlSpaceKey and in the FromVtlSpaceKey classes respectively.
--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.
++First, let us see what happens in the __mapping direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]__, i.e. when parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] (e.g. DF1(1.0.0)) need to be (% style="color:#2ecc71" %)mapped(%%) to distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] that are operand of some [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations.
--As already said, each VTL Data Set is assumed to contain all the observations of the
++As already said, each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] is assumed to contain all the observations of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] having INDICATOR=//INDICATORvalue //and COUNTRY=// COUNTRYvalue//. For example, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] ‘DF1(1.0.0)/POPULATION.USA’ would contain all the observations of DF1(1.0.0) having INDICATOR = POPULATION and COUNTRY = USA.
--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.
++In order to obtain the data structure of these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] one, it is assumed that the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure; this is possible because their values are fixed for each one of the invoked [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]]{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] specified for the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF1(1.0.0) is applied (i.e. basic, pivot …).
--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 …).
++In the example above, for all the [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] of the kind ‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] would have the identifier TIME_PERIOD only.
--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.
++It should be noted that the desired [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] (i.e. of the kind ‘DF1(1.0.0)/// INDICATORvalue//.//COUNTRYvalue//’) can be obtained also by applying the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “**sub**” (subspace) to the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF1(1.0.0), like in the following [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expression:
--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:
--
  [[image:1747388275998-621.png]]
--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}}
++In fact the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “sub” has exactly the same behaviour. Therefore, (% style="color:#2ecc71" %)mapping(%%) different parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] in the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] through the ordered concatenation notation is equivalent to a proper use of the operator “**sub**” on such a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]].{{footnote}}In case the ordered concatenation notation is used, the VTL Transformation described above, e.g. ‘DF1(1.0)/POPULATION.USA’ := DF1(1.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA”], is implicitly executed. In order to test the overall compliance of the VTL program to the VTL consistency rules, it has to be considered as part of the VTL program even if it is not explicitly coded.{{/footnote}}
--In the direction from SDMX to VTL it is allowed to omit the value of one or more
++In the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] it is allowed to omit the value of one or more DimensionComponents on which the (% style="color:#2ecc71" %)mapping(%%) is based, but maintaining all the separating dots (therefore it may happen to find two or more consecutive dots and dots in the beginning or in the end). The absence of value means that for the corresponding [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] all the values are kept and the [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] is not dropped.
--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.
++For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
--For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
++This is equivalent to the application of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] “sub” operator only to the identifier //INDICATOR//:
--This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
--
  [[image:1747388244829-693.png]]
  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
--Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different
++Heterogeneous invocations of the same [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are allowed, i.e. omitting different
  Dimensions in different invocations.
--Let us now analyse __the mapping direction from VTL to SDMX__.
++Let us now analyse __the mapping direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]__.
--In this situation, distinct parts of a SDMX Dataflow are calculated as distinct VTL datasets, under the constraint that they must have the same VTL data structure.
++In this situation, distinct parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are calculated as distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]], under the (% style="color:#2ecc71" %)constraint(%%) that they must have the same [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure.
--For example, let us assume that the VTL programmer wants to calculate the SDMX
++For example, let us assume that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programmer wants to calculate the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
  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:
--* 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}}
--* 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}}
++* each part is calculated as a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] derived [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]], result of a dedicated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation;{{footnote}}If the whole DF2(1.0) is calculated by means of just one VTL Transformation, then the mapping between the SDMX Dataflow and the corresponding VTL dataset is one-to-one and this kind of mapping (one SDMX Dataflow to many VTL datasets) does not apply.{{/footnote}}
++* the data structure of all these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.{{footnote}}This is possible as each VTL dataset corresponds to one particular combination of values of INDICATOR and COUNTRY.{{/footnote}}
--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}}.
++Under these hypothesis, such derived [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] can be (% style="color:#2ecc71" %)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}}.
--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}}
++The corresponding [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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}}
  ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
@@ -455,74 +455,72 @@
  [[image:1747388206717-256.png]]
--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:
++As said, it is assumed that these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] derived [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] have the TIME_PERIOD as the only identifier. In the mapping from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to SMDX, the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY are added to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure on order to obtain the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] one, with the following values respectively:
  [[image:1747388148322-387.png]]
--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:
++It should be noted that the application of this many-to-one mapping from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] is equivalent to an appropriate sequence of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations. These use the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “calc” to add the proper [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] identifiers (in the example, INDICATOR and COUNTRY) and to assign to them the proper values and the operator “union” in order to obtain the final [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] (in the example DF2(1.0.0)), that can be (% style="color:#2ecc71" %)mapped(%%) one-to-one to the homonymous [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]. Following the same example, these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations would be:
  [[image:1747388179021-814.png]]
--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
++In other words, starting from the [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] explicitly calculated through [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (in the example ‘DF2(1.0)/GDPPERCAPITA.USA’ and so on), the first step consists in calculating other (non-persistent) [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] (in the example DF2bis_GDPPERCAPITA_USA and so on) by adding the identifiers INDICATOR and COUNTRY with the desired values (//INDICATORvalue// and //COUNTRYvalue)//. Finally, all these non-persistent [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] are united and give the final result DF2(1.0){{footnote}}The result is persistent in this example but it can be also non persistent if needed.{{/footnote}}, which can be (% style="color:#2ecc71" %)mapped(%%) one-to-one to the homonymous [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] having the [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] [[components>>doc:xwiki:Glossary.Component.WebHome]] TIME_PERIOD, INDICATOR and COUNTRY.
--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.
++Therefore, (% style="color:#2ecc71" %)mapping(%%) different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] having the same data structure to different parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], i.e. in the direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], through the ordered concatenation notation is equivalent to a proper use of the operators “calc” and “union” on such [[datasets>>doc:xwiki:Glossary.Data set.WebHome]].{{footnote}}In case the ordered concatenation notation from VTL to SDMX is used, the set of Transformations described above is implicitly performed; therefore, in order to test the overall compliance of the VTL program to the VTL consistency rules, these implicit Transformations have to be considered as part of the VTL program even if they are not explicitly coded.{{/footnote}}
--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}}
++It is worth noting that in the direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] it is mandatory to specify the value for every [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] on which the (% style="color:#2ecc71" %)mapping(%%) is based (in other word, in the name of the calculated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] is __not__ possible to omit the value of some of the Dimensions).
--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).
--
  === 12.3.7 Mapping variables and value domains between VTL and SDMX ===
--With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
++With reference to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] “model for Variables and Value domains”, the following additional mappings have to be considered:
  (% style="width:895.294px" %)
  |(% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**
--|(% style="width:278px" %)**Data Set Component**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
++|(% style="width:278px" %)**[[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] [[Component>>doc:xwiki:Glossary.Component.WebHome]]**|(% style="width:613px" %)Although this abstraction exists in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a [[Component>>doc:xwiki:Glossary.Component.WebHome]] (either a DimensionComponent or a [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] or a DataAttribute) belonging to one specific [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
  |(% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((
--**Concept** with a definite
++(% style="color:#2ecc71" %)**Concept**(%%) with a definite
--Representation
++[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]
  )))
  |(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)(((
--**Representation** (see the Structure Pattern in the Base Package)
++**[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]** (see the Structure Pattern in the Base Package)
  )))
  |(% style="width:278px" %)**Enumerated Value Domain /
--Code List**|(% style="width:613px" %)**Codelist**
--|(% style="width:278px" %)**Code**|(% style="width:613px" %)(((
--**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
++[[Code>>doc:xwiki:Glossary.Code.WebHome]] List**|(% style="width:613px" %)**Codelist**
++|(% style="width:278px" %)**[[Code>>doc:xwiki:Glossary.Code.WebHome]]**|(% style="width:613px" %)(((
++**[[Code>>doc:xwiki:Glossary.Code.WebHome]]** (for enumerated DimensionComponent, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], DataAttribute)
  )))
  |(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)(((
--non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
++non-enumerated** [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] **(having [[Facets>>doc:xwiki:Glossary.Facet.WebHome]] / ExtendedFacets, see the Structure Pattern in the Base Package)
  )))
--|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations)
--|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
--|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
--|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
--|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX
++|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a **[[Code>>doc:xwiki:Glossary.Code.WebHome]]** of a Codelist (for enumerated [[Representations>>doc:xwiki:Glossary.Representation.WebHome]]) or to a valid **value **(for non-enumerated** **[[Representations>>doc:xwiki:Glossary.Representation.WebHome]])
++|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
++|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
++|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
++|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
--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).
++The main difference between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] relies on the fact that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] for defining subsets of Value Domains do not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], therefore the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] features for referring to predefined subsets are not available in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. These [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] are the Value Domain Subset (or Set), either enumerated or described, the Set List (list of values belonging to enumerated subsets) and the [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] [[Component>>doc:xwiki:Glossary.Component.WebHome]] (aimed at defining the set of values that the [[Component>>doc:xwiki:Glossary.Component.WebHome]] of a [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] can take, possibly a subset of the [[codes>>doc:xwiki:Glossary.Code.WebHome]] of Value Domain).
--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.
++Another difference consists in the fact that all Value Domains are considered as identifiable objects in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] either if enumerated or not, while in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] the Codelist (corresponding to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] enumerated Value Domain) is identifiable, while the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] non-enumerated [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] (corresponding to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] non-enumerated Value Domain) is not identifiable. As a consequence, the definition of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Rulesets, which in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can refer either to enumerated or non-enumerated value domains, in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] can refer only to enumerated Value Domains (i.e. to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Codelists). As for the (% style="color:#2ecc71" %)mapping(%%) between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] variables and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%), it should be noted that these [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] do not coincide perfectly. In fact, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] variables are represented variables, defined always on the same Value Domain (“[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]” in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) independently of the [[data set>>doc:xwiki:Glossary.Data set.WebHome]] / data structure in which they appear{{footnote}}By using represented variables, VTL can assume that data structures having the same variables as identifiers can be composed one another because the correspondent values can match.{{/footnote}}, while the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%) can have different [[Representations>>doc:xwiki:Glossary.Representation.WebHome]] in different DataStructures.{{footnote}}A Concept becomes a Component in a DataStructureDefinition, and Components can have different LocalRepresentations in different DataStructureDefinitions, also overriding the (possible) base representation of the Concept.{{/footnote}} This means that one [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concept(%%) can correspond to many [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Variables, one for each [[representation>>doc:xwiki:Glossary.Representation.WebHome]] the (% style="color:#2ecc71" %)Concept(%%) has.
--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
++Therefore, it is important to be aware that some [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operations (for example the binary operations at [[data set>>doc:xwiki:Glossary.Data set.WebHome]] (% style="color:#2ecc71" %)level(%%)) are consistent only if the [[components>>doc:xwiki:Glossary.Component.WebHome]] having the same names in the operated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] have also the same [[representation>>doc:xwiki:Glossary.Representation.WebHome]] (i.e. the same Value Domain as for [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]). For example, it is possible to obtain correct results from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expression
--DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
++DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]])
--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.
++if the matching [[components>>doc:xwiki:Glossary.Component.WebHome]] in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general [[representation>>doc:xwiki:Glossary.Representation.WebHome]]. In simpler words, DS_a and DS_b must use the same values/[[codes>>doc:xwiki:Glossary.Code.WebHome]] (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
--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
++As mentioned, the property above is not enforced by construction in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], and different [[representations>>doc:xwiki:Glossary.Representation.WebHome]] of the same (% style="color:#2ecc71" %)Concept(%%) can be not compatible one another (for example, it may happen that geo_area is represented by ISO-alpha-3 [[codes>>doc:xwiki:Glossary.Code.WebHome]] in DS_a and by ISO alpha-2 [[codes>>doc:xwiki:Glossary.Code.WebHome]] in DS_b). Therefore, it will be up to the definer of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]
--Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
++Transformations to ensure that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expressions are consistent with the actual [[representations>>doc:xwiki:Glossary.Representation.WebHome]] of the correspondent [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%).
--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.
++It remains up to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-[[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definer also the assurance of the consistency between a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Ruleset defined on Variables and the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] on which the Ruleset is applied. In fact, a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Ruleset is expressed by means of the values of the Variables (i.e. [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%)), i.e. assuming definite [[representations>>doc:xwiki:Glossary.Representation.WebHome]] for them (e.g. ISOalpha-3 for country). If the Ruleset is applied to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] that have the same name of the (% style="color:#2ecc71" %)Concept(%%) they refer to but different [[representations>>doc:xwiki:Glossary.Representation.WebHome]] (e.g. ISO-alpha-2 for country), the Ruleset cannot work properly.
  == 12.4 Mapping between SDMX and VTL Data Types ==
  === 12.4.1 VTL Data types ===
--According to the VTL User Guide the possible operations in VTL depend on the data types of the artefacts. For example, numbers can be multiplied but text strings cannot. In the VTL Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
++According to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] User Guide the possible operations in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] depend on the data types of the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]]. For example, numbers can be multiplied but text strings cannot. In the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
--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:
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data types are sub-divided in scalar types (like integers, strings, etc.), which are the types of the scalar values, and compound types (like [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]], [[Components>>doc:xwiki:Glossary.Component.WebHome]], Rulesets, etc.), which are the types of the compound structures. See below the diagram of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data types, taken from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] User Manual:
  [[image:1747388434672-948.png]]
@@ -529,9 +529,9 @@
  (% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
  **Figure 22 – VTL Data Types**
--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.
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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.
--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):
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types are listed below and follow a hierarchical structure in terms of supersets/subsets (e.g. "scalar" is the superset of all the basic scalar types):
  [[image:1747388465321-274.png]]
@@ -539,25 +539,25 @@
  === 12.4.2 VTL basic scalar types and SDMX data types ===
--The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] assumes that a basic scalar type has a unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] and can have more external [[representations>>doc:xwiki:Glossary.Representation.WebHome]].
--The internal representation is the format used within a VTL system to represent (and process) all the scalar values of a certain type. In principle, this format is hidden and not necessarily known by users. The external representations are instead the external formats of the values of a certain basic scalar type, i.e. the formats known by the users. For example, the internal representation of the dates can be an integer counting the days since a predefined date (e.g. from 01/01/4713 BC up to 31/12/5874897 AD like in Postgres) while two possible external representations are the formats YYYY-MMGG and MM-GG-YYYY (e.g. respectively 2010-12-31 and 12-31-2010).
++The internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is the format used within a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] system to represent (and process) all the scalar values of a certain type. In principle, this format is hidden and not necessarily known by users. The external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] are instead the external formats of the values of a certain basic scalar type, i.e. the formats known by the users. For example, the internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the dates can be an integer counting the days since a predefined date (e.g. from 01/01/4713 BC up to 31/12/5874897 AD like in Postgres) while two possible external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] are the formats YYYY-MMGG and MM-GG-YYYY (e.g. respectively 2010-12-31 and 12-31-2010).
--The internal representation is the reference format that allows VTL to operate on more values of the same type (for example on more dates) even if such values have different external formats: these values are all converted to the unique internal representation so that they can be composed together (e.g. to find the more recent date, to find the time span between these dates and so on).
++The internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is the reference format that allows [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to operate on more values of the same type (for example on more dates) even if such values have different external formats: these values are all converted to the unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] so that they can be composed together (e.g. to find the more recent date, to find the time span between these dates and so on).
--The VTL assumes that a unique internal representation exists for each basic scalar type but does not prescribe any particular format for it, leaving the VTL systems free to using they preferred or already existing internal format. By consequence, in VTL the basic scalar types are abstractions not associated to a specific format.
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] assumes that a unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] exists for each basic scalar type but does not prescribe any particular format for it, leaving the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] systems free to using they preferred or already existing internal format. By consequence, in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] the basic scalar types are abstractions not associated to a specific format.
--SDMX data types are conceived instead to support the data exchange, therefore they do have a format, which is known by the users and correspond, in VTL terms, to external representations. Therefore, for each VTL basic scalar type there can be more SDMX data types (the latter are explained in the section "General Notes for Implementers" of this document and are actually much more numerous than the former).
++[[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types are conceived instead to support the data exchange, therefore they do have a format, which is known by the users and correspond, in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] terms, to external [[representations>>doc:xwiki:Glossary.Representation.WebHome]]. Therefore, for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type there can be more [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types (the latter are explained in the section "General Notes for Implementers" of this document and are actually much more numerous than the former).
--The following paragraphs describe the mapping between the SDMX data types and the VTL basic scalar types. This mapping shall be presented in the two directions of possible conversion, i.e. from SDMX to VTL and vice-versa.
++The following paragraphs describe the mapping between the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types and the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types. This mapping shall be presented in the two directions of possible conversion, i.e. from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and vice-versa.
--The conversion from SDMX to VTL happens when an SDMX artefact acts as inputs of a VTL Transformation. As already said, in fact, at compile time the VTL needs to know the VTL type of the operands in order to check their compliance with the VTL operators and at runtime it must convert the values from their external (SDMX) representations to the corresponding internal (VTL) ones.
++The conversion from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] happens when an [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] acts as inputs of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation. As already said, in fact, at compile time the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] needs to know the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] type of the operands in order to check their compliance with the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operators and at runtime it must convert the values from their external ([[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) [[representations>>doc:xwiki:Glossary.Representation.WebHome]] to the corresponding internal ([[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]) ones.
--The opposite conversion, i.e. from VTL to SDMX, happens when a VTL result, i.e. a VTL Data Set output of a Transformation, must become a SDMX artefact (or part of it). The values of the VTL result must be converted into the desired (SDMX) external representations (data types) of the SDMX artefact.
++The opposite conversion, i.e. from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], happens when a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] result, i.e. a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] output of a Transformation, must become a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (or part of it). The values of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] result must be converted into the desired ([[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] (data types) of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]].
  === 12.4.3 Mapping SDMX data types to VTL basic scalar types ===
--The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
++The following table describes the default mapping for converting from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types.
  (% style="width:823.294px" %)
  |(% style="width:509px" %)**SDMX data type (BasicComponentDataType)**|(% style="width:312px" %)**Default VTL basic scalar type**
@@ -593,7 +593,7 @@
  Short
  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
  )))|(% style="width:312px" %)integer
--|(% 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
++|(% style="width:509px" %)[[Decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as [[decimals>>doc:xwiki:Glossary.Decimals.WebHome]])|(% style="width:312px" %)number
  |(% style="width:509px" %)(((
  Float
  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
@@ -604,7 +604,7 @@
  )))|(% style="width:312px" %)number
  |(% style="width:509px" %)(((
  Boolean
--(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of binary-valued logic: {true, false})
++(corresponds to the XML Schema xs:boolean datatype; support the mathematical (% style="color:#2ecc71" %)concept(%%) of binary-valued logic: {true, false})
  )))|(% style="width:312px" %)boolean
  (% style="width:822.294px" %)
@@ -618,15 +618,15 @@
  )))|(% colspan="1" style="width:311px" %)integer
  |(% colspan="2" style="width:507px" %)(((
  InclusiveValueRange
--(decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
++([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number within a closed interval, whose bounds are specified in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[representation>>doc:xwiki:Glossary.Representation.WebHome]] by the [[facets>>doc:xwiki:Glossary.Facet.WebHome]] minValue and maxValue)
  )))|(% colspan="1" style="width:311px" %)number
  |(% colspan="2" style="width:507px" %)(((
  ExclusiveValueRange
--(decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
++([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number within an open interval, whose bounds are specified in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[representation>>doc:xwiki:Glossary.Representation.WebHome]] by the [[facets>>doc:xwiki:Glossary.Facet.WebHome]] minValue and maxValue)
  )))|(% colspan="1" style="width:311px" %)number
  |(% colspan="2" style="width:507px" %)(((
  Incremental
--(decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
++([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number the increased by a specific interval (defined by the interval [[facet>>doc:xwiki:Glossary.Facet.WebHome]]), which is typically enforced outside of the XML validation)
  )))|(% colspan="1" style="width:311px" %)number
  |(% colspan="2" style="width:507px" %)(((
  ObservationalTimePeriod
@@ -683,19 +683,19 @@
  )))|(% colspan="2" style="width:312px" %)date
  |(% colspan="1" style="width:507px" %)(((
  TimeRange
--(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
++(YYYY-MM-DD(Thh:mm:ss)?/)
  )))|(% colspan="2" style="width:312px" %)time
  |(% colspan="1" style="width:507px" %)(((
  Month
--(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
++(MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
  )))|(% colspan="2" style="width:312px" %)string
  |(% colspan="1" style="width:507px" %)(((
  MonthDay
--(~-~-MM-DD; specifies a day within a month independent of a year; e.g. Christmas is December 25^^th^^; used to specify reporting year start day)
++(MM-DD; specifies a day within a month independent of a year; e.g. Christmas is December 25^^th^^; used to specify reporting year start day)
  )))|(% colspan="2" style="width:312px" %)string
  |(% colspan="1" style="width:507px" %)(((
  Day
--(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
++(-DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
  )))|(% colspan="2" style="width:312px" %)string
  |(% colspan="1" style="width:507px" %)(((
  Time
@@ -713,11 +713,11 @@
  (% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes" %)
  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
--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).
++When [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] takes in input [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]], it is assumed that a type conversion according to the table above always happens. In case a different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type is desired, it can be achieved in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] program taking in input the default [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type above and applying to it the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] type conversion features (see the implicit and explicit type conversion and the "cast" operator in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Reference Manual).
  === 12.4.4 Mapping VTL basic scalar types to SDMX data types ===
--The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
++The following table describes the default conversion from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types .
  (% style="width:1073.29px" %)
  |(% style="width:207px" %)(((
@@ -729,13 +729,13 @@
  |(% style="width:207px" %)Number|(% style="width:462px" %)Float|(% style="width:402px" %)Like XML (xs:float)
  |(% style="width:207px" %)Integer|(% style="width:462px" %)Integer|(% style="width:402px" %)Like XML (xs:int)
  |(% style="width:207px" %)Date|(% style="width:462px" %)DateTime|(% style="width:402px" %)YYYY-MM-DDT00:00:00Z
--|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)<date>/<date> (as defined above)
++|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)/ (as defined above)
  |(% style="width:207px" %)time_period|(% style="width:462px" %)(((
  ReportingTimePeriod
  (StandardReportingPeriod)
  )))|(% style="width:402px" %)(((
  YYYY-Pppp
--(according to SDMX )
++(according to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] )
  )))
  |(% style="width:207px" %)Duration|(% style="width:462px" %)Duration|(% style="width:402px" %)(((
  Like XML (xs:duration)
@@ -746,9 +746,9 @@
  (% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes-1" %)
  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
--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).
++In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] information model).
--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.
++The custom output formats can be specified by means of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] formatting mask described in the section "Type Conversion and Formatting Mask" of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Reference Manual. Such a section describes the masks for the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types "number", "integer", "date", "time", "time_period" and "duration" and gives examples. As for the types "string" and "boolean" the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] conventions are extended with some other special characters as described in the following table.
  (% style="width:713.294px" %)
  |(% colspan="2" style="width:710px" %)VTL special characters for the formatting masks
@@ -798,26 +798,26 @@
  |\|(% style="width:486px" %)prefix for the special characters that must appear in the mask
  |N|(% style="width:486px" %)fixed number of digits used in the preceding textual representation of the month or the day
--The default conversion, either standard or customized, can be used to deduce automatically the representation of the components of the result of a VTL Transformation. In alternative, the representation of the resulting SDMX Dataflow can be given explicitly by providing its DataStructureDefinition. In other words, the representation specified in the DSD, if available, overrides any default conversion{{footnote}}The representation given in the DSD should obviously be compatible with the VTL data type.{{/footnote}}.
++The default conversion, either standard or customized, can be used to deduce automatically the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the [[components>>doc:xwiki:Glossary.Component.WebHome]] of the result of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation. In alternative, the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the resulting [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] can be given explicitly by providing its DataStructureDefinition. In other words, the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] specified in the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]], if available, overrides any default conversion{{footnote}}The representation given in the DSD should obviously be compatible with the VTL data type.{{/footnote}}.
  === 12.4.5 Null Values ===
--In the conversions from SDMX to VTL it is assumed by default that a missing value in SDMX becomes a NULL in VTL. After the conversion, the NULLs can be manipulated through the proper VTL operators.
++In the conversions from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] it is assumed by default that a missing value in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] becomes a NULL in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]. After the conversion, the NULLs can be manipulated through the proper [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operators.
--On the other side, the VTL programs can produce in output NULL values for Measures and Attributes (Null values are not allowed in the Identifiers). In the conversion from VTL to SDMX, it is assumed that a NULL in VTL becomes a missing value in SDMX. In the conversion from VTL to SDMX, the default assumption can be overridden, separately for each VTL basic scalar type, by specifying which the value that represents the NULL in SDMX is. This can be specified in the attribute "nullValue" of the CustomType artefact (see also the section Transformations and Expressions of the SDMX information model). A CustomType belongs to a CustomTypeScheme, which can be referenced by one or more TransformationScheme (i.e. VTL programs). The overriding assumption is applied for all the SDMX Dataflows calculated in the TransformationScheme.
++On the other side, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs can produce in output NULL values for [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] and [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] (Null values are not allowed in the Identifiers). In the conversion from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it is assumed that a NULL in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] becomes a missing value in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. In the conversion from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], the default assumption can be overridden, separately for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type, by specifying which the value that represents the NULL in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] is. This can be specified in the [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] "nullValue" of the CustomType [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX information model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]). A CustomType belongs to a CustomTypeScheme, which can be referenced by one or more TransformationScheme (i.e. [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs). The overriding assumption is applied for all the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] calculated in the TransformationScheme.
  === 12.4.6 Format of the literals used in VTL Transformations ===
--The VTL programs can contain literals, i.e. specific values of certain data types written directly in the VTL definitions or expressions. The VTL does not prescribe a specific format for the literals and leave the specific VTL systems and the definers of VTL Transformations free of using their preferred formats.
++The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs can contain literals, i.e. specific values of certain data types written directly in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definitions or expressions. The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] does not prescribe a specific format for the literals and leave the specific [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] systems and the definers of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations free of using their preferred formats.
--Given this discretion, it is essential to know which are the external representations adopted for the literals in a VTL program, in order to interpret them correctly. For example, if the external format for the dates is YYYY-MM-DD the date literal 2010-0102 has the meaning of 2^^nd^^ January 2010, instead if the external format for the dates is YYYY-DD-MM the same literal has the meaning of 1^^st^^ February 2010.
++Given this discretion, it is essential to know which are the external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] adopted for the literals in a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] program, in order to interpret them correctly. For example, if the external format for the dates is YYYY-MM-DD the date literal 2010-0102 has the meaning of 2^^nd^^ January 2010, instead if the external format for the dates is YYYY-DD-MM the same literal has the meaning of 1^^st^^ February 2010.
--Hereinafter, i.e. in the SDMX implementation of the VTL, it is assumed that the literals are expressed according to the "default output format" of the table of the previous paragraph ("Mapping VTL basic scalar types to SDMX data types") unless otherwise specified.
++Hereinafter, i.e. in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] implementation of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], it is assumed that the literals are expressed according to the "default output format" of the table of the previous paragraph ("Mapping [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types") unless otherwise specified.
--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).
++A different format can be specified in the [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] "vtlLiteralFormat" of the CustomType [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX information model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]).
--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.
++Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type, if a value is found for the vtlLiteralFormat [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] of the CustomType of such [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type. The overriding assumption is applied for all the literals of a related [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] TransformationScheme.
--In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
++In case a literal is operand of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
  {{putFootnotes/}}