Changes for page 12 Validation and Transformation Language (VTL)

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 2 removed)
  • 1750070288958-132.png
  • 1750070310572-584.png
  • 1750067055028-964.png
• Objects (0 modified, 1 added, 1 removed)
  • SKMS.Methodology.Code.MethodologyClass[0]
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Tags

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

Content

...	...	@@ -18,7 +18,7 @@
18	18
19	19	This section does not explain the VTL language or any of the content published in the VTL guides. Rather, this is a description of how the VTL can be used in the SDMX context and applied to SDMX artefacts.
20	20
21		-== 12.2 References to SDMX artefacts from VTL statements ==
	21	+== 12.2 References to SDMX artefacts from VTL statements ==
22	22
23	23	=== 12.2.1 Introduction ===
24	24
...	...	@@ -78,16 +78,12 @@
78	78	* if the artefact is a Dimension, TimeDimension, Measure or DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
79	79	* if the artefact is a Concept (the object-id is the name of the Concept)
80	80
	81	+For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
81	81
	83	+>(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
	84	+>(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
	85	+>(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
82	82
83		-For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as
84		-
85		-{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
86		-
87		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
88		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
89		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
90		-
91	91	=== 12.2.3 Abbreviation of the URN ===
92	92
93	93	The complete formulation of the URN described above is exhaustive but verbose, even for very simple statements. In order to reduce the verbosity through a simplified identifier and make the work of transformation definers easier, proper abbreviations of the URN are possible. Using this approach, the referenced artefacts remain intelligible in the VTL code by a human reader.
...	...	@@ -101,8 +101,7 @@
101	101	** "codelist" for the class Codelist.
102	102	* The class-name can be omitted as it can be deduced from the VTL invocation. In particular, starting from the VTL class of the invoked artefact (e.g. dataset, component, identifier, measure, attribute, variable, valuedomain), which is known given the syntax of the invoking VTL operator{{footnote}}For the syntax of the VTL operators see the VTL Reference Manual{{/footnote}}, the SDMX class can be deduced from the mapping rules between VTL and SDMX (see the section "Mapping between VTL and SDMX" hereinafter){{footnote}}In case the invoked artefact is a VTL component, which can be invoked only within the invocation of a VTL data set (SDMX Dataflow), the specific SDMX class-name (e.g. Dimension, TimeDimension, Measure or DataAttribute) can be deduced from the data structure of the SDMX Dataflow, which the component belongs to.{{/footnote}}.
103	103	* If the agency-id is not specified, it is assumed by default equal to the agency-id of the TransformationScheme, UserDefinedOperatorScheme or RulesetScheme from which the artefact is invoked. For example, the agencyid can be omitted if it is the same as the invoking TransformationScheme and cannot be omitted if the artefact comes from another agency{{footnote}}If the Agency is composite (for example AgencyA.Dept1.Unit2), the agency is considered different even if only part of the composite name is different (for example AgencyA.Dept1.Unit3 is a different Agency than the previous one). Moreover the agency-id cannot be omitted in part (i.e., if a TransformationScheme owned by AgencyA.Dept1.Unit2 references an artefact coming from AgencyA.Dept1.Unit3, the specification of the agency-id becomes mandatory and must be complete, without omitting the possibly equal parts like AgencyA.Dept1){{/footnote}}. Take also into account that, according to the VTL consistency rules, the agency of the result of a Transformation must be the same as its TransformationScheme, therefore the agency-id can be omitted for all the results (left part of Transformation statements).
104		-* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted:
105		-** if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
	100	+* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted: o if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
106	106	** if the referenced artefact is a Dimension, TimeDimension, Measure, DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the dataStructure-id and can be omitted, given that these components are always invoked within the invocation of a Dataflow, whose dataStructure-id can be deduced from the SDMX structural definitions;
107	107	** if the referenced artefact is a Concept, which is not maintainable and belong to the ConceptScheme maintainable class, the maintained object is the conceptScheme-id and cannot be omitted;
108	108	** if the referenced artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
...	...	@@ -110,53 +110,55 @@
110	110	* As said, the container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
111	111	* The object-id does not exist for the artefacts belonging to the Dataflow, and Codelist classes, while it exists and cannot be omitted for the artefacts belonging to the classes Dimension, TimeDimension, Measure, DataAttribute and Concept, as for them the object-id is the main identifier of the artefact
112	112
113		-
114		-
115	115	The simplified object identifier is obtained by omitting all the first part of the URN, including the special characters, till the first part not omitted.
116	116
117	117	For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
118	118
119		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
120		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
121		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	112	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
122	122
	114	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
	115	+
	116	+'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
	117	+
123	123	by omitting all the non-essential parts would become simply:
124	124
125		-> DFR : = DF1 + DF2
	120	+DFR := DF1 + DF2
126	126
127	127	The references to the Codelists can be simplified similarly. For example, given the non-abbreviated reference to the Codelist AG:CL_FREQ(1.0.0), which is{{footnote}}Single quotes are needed because this reference is not a VTL regular name. 19 Single quotes are not needed in this case because CL_FREQ is a VTL regular name.{{/footnote}}:
128	128
129		-> 'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
	124	+'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
130	130
131	131	if the Codelist is referenced from a RulesetScheme belonging to the agency AG, omitting all the optional parts, the abbreviated reference would become simply^^19^^:
132	132
133		-> CL_FREQ
	128	+CL_FREQ
134	134
135	135	As for the references to the components, it can be enough to specify the componentId, given that the dataStructure-Id can be omitted. An example of non-abbreviated reference, if the data structure is DST1 and the component is SECTOR, is the following:
136	136
137		-> 'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S ECTOR'
	132	+'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S
138	138
	134	+ECTOR'
	135	+
139	139	The corresponding fully abbreviated reference, if made from a TransformationScheme belonging to AG, would become simply:
140	140
141		-> SECTOR
	138	+SECTOR
142	142
143	143	For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as{{footnote}}The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC{{/footnote}}:
144	144
145		-> 'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
	142	+'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
146	146
147	147	In the references to the Concepts, which can exist for example in the definition of the VTL Rulesets, at least the conceptScheme-id and the concept-id must be specified.
148	148
149	149	An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
150	150
151		-> 'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
	148	+'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
152	152
153	153	The corresponding fully abbreviated reference, if made from a RulesetScheme belonging to AG, would become simply:
154	154
155		-> CS1(1.0.0).SECTOR
	152	+CS1(1.0.0).SECTOR
156	156
157	157	The Codes and in general all the Values can be written without any other specification, for example, the transformation to check if the values of the measures of the Dataflow DF1 are between 0 and 25000 can be written like follows:
158	158
159		-> 'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
	156	+'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
160	160
161	161	The artefact (Component, Concept, Codelist …) which the Values are referred to can be deduced from the context in which the reference is made, taking also into account the VTL syntax. In the Transformation above, for example, the values 0 and 2500 are compared to the values of the measures of DF1(1.0.0).
162	162
...	...	@@ -168,16 +168,14 @@
168	168
169	169	=== 12.2.5 References to SDMX artefacts from VTL Rulesets ===
170	170
171		-The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
	168	+The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: (i) when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
172	172
173	173	The VTL Rulesets have a signature, in which the Value Domains or the Variables on which the Ruleset is defined are declared, and a body, which contains the Rules.
174	174
175	175	In the signature, given the mapping between VTL and SDMX better described in the following paragraphs, a reference to a VTL Value Domain becomes a reference to a SDMX Codelist, while a reference to a VTL Represented Variable becomes a reference to a SDMX Concept, assuming for it a definite representation{{footnote}}Rulesets of this kind cannot be reused when the referenced Concept has a different representation.{{/footnote}}.
176	176
177		-In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets).
	174	+In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets). The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
178	178
179		-The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
180		-
181	181	In the body of the Rulesets, the Codes and in general all the Values can be written without any other specification, because the artefact, which the Values are referred (Codelist, Concept) to can be deduced from the Ruleset signature.
182	182
183	183	== 12.3 Mapping between SDMX and VTL artefacts ==
...	...	@@ -206,7 +206,7 @@
206	206
207	207	The possible mapping options are described in more detail in the following sections.
208	208
209		-=== 12.3.3 Mapping from SDMX to VTL data structures ===
	204	+=== 12.3.2 Mapping from SDMX to VTL data structures ===
210	210
211	211	==== 12.3.3.1 Basic Mapping ====
212	212
...	...	@@ -214,12 +214,11 @@
214	214
215	215	When transforming **from SDMX to VTL**, this method consists in leaving the components unchanged and maintaining their names and roles, according to the following table:
216	216
217		-(% style="width:468.294px" %)
218		-|(% style="width:196px" %)**SDMX**|(% style="width:269px" %)**VTL**
219		-|(% style="width:196px" %)Dimension|(% style="width:269px" %)(Simple) Identifier
220		-|(% style="width:196px" %)TimeDimension|(% style="width:269px" %)(Time) Identifier
221		-|(% style="width:196px" %)Measure|(% style="width:269px" %)Measure
222		-|(% style="width:196px" %)DataAttribute|(% style="width:269px" %)Attribute
	212	+|**SDMX**|**VTL**
	213	+|Dimension|(Simple) Identifier
	214	+|TimeDimension|(Time) Identifier
	215	+|Measure|Measure
	216	+|DataAttribute|Attribute
223	223
224	224	The SDMX DataAttributes, in VTL they are all considered "at data point / observation level" (i.e. dependent on all the VTL Identifiers), because VTL does not have the SDMX AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, dimension or set or group of dimensions, whole data set).
225	225
...	...	@@ -229,8 +229,10 @@
229	229
230	230	An alternative mapping method from SDMX to VTL is the **Pivot **mapping, which makes sense and is different from the Basic method only for the SDMX data structures that contain a Dimension that plays the role of measure dimension (like in SDMX 2.1) and just one Measure. Through this method, these structures can be mapped to multimeasure VTL data structures. Besides that, a user may choose to use any Dimension acting as a list of Measures (e.g., a Dimension with indicators), either by considering the “Measure” role of a Dimension, or at will using any coded Dimension. Of course, in SDMX 3.0, this can only work when only one Measure is defined in the DSD.
231	231
232		-In SDMX 2.1 the MeasureDimension was a subclass of DimensionComponent like Dimension and TimeDimension. In the current SDMX version, this subclass does not exist anymore, however a Dimension can have the role of measure dimension (i.e. a Dimension that contributes to the identification of the measures). In SDMX 2.1 a DataStructure could have zero or one MeasureDimensions, in the current version of the standard, from zero to many Dimension may have the role of measure dimension. Hereinafter a Dimension that plays the role of measure dimension is referenced for simplicity as “MeasureDimension“, i.e. maintaining the capital letters and the courier font even if the MeasureDimension is not anymore a class in the SDMX Information Model of the current SDMX version. For the sake of simplicity, the description below considers just one Dimension having the role of MeasureDimension (i.e., the more simple and common case). Nevertheless, it maintains its validity also if in the DataStructure there are more dimension with the role of MeasureDimensions: in this case what is said about the MeasureDimension must be applied to the combination of all the MeasureDimensions considered as a joint variable{{footnote}}E.g., if in the data structure there exist 3 Dimensions C,D,E having the role of MeasureDimension, they should be considered as a joint MeasureDimension Z=(C,D,E); therefore when the description says “each possible value Cj of the MeasureDimension …” it means “each possible combination of values (Cj, Dk, Ew) of the joint MeasureDimension Z=(C,D,E)”.{{/footnote}}.
	226	+In SDMX 2.1 the MeasureDimension was a subclass of DimensionComponent like Dimension and TimeDimension. In the current SDMX version, this subclass does not exist anymore, however a Dimension can have the role of measure dimension (i.e. a Dimension that contributes to the identification of the measures). In SDMX 2.1 a DataStructure could have zero or one MeasureDimensions, in the current version of the standard, from zero to many Dimension may have the role of measure dimension. Hereinafter a Dimension that plays the role of measure dimension is referenced for simplicity as “MeasureDimension“, i.e. maintaining the capital letters and the courier font even if the MeasureDimension is not anymore a class in the SDMX Information Model of the current SDMX version. For the sake of simplicity, the description below considers just one Dimension having the role of MeasureDimension (i.e., the more simple and common case). Nevertheless, it maintains its validity also if in the DataStructure there are more dimension with the role of MeasureDimensions: in this case what is said about the MeasureDimension must be applied to the combination of all the
233	233
	228	+MeasureDimensions considered as a joint variable{{footnote}}E.g., if in the data structure there exist 3 Dimensions C,D,E having the role of MeasureDimension, they should be considered as a joint MeasureDimension Z=(C,D,E); therefore when the description says “each possible value Cj of the MeasureDimension …” it means “each possible combination of values (Cj, Dk, Ew) of the joint MeasureDimension Z=(C,D,E)”.{{/footnote}}.
	229	+
234	234	Among other things, the Pivot method provides also backward compatibility with the SDMX 2.1 data structures that contained a MeasureDimension.
235	235
236	236	If applied to SDMX structures that do not contain any MeasureDimension, this method behaves like the Basic mapping (see the previous paragraph).
...	...	@@ -243,18 +243,16 @@
243	243	* The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
244	244	* An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
245	245	** If, according to the SDMX AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the SDMX DataAttribute becomes a VTL Attribute having the same name. This happens if the AttributeRelationship is not specified (i.e. the DataAttribute does not depend on any DimensionComponent and therefore is at data set level), or if it refers to a set (or a group) of dimensions which does not include the MeasureDimension;
246		-** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators).
247		-** Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
	242	+** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators). o Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
