Changes for page 12 Validation and Transformation Language (VTL)

Summary

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

Details

Page properties

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
...	...	@@ -116,7 +116,7 @@
116	116
117	117	by omitting all the non-essential parts would become simply:
118	118
119		-> DFR  : =  DF1 + DF2
	119	+> DFR  : = DF1 + DF2
120	120
121	121	The references to the Codelists can be simplified similarly. For example, given the non-abbreviated reference to the Codelist AG:CL_FREQ(1.0.0), which is{{footnote}}Single quotes are needed because this reference is not a VTL regular name. 19 Single quotes are not needed in this case because CL_FREQ is a VTL regular name.{{/footnote}}:
122	122
...	...	@@ -313,11 +313,12 @@
313	313
314	314	The summary mapping table of the **unpivot** mapping method is the following:
315	315
316		-|**VTL**|**SDMX**
317		-|(Simple) Identifier|Dimension
318		-|(Time) Identifier|TimeDimension
319		-|All Measure Components|MeasureDimension (having one Code for each VTL measure component) & one Measure
320		-|Attribute|DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
	316	+(% style="width:638.294px" %)
	317	+|(% style="width:200px" %)**VTL**|(% style="width:435px" %)**SDMX**
	318	+|(% style="width:200px" %)(Simple) Identifier|(% style="width:435px" %)Dimension
	319	+|(% style="width:200px" %)(Time) Identifier|(% style="width:435px" %)TimeDimension
	320	+|(% style="width:200px" %)All Measure Components|(% style="width:435px" %)MeasureDimension (having one Code for each VTL measure component) & one Measure
	321	+|(% style="width:200px" %)Attribute|(% style="width:435px" %)DataAttribute depending on all SDMX Dimensions including the TimeDimension and except the MeasureDimension
321	321
322	322	At observation / data point level:
323	323
...	...	@@ -339,12 +339,13 @@
339	339
340	340	The mapping table is the following:
341	341
342		-|VTL|SDMX
343		-|(Simple) Identifier|Dimension
344		-|(Time) Identifier|TimeDimension
345		-|Some Measures|Measure
346		-|Other Measures|DataAttribute
347		-|Attribute|DataAttribute
	343	+(% style="width:467.294px" %)
	344	+|(% style="width:214px" %)VTL|(% style="width:250px" %)SDMX
	345	+|(% style="width:214px" %)(Simple) Identifier|(% style="width:250px" %)Dimension
	346	+|(% style="width:214px" %)(Time) Identifier|(% style="width:250px" %)TimeDimension
	347	+|(% style="width:214px" %)Some Measures|(% style="width:250px" %)Measure
	348	+|(% style="width:214px" %)Other Measures|(% style="width:250px" %)DataAttribute
	349	+|(% style="width:214px" %)Attribute|(% style="width:250px" %)DataAttribute
348	348
349	349	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.
350	350
...	...	@@ -382,11 +382,11 @@
382	382
383	383	Therefore, the generic name of this kind of VTL datasets would be:
384	384
385		-'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
	387	+> 'DF(1.0.0)/INDICATORvalue.COUNTRYvalue'
386	386
387	387	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:
388	388
389		-‘DF(1.0.0)/POPULATION.USA’
	391	+> ‘DF(1.0.0)/POPULATION.USA’
390	390
391	391	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.
392	392
...	...	@@ -400,26 +400,22 @@
400	400
401	401	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.
402	402
403		-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.
	405	+In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e. basic, pivot …).
404	404
405		-basic, pivot …).
406		-
407	407	In the example above, for all the datasets of the kind
408	408
409		-‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
	409	+> ‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
