Changes for page 12 Validation and Transformation Language (VTL)
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -243,7 +243,7 @@ 243 243 244 244 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; 245 245 246 -* 246 +* 247 247 ** 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). 248 248 ** 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. 249 249 ... ... @@ -580,10 +580,8 @@ 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) 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. 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 - 587 587 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 588 588 589 589 Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts. ... ... @@ -600,8 +600,7 @@ 600 600 601 601 [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_e3df33ae.png||height="543" width="483"]] 602 602 603 -(% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %) 604 -**Figure 22 – VTL Data Types** 601 +==== Figure 22 – VTL Data Types ==== 605 605 606 606 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. 607 607 ... ... @@ -608,12 +608,131 @@ 608 608 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): 609 609 610 610 611 -**Figure 23 – VTL Basic Scalar Types** 612 612 613 613 ((( 614 - 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"]] 615 615 ))) 616 616 731 +==== Figure 23 – VTL Basic Scalar Types ==== 732 + 617 617 === 12.4.2 VTL basic scalar types and SDMX data types === 618 618 619 619 The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations. ... ... @@ -636,159 +636,204 @@ 636 636 637 637 The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types. 638 638 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" %)((( 755 +|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type 756 +|((( 642 642 String 758 + 643 643 (string allowing any character) 644 -)))| (%style="width:312px" %)string645 -|( % style="width:509px" %)(((760 +)))|string 761 +|((( 646 646 Alpha 763 + 647 647 (string which only allows A-z) 648 -)))| (%style="width:312px" %)string649 -|( % style="width:509px" %)(((765 +)))|string 766 +|((( 650 650 AlphaNumeric 768 + 651 651 (string which only allows A-z and 0-9) 652 -)))| (%style="width:312px" %)string653 -|( % style="width:509px" %)(((770 +)))|string 771 +|((( 654 654 Numeric 773 + 655 655 (string which only allows 0-9, but is not numeric so that is can having leading zeros) 656 -)))| (%style="width:312px" %)string657 -|( % style="width:509px" %)(((775 +)))|string 776 +|((( 658 658 BigInteger 778 + 659 659 (corresponds to XML Schema xs:integer datatype; infinite set of integer values) 660 -)))| (% style="width:312px" %)integer661 -|( % style="width:509px" %)(((780 +)))|integer 781 +|((( 662 662 Integer 663 -(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647 (inclusive)) 664 -)))|(% style="width:312px" %)integer 665 -|(% style="width:509px" %)((( 783 + 784 +(corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647 785 + 786 +(inclusive)) 787 +)))|integer 788 +|((( 666 666 Long 667 -(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and +9223372036854775807 (inclusive)) 668 -)))|(% style="width:312px" %)integer 669 -|(% style="width:509px" %)((( 790 + 791 +(corresponds to XML Schema xs:long datatype; between -9223372036854775808 and 792 + 793 ++9223372036854775807 (inclusive)) 794 +)))|integer 795 +|((( 670 670 Short 797 + 671 671 (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive)) 672 -)))| (% style="width:312px" %)integer673 -| (% style="width:509px" %)Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:312px" %)number674 -|( % style="width:509px" %)(((799 +)))|integer 800 +|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number 801 +|((( 675 675 Float 803 + 676 676 (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type) 677 -)))| (% style="width:312px" %)number678 -|( % style="width:509px" %)(((805 +)))|number 806 +|((( 679 679 Double 808 + 680 680 (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type) 681 -)))| (% style="width:312px" %)number682 -|( % style="width:509px" %)(((810 +)))|number 811 +|((( 683 683 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 686 686 687 -(% style="width:822.294px" %) 688 -|(% colspan="2" style="width:507px" %)((( 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" %)((( 689 689 URI 821 + 690 690 (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference) 691 -)))|(% colspan=" 1"style="width:311px"%)string692 -|(% colspan="2" style="width:507px"%)(((823 +)))|(% colspan="2" %)string 824 +| |(% colspan="2" %)((( 693 693 Count 826 + 694 694 (an integer following a sequential pattern, increasing by 1 for each occurrence) 695 -)))|(% colspan=" 1"style="width:311px"%)integer696 -|(% colspan="2" style="width:507px"%)(((828 +)))|(% colspan="2" %)integer 829 +| |(% colspan="2" %)((( 697 697 InclusiveValueRange 831 + 698 698 (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue) 699 -)))|(% colspan=" 1"style="width:311px"%)number700 -|(% colspan="2" style="width:507px"%)(((833 +)))|(% colspan="2" %)number 834 +| |(% colspan="2" %)((( 701 701 ExclusiveValueRange 836 + 702 702 (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue) 703 -)))|(% colspan=" 1"style="width:311px"%)number704 -|(% colspan="2" style="width:507px"%)(((838 +)))|(% colspan="2" %)number 839 +| |(% colspan="2" %)((( 705 705 Incremental 841 + 706 706 (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation) 707 -)))|(% colspan=" 1"style="width:311px"%)number708 -|(% colspan="2" style="width:507px"%)(((843 +)))|(% colspan="2" %)number 844 +| |(% colspan="2" %)((( 709 709 ObservationalTimePeriod 846 + 710 710 (superset of StandardTimePeriod and TimeRange) 711 -)))|(% colspan=" 1"style="width:311px"%)time712 -|(% colspan="2" style="width:507px"%)(((848 +)))|(% colspan="2" %)time 849 +| |(% colspan="2" %)((( 713 713 StandardTimePeriod 714 -(superset of BasicTimePeriod and ReportingTimePeriod) 715 -)))|(% colspan="1" style="width:311px" %)time 716 -|(% colspan="2" style="width:507px" %)((( 851 + 852 +(superset of BasicTimePeriod and 853 + 854 +ReportingTimePeriod) 855 +)))|(% colspan="2" %)time 856 +| |(% colspan="2" %)((( 717 717 BasicTimePeriod 858 + 718 718 (superset of GregorianTimePeriod and DateTime) 719 -)))|(% colspan=" 1"style="width:311px"%)date720 -|(% colspan="2" style="width:507px"%)(((860 +)))|(% colspan="2" %)date 861 +| |(% colspan="2" %)((( 721 721 GregorianTimePeriod 863 + 722 722 (superset of GregorianYear, GregorianYearMonth, and GregorianDay) 723 -)))|(% colspan=" 1"style="width:311px"%)date724 -|(% colspan="2" style="width:507px"%)GregorianYear (YYYY)|(% colspan="1"style="width:311px"%)date725 -|(% colspan="2" style="width:507px"%)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% colspan="1"style="width:311px"%)date726 -|(% colspan="2" style="width:507px"%)GregorianDay (YYYY-MM-DD)|(% colspan="1"style="width:311px"%)date727 -|(% colspan="2" style="width:507px"%)(((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" %)((( 728 728 ReportingTimePeriod 729 -(superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay) 730 -)))|(% colspan="1" style="width:311px" %)time_period 731 -|(% colspan="2" style="width:507px" %)((( 871 + 872 +(superset of RepostingYear, ReportingSemester, 873 + 874 +ReportingTrimester, ReportingQuarter, 875 + 876 +ReportingMonth, ReportingWeek, ReportingDay) 877 +)))|(% colspan="2" %)time_period 878 +| |(% colspan="2" %)((( 732 732 ReportingYear 880 + 733 733 (YYYY-A1 – 1 year period) 734 -)))|(% colspan=" 1"style="width:311px"%)time_period735 -|(% colspan="2" style="width:507px"%)(((882 +)))|(% colspan="2" %)time_period 883 +| |(% colspan="2" %)((( 736 736 ReportingSemester 885 + 737 737 (YYYY-Ss – 6 month period) 738 -)))|(% colspan=" 1"style="width:311px"%)time_period739 -|(% colspan="2" style="width:507px"%)(((887 +)))|(% colspan="2" %)time_period 888 +| |(% colspan="2" %)((( 740 740 ReportingTrimester 890 + 741 741 (YYYY-Tt – 4 month period) 742 -)))|(% colspan=" 1"style="width:311px"%)time_period743 -|(% colspan="2" style="width:507px"%)(((892 +)))|(% colspan="2" %)time_period 893 +| |(% colspan="2" %)((( 744 744 ReportingQuarter 895 + 745 745 (YYYY-Qq – 3 month period) 746 -)))|(% colspan=" 1"style="width:311px"%)time_period747 -|(% colspan="2" style="width:507px"%)(((897 +)))|(% colspan="2" %)time_period 898 +| |(% colspan="2" %)((( 748 748 ReportingMonth 900 + 749 749 (YYYY-Mmm – 1 month period) 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" %)((( 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" %)((( 754 754 ReportingDay 909 + 755 755 (YYYY-Dddd – 1 day period) 756 -)))|(% colspan="2" style="width:312px"%)time_period757 -|(% colspan=" 1"style="width:507px"%)(((911 +)))|(% colspan="2" %)time_period| 912 +|(% colspan="2" %)((( 758 758 DateTime 914 + 759 759 (YYYY-MM-DDThh:mm:ss) 760 -)))|(% colspan="2" style="width:312px"%)date761 -|(% colspan=" 1"style="width:507px"%)(((916 +)))|(% colspan="2" %)date| 917 +|(% colspan="2" %)((( 762 762 TimeRange 919 + 763 763 (YYYY-MM-DD(Thh:mm:ss)?/<duration>) 764 -)))|(% colspan="2" style="width:312px"%)time765 -|(% colspan=" 1"style="width:507px"%)(((921 +)))|(% colspan="2" %)time| 922 +|(% colspan="2" %)((( 766 766 Month 924 + 767 767 (~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States) 768 -)))|(% colspan="2" style="width:312px"%)string769 -|(% colspan=" 1"style="width:507px"%)(((926 +)))|(% colspan="2" %)string| 927 +|(% colspan="2" %)((( 770 770 MonthDay 929 + 771 771 (~-~-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) 772 -)))|(% colspan="2" style="width:312px"%)string773 -|(% colspan=" 1"style="width:507px"%)(((931 +)))|(% colspan="2" %)string| 932 +|(% colspan="2" %)((( 774 774 Day 934 + 775 775 (~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday) 776 -)))|(% colspan="2" style="width:312px"%)string777 -|(% colspan=" 1"style="width:507px"%)(((936 +)))|(% colspan="2" %)string| 937 +|(% colspan="2" %)((( 778 778 Time 939 + 779 779 (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM) 780 -)))|(% colspan="2" style="width:312px"%)string781 -|(% colspan=" 1"style="width:507px"%)(((941 +)))|(% colspan="2" %)string| 942 +|(% colspan="2" %)((( 782 782 Duration 944 + 783 783 (corresponds to XML Schema xs:duration datatype) 784 -)))|(% colspan="2" style="width:312px"%)duration785 -|(% colspan=" 1"style="width:507px"%)XHTML|(% colspan="2"style="width:312px"%)Metadata type – not applicable786 -|(% colspan=" 1"style="width:507px"%)KeyValues|(% colspan="2"style="width:312px"%)Metadata type – not applicable787 -|(% colspan=" 1"style="width:507px"%)IdentifiableReference|(% colspan="2"style="width:312px"%)Metadata type – not applicable788 -|(% colspan=" 1"style="width:507px"%)DataSetReference|(% colspan="2"style="width:312px"%)Metadata type – not applicable946 +)))|(% 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| 789 789 790 -(% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes" %) 791 -**Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types** 952 +==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ==== 792 792 793 793 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). 794 794 ... ... @@ -796,29 +796,37 @@ 796 796 797 797 The following table describes the default conversion from the VTL basic scalar types to the SDMX data types . 798 798 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" %)((( 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|((( 811 811 ReportingTimePeriod 978 + 812 812 (StandardReportingPeriod) 813 -)))|( % style="width:402px" %)(((980 +)))|((( 814 814 YYYY-Pppp 982 + 815 815 (according to SDMX ) 816 816 ))) 817 -| (% style="width:207px" %)Duration|(% style="width:462px" %)Duration|(% style="width:402px" %)(((985 +|Duration|Duration|((( 818 818 Like XML (xs:duration) 987 + 819 819 PnYnMnDTnHnMnS 820 820 ))) 821 -| (% style="width:207px" %)Boolean|(% style="width:462px" %)Boolean|(% style="width:402px" %)Like XML (xs:boolean) with the values "true" or "false"990 +|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false" 822 822 823 823 ==== Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types ==== 824 824 ... ... @@ -874,7 +874,7 @@ 874 874 |N|fixed number of digits used in the preceding textual representation of the month or the day 875 875 | | 876 876 877 -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 wikiinternallink" %)^^42^^>>path:#sdfootnote42sym||name="sdfootnote42anc"]](%%)^^.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 878 879 879 === 12.4.5 Null Values === 880 880