248	248
249	249	The summary mapping table of the "pivot" mapping from SDMX to VTL for the SDMX data structures that contain a MeasureDimension is the following:
250	250
251		-(% style="width:739.294px" %)
252		-|(% style="width:335px" %)**SDMX**|(% style="width:400px" %)**VTL**
253		-|(% style="width:335px" %)Dimension|(% style="width:400px" %)(Simple) Identifier
254		-|(% style="width:335px" %)TimeDimension|(% style="width:400px" %)(Time) Identifier
255		-|(% style="width:335px" %)MeasureDimension & one Measure|(% style="width:400px" %)One Measure for each Code of the SDMX MeasureDimension
256		-|(% style="width:335px" %)DataAttribute not depending on the MeasureDimension|(% style="width:400px" %)Attribute
257		-|(% style="width:335px" %)DataAttribute depending on the MeasureDimension|(% style="width:400px" %)(((
	246	+|**SDMX**|**VTL**
	247	+|Dimension|(Simple) Identifier
	248	+|TimeDimension|(Time) Identifier
	249	+|MeasureDimension & one Measure|One Measure for each Code of the SDMX MeasureDimension
	250	+|DataAttribute not depending on the MeasureDimension|Attribute
	251	+|DataAttribute depending on the MeasureDimension|(((
258	258	One Attribute for each Code of the
259	259	SDMX MeasureDimension
260	260	)))
...	...	@@ -264,14 +264,19 @@
264	264	At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
265	265
266	266	* The set of SDMX observations having the same values for all the Dimensions except than the MeasureDimension become one multi-measure VTL Data Point, having one Measure for each Code Cj of the SDMX MeasureDimension;
267		-* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple) Identifiers, (time) Identifier and Attributes.
	261	+* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple)
	262	+
	263	+Identifiers, (time) Identifier and Attributes.
	264	+
268	268	* The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
269	269	* For the SDMX DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Attribute DA_Cj
270	270
271	271	==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
272	272
273		-* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain Attributes.
	270	+* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain
274	274
	272	+Attributes.
	273	+
275	275	The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final VTL components, which according to the Basic and Pivot methods would have had the role of Attribute, assume instead the role of Measure.
276	276
277	277	Proper VTL features allow changing the role of specific attributes even after the SDMX to VTL mapping: they can be useful when only some of the DataAttributes need to be managed as VTL Measures.
...	...	@@ -288,12 +288,11 @@
288	288
289	289	Mapping table:
290	290
291		-(% style="width:470.294px" %)
292		-|(% style="width:262px" %)**VTL**|(% style="width:205px" %)**SDMX**
293		-|(% style="width:262px" %)(Simple) Identifier|(% style="width:205px" %)Dimension
294		-|(% style="width:262px" %)(Time) Identifier|(% style="width:205px" %)TimeDimension
295		-|(% style="width:262px" %)Measure|(% style="width:205px" %)Measure
296		-|(% style="width:262px" %)Attribute|(% style="width:205px" %)DataAttribute
	290	+|**VTL**|**SDMX**
	291	+|(Simple) Identifier|Dimension
	292	+|(Time) Identifier|TimeDimension
	293	+|Measure|Measure
	294	+|Attribute|DataAttribute
297	297
298	298	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.
299	299
...	...	@@ -321,12 +321,11 @@
321	321
322	322	The summary mapping table of the **unpivot** mapping method is the following:
323	323
324		-(% style="width:638.294px" %)
325		-|(% style="width:200px" %)**VTL**|(% style="width:435px" %)**SDMX**
326		-|(% style="width:200px" %)(Simple) Identifier|(% style="width:435px" %)Dimension
327		-|(% style="width:200px" %)(Time) Identifier|(% style="width:435px" %)TimeDimension
328		-|(% style="width:200px" %)All Measure Components|(% style="width:435px" %)MeasureDimension (having one Code for each VTL measure component) & one Measure
329		-|(% style="width:200px" %)Attribute|(% style="width:435px" %)DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
	322	+|**VTL**|**SDMX**
	323	+|(Simple) Identifier|Dimension
	324	+|(Time) Identifier|TimeDimension
	325	+|All Measure Components|MeasureDimension (having one Code for each VTL measure component) & one Measure
	326	+|Attribute|DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
330	330
331	331	At observation / data point level:
332	332
...	...	@@ -348,13 +348,12 @@
348	348
349	349	The mapping table is the following:
350	350
351		-(% style="width:467.294px" %)
352		-|(% style="width:214px" %)VTL|(% style="width:250px" %)SDMX
353		-|(% style="width:214px" %)(Simple) Identifier|(% style="width:250px" %)Dimension
354		-|(% style="width:214px" %)(Time) Identifier|(% style="width:250px" %)TimeDimension
355		-|(% style="width:214px" %)Some Measures|(% style="width:250px" %)Measure
356		-|(% style="width:214px" %)Other Measures|(% style="width:250px" %)DataAttribute
357		-|(% style="width:214px" %)Attribute|(% style="width:250px" %)DataAttribute
	348	+|VTL|SDMX
	349	+|(Simple) Identifier|Dimension
	350	+|(Time) Identifier|TimeDimension
	351	+|Some Measures|Measure
	352	+|Other Measures|DataAttribute
	353	+|Attribute|DataAttribute
358	358
359	359	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.
360	360
...	...	@@ -392,11 +392,11 @@
392	392
393	393	Therefore, the generic name of this kind of VTL datasets would be:
394	394
395		-> 'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
	391	+'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
396	396
397	397	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:
398	398
399		-> ‘DF(1.0.0)/POPULATION.USA’
	395	+‘DF(1.0.0)/POPULATION.USA’
400	400
401	401	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.
402	402
...	...	@@ -410,22 +410,26 @@
410	410
411	411	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.
412	412
413		-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 …).
	409	+In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e.