410	410
411	411	It should be noted that the desired VTL Data Sets (i.e. of the kind ‘DF1(1.0.0)/// INDICATORvalue//.//COUNTRYvalue//’) can be obtained also by applying the VTL operator “**sub**” (subspace) to the Dataflow DF1(1.0.0), like in the following VTL expression:
412	412
413		-‘DF1(1.0.0)/POPULATION.USA’ :=
	413	+> ‘DF1(1.0.0)/POPULATION.USA’ :=
	414	+> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
	415	+>
	416	+> ‘DF1(1.0.0)/POPULATION.CANADA’ :=
	417	+> DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
	418	+>
	419	+> … … …
414	414
415		-DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
416		-
417		-‘DF1(1.0.0)/POPULATION.CANADA’ :=
418		-
419		-DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
420		-
421		-… … …
422		-
423	423	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}}
424	424
425	425	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.
...	...	@@ -428,10 +428,9 @@
428	428
429	429	This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
430	430
431		-‘DF1(1.0.0)/POPULATION.’ :=
	429	+> ‘DF1(1.0.0)/POPULATION.’ :=
	430	+> DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
432	432
433		-DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
434		-
435	435	Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
436	436
437	437	Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different Dimensions in different invocations.
...	...	@@ -449,41 +449,39 @@
449	449
450	450	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}}
451	451
452		-‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
	449	+> ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
453	453
454	454	Some examples follow, for some specific values of INDICATOR and COUNTRY:
455	455
456		-‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
457		-… … …
	453	+> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
	454	+> … … …
	455	+> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
	456	+> ‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
	457	+> … … …
458	458
459		-‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
460		-‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
461		-… … …
462		-
463	463	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:
464	464
465		-VTL dataset   INDICATOR value COUNTRY value
	461	+> VTL dataset  INDICATOR value COUNTRY value
	462	+>
	463	+> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
	464	+> ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
	465	+>
	466	+> ‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
	467	+> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
	468	+> … … …
