Skip to Content
Last modified by Helena K. on 2026/06/10 10:09
From version 1.25
edited by Helena K.
on 2025/06/16 13:38
Change comment: There is no comment for this version
To version 10.1
edited by Helena K.
on 2026/06/09 20:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Code|Code list|Component|Concept scheme|Currency|Data set|Data structure definition|Dataflow|Dimension|Facet|Maintainable artefact|Measure|Nameable artefact|Representation|SDMX Information Model|Statistical data and metadata exchange|Structural metadata|Validation and transformation language
Content
... ... @@ -18,7 +18,7 @@
18 18  
19 19  This section does not explain the VTL language or any of the content published in the VTL guides. Rather, this is a description of how the VTL can be used in the SDMX context and applied to SDMX artefacts.
20 20  
21 -== 12.2 References to SDMX artefacts from VTL statements ==
21 +== 12.2 References to SDMX artefacts from VTL statements ==
22 22  
23 23  === 12.2.1 Introduction ===
24 24  
... ... @@ -78,8 +78,12 @@
78 78  * if the artefact is a Dimension, TimeDimension, Measure or DataAttribute (the object-id is the name of one of the artefacts above, which are data structure components)
79 79  * if the artefact is a Concept (the object-id is the name of the Concept)
80 80  
81 -For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
82 82  
82 +
83 +For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as
84 +
85 +{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
86 +
83 83  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84 84  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85 85  > 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
... ... @@ -106,6 +106,8 @@
106 106  * As said, the container-object-id does not apply to the classes that can be referenced in VTL Transformations, therefore is not present in their URN
107 107  * The object-id does not exist for the artefacts belonging to the Dataflow, and Codelist classes, while it exists and cannot be omitted for the artefacts belonging to the classes Dimension, TimeDimension, Measure, DataAttribute and Concept, as for them the object-id is the main identifier of the artefact
108 108  
113 +
114 +
109 109  The simplified object identifier is obtained by omitting all the first part of the URN, including the special characters, till the first part not omitted.
110 110  
111 111  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
... ... @@ -116,7 +116,7 @@
116 116  
117 117  by omitting all the non-essential parts would become simply:
118 118  
119 -> DFR  : =  DF1 + DF2
125 +> 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  
... ... @@ -162,14 +162,16 @@
162 162  
163 163  === 12.2.5 References to SDMX artefacts from VTL Rulesets ===
164 164  
165 -The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: (i) when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
171 +The VTL Rulesets allow defining sets of reusable Rules that can be applied by some VTL operators, like the ones for validation and hierarchical roll-up. A "Rule" consists in a relationship between Values belonging to some Value Domains or taken by some Variables, for example: when the Country is USA then the Currency is USD; (ii) the Benelux is composed by Belgium, Luxembourg, Netherlands.
166 166  
167 167  The VTL Rulesets have a signature, in which the Value Domains or the Variables on which the Ruleset is defined are declared, and a body, which contains the Rules.
168 168  
169 169  In the signature, given the mapping between VTL and SDMX better described in the following paragraphs, a reference to a VTL Value Domain becomes a reference to a SDMX Codelist, while a reference to a VTL Represented Variable becomes a reference to a SDMX Concept, assuming for it a definite representation{{footnote}}Rulesets of this kind cannot be reused when the referenced Concept has a different representation.{{/footnote}}.
170 170  
171 -In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets). The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
177 +In general, for referencing SDMX Codelists and Concepts, the conventions described in the previous paragraphs apply. In the Ruleset syntax, the elements that reference SDMX artefacts are called "valueDomain" and "variable" for the Datapoint Rulesets and "ruleValueDomain", "ruleVariable", "condValueDomain" "condVariable" for the Hierarchical Rulesets).
172 172  
179 +The syntax of the Ruleset signature allows also to define aliases of the elements above, these aliases are valid only within the specific Ruleset definition statement and cannot be mapped to SDMX.{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}}
180 +
173 173  In the body of the Rulesets, the Codes and in general all the Values can be written without any other specification, because the artefact, which the Values are referred (Codelist, Concept) to can be deduced from the Ruleset signature.
174 174  
175 175  == 12.3 Mapping between SDMX and VTL artefacts ==
... ... @@ -452,31 +452,26 @@
452 452  
453 453  > ‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
454 454  > … … …
455 -> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
463 +> ‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
456 456  > ‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
457 457  > … … …
458 458  
459 459  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:
460 460  
461 -VTL dataset   INDICATOR value COUNTRY value
462 -
463 -> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
469 +> VTL dataset INDICATOR value COUNTRY value
470 +>
471 +> ‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
464 464  > ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
465 -> ‘DF2(1.0.0)/POPGROWTH.USA’  POPGROWTH USA
466 -> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
473 +>
474 +> ‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
475 +> ‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
467 467  > … … …
468 468  
469 469  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:
470 470  
471 -> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
472 -> DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
473 -> DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’  [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
474 -> DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
475 -> DF2(1.0) <- UNION  (DF2bis_GDPPERCAPITA_USA’,
476 -> DF2bis_GDPPERCAPITA_CANADA’,
480 +> DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”]; DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”];… … … DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”]; DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”];… … … DF2(1.0) <- UNION (DF2bis_GDPPERCAPITA_USA’, DF2bis_GDPPERCAPITA_CANADA’,
477 477  > … ,
478 -> DF2bis_POPGROWTH_USA’,
479 -> DF2bis_POPGROWTH_CANADA’
482 +> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
480 480  > …);
481 481  
482 482  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.
... ... @@ -534,7 +534,6 @@
534 534  
535 535  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:
536 536  
537 -
538 538  [[image:1750070288958-132.png]]
539 539  
540 540  **Figure 22 – VTL Data Types**
... ... @@ -543,6 +543,8 @@
543 543  
544 544  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):
545 545  
548 +[[image:1750070310572-584.png]]
549 +
546 546  **Figure 23 – VTL Basic Scalar Types**
547 547  
548 548  === 12.4.2 VTL basic scalar types and SDMX data types ===
... ... @@ -567,158 +567,159 @@
567 567  
568 568  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
569 569  
570 -|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
571 -|(((
574 +(% style="width:583.294px" %)
575 +|(% style="width:360px" %)SDMX data type
576 +(BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
577 +|(% style="width:360px" %)(((
572 572  String
573 573  (string allowing any character)
574 -)))|string
575 -|(((
576 -Alpha 
577 -
580 +)))|(% style="width:221px" %)string
581 +|(% style="width:360px" %)(((
582 +Alpha
578 578  (string which only allows A-z)
579 -)))|string
580 -|(((
584 +)))|(% style="width:221px" %)string
585 +|(% style="width:360px" %)(((
581 581  AlphaNumeric
582 582  (string which only allows A-z and 0-9)
583 -)))|string
584 -|(((
588 +)))|(% style="width:221px" %)string
589 +|(% style="width:360px" %)(((
585 585  Numeric
586 -
587 587  (string which only allows 0-9, but is not numeric so that is can having leading zeros)
588 -)))|string
589 -|(((
592 +)))|(% style="width:221px" %)string
593 +|(% style="width:360px" %)(((
590 590  BigInteger
591 591  (corresponds to XML Schema xs:integer datatype; infinite set of integer values)
592 -)))|integer
593 -|(((
596 +)))|(% style="width:221px" %)integer
597 +|(% style="width:360px" %)(((
594 594  Integer
595 595  (corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
596 596  (inclusive))
597 -)))|integer
598 -|(((
601 +)))|(% style="width:221px" %)integer
602 +|(% style="width:360px" %)(((
599 599  Long
600 600  (corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
601 601  +9223372036854775807 (inclusive))
602 -)))|integer
603 -|(((
606 +)))|(% style="width:221px" %)integer
607 +|(% style="width:360px" %)(((
604 604  Short
605 605  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
606 -)))|integer
607 -|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
608 -|(((
610 +)))|(% style="width:221px" %)integer
611 +|(% style="width:360px" %)Decimal
612 +(corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|(% style="width:221px" %)number
613 +|(% style="width:360px" %)(((
609 609  Float
610 610  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
611 -)))|number
612 -|(((
616 +)))|(% style="width:221px" %)number
617 +|(% style="width:360px" %)(((
613 613  Double
614 614  (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
615 -)))|number
616 -|(((
620 +)))|(% style="width:221px" %)number
621 +|(% style="width:360px" %)(((
617 617  Boolean
618 618  (corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
619 619  binary-valued logic: {true, false})
620 -)))|boolean
621 -|(((
625 +)))|(% style="width:221px" %)boolean
626 +|(% style="width:360px" %)(((
622 622  URI
623 623  (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
624 -)))|string
625 -|(((
629 +)))|(% style="width:221px" %)string
630 +|(% style="width:360px" %)(((
626 626  Count
627 627  (an integer following a sequential pattern, increasing by 1 for each occurrence)
628 -)))|integer
629 -|(((
633 +)))|(% style="width:221px" %)integer
634 +|(% style="width:360px" %)(((
630 630  InclusiveValueRange
631 631  (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
632 -)))|number
633 -|(((
637 +)))|(% style="width:221px" %)number
638 +|(% style="width:360px" %)(((
634 634  ExclusiveValueRange
635 635  (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
636 -)))|number
637 -|(((
641 +)))|(% style="width:221px" %)number
642 +|(% style="width:360px" %)(((
638 638  Incremental
639 639  (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
640 -)))|number
641 -|(((
645 +)))|(% style="width:221px" %)number
646 +|(% style="width:360px" %)(((
642 642  ObservationalTimePeriod
643 643  (superset of StandardTimePeriod and TimeRange)
644 -)))|time
645 -|(((
649 +)))|(% style="width:221px" %)time
650 +|(% style="width:360px" %)(((
646 646  StandardTimePeriod
647 647  (superset of BasicTimePeriod and ReportingTimePeriod)
648 -)))|time
649 -|(((
653 +)))|(% style="width:221px" %)time
654 +|(% style="width:360px" %)(((
650 650  BasicTimePeriod
651 651  (superset of GregorianTimePeriod and DateTime)
652 -)))|date
653 -|(((
657 +)))|(% style="width:221px" %)date
658 +|(% style="width:360px" %)(((
654 654  GregorianTimePeriod
655 655  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
656 -)))|date
657 -|GregorianYear (YYYY)|date
658 -|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
659 -|GregorianDay (YYYY-MM-DD)|date
660 -|(((
661 +)))|(% style="width:221px" %)date
662 +|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
663 +|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
664 +|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
665 +|(% style="width:360px" %)(((
661 661  ReportingTimePeriod
662 662  (superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
663 -)))|time_period
664 -|(((
668 +)))|(% style="width:221px" %)time_period
669 +|(% style="width:360px" %)(((
665 665  ReportingYear
666 666  (YYYY-A1 – 1 year period)
667 -)))|time_period
668 -|(((
672 +)))|(% style="width:221px" %)time_period
673 +|(% style="width:360px" %)(((
669 669  ReportingSemester
670 670  (YYYY-Ss – 6 month period)
671 -)))|time_period
672 -|(((
676 +)))|(% style="width:221px" %)time_period
677 +|(% style="width:360px" %)(((
673 673  ReportingTrimester
674 674  (YYYY-Tt – 4 month period)
675 -)))|time_period
676 -|(((
680 +)))|(% style="width:221px" %)time_period
681 +|(% style="width:360px" %)(((
677 677  ReportingQuarter
678 678  (YYYY-Qq – 3 month period)
679 -)))|time_period
680 -|(((
684 +)))|(% style="width:221px" %)time_period
685 +|(% style="width:360px" %)(((
681 681  ReportingMonth
682 682  (YYYY-Mmm – 1 month period)
683 -)))|time_period
684 -|ReportingWeek|time_period
685 -| (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|
686 -|(((
688 +)))|(% style="width:221px" %)time_period
689 +|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
690 +|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
691 +|(% style="width:360px" %)(((
687 687  ReportingDay
688 688  (YYYY-Dddd – 1 day period)
689 -)))|time_period
690 -|(((
694 +)))|(% style="width:221px" %)time_period
695 +|(% style="width:360px" %)(((
691 691  DateTime
692 692  (YYYY-MM-DDThh:mm:ss)
693 -)))|date
694 -|(((
698 +)))|(% style="width:221px" %)date
699 +|(% style="width:360px" %)(((
695 695  TimeRange
696 -(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
697 -)))|time
698 -|(((
701 +(YYYY-MM-DD(Thh:mm:ss)?/)
702 +)))|(% style="width:221px" %)time
703 +|(% style="width:360px" %)(((
699 699  Month
700 -(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
701 -)))|string
702 -|(((
705 +(MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
706 +)))|(% style="width:221px" %)string
707 +|(% style="width:360px" %)(((
703 703  MonthDay
704 -(~-~-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)
705 -)))|string
706 -|(((
709 +(MM-DD; specifies a day within a month independent of a year; e.g. Christmas is December 25^^th^^; used to specify reporting year start day)
710 +)))|(% style="width:221px" %)string
711 +|(% style="width:360px" %)(((
707 707  Day
708 -(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
709 -)))|string
710 -|(((
713 +(-DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
714 +)))|(% style="width:221px" %)string
715 +|(% style="width:360px" %)(((
711 711  Time
712 712  (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
713 -)))|string
714 -|(((
718 +)))|(% style="width:221px" %)string
719 +|(% style="width:360px" %)(((
715 715  Duration
716 716  (corresponds to XML Schema xs:duration datatype)
717 -)))|duration
718 -|XHTML|Metadata type – not applicable
719 -|KeyValues|Metadata type – not applicable
720 -|IdentifiableReference|Metadata type – not applicable
721 -|DataSetReference|Metadata type – not applicable
722 +)))|(% style="width:221px" %)duration
723 +|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
724 +|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
725 +|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
726 +|(% style="width:360px" %)DataSetReference|(% style="width:221px" %)Metadata type – not applicable
722 722  
723 723  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
724 724  
... ... @@ -728,84 +728,82 @@
728 728  
729 729  The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
730 730  
731 -|(((
732 -VTL basic
733 -scalar type
734 -)))|(((
736 +(% style="width:748.294px" %)
737 +|(% style="width:164px" %)(((
738 +VTL basic scalar type
739 +)))|(% style="width:304px" %)(((
735 735  Default SDMX data type
736 -(BasicComponentDataType
737 -)
738 -)))|Default output format
739 -|String|String|Like XML (xs:string)
740 -|Number|Float|Like XML (xs:float)
741 -|Integer|Integer|Like XML (xs:int)
742 -|Date|DateTime|YYYY-MM-DDT00:00:00Z
743 -|Time|StandardTimePeriod|<date>/<date> (as defined above)
744 -|time_period|(((
741 +(BasicComponentDataType)
742 +)))|(% style="width:277px" %)Default output format
743 +|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
744 +|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
745 +|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
746 +|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
747 +|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
748 +|(% style="width:164px" %)time_period|(% style="width:304px" %)(((
745 745  ReportingTimePeriod
746 746  (StandardReportingPeriod)
747 -)))|(((
751 +)))|(% style="width:277px" %)(((
748 748   YYYY-Pppp
749 749  (according to SDMX )
750 750  )))
751 -|Duration|Duration|Like XML (xs:duration) PnYnMnDTnHnMnS
752 -|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
755 +|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
756 +|(% style="width:164px" %)Boolean|(% style="width:304px" %)Boolean|(% style="width:277px" %)Like XML (xs:boolean) with the values "true" or "false"
753 753  
754 754  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
755 755  
756 -In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section
760 +In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section Transformations and Expressions of the SDMX information model).
757 757  
758 -Transformations and Expressions of the SDMX information model).
759 -
760 760  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.
761 761  
762 -|(% colspan="2" %)VTL special characters for the formatting masks
763 -|(% colspan="2" %)
764 -|(% colspan="2" %)Number
765 -|D|one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
766 -|E|one numeric digit (for the exponent of the scientific notation)
767 -|. (dot)|possible separator between the integer and the decimal parts.
768 -|, (comma)|possible separator between the integer and the decimal parts.
769 -| |
770 -|(% colspan="2" %)Time and duration
771 -|C|century
772 -|Y|year
773 -|S|semester
774 -|Q|quarter
775 -|M|month
776 -|W|week
777 -|D|day
778 -|h|hour digit (by default on 24 hours)
779 -|M|minute
780 -|S|second
781 -|D|decimal of second
782 -|P|period indicator (representation in one digit for the duration)
783 -|P|number of the periods specified in the period indicator
784 -|AM/PM|indicator of AM / PM (e.g. am/pm for "am" or "pm")
785 -|MONTH|uppercase textual representation of the month (e.g., JANUARY for January)
786 -|DAY|uppercase textual representation of the day (e.g., MONDAY for Monday)
787 -|Month|lowercase textual representation of the month (e.g., january)
788 -|Day|lowercase textual representation of the month (e.g., monday)
789 -|Month|First character uppercase, then lowercase textual representation of the month (e.g., January)
790 -|Day|First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
791 -| |
792 -|(% colspan="2" %)String
793 -|X|any string character
794 -|Z|any string character from "A" to "z"
795 -|9|any string character from "0" to "9"
796 -| |
797 -|(% colspan="2" %)Boolean
798 -|B|Boolean using "true" for True and "false" for False
799 -|1|Boolean using "1" for True and "0" for False
800 -|0|Boolean using "0" for True and "1" for False
801 -| |
802 -|(% colspan="2" %)Other qualifiers
803 -|*|an arbitrary number of digits (of the preceding type)
804 -|+|at least one digit (of the preceding type)
805 -|( )|optional digits (specified within the brackets)
806 -|\|prefix for the special characters that must appear in the mask
807 -|N|fixed number of digits used in the preceding textual representation of the month or the day
808 -| |
764 +(% style="width:717.294px" %)
765 +|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
766 +|(% colspan="2" style="width:714px" %)
767 +|(% colspan="2" style="width:714px" %)Number
768 +|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
769 +|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
770 +|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
771 +|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
772 +|(% style="width:122px" %) |(% style="width:591px" %)
773 +|(% colspan="2" style="width:714px" %)Time and duration
774 +|(% style="width:122px" %)C|(% style="width:591px" %)century
775 +|(% style="width:122px" %)Y|(% style="width:591px" %)year
776 +|(% style="width:122px" %)S|(% style="width:591px" %)semester
777 +|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
778 +|(% style="width:122px" %)M|(% style="width:591px" %)month
779 +|(% style="width:122px" %)W|(% style="width:591px" %)week
780 +|(% style="width:122px" %)D|(% style="width:591px" %)day
781 +|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
782 +|(% style="width:122px" %)M|(% style="width:591px" %)minute
783 +|(% style="width:122px" %)S|(% style="width:591px" %)second
784 +|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
785 +|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
786 +|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
787 +|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
788 +|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
789 +|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
790 +|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
791 +|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
792 +|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
793 +|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
794 +|(% style="width:122px" %) |(% style="width:591px" %)
795 +|(% colspan="2" style="width:714px" %)String
796 +|(% style="width:122px" %)X|(% style="width:591px" %)any string character
797 +|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
798 +|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
799 +|(% style="width:122px" %) |(% style="width:591px" %)
800 +|(% colspan="2" style="width:714px" %)Boolean
801 +|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
802 +|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
803 +|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
804 +|(% style="width:122px" %) |(% style="width:591px" %)
805 +|(% colspan="2" style="width:714px" %)Other qualifiers
806 +|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
807 +|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
808 +|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
809 +|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
810 +|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
811 +|(% style="width:122px" %) |(% style="width:591px" %)
809 809  
810 810  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}}.
811 811  
1750067055028-964.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -5.5 KB
Content
1750070310572-584.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,0 +1,1 @@
1 +18.9 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,0 +1,1 @@
1 +12
© Semantic R&D Group, 2026