414	414
	411	+basic, pivot …).
	412	+
415	415	In the example above, for all the datasets of the kind
416	416
417		-> ‘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.
	415	+‘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.
418	418
419	419	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:
420	420
421		-> ‘DF1(1.0.0)/POPULATION.USA’ :=
422		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
423		->
424		-> ‘DF1(1.0.0)/POPULATION.CANADA’ :=
425		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
426		->
427		-> … … …
	419	+‘DF1(1.0.0)/POPULATION.USA’ :=
428	428
	421	+DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
	422	+
	423	+‘DF1(1.0.0)/POPULATION.CANADA’ :=
	424	+
	425	+DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
	426	+
	427	+… … …
	428	+
429	429	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}}
430	430
431	431	In the direction from SDMX to VTL it is allowed to omit the value of one or more DimensionComponents on which the mapping is based, but maintaining all the separating dots (therefore it may happen to find two or more consecutive dots and dots in the beginning or in the end). The absence of value means that for the corresponding Dimension all the values are kept and the Dimension is not dropped.
...	...	@@ -434,9 +434,10 @@
434	434
435	435	This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
436	436
437		-> ‘DF1(1.0.0)/POPULATION.’ :=
438		-> DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
	437	+‘DF1(1.0.0)/POPULATION.’ :=