466	466
467		-‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
468		-‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
469		-‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
470		-‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
471		-
472		-… … …
473		-
474	474	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:
475	475
476		-DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
477		-DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
478		-DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’
479		-[calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
480		-DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
481		-DF2(1.0) <- UNION  (DF2bis_GDPPERCAPITA_USA’,
482		-DF2bis_GDPPERCAPITA_CANADA’,
483		-… ,
484		-DF2bis_POPGROWTH_USA’,
485		-DF2bis_POPGROWTH_CANADA’
486		-…);
	472	+> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
	473	+> DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
	474	+> DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’  [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
	475	+> DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
	476	+> DF2(1.0) <- UNION  (DF2bis_GDPPERCAPITA_USA’,
	477	+> DF2bis_GDPPERCAPITA_CANADA’,
	478	+> … ,
	479	+> DF2bis_POPGROWTH_USA’,
	480	+> DF2bis_POPGROWTH_CANADA’
	481	+> …);
487	487
488	488	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.
489	489
...	...	@@ -495,25 +495,26 @@
495	495
496	496	With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
497	497
498		-|VTL|SDMX
499		-|**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^^
500		-|**Represented Variable**|**Concept** with a definite Representation
501		-|**Value Domain**|(((
	493	+(% style="width:706.294px" %)
	494	+|(% style="width:257px" %)VTL|(% style="width:446px" %)SDMX
	495	+|(% 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^^
	496	+|(% style="width:257px" %)**Represented Variable**|(% style="width:446px" %)**Concept** with a definite Representation
	497	+|(% style="width:257px" %)**Value Domain**|(% style="width:446px" %)(((
502	502	**Representation** (see the Structure
503	503	Pattern in the Base Package)
504	504	)))
505		-|**Enumerated Value Domain / Code List**|**Codelist**
506		-|**Code**|**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
507		-|**Described Value Domain**|(((
	501	+|(% style="width:257px" %)**Enumerated Value Domain / Code List**|(% style="width:446px" %)**Codelist**
	502	+|(% style="width:257px" %)**Code**|(% style="width:446px" %)**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
	503	+|(% style="width:257px" %)**Described Value Domain**|(% style="width:446px" %)(((
508	508	non-enumerated** Representation**
509	509	(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
510	510	)))
511		-|**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
512		-| |to a valid **value **(for non-enumerated** **Representations)
513		-|**Value Domain Subset / Set**|This abstraction does not exist in SDMX
514		-|**Enumerated Value Domain Subset / Enumerated Set**|This abstraction does not exist in SDMX
515		-|**Described Value Domain Subset / Described Set**|This abstraction does not exist in SDMX
516		-|**Set list**|This abstraction does not exist in SDMX
	507	+|(% 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
	508	+|(% style="width:257px" %) |(% style="width:446px" %)to a valid **value **(for non-enumerated** **Representations)
	509	+|(% style="width:257px" %)**Value Domain Subset / Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
	510	+|(% style="width:257px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
	511	+|(% style="width:257px" %)**Described Value Domain Subset / Described Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
	512	+|(% style="width:257px" %)**Set list**|(% style="width:446px" %)This abstraction does not exist in SDMX
517	517
518	518	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).
519	519
...	...	@@ -521,8 +521,10 @@
521	521
522	522	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
523	523
524		-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.
	520	+> DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
525	525
	522	+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	+
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,8 +537,9 @@
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:1750067055028-964.png]]
541	541
	539	+[[image:1750070288958-132.png]]
	540	+
542	542	**Figure 22 – VTL Data Types**
543	543
544	544	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.
...	...	@@ -545,6 +545,8 @@
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
	547	+[[image:1750070310572-584.png]]
	548	+
548	548	**Figure 23 – VTL Basic Scalar Types**
549	549
550	550	=== 12.4.2 VTL basic scalar types and SDMX data types ===
...	...	@@ -569,158 +569,157 @@
569	569
570	570	The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
571	571
572		-|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
573		-|(((
	573	+(% style="width:583.294px" %)
	574	+|(% style="width:360px" %)SDMX data type (BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
	575	+|(% style="width:360px" %)(((
574	574	String
575	575	(string allowing any character)
576		-)))|string
577		-|(((
578		-Alpha
579		-
	578	+)))|(% style="width:221px" %)string
	579	+|(% style="width:360px" %)(((
	580	+Alpha
580	580	(string which only allows A-z)
581		-)))|string
582		-|(((
	582	+)))|(% style="width:221px" %)string
	583	+|(% style="width:360px" %)(((
583	583	AlphaNumeric
584	584	(string which only allows A-z and 0-9)
585		-)))|string
586		-|(((
	586	+)))|(% style="width:221px" %)string
	587	+|(% style="width:360px" %)(((
587	587	Numeric
588		-
589	589	(string which only allows 0-9, but is not numeric so that is can having leading zeros)
590		-)))|string
591		-|(((
	590	+)))|(% style="width:221px" %)string
	591	+|(% style="width:360px" %)(((
592	592	BigInteger
593	593	(corresponds to XML Schema xs:integer datatype; infinite set of integer values)
594		-)))|integer
595		-|(((
	594	+)))|(% style="width:221px" %)integer
	595	+|(% style="width:360px" %)(((
596	596	Integer
597	597	(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
598	598	(inclusive))
599		-)))|integer
600		-|(((
	599	+)))|(% style="width:221px" %)integer
	600	+|(% style="width:360px" %)(((
601	601	Long
602	602	(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
603	603	+9223372036854775807 (inclusive))
604		-)))|integer
605		-|(((
	604	+)))|(% style="width:221px" %)integer
	605	+|(% style="width:360px" %)(((
606	606	Short
607	607	(corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
608		-)))|integer
609		-|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
610		-|(((
	608	+)))|(% style="width:221px" %)integer
	609	+|(% style="width:360px" %)Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:221px" %)number
	610	+|(% style="width:360px" %)(((
611	611	Float
612	612	(corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
613		-)))|number
614		-|(((
	613	+)))|(% style="width:221px" %)number
	614	+|(% style="width:360px" %)(((
615	615	Double
616	616	(corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
617		-)))|number
618		-|(((
	617	+)))|(% style="width:221px" %)number
	618	+|(% style="width:360px" %)(((
619	619	Boolean
620	620	(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
621	621	binary-valued logic: {true, false})
622		-)))|boolean
623		-|(((
	622	+)))|(% style="width:221px" %)boolean
	623	+|(% style="width:360px" %)(((
624	624	URI
625	625	(corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
626		-)))|string
627		-|(((
	626	+)))|(% style="width:221px" %)string
	627	+|(% style="width:360px" %)(((
628	628	Count
629	629	(an integer following a sequential pattern, increasing by 1 for each occurrence)
630		-)))|integer
631		-|(((
	630	+)))|(% style="width:221px" %)integer
	631	+|(% style="width:360px" %)(((
632	632	InclusiveValueRange
633	633	(decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
634		-)))|number
635		-|(((
	634	+)))|(% style="width:221px" %)number
	635	+|(% style="width:360px" %)(((
636	636	ExclusiveValueRange
637	637	(decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
638		-)))|number
639		-|(((
	638	+)))|(% style="width:221px" %)number
	639	+|(% style="width:360px" %)(((
640	640	Incremental
641	641	(decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
642		-)))|number
643		-|(((
	642	+)))|(% style="width:221px" %)number
	643	+|(% style="width:360px" %)(((
644	644	ObservationalTimePeriod
645	645	(superset of StandardTimePeriod and TimeRange)
646		-)))|time
647		-|(((
	646	+)))|(% style="width:221px" %)time
	647	+|(% style="width:360px" %)(((
648	648	StandardTimePeriod
649	649	(superset of BasicTimePeriod and ReportingTimePeriod)
650		-)))|time
651		-|(((
	650	+)))|(% style="width:221px" %)time
	651	+|(% style="width:360px" %)(((
652	652	BasicTimePeriod
653	653	(superset of GregorianTimePeriod and DateTime)
654		-)))|date
655		-|(((
	654	+)))|(% style="width:221px" %)date
	655	+|(% style="width:360px" %)(((
656	656	GregorianTimePeriod
657	657	(superset of GregorianYear, GregorianYearMonth, and GregorianDay)
658		-)))|date
659		-|GregorianYear (YYYY)|date
660		-|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
661		-|GregorianDay (YYYY-MM-DD)|date
662		-|(((
	658	+)))|(% style="width:221px" %)date
	659	+|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
	660	+|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
	661	+|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
	662	+|(% style="width:360px" %)(((
663	663	ReportingTimePeriod
664	664	(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
665		-)))|time_period
666		-|(((
	665	+)))|(% style="width:221px" %)time_period
	666	+|(% style="width:360px" %)(((
667	667	ReportingYear
668	668	(YYYY-A1 – 1 year period)
669		-)))|time_period
670		-|(((
	669	+)))|(% style="width:221px" %)time_period
	670	+|(% style="width:360px" %)(((
671	671	ReportingSemester
672	672	(YYYY-Ss – 6 month period)
673		-)))|time_period
674		-|(((
	673	+)))|(% style="width:221px" %)time_period
	674	+|(% style="width:360px" %)(((
675	675	ReportingTrimester
676	676	(YYYY-Tt – 4 month period)
677		-)))|time_period
678		-|(((
	677	+)))|(% style="width:221px" %)time_period
	678	+|(% style="width:360px" %)(((
679	679	ReportingQuarter
680	680	(YYYY-Qq – 3 month period)
681		-)))|time_period
682		-|(((
	681	+)))|(% style="width:221px" %)time_period
	682	+|(% style="width:360px" %)(((
683	683	ReportingMonth
684	684	(YYYY-Mmm – 1 month period)
685		-)))|time_period
686		-|ReportingWeek|time_period
687		-| (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|
688		-|(((
	685	+)))|(% style="width:221px" %)time_period
	686	+|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
	687	+|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
	688	+|(% style="width:360px" %)(((
689	689	ReportingDay
690	690	(YYYY-Dddd – 1 day period)
691		-)))|time_period
692		-|(((
	691	+)))|(% style="width:221px" %)time_period
	692	+|(% style="width:360px" %)(((
693	693	DateTime
694	694	(YYYY-MM-DDThh:mm:ss)
695		-)))|date
696		-|(((
	695	+)))|(% style="width:221px" %)date
	696	+|(% style="width:360px" %)(((
697	697	TimeRange
698	698	(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
699		-)))|time
700		-|(((
	699	+)))|(% style="width:221px" %)time
	700	+|(% style="width:360px" %)(((
701	701	Month
702	702	(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
703		-)))|string
704		-|(((
	703	+)))|(% style="width:221px" %)string
	704	+|(% style="width:360px" %)(((
705	705	MonthDay
706	706	(~-~-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)
707		-)))|string
708		-|(((
	707	+)))|(% style="width:221px" %)string
	708	+|(% style="width:360px" %)(((
709	709	Day
710	710	(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
711		-)))|string
712		-|(((
	711	+)))|(% style="width:221px" %)string
	712	+|(% style="width:360px" %)(((
713	713	Time
714	714	(hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
715		-)))|string
716		-|(((
	715	+)))|(% style="width:221px" %)string
	716	+|(% style="width:360px" %)(((
717	717	Duration
718	718	(corresponds to XML Schema xs:duration datatype)
719		-)))|duration
720		-|XHTML|Metadata type – not applicable
721		-|KeyValues|Metadata type – not applicable
722		-|IdentifiableReference|Metadata type – not applicable
723		-|DataSetReference|Metadata type – not applicable
	719	+)))|(% style="width:221px" %)duration
	720	+|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
	721	+|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
	722	+|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
	723	+|(% style="width:360px" %)DataSetReference|(% style="width:221px" %)Metadata type – not applicable
724	724
725	725	**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
726	726
...	...	@@ -730,84 +730,82 @@
730	730
731	731	The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
732	732
733		-|(((
734		-VTL basic
735		-scalar type
736		-)))|(((
	733	+(% style="width:748.294px" %)
	734	+|(% style="width:164px" %)(((
	735	+VTL basic scalar type
	736	+)))|(% style="width:304px" %)(((
737	737	Default SDMX data type
738		-(BasicComponentDataType
739		-)
740		-)))|Default output format
741		-|String|String|Like XML (xs:string)
742		-|Number|Float|Like XML (xs:float)
743		-|Integer|Integer|Like XML (xs:int)
744		-|Date|DateTime|YYYY-MM-DDT00:00:00Z
745		-|Time|StandardTimePeriod|<date>/<date> (as defined above)
746		-|time_period|(((
	738	+(BasicComponentDataType)
	739	+)))|(% style="width:277px" %)Default output format
	740	+|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
	741	+|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
	742	+|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
	743	+|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
	744	+|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
	745	+|(% style="width:164px" %)time_period|(% style="width:304px" %)(((
747	747	ReportingTimePeriod
748	748	(StandardReportingPeriod)
749		-)))|(((
	748	+)))|(% style="width:277px" %)(((
750	750	YYYY-Pppp
751	751	(according to SDMX )
752	752	)))
753		-|Duration|Duration|Like XML (xs:duration) PnYnMnDTnHnMnS
754		-|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
	752	+|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
	753	+|(% style="width:164px" %)Boolean|(% style="width:304px" %)Boolean|(% style="width:277px" %)Like XML (xs:boolean) with the values "true" or "false"
755	755
756	756	**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
757	757
758		-In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section
	757	+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).
759	759
760		-Transformations and Expressions of the SDMX information model).
761		-
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		-|(% colspan="2" %)VTL special characters for the formatting masks
765		-|(% colspan="2" %)
766		-|(% colspan="2" %)Number
767		-|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
768		-|E|one numeric digit (for the exponent of the scientific notation)
769		-|. (dot)|possible separator between the integer and the decimal parts.
770		-|, (comma)|possible separator between the integer and the decimal parts.
771		-| |
772		-|(% colspan="2" %)Time and duration
773		-|C|century
774		-|Y|year
775		-|S|semester
776		-|Q|quarter
777		-|M|month
778		-|W|week
779		-|D|day
780		-|h|hour digit (by default on 24 hours)
781		-|M|minute
782		-|S|second
783		-|D|decimal of second
784		-|P|period indicator (representation in one digit for the duration)
785		-|P|number of the periods specified in the period indicator
786		-|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
787		-|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
788		-|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
789		-|Month|lowercase textual representation of the month (e.g., january)
790		-|Day|lowercase textual representation of the month (e.g., monday)
791		-|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
792		-|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
793		-| |
794		-|(% colspan="2" %)String
795		-|X|any string character
796		-|Z|any string character from "A" to "z"
797		-|9|any string character from "0" to "9"
798		-| |
799		-|(% colspan="2" %)Boolean
800		-|B|Boolean using "true" for True and "false" for False
801		-|1|Boolean using "1" for True and "0" for False
802		-|0|Boolean using "0" for True and "1" for False
803		-| |
804		-|(% colspan="2" %)Other qualifiers
805		-|*|an arbitrary number of digits (of the preceding type)
806		-|+|at least one digit (of the preceding type)
807		-|( )|optional digits (specified within the brackets)
808		-|\|prefix for the special characters that must appear in the mask
809		-|N|fixed number of digits used in the preceding textual representation of the month or the day
810		-| |
	761	+(% style="width:717.294px" %)
	762	+|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
	763	+|(% colspan="2" style="width:714px" %)
	764	+|(% colspan="2" style="width:714px" %)Number
	765	+|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
	766	+|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
	767	+|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
	768	+|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
	769	+|(% style="width:122px" %) |(% style="width:591px" %)
	770	+|(% colspan="2" style="width:714px" %)Time and duration
	771	+|(% style="width:122px" %)C|(% style="width:591px" %)century
	772	+|(% style="width:122px" %)Y|(% style="width:591px" %)year
	773	+|(% style="width:122px" %)S|(% style="width:591px" %)semester
	774	+|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
	775	+|(% style="width:122px" %)M|(% style="width:591px" %)month
	776	+|(% style="width:122px" %)W|(% style="width:591px" %)week
	777	+|(% style="width:122px" %)D|(% style="width:591px" %)day
	778	+|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
	779	+|(% style="width:122px" %)M|(% style="width:591px" %)minute
	780	+|(% style="width:122px" %)S|(% style="width:591px" %)second
	781	+|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
	782	+|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
	783	+|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
	784	+|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
	785	+|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
	786	+|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
	787	+|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
	788	+|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
	789	+|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
	790	+|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
	791	+|(% style="width:122px" %) |(% style="width:591px" %)
	792	+|(% colspan="2" style="width:714px" %)String
	793	+|(% style="width:122px" %)X|(% style="width:591px" %)any string character
	794	+|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
	795	+|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
	796	+|(% style="width:122px" %) |(% style="width:591px" %)
	797	+|(% colspan="2" style="width:714px" %)Boolean
	798	+|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
	799	+|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
	800	+|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
	801	+|(% style="width:122px" %) |(% style="width:591px" %)
	802	+|(% colspan="2" style="width:714px" %)Other qualifiers
	803	+|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
	804	+|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
	805	+|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
	806	+|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
	807	+|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
	808	+|(% style="width:122px" %) |(% style="width:591px" %)
811	811
812	812	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}}.
813	813

1750067055028-964.png

Author

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

Size

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

Content

1750070288958-132.png

Author

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

Size

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

Content

1750070310572-584.png

Author

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

Size

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

Content