Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/06/16 13:45
Change comment: There is no comment for this version
To version 1.24
edited by Helena
on 2025/06/16 13:29
Change comment: There is no comment for this version

Summary

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  
... ... @@ -410,14 +410,16 @@
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’ :=
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 -> … … …
413 +‘DF1(1.0.0)/POPULATION.USA’ :=
420 420  
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 +
421 421  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}}
422 422  
423 423  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.
... ... @@ -426,9 +426,10 @@
426 426  
427 427  This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
428 428  
429 -> ‘DF1(1.0.0)/POPULATION.’ :=
430 -> DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
431 +‘DF1(1.0.0)/POPULATION.’ :=
431 431  
433 +DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
434 +
432 432  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
433 433  
434 434  Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different Dimensions in different invocations.
... ... @@ -446,33 +446,41 @@
446 446  
447 447  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}}
448 448  
449 -> ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
452 +‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
450 450  
451 451  Some examples follow, for some specific values of INDICATOR and COUNTRY:
452 452  
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 -> … … …
456 +‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
457 +… … …
458 458  
459 +‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
460 +‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
461 +… … …
462 +
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
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 -> … … …
465 +VTL dataset   INDICATOR value COUNTRY value
469 469  
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 +
470 470  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:
471 471  
472 -> 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’,
473 -> … ,
474 -> DF2bis_POPGROWTH_USA’, DF2bis_POPGROWTH_CANADA’
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 +…);
476 476  
477 477  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.
478 478  
... ... @@ -484,26 +484,25 @@
484 484  
485 485  With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
486 486  
487 -(% style="width:706.294px" %)
488 -|(% style="width:257px" %)VTL|(% style="width:446px" %)SDMX
489 -|(% 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^^
490 -|(% style="width:257px" %)**Represented Variable**|(% style="width:446px" %)**Concept** with a definite Representation
491 -|(% style="width:257px" %)**Value Domain**|(% style="width:446px" %)(((
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**|(((
492 492  **Representation** (see the Structure
493 493  Pattern in the Base Package)
494 494  )))
495 -|(% style="width:257px" %)**Enumerated Value Domain / Code List**|(% style="width:446px" %)**Codelist**
496 -|(% style="width:257px" %)**Code**|(% style="width:446px" %)**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
497 -|(% style="width:257px" %)**Described Value Domain**|(% style="width:446px" %)(((
505 +|**Enumerated Value Domain / Code List**|**Codelist**
506 +|**Code**|**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
507 +|**Described Value Domain**|(((
498 498  non-enumerated** Representation**
499 499  (having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
500 500  )))
501 -|(% 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
502 -|(% style="width:257px" %) |(% style="width:446px" %)to a valid **value **(for non-enumerated** **Representations)
503 -|(% style="width:257px" %)**Value Domain Subset / Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
504 -|(% style="width:257px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
505 -|(% style="width:257px" %)**Described Value Domain Subset / Described Set**|(% style="width:446px" %)This abstraction does not exist in SDMX
506 -|(% style="width:257px" %)**Set list**|(% style="width:446px" %)This abstraction does not exist in SDMX
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 507  
508 508  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).
509 509  
... ... @@ -511,10 +511,8 @@
511 511  
512 512  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
513 513  
514 -> DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
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.
515 515  
516 -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.
517 -
518 518  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
519 519  
520 520  Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
... ... @@ -529,9 +529,8 @@
529 529  
530 530  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:
531 531  
540 +[[image:1750067055028-964.png]]
532 532  
533 -[[image:1750070288958-132.png]]
534 -
535 535  **Figure 22 – VTL Data Types**
536 536  
537 537  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.
... ... @@ -538,8 +538,6 @@
538 538  
539 539  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):
540 540  
541 -[[image:1750070310572-584.png]]
542 -
543 543  **Figure 23 – VTL Basic Scalar Types**
544 544  
545 545  === 12.4.2 VTL basic scalar types and SDMX data types ===
... ... @@ -564,157 +564,158 @@
564 564  
565 565  The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
566 566  
567 -(% style="width:583.294px" %)
568 -|(% style="width:360px" %)SDMX data type (BasicComponentDataType)|(% style="width:221px" %)Default VTL basic scalar type
569 -|(% style="width:360px" %)(((
572 +|SDMX data type (BasicComponentDataType)|Default VTL basic scalar type
573 +|(((
570 570  String
571 571  (string allowing any character)
572 -)))|(% style="width:221px" %)string
573 -|(% style="width:360px" %)(((
574 -Alpha
576 +)))|string
577 +|(((
578 +Alpha 
579 +
575 575  (string which only allows A-z)
576 -)))|(% style="width:221px" %)string
577 -|(% style="width:360px" %)(((
581 +)))|string
582 +|(((
578 578  AlphaNumeric
579 579  (string which only allows A-z and 0-9)
580 -)))|(% style="width:221px" %)string
581 -|(% style="width:360px" %)(((
585 +)))|string
586 +|(((
582 582  Numeric
588 +
583 583  (string which only allows 0-9, but is not numeric so that is can having leading zeros)
584 -)))|(% style="width:221px" %)string
585 -|(% style="width:360px" %)(((
590 +)))|string
591 +|(((
586 586  BigInteger
587 587  (corresponds to XML Schema xs:integer datatype; infinite set of integer values)
588 -)))|(% style="width:221px" %)integer
589 -|(% style="width:360px" %)(((
594 +)))|integer
595 +|(((
590 590  Integer
591 591  (corresponds to XML Schema xs:int datatype; between -2147483648 and +2147483647
592 592  (inclusive))
593 -)))|(% style="width:221px" %)integer
594 -|(% style="width:360px" %)(((
599 +)))|integer
600 +|(((
595 595  Long
596 596  (corresponds to XML Schema xs:long datatype; between -9223372036854775808 and
597 597  +9223372036854775807 (inclusive))
598 -)))|(% style="width:221px" %)integer
599 -|(% style="width:360px" %)(((
604 +)))|integer
605 +|(((
600 600  Short
601 601  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
602 -)))|(% style="width:221px" %)integer
603 -|(% 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
604 -|(% style="width:360px" %)(((
608 +)))|integer
609 +|Decimal (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as decimals)|number
610 +|(((
605 605  Float
606 606  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
607 -)))|(% style="width:221px" %)number
608 -|(% style="width:360px" %)(((
613 +)))|number
614 +|(((
609 609  Double
610 610  (corresponds to XML Schema xs:double datatype; patterned after the IEEE double-precision 64-bit floating point type)
611 -)))|(% style="width:221px" %)number
612 -|(% style="width:360px" %)(((
617 +)))|number
618 +|(((
613 613  Boolean
614 614  (corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of
615 615  binary-valued logic: {true, false})
616 -)))|(% style="width:221px" %)boolean
617 -|(% style="width:360px" %)(((
622 +)))|boolean
623 +|(((
618 618  URI
619 619  (corresponds to the XML Schema xs:anyURI; absolute or relative Uniform Resource Identifier Reference)
620 -)))|(% style="width:221px" %)string
621 -|(% style="width:360px" %)(((
626 +)))|string
627 +|(((
622 622  Count
623 623  (an integer following a sequential pattern, increasing by 1 for each occurrence)
624 -)))|(% style="width:221px" %)integer
625 -|(% style="width:360px" %)(((
630 +)))|integer
631 +|(((
626 626  InclusiveValueRange
627 627  (decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
628 -)))|(% style="width:221px" %)number
629 -|(% style="width:360px" %)(((
634 +)))|number
635 +|(((
630 630  ExclusiveValueRange
631 631  (decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
632 -)))|(% style="width:221px" %)number
633 -|(% style="width:360px" %)(((
638 +)))|number
639 +|(((
634 634  Incremental
635 635  (decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
636 -)))|(% style="width:221px" %)number
637 -|(% style="width:360px" %)(((
642 +)))|number
643 +|(((
638 638  ObservationalTimePeriod
639 639  (superset of StandardTimePeriod and TimeRange)
640 -)))|(% style="width:221px" %)time
641 -|(% style="width:360px" %)(((
646 +)))|time
647 +|(((
642 642  StandardTimePeriod
643 643  (superset of BasicTimePeriod and ReportingTimePeriod)
644 -)))|(% style="width:221px" %)time
645 -|(% style="width:360px" %)(((
650 +)))|time
651 +|(((
646 646  BasicTimePeriod
647 647  (superset of GregorianTimePeriod and DateTime)
648 -)))|(% style="width:221px" %)date
649 -|(% style="width:360px" %)(((
654 +)))|date
655 +|(((
650 650  GregorianTimePeriod
651 651  (superset of GregorianYear, GregorianYearMonth, and GregorianDay)
652 -)))|(% style="width:221px" %)date
653 -|(% style="width:360px" %)GregorianYear (YYYY)|(% style="width:221px" %)date
654 -|(% style="width:360px" %)GregorianYearMonth / GregorianMonth (YYYY-MM)|(% style="width:221px" %)date
655 -|(% style="width:360px" %)GregorianDay (YYYY-MM-DD)|(% style="width:221px" %)date
656 -|(% style="width:360px" %)(((
658 +)))|date
659 +|GregorianYear (YYYY)|date
660 +|GregorianYearMonth / GregorianMonth (YYYY-MM)|date
661 +|GregorianDay (YYYY-MM-DD)|date
662 +|(((
657 657  ReportingTimePeriod
658 658  (superset of RepostingYear, ReportingSemester, ReportingTrimester, ReportingQuarter, ReportingMonth, ReportingWeek, ReportingDay)
659 -)))|(% style="width:221px" %)time_period
660 -|(% style="width:360px" %)(((
665 +)))|time_period
666 +|(((
661 661  ReportingYear
662 662  (YYYY-A1 – 1 year period)
663 -)))|(% style="width:221px" %)time_period
664 -|(% style="width:360px" %)(((
669 +)))|time_period
670 +|(((
665 665  ReportingSemester
666 666  (YYYY-Ss – 6 month period)
667 -)))|(% style="width:221px" %)time_period
668 -|(% style="width:360px" %)(((
673 +)))|time_period
674 +|(((
669 669  ReportingTrimester
670 670  (YYYY-Tt – 4 month period)
671 -)))|(% style="width:221px" %)time_period
672 -|(% style="width:360px" %)(((
677 +)))|time_period
678 +|(((
673 673  ReportingQuarter
674 674  (YYYY-Qq – 3 month period)
675 -)))|(% style="width:221px" %)time_period
676 -|(% style="width:360px" %)(((
681 +)))|time_period
682 +|(((
677 677  ReportingMonth
678 678  (YYYY-Mmm – 1 month period)
679 -)))|(% style="width:221px" %)time_period
680 -|(% style="width:360px" %)ReportingWeek|(% style="width:221px" %)time_period
681 -|(% style="width:360px" %) (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|(% style="width:221px" %)
682 -|(% style="width:360px" %)(((
685 +)))|time_period
686 +|ReportingWeek|time_period
687 +| (YYYY-Www – 7 day period; following ISO 8601 definition of a week in a year)|
688 +|(((
683 683  ReportingDay
684 684  (YYYY-Dddd – 1 day period)
685 -)))|(% style="width:221px" %)time_period
686 -|(% style="width:360px" %)(((
691 +)))|time_period
692 +|(((
687 687  DateTime
688 688  (YYYY-MM-DDThh:mm:ss)
689 -)))|(% style="width:221px" %)date
690 -|(% style="width:360px" %)(((
695 +)))|date
696 +|(((
691 691  TimeRange
692 692  (YYYY-MM-DD(Thh:mm:ss)?/<duration>)
693 -)))|(% style="width:221px" %)time
694 -|(% style="width:360px" %)(((
699 +)))|time
700 +|(((
695 695  Month
696 696  (~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
697 -)))|(% style="width:221px" %)string
698 -|(% style="width:360px" %)(((
703 +)))|string
704 +|(((
699 699  MonthDay
700 700  (~-~-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)
701 -)))|(% style="width:221px" %)string
702 -|(% style="width:360px" %)(((
707 +)))|string
708 +|(((
703 703  Day
704 704  (~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
705 -)))|(% style="width:221px" %)string
706 -|(% style="width:360px" %)(((
711 +)))|string
712 +|(((
707 707  Time
708 708  (hh:mm:ss; time independent of a date; e.g. coffee break is at 10:00 AM)
709 -)))|(% style="width:221px" %)string
710 -|(% style="width:360px" %)(((
715 +)))|string
716 +|(((
711 711  Duration
712 712  (corresponds to XML Schema xs:duration datatype)
713 -)))|(% style="width:221px" %)duration
714 -|(% style="width:360px" %)XHTML|(% style="width:221px" %)Metadata type – not applicable
715 -|(% style="width:360px" %)KeyValues|(% style="width:221px" %)Metadata type – not applicable
716 -|(% style="width:360px" %)IdentifiableReference|(% style="width:221px" %)Metadata type – not applicable
717 -|(% style="width:360px" %)DataSetReference|(% style="width:221px" %)Metadata type – not applicable
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
718 718  
719 719  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
720 720  
... ... @@ -724,82 +724,84 @@
724 724  
725 725  The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
726 726  
727 -(% style="width:748.294px" %)
728 -|(% style="width:164px" %)(((
729 -VTL basic scalar type
730 -)))|(% style="width:304px" %)(((
733 +|(((
734 +VTL basic
735 +scalar type
736 +)))|(((
731 731  Default SDMX data type
732 -(BasicComponentDataType)
733 -)))|(% style="width:277px" %)Default output format
734 -|(% style="width:164px" %)String|(% style="width:304px" %)String|(% style="width:277px" %)Like XML (xs:string)
735 -|(% style="width:164px" %)Number|(% style="width:304px" %)Float|(% style="width:277px" %)Like XML (xs:float)
736 -|(% style="width:164px" %)Integer|(% style="width:304px" %)Integer|(% style="width:277px" %)Like XML (xs:int)
737 -|(% style="width:164px" %)Date|(% style="width:304px" %)DateTime|(% style="width:277px" %)YYYY-MM-DDT00:00:00Z
738 -|(% style="width:164px" %)Time|(% style="width:304px" %)StandardTimePeriod|(% style="width:277px" %)<date>/<date> (as defined above)
739 -|(% style="width:164px" %)time_period|(% style="width:304px" %)(((
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|(((
740 740  ReportingTimePeriod
741 741  (StandardReportingPeriod)
742 -)))|(% style="width:277px" %)(((
749 +)))|(((
743 743   YYYY-Pppp
744 744  (according to SDMX )
745 745  )))
746 -|(% style="width:164px" %)Duration|(% style="width:304px" %)Duration|(% style="width:277px" %)Like XML (xs:duration) PnYnMnDTnHnMnS
747 -|(% style="width:164px" %)Boolean|(% style="width:304px" %)Boolean|(% style="width:277px" %)Like XML (xs:boolean) with the values "true" or "false"
753 +|Duration|Duration|Like XML (xs:duration) PnYnMnDTnHnMnS
754 +|Boolean|Boolean|Like XML (xs:boolean) with the values "true" or "false"
748 748  
749 749  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
750 750  
751 -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).
758 +In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType artefacts (see also the section
752 752  
760 +Transformations and Expressions of the SDMX information model).
761 +
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:717.294px" %)
756 -|(% colspan="2" style="width:714px" %)VTL special characters for the formatting masks
757 -|(% colspan="2" style="width:714px" %)
758 -|(% colspan="2" style="width:714px" %)Number
759 -|(% style="width:122px" %)D|(% style="width:591px" %)one numeric digit (if the scientific notation is adopted, D is only for the mantissa)
760 -|(% style="width:122px" %)E|(% style="width:591px" %)one numeric digit (for the exponent of the scientific notation)
761 -|(% style="width:122px" %). (dot)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
762 -|(% style="width:122px" %), (comma)|(% style="width:591px" %)possible separator between the integer and the decimal parts.
763 -|(% style="width:122px" %) |(% style="width:591px" %)
764 -|(% colspan="2" style="width:714px" %)Time and duration
765 -|(% style="width:122px" %)C|(% style="width:591px" %)century
766 -|(% style="width:122px" %)Y|(% style="width:591px" %)year
767 -|(% style="width:122px" %)S|(% style="width:591px" %)semester
768 -|(% style="width:122px" %)Q|(% style="width:591px" %)quarter
769 -|(% style="width:122px" %)M|(% style="width:591px" %)month
770 -|(% style="width:122px" %)W|(% style="width:591px" %)week
771 -|(% style="width:122px" %)D|(% style="width:591px" %)day
772 -|(% style="width:122px" %)h|(% style="width:591px" %)hour digit (by default on 24 hours)
773 -|(% style="width:122px" %)M|(% style="width:591px" %)minute
774 -|(% style="width:122px" %)S|(% style="width:591px" %)second
775 -|(% style="width:122px" %)D|(% style="width:591px" %)decimal of second
776 -|(% style="width:122px" %)P|(% style="width:591px" %)period indicator (representation in one digit for the duration)
777 -|(% style="width:122px" %)P|(% style="width:591px" %)number of the periods specified in the period indicator
778 -|(% style="width:122px" %)AM/PM|(% style="width:591px" %)indicator of AM / PM (e.g. am/pm for "am" or "pm")
779 -|(% style="width:122px" %)MONTH|(% style="width:591px" %)uppercase textual representation of the month (e.g., JANUARY for January)
780 -|(% style="width:122px" %)DAY|(% style="width:591px" %)uppercase textual representation of the day (e.g., MONDAY for Monday)
781 -|(% style="width:122px" %)Month|(% style="width:591px" %)lowercase textual representation of the month (e.g., january)
782 -|(% style="width:122px" %)Day|(% style="width:591px" %)lowercase textual representation of the month (e.g., monday)
783 -|(% style="width:122px" %)Month|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the month (e.g., January)
784 -|(% style="width:122px" %)Day|(% style="width:591px" %)First character uppercase, then lowercase textual representation of the day using (e.g. Monday)
785 -|(% style="width:122px" %) |(% style="width:591px" %)
786 -|(% colspan="2" style="width:714px" %)String
787 -|(% style="width:122px" %)X|(% style="width:591px" %)any string character
788 -|(% style="width:122px" %)Z|(% style="width:591px" %)any string character from "A" to "z"
789 -|(% style="width:122px" %)9|(% style="width:591px" %)any string character from "0" to "9"
790 -|(% style="width:122px" %) |(% style="width:591px" %)
791 -|(% colspan="2" style="width:714px" %)Boolean
792 -|(% style="width:122px" %)B|(% style="width:591px" %)Boolean using "true" for True and "false" for False
793 -|(% style="width:122px" %)1|(% style="width:591px" %)Boolean using "1" for True and "0" for False
794 -|(% style="width:122px" %)0|(% style="width:591px" %)Boolean using "0" for True and "1" for False
795 -|(% style="width:122px" %) |(% style="width:591px" %)
796 -|(% colspan="2" style="width:714px" %)Other qualifiers
797 -|(% style="width:122px" %)*|(% style="width:591px" %)an arbitrary number of digits (of the preceding type)
798 -|(% style="width:122px" %)+|(% style="width:591px" %)at least one digit (of the preceding type)
799 -|(% style="width:122px" %)( )|(% style="width:591px" %)optional digits (specified within the brackets)
800 -|(% style="width:122px" %)\|(% style="width:591px" %)prefix for the special characters that must appear in the mask
801 -|(% style="width:122px" %)N|(% style="width:591px" %)fixed number of digits used in the preceding textual representation of the month or the day
802 -|(% style="width:122px" %) |(% style="width:591px" %)
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 +| |
803 803  
804 804  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}}.
805 805  
1750070288958-132.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -45.9 KB
Content
1750070310572-584.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -18.9 KB
Content
1750067055028-964.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +5.5 KB
Content