439	439
	439	+DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
	440	+
440	440	Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
441	441
442	442	Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different Dimensions in different invocations.
...	...	@@ -454,33 +454,41 @@
454	454
455	455	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}}
456	456
457		-> ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
	458	+‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
458	458
459	459	Some examples follow, for some specific values of INDICATOR and COUNTRY:
460	460
461		-> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
462		-> … … …
463		-> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
464		-> ‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
465		-> … … …
	462	+‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
	463	+… … …
466	466
	465	+‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
	466	+‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
	467	+… … …
	468	+
467	467	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:
468	468
469		-> VTL dataset INDICATOR value COUNTRY value
470		->
471		-> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
472		-> ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
473		->
474		-> ‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
475		-> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
476		-> … … …
	471	+VTL dataset   INDICATOR value COUNTRY value
477	477
	473	+‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
	474	+‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
	475	+‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
	476	+‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
	477	+
	478	+… … …
	479	+
478	478	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:
479	479
480		-> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”]; DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”];… … … DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”]; DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”];… … … DF2(1.0) <- UNION (DF2bis_GDPPERCAPITA_USA’, DF2bis_GDPPERCAPITA_CANADA’,
481		-> … ,
482		-> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
483		-> …);
	482	+DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
	483	+DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
	484	+DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’
	485	+[calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
	486	+DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
	487	+DF2(1.0) <- UNION  (DF2bis_GDPPERCAPITA_USA’,
	488	+DF2bis_GDPPERCAPITA_CANADA’,
	489	+… ,
	490	+DF2bis_POPGROWTH_USA’,
	491	+DF2bis_POPGROWTH_CANADA’
	492	+…);
484	484
485	485	In other words, starting from the datasets explicitly calculated through VTL (in the example ‘DF2(1.0)/GDPPERCAPITA.USA’ and so on), the first step consists in calculating other (non-persistent) VTL datasets (in the example DF2bis_GDPPERCAPITA_USA and so on) by adding the identifiers INDICATOR and COUNTRY with the desired values (//INDICATORvalue// and //COUNTRYvalue)//. Finally, all these non-persistent Data Sets are united and give the final result DF2(1.0){{footnote}}The result is persistent in this example but it can be also non persistent if needed.{{/footnote}}, which can be mapped one-to-one to the homonymous SDMX Dataflow having the dimension components TIME_PERIOD, INDICATOR and COUNTRY.
486	486
...	...	@@ -492,26 +492,25 @@
492	492
493	493	With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
494	494
495		-(% style="width:706.294px" %)
496		-|(% style="width:257px" %)VTL|(% style="width:446px" %)SDMX
497		-|(% style="width:257px" %)**Data Set Component**|(% style="width:446px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow^^43^^
498		-|(% style="width:257px" %)**Represented Variable**|(% style="width:446px" %)**Concept** with a definite Representation
499		-|(% style="width:257px" %)**Value Domain**|(% style="width:446px" %)(((
	504	+|VTL|SDMX
	505	+|**Data Set Component**|Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow^^43^^
	506	+|**Represented Variable**|**Concept** with a definite Representation
	507	+|**Value Domain**|(((
500	500	**Representation** (see the Structure
501	501	Pattern in the Base Package)
502	502	)))
503		-|(% style="width:257px" %)**Enumerated Value Domain / Code List**|(% style="width:446px" %)**Codelist**
504		-|(% style="width:257px" %)**Code**|(% style="width:446px" %)**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
505		-|(% style="width:257px" %)**Described Value Domain**|(% style="width:446px" %)(((
	511	+|**Enumerated Value Domain / Code List**|**Codelist**
	512	+|**Code**|**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
	513	+|**Described Value Domain**|(((
506	506	non-enumerated** Representation**
507	507	(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
508	508	)))
509		-|(% style="width:257px" %)**Value**|(% style="width:446px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or
510		-|(% style="width:257px" %) |(% style="width:446px" %)to a valid **value **(for non-enumerated** **Representations)
511		-|(% style="width:257px" %)**Value Domain Subset / Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
512		-|(% style="width:257px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
513		-|(% style="width:257px" %)**Described Value Domain Subset / Described Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
514		-|(% style="width:257px" %)**Set list**|(% style="width:446px" %)This abstraction does not exist in SDMX
	517	+|**Value**|Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or
	518	+| |to a valid **value **(for non-enumerated** **Representations)
	519	+|**Value Domain Subset / Set**|This abstraction does not exist in SDMX
	520	+|**Enumerated Value Domain Subset / Enumerated Set**|This abstraction does not exist in SDMX
	521	+|**Described Value Domain Subset / Described Set**|This abstraction does not exist in SDMX
	522	+|**Set list**|This abstraction does not exist in SDMX
515	515
516	516	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).
517	517
...	...	@@ -519,10 +519,8 @@
519	519
520	520	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
521	521
522		-> DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
	530	+DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets) if the matching components in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general representation. In simpler words, DS_a and DS_b must use the same values/codes (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
523	523
524		-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.
525		-
526	526	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
527	527
528	528	Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
...	...	@@ -537,7 +537,7 @@
537	537
538	538	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:
539	539
540		-[[image:1750070288958-132.png]]
	546	+[[image:1750067055028-964.png]]
541	541
542	542	**Figure 22 – VTL Data Types**
543	543
...	...	@@ -545,8 +545,6 @@
545	545
546	546	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):
547	547
548		-[[image:1750070310572-584.png]]
549		-
550	550	**Figure 23 – VTL Basic Scalar Types**
551	551
552	552	=== 12.4.2 VTL basic scalar types and SDMX data types ===
...	...	@@ -571,159 +571,158 @@
571	571
572	572	The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
573	573
574		-(% style="width:583.294px" %)
575		-|(% style="width:360px" %)SDMX data type
576		-(BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
577		-|(% style="width:360px" %)(((
	578	+|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
	579	+|(((
578	578	String
579	579	(string allowing any character)
580		-)))|(% style="width:221px" %)string
581		-|(% style="width:360px" %)(((
582		-Alpha
	582	+)))|string
	583	+|(((
	584	+Alpha
	585	+
583	583	(string which only allows A-z)
584		-)))|(% style="width:221px" %)string
585		-|(% style="width:360px" %)(((
	587	+)))|string
	588	+|(((
586	586	AlphaNumeric
587	587	(string which only allows A-z and 0-9)
588		-)))|(% style="width:221px" %)string
589		-|(% style="width:360px" %)(((
	591	+)))|string
	592	+|(((
590	590	Numeric
	594	+
591	591	(string which only allows 0-9, but is not numeric so that is can having leading zeros)
592		-)))|(% style="width:221px" %)string
593		-|(% style="width:360px" %)(((
	596	+)))|string
	597	+|(((
594	594	BigInteger
595	595	(corresponds to XML Schema xs:integer datatype; infinite set of integer values)
596		-)))|(% style="width:221px" %)integer
597		-|(% style="width:360px" %)(((
	600	+)))|integer
	601	+|(((
598	598	Integer
599	599	(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
600	600	(inclusive))
601		-)))|(% style="width:221px" %)integer
602		-|(% style="width:360px" %)(((
	605	+)))|integer
	606	+|(((
603	603	Long
604	604	(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
605	605	+9223372036854775807 (inclusive))
606		-)))|(% style="width:221px" %)integer
607		-|(% style="width:360px" %)(((
	610	+)))|integer
	611	+|(((
608	608	Short
609	609	(corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
610		-)))|(% style="width:221px" %)integer
611		-|(% style="width:360px" %)Decimal
612		-(corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:221px" %)number
613		-|(% style="width:360px" %)(((
	614	+)))|integer
	615	+|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
	616	+|(((
614	614	Float
615	615	(corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
616		-)))|(% style="width:221px" %)number
617		-|(% style="width:360px" %)(((
	619	+)))|number
	620	+|(((
618	618	Double
619	619	(corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
620		-)))|(% style="width:221px" %)number
621		-|(% style="width:360px" %)(((
	623	+)))|number
	624	+|(((
622	622	Boolean
623	623	(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
624	624	binary-valued logic: {true, false})
625		-)))|(% style="width:221px" %)boolean
626		-|(% style="width:360px" %)(((
	628	+)))|boolean
	629	+|(((
627	627	URI
628	628	(corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
629		-)))|(% style="width:221px" %)string
630		-|(% style="width:360px" %)(((
	632	+)))|string
	633	+|(((
631	631	Count
632	632	(an integer following a sequential pattern, increasing by 1 for each occurrence)
633		-)))|(% style="width:221px" %)integer
634		-|(% style="width:360px" %)(((
	636	+)))|integer
	637	+|(((
635	635	InclusiveValueRange
636	636	(decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
637		-)))|(% style="width:221px" %)number
638		-|(% style="width:360px" %)(((
	640	+)))|number
	641	+|(((
639	639	ExclusiveValueRange
640	640	(decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
641		-)))|(% style="width:221px" %)number
642		-|(% style="width:360px" %)(((
	644	+)))|number
	645	+|(((
643	643	Incremental
644	644	(decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
645		-)))|(% style="width:221px" %)number
646		-|(% style="width:360px" %)(((
	648	+)))|number
	649	+|(((
647	647	ObservationalTimePeriod
648	648	(superset of StandardTimePeriod and TimeRange)
649		-)))|(% style="width:221px" %)time
650		-|(% style="width:360px" %)(((
	652	+)))|time
	653	+|(((
651	651	StandardTimePeriod
652	652	(superset of BasicTimePeriod and ReportingTimePeriod)
653		-)))|(% style="width:221px" %)time
654		-|(% style="width:360px" %)(((
	656	+)))|time
	657	+|(((
655	655	BasicTimePeriod
656	656	(superset of GregorianTimePeriod and DateTime)
657		-)))|(% style="width:221px" %)date
658		-|(% style="width:360px" %)(((
	660	+)))|date
	661	+|(((
659	659	GregorianTimePeriod
660	660	(superset of GregorianYear, GregorianYearMonth, and GregorianDay)
661		-)))|(% style="width:221px" %)date
662		-|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
663		-|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
664		-|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
665		-|(% style="width:360px" %)(((
	664	+)))|date
	665	+|GregorianYear (YYYY)|date
	666	+|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
	667	+|GregorianDay (YYYY-MM-DD)|date
	668	+|(((
666	666	ReportingTimePeriod
667	667	(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
668		-)))|(% style="width:221px" %)time_period
669		-|(% style="width:360px" %)(((
	671	+)))|time_period
	672	+|(((
670	670	ReportingYear
671	671	(YYYY-A1 – 1 year period)
672		-)))|(% style="width:221px" %)time_period
673		-|(% style="width:360px" %)(((
	675	+)))|time_period
	676	+|(((
674	674	ReportingSemester
675	675	(YYYY-Ss – 6 month period)
676		-)))|(% style="width:221px" %)time_period
677		-|(% style="width:360px" %)(((
	679	+)))|time_period
	680	+|(((
678	678	ReportingTrimester
679	679	(YYYY-Tt – 4 month period)
680		-)))|(% style="width:221px" %)time_period
681		-|(% style="width:360px" %)(((
	683	+)))|time_period
	684	+|(((
682	682	ReportingQuarter
683	683	(YYYY-Qq – 3 month period)
684		-)))|(% style="width:221px" %)time_period
685		-|(% style="width:360px" %)(((
	687	+)))|time_period
	688	+|(((
686	686	ReportingMonth
687	687	(YYYY-Mmm – 1 month period)
688		-)))|(% style="width:221px" %)time_period
689		-|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
690		-|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
691		-|(% style="width:360px" %)(((
	691	+)))|time_period
	692	+|ReportingWeek|time_period
	693	+| (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|
	694	+|(((
692	692	ReportingDay
693	693	(YYYY-Dddd – 1 day period)
694		-)))|(% style="width:221px" %)time_period
695		-|(% style="width:360px" %)(((
	697	+)))|time_period
	698	+|(((
696	696	DateTime
697	697	(YYYY-MM-DDThh:mm:ss)
698		-)))|(% style="width:221px" %)date
699		-|(% style="width:360px" %)(((
	701	+)))|date
	702	+|(((
700	700	TimeRange
701		-(YYYY-MM-DD(Thh:mm:ss)?/)
702		-)))|(% style="width:221px" %)time
703		-|(% style="width:360px" %)(((
	704	+(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
	705	+)))|time
	706	+|(((
704	704	Month
705		-(MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
706		-)))|(% style="width:221px" %)string
707		-|(% style="width:360px" %)(((
	708	+(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
	709	+)))|string
	710	+|(((
708	708	MonthDay
709		-(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)
710		-)))|(% style="width:221px" %)string
711		-|(% style="width:360px" %)(((
	712	+(~-~-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)
	713	+)))|string
	714	+|(((
712	712	Day
713		-(-DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
714		-)))|(% style="width:221px" %)string
715		-|(% style="width:360px" %)(((
	716	+(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
	717	+)))|string
	718	+|(((
716	716	Time
717	717	(hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
718		-)))|(% style="width:221px" %)string
719		-|(% style="width:360px" %)(((
	721	+)))|string
	722	+|(((
720	720	Duration
721	721	(corresponds to XML Schema xs:duration datatype)
722		-)))|(% style="width:221px" %)duration
723		-|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
724		-|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
725		-|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
726		-|(% style="width:360px" %)DataSetReference|(% style="width:221px" %)Metadata type – not applicable
	725	+)))|duration
	726	+|XHTML|Metadata type – not applicable
	727	+|KeyValues|Metadata type – not applicable
	728	+|IdentifiableReference|Metadata type – not applicable
	729	+|DataSetReference|Metadata type – not applicable
727	727
728	728	**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
729	729
...	...	@@ -733,82 +733,84 @@
733	733
734	734	The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
735	735
736		-(% style="width:748.294px" %)
737		-|(% style="width:164px" %)(((
738		-VTL basic scalar type
739		-)))|(% style="width:304px" %)(((
	739	+|(((
	740	+VTL basic
	741	+scalar type
	742	+)))|(((
740	740	Default SDMX data type
741		-(BasicComponentDataType)
742		-)))|(% style="width:277px" %)Default output format
743		-|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
744		-|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
745		-|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
746		-|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
747		-|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
748		-|(% style="width:164px" %)time_period|(% style="width:304px" %)(((
	744	+(BasicComponentDataType
	745	+)
	746	+)))|Default output format
	747	+|String|String|Like XML (xs:string)
	748	+|Number|Float|Like XML (xs:float)
	749	+|Integer|Integer|Like XML (xs:int)
	750	+|Date|DateTime|YYYY-MM-DDT00:00:00Z
	751	+|Time|StandardTimePeriod|<date>/<date> (as defined above)
	752	+|time_period|(((
749	749	ReportingTimePeriod
750	750	(StandardReportingPeriod)
751		-)))|(% style="width:277px" %)(((
	755	+)))|(((
752	752	YYYY-Pppp
753	753	(according to SDMX )
754	754	)))
755		-|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
756		-|(% style="width:164px" %)Boolean|(% style="width:304px" %)Boolean|(% style="width:277px" %)Like XML (xs:boolean) with the values "true" or "false"
	759	+|Duration|Duration|Like XML (xs:duration) PnYnMnDTnHnMnS
	760	+|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
757	757
758	758	**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
759	759
760		-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).
	764	+In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section
761	761
	766	+Transformations and Expressions of the SDMX information model).
	767	+
762	762	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.
763	763
764		-(% style="width:717.294px" %)
765		-|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
766		-|(% colspan="2" style="width:714px" %)
767		-|(% colspan="2" style="width:714px" %)Number
768		-|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
769		-|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
770		-|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
771		-|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
772		-|(% style="width:122px" %) |(% style="width:591px" %)
773		-|(% colspan="2" style="width:714px" %)Time and duration
774		-|(% style="width:122px" %)C|(% style="width:591px" %)century
775		-|(% style="width:122px" %)Y|(% style="width:591px" %)year
776		-|(% style="width:122px" %)S|(% style="width:591px" %)semester
777		-|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
778		-|(% style="width:122px" %)M|(% style="width:591px" %)month
779		-|(% style="width:122px" %)W|(% style="width:591px" %)week
780		-|(% style="width:122px" %)D|(% style="width:591px" %)day
781		-|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
782		-|(% style="width:122px" %)M|(% style="width:591px" %)minute
783		-|(% style="width:122px" %)S|(% style="width:591px" %)second
784		-|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
785		-|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
786		-|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
787		-|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
788		-|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
789		-|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
790		-|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
791		-|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
792		-|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
793		-|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
794		-|(% style="width:122px" %) |(% style="width:591px" %)
795		-|(% colspan="2" style="width:714px" %)String
796		-|(% style="width:122px" %)X|(% style="width:591px" %)any string character
797		-|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
798		-|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
799		-|(% style="width:122px" %) |(% style="width:591px" %)
800		-|(% colspan="2" style="width:714px" %)Boolean
801		-|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
802		-|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
803		-|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
804		-|(% style="width:122px" %) |(% style="width:591px" %)
805		-|(% colspan="2" style="width:714px" %)Other qualifiers
806		-|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
807		-|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
808		-|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
809		-|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
810		-|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
811		-|(% style="width:122px" %) |(% style="width:591px" %)
	770	+|(% colspan="2" %)VTL special characters for the formatting masks
	771	+|(% colspan="2" %)
	772	+|(% colspan="2" %)Number
	773	+|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
	774	+|E|one numeric digit (for the exponent of the scientific notation)
	775	+|. (dot)|possible separator between the integer and the decimal parts.
	776	+|, (comma)|possible separator between the integer and the decimal parts.
	777	+| |
	778	+|(% colspan="2" %)Time and duration
	779	+|C|century
	780	+|Y|year
	781	+|S|semester
	782	+|Q|quarter
	783	+|M|month
	784	+|W|week
	785	+|D|day
	786	+|h|hour digit (by default on 24 hours)
	787	+|M|minute
	788	+|S|second
	789	+|D|decimal of second
	790	+|P|period indicator (representation in one digit for the duration)
	791	+|P|number of the periods specified in the period indicator
	792	+|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
	793	+|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
	794	+|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
	795	+|Month|lowercase textual representation of the month (e.g., january)
	796	+|Day|lowercase textual representation of the month (e.g., monday)
	797	+|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
	798	+|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
	799	+| |
	800	+|(% colspan="2" %)String
	801	+|X|any string character
	802	+|Z|any string character from "A" to "z"
	803	+|9|any string character from "0" to "9"
	804	+| |
	805	+|(% colspan="2" %)Boolean
	806	+|B|Boolean using "true" for True and "false" for False
	807	+|1|Boolean using "1" for True and "0" for False
	808	+|0|Boolean using "0" for True and "1" for False
	809	+| |
	810	+|(% colspan="2" %)Other qualifiers
	811	+|*|an arbitrary number of digits (of the preceding type)
	812	+|+|at least one digit (of the preceding type)
	813	+|( )|optional digits (specified within the brackets)
	814	+|\|prefix for the special characters that must appear in the mask
	815	+|N|fixed number of digits used in the preceding textual representation of the month or the day
	816	+| |
812	812
813	813	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}}.
814	814

1750070288958-132.png

Author

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

Size

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

Content

1750070310572-584.png

Author

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

Size

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

Content

1750067055028-964.png

Author

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

Size

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

Content

SKMS.Methodology.Code.MethodologyClass[0]

Index

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

SUZ.Methodology.Code.MethodologyClass[0]