Changes for page 12 Validation and Transformation Language (VTL)

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • 1747388434672-948.png
  • 1747388465321-274.png

Details

Page properties

Content

...	...	@@ -477,30 +477,31 @@
477	477
478	478	With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
479	479
480		-(% style="width:895.294px" %)
481		-|(% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**
482		-|(% style="width:278px" %)**Data Set Component**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
483		-|(% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((
	480	+(% style="width:1170.29px" %)
	481	+|(% style="width:392px" %)**VTL**|(% style="width:776px" %)**SDMX**
	482	+|(% style="width:392px" %)**Data Set Component**|(% style="width:776px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
	483	+|(% style="width:392px" %)**Represented Variable**|(% style="width:776px" %)(((
484	484	**Concept** with a definite
485	485
486	486	Representation
487	487	)))
488		-|(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)(((
	488	+|(% style="width:392px" %)**Value Domain**|(% style="width:776px" %)(((
489	489	**Representation** (see the Structure Pattern in the Base Package)
490	490	)))
491		-|(% style="width:278px" %)**Enumerated Value Domain /
492		-Code List**|(% style="width:613px" %)**Codelist**
493		-|(% style="width:278px" %)**Code**|(% style="width:613px" %)(((
494		-**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
	491	+|(% style="width:392px" %)**Enumerated Value Domain / Code List**|(% style="width:776px" %)**Codelist**
	492	+|(% style="width:392px" %)**Code**|(% style="width:776px" %)(((
	493	+**Code** (for enumerated
	494	+
	495	+DimensionComponent, Measure, DataAttribute)
495	495	)))
496		-|(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)(((
	497	+|(% style="width:392px" %)**Described Value Domain**|(% style="width:776px" %)(((
497	497	non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
498	498	)))
499		-|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations)
500		-|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
501		-|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
502		-|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
503		-|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX
	500	+|(% style="width:392px" %)**Value**|(% style="width:776px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations)
	501	+|(% style="width:392px" %)**Value Domain Subset / Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
	502	+|(% style="width:392px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
	503	+|(% style="width:392px" %)**Described Value Domain Subset / Described Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
	504	+|(% style="width:392px" %)**Set list**|(% style="width:776px" %)This abstraction does not exist in SDMX
504	504
505	505	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).
506	506
...	...	@@ -526,7 +526,7 @@
526	526
527	527	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:
528	528
529		-[[image:1747388434672-948.png]]
	530	+[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]]
530	530
531	531	(% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
532	532	**Figure 22 – VTL Data Types**
...	...	@@ -535,10 +535,13 @@
535	535
536	536	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):
537	537
538		-[[image:1747388465321-274.png]]
539	539
540	540	**Figure 23 – VTL Basic Scalar Types**
541	541
	542	+(((
	543	+
	544	+)))
	545	+
542	542	=== 12.4.2 VTL basic scalar types and SDMX data types ===
543	543
544	544	The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
...	...	@@ -752,53 +752,53 @@
752	752
753	753	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.
754	754
755		-(% style="width:713.294px" %)
756		-|(% colspan="2" style="width:710px" %)VTL special characters for the formatting masks
757		-|(% colspan="2" style="width:710px" %)
758		-|(% colspan="2" style="width:710px" %)Number
759		-|D|(% style="width:486px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
760		-|E|(% style="width:486px" %)one numeric digit (for the exponent of the scientific notation)
761		-|. (dot)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
762		-|, (comma)|(% style="width:486px" %)possible separator between the integer and the decimal parts.
763		-| |(% style="width:486px" %)
764		-|(% colspan="2" style="width:710px" %)Time and duration
765		-|C|(% style="width:486px" %)century
766		-|Y|(% style="width:486px" %)year
767		-|S|(% style="width:486px" %)semester
768		-|Q|(% style="width:486px" %)quarter
769		-|M|(% style="width:486px" %)month
770		-|W|(% style="width:486px" %)week
771		-|D|(% style="width:486px" %)day
772		-|h|(% style="width:486px" %)hour digit (by default on 24 hours)
773		-|M|(% style="width:486px" %)minute
774		-|S|(% style="width:486px" %)second
775		-|D|(% style="width:486px" %)decimal of second
776		-|P|(% style="width:486px" %)period indicator (representation in one digit for the duration)
777		-|P|(% style="width:486px" %)number of the periods specified in the period indicator
778		-|AM/PM|(% style="width:486px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
779		-|MONTH|(% style="width:486px" %)uppercase textual representation of the month (e.g., JANUARY for January)
780		-|DAY|(% style="width:486px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
781		-|Month|(% style="width:486px" %)lowercase textual representation of the month (e.g., january)
782		-|Day|(% style="width:486px" %)lowercase textual representation of the month (e.g., monday)
783		-|Month|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
784		-|Day|(% style="width:486px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
785		-| |(% style="width:486px" %)
786		-|(% colspan="2" style="width:710px" %)String
787		-|X|(% style="width:486px" %)any string character
788		-|Z|(% style="width:486px" %)any string character from "A" to "z"
789		-|9|(% style="width:486px" %)any string character from "0" to "9"
790		-| |(% style="width:486px" %)
791		-|(% colspan="2" style="width:710px" %)Boolean
792		-|B|(% style="width:486px" %)Boolean using "true" for True and "false" for False
793		-|1|(% style="width:486px" %)Boolean using "1" for True and "0" for False
794		-|0|(% style="width:486px" %)Boolean using "0" for True and "1" for False
795		-| |(% style="width:486px" %)
796		-|(% colspan="2" style="width:710px" %)Other qualifiers
797		-|*|(% style="width:486px" %)an arbitrary number of digits (of the preceding type)
798		-|+|(% style="width:486px" %)at least one digit (of the preceding type)
799		-|( )|(% style="width:486px" %)optional digits (specified within the brackets)
800		-|\|(% style="width:486px" %)prefix for the special characters that must appear in the mask
801		-|N|(% style="width:486px" %)fixed number of digits used in the preceding textual representation of the month or the day
	759	+|(% colspan="2" %)VTL special characters for the formatting masks
	760	+|(% colspan="2" %)
	761	+|(% colspan="2" %)Number
	762	+|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
	763	+|E|one numeric digit (for the exponent of the scientific notation)
	764	+|. (dot)|possible separator between the integer and the decimal parts.
	765	+|, (comma)|possible separator between the integer and the decimal parts.
	766	+| |
	767	+|(% colspan="2" %)Time and duration
	768	+|C|century
	769	+|Y|year
	770	+|S|semester
	771	+|Q|quarter
	772	+|M|month
	773	+|W|week
	774	+|D|day
	775	+|h|hour digit (by default on 24 hours)
	776	+|M|minute
	777	+|S|second
	778	+|D|decimal of second
	779	+|P|period indicator (representation in one digit for the duration)
	780	+|P|number of the periods specified in the period indicator
	781	+|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
	782	+|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
	783	+|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
	784	+|Month|lowercase textual representation of the month (e.g., january)
	785	+|Day|lowercase textual representation of the month (e.g., monday)
	786	+|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
	787	+|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
	788	+| |
	789	+|(% colspan="2" %)String
	790	+|X|any string character
	791	+|Z|any string character from "A" to "z"
	792	+|9|any string character from "0" to "9"
	793	+| |
	794	+|(% colspan="2" %)Boolean
	795	+|B|Boolean using "true" for True and "false" for False
	796	+|1|Boolean using "1" for True and "0" for False
	797	+|0|Boolean using "0" for True and "1" for False
	798	+| |
	799	+|(% colspan="2" %)Other qualifiers
	800	+|*|an arbitrary number of digits (of the preceding type)
	801	+|+|at least one digit (of the preceding type)
	802	+|( )|optional digits (specified within the brackets)
	803	+|\|prefix for the special characters that must appear in the mask
	804	+|N|fixed number of digits used in the preceding textual representation of the month or the day
	805	+| |
802	802
803	803	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}}.
804	804

1747388434672-948.png

Author

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

Size

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

Content

1747388465321-274.png

Author

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

Size

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

Content