Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.22
edited by Helena
on 2025/05/16 08:59
Change comment: There is no comment for this version
To version 5.28
edited by Helena
on 2025/05/16 09:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -580,8 +580,10 @@
580 580  
581 581  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
582 582  
583 -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.
583 +DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
584 584  
585 +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.
586 +
585 585  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
586 586  
587 587  Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
... ... @@ -598,7 +598,8 @@
598 598  
599 599  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]]
600 600  
601 -==== Figure 22 – VTL Data Types ====
603 +(% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
604 +**Figure 22 – VTL Data Types**
602 602  
603 603  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.
604 604  
... ... @@ -605,131 +605,12 @@
605 605  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):
606 606  
607 607  
611 +**Figure 23 – VTL Basic Scalar Types**
608 608  
609 609  (((
610 -//n//
611 -
612 -//a//
613 -
614 -//e//
615 -
616 -//l//
617 -
618 -//o//
619 -
620 -//o//
621 -
622 -//B//
623 -
624 -//n//
625 -
626 -//o//
627 -
628 -//i//
629 -
630 -//t//
631 -
632 -//a//
633 -
634 -//r//
635 -
636 -//u//
637 -
638 -//D//
639 -
640 -//d//
641 -
642 -//o//
643 -
644 -//i//
645 -
646 -//r//
647 -
648 -//e//
649 -
650 -//p//
651 -
652 -//_//
653 -
654 -//e//
655 -
656 -//m//
657 -
658 -//i//
659 -
660 -//T//
661 -
662 -//e//
663 -
664 -//t//
665 -
666 -//a//
667 -
668 -//D//
669 -
670 -//e//
671 -
672 -//m//
673 -
674 -//i//
675 -
676 -//T//
677 -
678 -//r//
679 -
680 -//e//
681 -
682 -//g//
683 -
684 -//e//
685 -
686 -//t//
687 -
688 -//n//
689 -
690 -//I//
691 -
692 -//r//
693 -
694 -//e//
695 -
696 -//b//
697 -
698 -//m//
699 -
700 -//u//
701 -
702 -//N//
703 -
704 -//g//
705 -
706 -//n//
707 -
708 -//i//
709 -
710 -//r//
711 -
712 -//t//
713 -
714 -//S//
715 -
716 -//r//
717 -
718 -//a//
719 -
720 -//l//
721 -
722 -//a//
723 -
724 -//c//
725 -
726 -//S//
727 -
728 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_82d45833.gif||alt="Shape6" height="231" width="184"]]
614 +
729 729  )))
730 730  
731 -==== Figure 23 – VTL Basic Scalar Types ====
732 -
733 733  === 12.4.2 VTL basic scalar types and SDMX data types ===
734 734  
735 735  The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
... ... @@ -752,204 +752,159 @@
752 752  
753 753  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
754 754  
755 -|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
756 -|(((
639 +(% style="width:823.294px" %)
640 +|(% style="width:509px" %)**SDMX data type (BasicComponentDataType)**|(% style="width:312px" %)**Default VTL basic scalar type**
641 +|(% style="width:509px" %)(((
757 757  String
758 -
759 759  (string allowing any character)
760 -)))|string
761 -|(((
644 +)))|(% style="width:312px" %)string
645 +|(% style="width:509px" %)(((
762 762  Alpha
763 -
764 764  (string which only allows A-z)
765 -)))|string
766 -|(((
648 +)))|(% style="width:312px" %)string
649 +|(% style="width:509px" %)(((
767 767  AlphaNumeric
768 -
769 769  (string which only allows A-z and 0-9)
770 -)))|string
771 -|(((
652 +)))|(% style="width:312px" %)string
653 +|(% style="width:509px" %)(((
772 772  Numeric
773 -
774 774  (string which only allows 0-9, but is not numeric so that is can having leading zeros)
775 -)))|string
776 -|(((
656 +)))|(% style="width:312px" %)string
657 +|(% style="width:509px" %)(((
777 777  BigInteger
778 -
779 779  (corresponds to XML Schema xs:integer datatype; infinite set of integer values)
780 -)))|integer
781 -|(((
660 +)))|(% style="width:312px" %)integer
661 +|(% style="width:509px" %)(((
782 782  Integer
783 -
784 -(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
785 -
786 -(inclusive))
787 -)))|integer
788 -|(((
663 +(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647 (inclusive))
664 +)))|(% style="width:312px" %)integer
665 +|(% style="width:509px" %)(((
789 789  Long
790 -
791 -(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
792 -
793 -+9223372036854775807 (inclusive))
794 -)))|integer
795 -|(((
667 +(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and +9223372036854775807 (inclusive))
668 +)))|(% style="width:312px" %)integer
669 +|(% style="width:509px" %)(((
796 796  Short
797 -
798 798  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
799 -)))|integer
800 -|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
801 -|(((
672 +)))|(% style="width:312px" %)integer
673 +|(% style="width:509px" %)Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:312px" %)number
674 +|(% style="width:509px" %)(((
802 802  Float
803 -
804 804  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
805 -)))|number
806 -|(((
677 +)))|(% style="width:312px" %)number
678 +|(% style="width:509px" %)(((
807 807  Double
808 -
809 809  (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
810 -)))|number
811 -|(((
681 +)))|(% style="width:312px" %)number
682 +|(% style="width:509px" %)(((
812 812  Boolean
684 +(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of binary-valued logic: {true, false})
685 +)))|(% style="width:312px" %)boolean
813 813  
814 -(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
815 -
816 -binary-valued logic: {true, false})
817 -)))|boolean
818 -
819 -| |(% colspan="2" %)(((
687 +(% style="width:822.294px" %)
688 +|(% colspan="2" style="width:507px" %)(((
820 820  URI
821 -
822 822  (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
823 -)))|(% colspan="2" %)string
824 -| |(% colspan="2" %)(((
691 +)))|(% colspan="1" style="width:311px" %)string
692 +|(% colspan="2" style="width:507px" %)(((
825 825  Count
826 -
827 827  (an integer following a sequential pattern, increasing by 1 for each occurrence)
828 -)))|(% colspan="2" %)integer
829 -| |(% colspan="2" %)(((
695 +)))|(% colspan="1" style="width:311px" %)integer
696 +|(% colspan="2" style="width:507px" %)(((
830 830  InclusiveValueRange
831 -
832 832  (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
833 -)))|(% colspan="2" %)number
834 -| |(% colspan="2" %)(((
699 +)))|(% colspan="1" style="width:311px" %)number
700 +|(% colspan="2" style="width:507px" %)(((
835 835  ExclusiveValueRange
836 -
837 837  (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
838 -)))|(% colspan="2" %)number
839 -| |(% colspan="2" %)(((
703 +)))|(% colspan="1" style="width:311px" %)number
704 +|(% colspan="2" style="width:507px" %)(((
840 840  Incremental
841 -
842 842  (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
843 -)))|(% colspan="2" %)number
844 -| |(% colspan="2" %)(((
707 +)))|(% colspan="1" style="width:311px" %)number
708 +|(% colspan="2" style="width:507px" %)(((
845 845  ObservationalTimePeriod
846 -
847 847  (superset of StandardTimePeriod and TimeRange)
848 -)))|(% colspan="2" %)time
849 -| |(% colspan="2" %)(((
711 +)))|(% colspan="1" style="width:311px" %)time
712 +|(% colspan="2" style="width:507px" %)(((
850 850  StandardTimePeriod
851 -
852 -(superset of BasicTimePeriod and
853 -
854 -ReportingTimePeriod)
855 -)))|(% colspan="2" %)time
856 -| |(% colspan="2" %)(((
714 +(superset of BasicTimePeriod and ReportingTimePeriod)
715 +)))|(% colspan="1" style="width:311px" %)time
716 +|(% colspan="2" style="width:507px" %)(((
857 857  BasicTimePeriod
858 -
859 859  (superset of GregorianTimePeriod and DateTime)
860 -)))|(% colspan="2" %)date
861 -| |(% colspan="2" %)(((
719 +)))|(% colspan="1" style="width:311px" %)date
720 +|(% colspan="2" style="width:507px" %)(((
862 862  GregorianTimePeriod
863 -
864 864  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
865 -)))|(% colspan="2" %)date
866 -| |(% colspan="2" %)GregorianYear (YYYY)|(% colspan="2" %)date
867 -| |(% colspan="2" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% colspan="2" %)date
868 -| |(% colspan="2" %)GregorianDay (YYYY-MM-DD)|(% colspan="2" %)date
869 -| |(% colspan="2" %)(((
723 +)))|(% colspan="1" style="width:311px" %)date
724 +|(% colspan="2" style="width:507px" %)GregorianYear (YYYY)|(% colspan="1" style="width:311px" %)date
725 +|(% colspan="2" style="width:507px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% colspan="1" style="width:311px" %)date
726 +|(% colspan="2" style="width:507px" %)GregorianDay (YYYY-MM-DD)|(% colspan="1" style="width:311px" %)date
727 +|(% colspan="2" style="width:507px" %)(((
870 870  ReportingTimePeriod
871 -
872 -(superset of RepostingYear, ReportingSemester,
873 -
874 -ReportingTrimester, ReportingQuarter,
875 -
876 -ReportingMonth, ReportingWeek, ReportingDay)
877 -)))|(% colspan="2" %)time_period
878 -| |(% colspan="2" %)(((
729 +(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
730 +)))|(% colspan="1" style="width:311px" %)time_period
731 +|(% colspan="2" style="width:507px" %)(((
879 879  ReportingYear
880 -
881 881  (YYYY-A1 – 1 year period)
882 -)))|(% colspan="2" %)time_period
883 -| |(% colspan="2" %)(((
734 +)))|(% colspan="1" style="width:311px" %)time_period
735 +|(% colspan="2" style="width:507px" %)(((
884 884  ReportingSemester
885 -
886 886  (YYYY-Ss – 6 month period)
887 -)))|(% colspan="2" %)time_period
888 -| |(% colspan="2" %)(((
738 +)))|(% colspan="1" style="width:311px" %)time_period
739 +|(% colspan="2" style="width:507px" %)(((
889 889  ReportingTrimester
890 -
891 891  (YYYY-Tt – 4 month period)
892 -)))|(% colspan="2" %)time_period
893 -| |(% colspan="2" %)(((
742 +)))|(% colspan="1" style="width:311px" %)time_period
743 +|(% colspan="2" style="width:507px" %)(((
894 894  ReportingQuarter
895 -
896 896  (YYYY-Qq – 3 month period)
897 -)))|(% colspan="2" %)time_period
898 -| |(% colspan="2" %)(((
746 +)))|(% colspan="1" style="width:311px" %)time_period
747 +|(% colspan="2" style="width:507px" %)(((
899 899  ReportingMonth
900 -
901 901  (YYYY-Mmm – 1 month period)
902 -)))|(% colspan="2" %)time_period
903 -| |(% colspan="2" %)ReportingWeek|(% colspan="2" %)time_period
904 -| |(% colspan="2" %) |(% colspan="2" %)
905 -| |(% colspan="2" %) |(% colspan="2" %)
906 -|(% colspan="2" %)(YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% colspan="2" %) |
907 -|(% colspan="2" %)(((
750 +)))|(% colspan="1" style="width:311px" %)time_period
751 +|(% colspan="2" style="width:507px" %)ReportingWeek|(% colspan="1" style="width:311px" %)time_period
752 +|(% colspan="1" style="width:507px" %)(YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% colspan="2" style="width:312px" %)
753 +|(% colspan="1" style="width:507px" %)(((
908 908  ReportingDay
909 -
910 910  (YYYY-Dddd – 1 day period)
911 -)))|(% colspan="2" %)time_period|
912 -|(% colspan="2" %)(((
756 +)))|(% colspan="2" style="width:312px" %)time_period
757 +|(% colspan="1" style="width:507px" %)(((
913 913  DateTime
914 -
915 915  (YYYY-MM-DDThh:mm:ss)
916 -)))|(% colspan="2" %)date|
917 -|(% colspan="2" %)(((
760 +)))|(% colspan="2" style="width:312px" %)date
761 +|(% colspan="1" style="width:507px" %)(((
918 918  TimeRange
919 -
920 920  (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
921 -)))|(% colspan="2" %)time|
922 -|(% colspan="2" %)(((
764 +)))|(% colspan="2" style="width:312px" %)time
765 +|(% colspan="1" style="width:507px" %)(((
923 923  Month
924 -
925 925  (~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
926 -)))|(% colspan="2" %)string|
927 -|(% colspan="2" %)(((
768 +)))|(% colspan="2" style="width:312px" %)string
769 +|(% colspan="1" style="width:507px" %)(((
928 928  MonthDay
929 -
930 930  (~-~-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)
931 -)))|(% colspan="2" %)string|
932 -|(% colspan="2" %)(((
772 +)))|(% colspan="2" style="width:312px" %)string
773 +|(% colspan="1" style="width:507px" %)(((
933 933  Day
934 -
935 935  (~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
936 -)))|(% colspan="2" %)string|
937 -|(% colspan="2" %)(((
776 +)))|(% colspan="2" style="width:312px" %)string
777 +|(% colspan="1" style="width:507px" %)(((
938 938  Time
939 -
940 940  (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
941 -)))|(% colspan="2" %)string|
942 -|(% colspan="2" %)(((
780 +)))|(% colspan="2" style="width:312px" %)string
781 +|(% colspan="1" style="width:507px" %)(((
943 943  Duration
944 -
945 945  (corresponds to XML Schema xs:duration datatype)
946 -)))|(% colspan="2" %)duration|
947 -|(% colspan="2" %)XHTML|(% colspan="2" %)Metadata type – not applicable|
948 -|(% colspan="2" %)KeyValues|(% colspan="2" %)Metadata type – not applicable|
949 -|(% colspan="2" %)IdentifiableReference|(% colspan="2" %)Metadata type – not applicable|
950 -|(% colspan="2" %)DataSetReference|(% colspan="2" %)Metadata type – not applicable|
784 +)))|(% colspan="2" style="width:312px" %)duration
785 +|(% colspan="1" style="width:507px" %)XHTML|(% colspan="2" style="width:312px" %)Metadata type – not applicable
786 +|(% colspan="1" style="width:507px" %)KeyValues|(% colspan="2" style="width:312px" %)Metadata type – not applicable
787 +|(% colspan="1" style="width:507px" %)IdentifiableReference|(% colspan="2" style="width:312px" %)Metadata type – not applicable
788 +|(% colspan="1" style="width:507px" %)DataSetReference|(% colspan="2" style="width:312px" %)Metadata type – not applicable
951 951  
952 -==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
790 +(% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes" %)
791 +**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
953 953  
954 954  When VTL takes in input SDMX artefacts, it is assumed that a type conversion according to the table above always happens. In case a different VTL basic scalar type is desired, it can be achieved in the VTL program taking in input the default VTL basic scalar type above and applying to it the VTL type conversion features (see the implicit and explicit type conversion and the "cast" operator in the VTL Reference Manual).
955 955  
... ... @@ -957,39 +957,32 @@
957 957  
958 958  The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
959 959  
960 -|(((
961 -VTL basic
962 -
963 -scalar type
964 -)))|(((
965 -Default SDMX data type
966 -
967 -(BasicComponentDataType
968 -
969 -)
970 -)))|Default output format
971 -|String|String|Like XML (xs:string)
972 -|Number|Float|Like XML (xs:float)
973 -|Integer|Integer|Like XML (xs:int)
974 -|Date|DateTime|YYYY-MM-DDT00:00:00Z
975 -|Time|StandardTimePeriod|<date>/<date> (as defined above)
976 -|time_period|(((
799 +(% style="width:1073.29px" %)
800 +|(% style="width:207px" %)(((
801 +**VTL basic scalar type**
802 +)))|(% style="width:462px" %)(((
803 +**Default SDMX data type (BasicComponentDataType)**
804 +)))|(% style="width:402px" %)**Default output format**
805 +|(% style="width:207px" %)String|(% style="width:462px" %)String|(% style="width:402px" %)Like XML (xs:string)
806 +|(% style="width:207px" %)Number|(% style="width:462px" %)Float|(% style="width:402px" %)Like XML (xs:float)
807 +|(% style="width:207px" %)Integer|(% style="width:462px" %)Integer|(% style="width:402px" %)Like XML (xs:int)
808 +|(% style="width:207px" %)Date|(% style="width:462px" %)DateTime|(% style="width:402px" %)YYYY-MM-DDT00:00:00Z
809 +|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)<date>/<date> (as defined above)
810 +|(% style="width:207px" %)time_period|(% style="width:462px" %)(((
977 977  ReportingTimePeriod
978 -
979 979  (StandardReportingPeriod)
980 -)))|(((
813 +)))|(% style="width:402px" %)(((
981 981  YYYY-Pppp
982 -
983 983  (according to SDMX )
984 984  )))
985 -|Duration|Duration|(((
817 +|(% style="width:207px" %)Duration|(% style="width:462px" %)Duration|(% style="width:402px" %)(((
986 986  Like XML (xs:duration)
987 -
988 988  PnYnMnDTnHnMnS
989 989  )))
990 -|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
821 +|(% style="width:207px" %)Boolean|(% style="width:462px" %)Boolean|(% style="width:402px" %)Like XML (xs:boolean) with the values "true" or "false"
991 991  
992 -==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ====
823 +(% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes-1" %)
824 +**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
993 993  
994 994  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).
995 995  
... ... @@ -1043,7 +1043,7 @@
1043 1043  |N|fixed number of digits used in the preceding textual representation of the month or the day
1044 1044  | |
1045 1045  
1046 -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^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^42^^>>path:#sdfootnote42sym||name="sdfootnote42anc"]](%%)^^.
878 +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}}.
1047 1047  
1048 1048  === 12.4.5 Null Values ===
1049 1049  
... ... @@ -1061,10 +1061,8 @@
1061 1061  
1062 1062  A different format can be specified in the attribute "vtlLiteralFormat" of the CustomType artefact (see also the section Transformations and Expressions of the SDMX information model).
1063 1063  
1064 -Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain VTL basic scalar type, if a value is found for the vtlLiteralFormat attribute of the CustomType of such VTL basic scalar type. The overriding assumption is applied for all the literals of a related VTL
896 +Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain VTL basic scalar type, if a value is found for the vtlLiteralFormat attribute of the CustomType of such VTL basic scalar type. The overriding assumption is applied for all the literals of a related VTL TransformationScheme.
1065 1065  
1066 -TransformationScheme.
1067 -
1068 1068  In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
1069 1069  
1070 1070  {{putFootnotes/}}