Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.3
edited by Helena
on 2025/05/17 00:31
Change comment: There is no comment for this version
To version 10.1
edited by Artur
on 2025/05/21 10:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 3\.0 Standards\. Section 6\. Technical notes.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Code|Component|Concept scheme|Currency|Data set|Data structure definition|Dataflow|Decimals|Dimension|Facet|Maintainable artefact|Measure|Nameable artefact|Representation|SDMX Information Model|Statistical data and metadata exchange|Structural metadata|Validation and transformation language
Content
... ... @@ -412,38 +412,36 @@
412 412  
413 413  [[image:1747388275998-621.png]]
414 414  
415 -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}}
415 +In fact the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “sub” has exactly the same behaviour. Therefore, (% style="color:#2ecc71" %)mapping(%%) different parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] to different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] in the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] through the ordered concatenation notation is equivalent to a proper use of the operator “**sub**” on such a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]].{{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}}
416 416  
417 -In the direction from SDMX to VTL it is allowed to omit the value of one or more
417 +In the direction from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] it is allowed to omit the value of one or more DimensionComponents on which the (% style="color:#2ecc71" %)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>>doc:xwiki:Glossary.Dimension.WebHome]] all the values are kept and the [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] is not dropped.
418 418  
419 -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.
419 +For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] that contains all the observations of the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
420 420  
421 -For example, ‘DF(1.0.0)/POPULATION.’ (note the dot in the end of the name) is the VTL dataset that contains all the observations of the Dataflow DF(1.0.0) for which //INDICATOR// = POPULATION and COUNTRY = any value.
421 +This is equivalent to the application of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] “sub” operator only to the identifier //INDICATOR//:
422 422  
423 -This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
424 -
425 425  [[image:1747388244829-693.png]]
426 426  
427 427  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
428 428  
429 -Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different
427 +Heterogeneous invocations of the same [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are allowed, i.e. omitting different
430 430  
431 431  Dimensions in different invocations.
432 432  
433 -Let us now analyse __the mapping direction from VTL to SDMX__.
431 +Let us now analyse __the mapping direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]__.
434 434  
435 -In this situation, distinct parts of a SDMX Dataflow are calculated as distinct VTL datasets, under the constraint that they must have the same VTL data structure.
433 +In this situation, distinct parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] are calculated as distinct [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]], under the (% style="color:#2ecc71" %)constraint(%%) that they must have the same [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure.
436 436  
437 -For example, let us assume that the VTL programmer wants to calculate the SDMX
435 +For example, let us assume that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programmer wants to calculate the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
438 438  
439 439  Dataflow DF2(1.0.0) having the Dimensions TIME_PERIOD, INDICATOR, and COUNTRY and that such a programmer finds it convenient to calculate separately the parts of DF2(1.0.0) that have different combinations of values for INDICATOR and COUNTRY:
440 440  
441 -* each part is calculated as a VTL derived Data Set, result of a dedicated VTL Transformation;{{footnote}}If the whole DF2(1.0) is calculated by means of just one VTL Transformation, then the mapping between the SDMX Dataflow and the corresponding VTL dataset is one-to-one and this kind of mapping (one SDMX Dataflow to many VTL datasets) does not apply.{{/footnote}}
442 -* the data structure of all these VTL Data Sets has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.{{footnote}}This is possible as each VTL dataset corresponds to one particular combination of values of INDICATOR and COUNTRY.{{/footnote}}
439 +* each part is calculated as a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] derived [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]], result of a dedicated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation;{{footnote}}If the whole DF2(1.0) is calculated by means of just one VTL Transformation, then the mapping between the SDMX Dataflow and the corresponding VTL dataset is one-to-one and this kind of mapping (one SDMX Dataflow to many VTL datasets) does not apply.{{/footnote}}
440 +* the data structure of all these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] has the TIME_PERIOD identifier and does not have the INDICATOR and COUNTRY identifiers.{{footnote}}This is possible as each VTL dataset corresponds to one particular combination of values of INDICATOR and COUNTRY.{{/footnote}}
443 443  
444 -Under these hypothesis, such derived VTL Data Sets can be mapped to DF2(1.0.0) by declaring the DimensionComponents INDICATOR and COUNTRY as mapping dimensions{{footnote}}The mapping dimensions are defined as FromVtlSpaceKeys of the FromVtlSuperSpace of the VtlDataflowMapping relevant to DF2(1.0).{{/footnote}}.
442 +Under these hypothesis, such derived [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] can be (% style="color:#2ecc71" %)mapped(%%) to DF2(1.0.0) by declaring the DimensionComponents INDICATOR and COUNTRY as mapping dimensions{{footnote}}The mapping dimensions are defined as FromVtlSpaceKeys of the FromVtlSuperSpace of the VtlDataflowMapping relevant to DF2(1.0).{{/footnote}}.
445 445  
446 -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}}
444 +The corresponding [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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}}
447 447  
448 448  ‘DF2(1.0.0)/INDICATORvalue.COUNTRYvalue’ <- expression
449 449  
... ... @@ -453,74 +453,72 @@
453 453  
454 454  [[image:1747388206717-256.png]]
455 455  
456 -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:
454 +As said, it is assumed that these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] derived [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] have the TIME_PERIOD as the only identifier. In the mapping from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to SMDX, the [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] INDICATOR and COUNTRY are added to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data structure on order to obtain the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] one, with the following values respectively:
457 457  
458 458  [[image:1747388148322-387.png]]
459 459  
460 -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:
458 +It should be noted that the application of this many-to-one mapping from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] is equivalent to an appropriate sequence of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations. These use the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operator “calc” to add the proper [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] (in the example DF2(1.0.0)), that can be (% style="color:#2ecc71" %)mapped(%%) one-to-one to the homonymous [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]. Following the same example, these [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations would be:
461 461  
462 462  [[image:1747388179021-814.png]]
463 463  
464 -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
462 +In other words, starting from the [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] explicitly calculated through [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] (in the example ‘DF2(1.0)/GDPPERCAPITA.USA’ and so on), the first step consists in calculating other (non-persistent) [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] (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>>doc:xwiki:Glossary.Data set.WebHome]] 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 (% style="color:#2ecc71" %)mapped(%%) one-to-one to the homonymous [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] having the [[dimension>>doc:xwiki:Glossary.Dimension.WebHome]] [[components>>doc:xwiki:Glossary.Component.WebHome]] TIME_PERIOD, INDICATOR and COUNTRY.
465 465  
466 -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.
464 +Therefore, (% style="color:#2ecc71" %)mapping(%%) different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] having the same data structure to different parts of a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], i.e. in the direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], through the ordered concatenation notation is equivalent to a proper use of the operators “calc” and “union” on such [[datasets>>doc:xwiki:Glossary.Data set.WebHome]].{{footnote}}In case the ordered concatenation notation from VTL to SDMX is used, the set of Transformations described above is implicitly performed; therefore, in order to test the overall compliance of the VTL program to the VTL consistency rules, these implicit Transformations have to be considered as part of the VTL program even if they are not explicitly coded.{{/footnote}}
467 467  
468 -Therefore, mapping different VTL datasets having the same data structure to different parts of a SDMX Dataflow, i.e. in the direction from VTL to SDMX, through the ordered concatenation notation is equivalent to a proper use of the operators “calc” and “union” on such datasets.{{footnote}}In case the ordered concatenation notation from VTL to SDMX is used, the set of Transformations described above is implicitly performed; therefore, in order to test the overall compliance of the VTL program to the VTL consistency rules, these implicit Transformations have to be considered as part of the VTL program even if they are not explicitly coded.{{/footnote}}
466 +It is worth noting that in the direction from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] it is mandatory to specify the value for every [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] on which the (% style="color:#2ecc71" %)mapping(%%) is based (in other word, in the name of the calculated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] is __not__ possible to omit the value of some of the Dimensions).
469 469  
470 -It is worth noting that in the direction from VTL to SDMX it is mandatory to specify the value for every Dimension on which the mapping is based (in other word, in the name of the calculated VTL dataset is __not__ possible to omit the value of some of the Dimensions).
471 -
472 472  === 12.3.7 Mapping variables and value domains between VTL and SDMX ===
473 473  
474 -With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
470 +With reference to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] “model for Variables and Value domains”, the following additional mappings have to be considered:
475 475  
476 476  (% style="width:895.294px" %)
477 477  |(% style="width:278px" %)**VTL**|(% style="width:613px" %)**SDMX**
478 -|(% style="width:278px" %)**Data Set Component**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a Component (either a DimensionComponent or a Measure or a DataAttribute) belonging to one specific Dataflow{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
474 +|(% style="width:278px" %)**[[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] [[Component>>doc:xwiki:Glossary.Component.WebHome]]**|(% style="width:613px" %)Although this abstraction exists in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a [[Component>>doc:xwiki:Glossary.Component.WebHome]] (either a DimensionComponent or a [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] or a DataAttribute) belonging to one specific [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]{{footnote}}Through SDMX Constraints, it is possible to specify the values that a Component of a Dataflow can assume.{{/footnote}}
479 479  |(% style="width:278px" %)**Represented Variable**|(% style="width:613px" %)(((
480 -**Concept** with a definite
476 +(% style="color:#2ecc71" %)**Concept**(%%) with a definite
481 481  
482 -Representation
478 +[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]
483 483  )))
484 484  |(% style="width:278px" %)**Value Domain**|(% style="width:613px" %)(((
485 -**Representation** (see the Structure Pattern in the Base Package)
481 +**[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]** (see the Structure Pattern in the Base Package)
486 486  )))
487 487  |(% style="width:278px" %)**Enumerated Value Domain /
488 -Code List**|(% style="width:613px" %)**Codelist**
489 -|(% style="width:278px" %)**Code**|(% style="width:613px" %)(((
490 -**Code** (for enumerated DimensionComponent, Measure, DataAttribute)
484 +[[Code>>doc:xwiki:Glossary.Code.WebHome]] List**|(% style="width:613px" %)**Codelist**
485 +|(% style="width:278px" %)**[[Code>>doc:xwiki:Glossary.Code.WebHome]]**|(% style="width:613px" %)(((
486 +**[[Code>>doc:xwiki:Glossary.Code.WebHome]]** (for enumerated DimensionComponent, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], DataAttribute)
491 491  )))
492 492  |(% style="width:278px" %)**Described Value Domain**|(% style="width:613px" %)(((
493 -non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
489 +non-enumerated** [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] **(having [[Facets>>doc:xwiki:Glossary.Facet.WebHome]] / ExtendedFacets, see the Structure Pattern in the Base Package)
494 494  )))
495 -|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in SDMX, it does not have an explicit definition and correspond to a **Code** of a Codelist (for enumerated Representations) or to a valid **value **(for non-enumerated** **Representations)
496 -|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
497 -|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
498 -|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in SDMX
499 -|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in SDMX
491 +|(% style="width:278px" %)**Value**|(% style="width:613px" %)Although this abstraction exists in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it does not have an explicit definition and correspond to a **[[Code>>doc:xwiki:Glossary.Code.WebHome]]** of a Codelist (for enumerated [[Representations>>doc:xwiki:Glossary.Representation.WebHome]]) or to a valid **value **(for non-enumerated** **[[Representations>>doc:xwiki:Glossary.Representation.WebHome]])
492 +|(% style="width:278px" %)**Value Domain Subset / Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
493 +|(% style="width:278px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
494 +|(% style="width:278px" %)**Described Value Domain Subset / Described Set**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
495 +|(% style="width:278px" %)**Set list**|(% style="width:613px" %)This abstraction does not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]
500 500  
501 -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).
497 +The main difference between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] relies on the fact that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] for defining subsets of Value Domains do not exist in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], therefore the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] features for referring to predefined subsets are not available in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. These [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] 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>>doc:xwiki:Glossary.Data set.WebHome]] [[Component>>doc:xwiki:Glossary.Component.WebHome]] (aimed at defining the set of values that the [[Component>>doc:xwiki:Glossary.Component.WebHome]] of a [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] can take, possibly a subset of the [[codes>>doc:xwiki:Glossary.Code.WebHome]] of Value Domain).
502 502  
503 -Another difference consists in the fact that all Value Domains are considered as identifiable objects in VTL either if enumerated or not, while in SDMX the Codelist (corresponding to a VTL enumerated Value Domain) is identifiable, while the SDMX non-enumerated Representation (corresponding to a VTL non-enumerated Value Domain) is not identifiable. As a consequence, the definition of the VTL Rulesets, which in VTL can refer either to enumerated or non-enumerated value domains, in SDMX can refer only to enumerated Value Domains (i.e. to SDMX Codelists). As for the mapping between VTL variables and SDMX Concepts, it should be noted that these artefacts do not coincide perfectly. In fact, the VTL variables are represented variables, defined always on the same Value Domain (“Representation” in SDMX) independently of the data set / data structure in which they appear{{footnote}}By using represented variables, VTL can assume that data structures having the same variables as identifiers can be composed one another because the correspondent values can match.{{/footnote}}, while the SDMX Concepts can have different Representations in different DataStructures.{{footnote}}A Concept becomes a Component in a DataStructureDefinition, and Components can have different LocalRepresentations in different DataStructureDefinitions, also overriding the (possible) base representation of the Concept.{{/footnote}} This means that one SDMX Concept can correspond to many VTL Variables, one for each representation the Concept has.
499 +Another difference consists in the fact that all Value Domains are considered as identifiable objects in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] either if enumerated or not, while in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] the Codelist (corresponding to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] enumerated Value Domain) is identifiable, while the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] non-enumerated [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] (corresponding to a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] non-enumerated Value Domain) is not identifiable. As a consequence, the definition of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Rulesets, which in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] can refer either to enumerated or non-enumerated value domains, in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] can refer only to enumerated Value Domains (i.e. to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Codelists). As for the (% style="color:#2ecc71" %)mapping(%%) between [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] variables and [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%), it should be noted that these [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] do not coincide perfectly. In fact, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] variables are represented variables, defined always on the same Value Domain (“[[Representation>>doc:xwiki:Glossary.Representation.WebHome]]” in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) independently of the [[data set>>doc:xwiki:Glossary.Data set.WebHome]] / data structure in which they appear{{footnote}}By using represented variables, VTL can assume that data structures having the same variables as identifiers can be composed one another because the correspondent values can match.{{/footnote}}, while the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%) can have different [[Representations>>doc:xwiki:Glossary.Representation.WebHome]] in different DataStructures.{{footnote}}A Concept becomes a Component in a DataStructureDefinition, and Components can have different LocalRepresentations in different DataStructureDefinitions, also overriding the (possible) base representation of the Concept.{{/footnote}} This means that one [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concept(%%) can correspond to many [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Variables, one for each [[representation>>doc:xwiki:Glossary.Representation.WebHome]] the (% style="color:#2ecc71" %)Concept(%%) has.
504 504  
505 -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
501 +Therefore, it is important to be aware that some [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operations (for example the binary operations at [[data set>>doc:xwiki:Glossary.Data set.WebHome]] (% style="color:#2ecc71" %)level(%%)) are consistent only if the [[components>>doc:xwiki:Glossary.Component.WebHome]] having the same names in the operated [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]] have also the same [[representation>>doc:xwiki:Glossary.Representation.WebHome]] (i.e. the same Value Domain as for [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]). For example, it is possible to obtain correct results from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expression
506 506  
507 -DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are VTL Data Sets)
503 +DS_c := DS_a + DS_b (where DS_a, DS_b, DS_c are [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Sets>>doc:xwiki:Glossary.Data set.WebHome]])
508 508  
509 -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.
505 +if the matching [[components>>doc:xwiki:Glossary.Component.WebHome]] in DS_a and DS_b (e.g. ref_date, geo_area, sector …) refer to the same general [[representation>>doc:xwiki:Glossary.Representation.WebHome]]. In simpler words, DS_a and DS_b must use the same values/[[codes>>doc:xwiki:Glossary.Code.WebHome]] (for ref_date, geo_area, sector … ), otherwise the relevant values would not match and the result of the operation would be wrong.
510 510  
511 -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
507 +As mentioned, the property above is not enforced by construction in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], and different [[representations>>doc:xwiki:Glossary.Representation.WebHome]] of the same (% style="color:#2ecc71" %)Concept(%%) can be not compatible one another (for example, it may happen that geo_area is represented by ISO-alpha-3 [[codes>>doc:xwiki:Glossary.Code.WebHome]] in DS_a and by ISO alpha-2 [[codes>>doc:xwiki:Glossary.Code.WebHome]] in DS_b). Therefore, it will be up to the definer of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]
512 512  
513 -Transformations to ensure that the VTL expressions are consistent with the actual representations of the correspondent SDMX Concepts.
509 +Transformations to ensure that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] expressions are consistent with the actual [[representations>>doc:xwiki:Glossary.Representation.WebHome]] of the correspondent [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%).
514 514  
515 -It remains up to the SDMX-VTL definer also the assurance of the consistency between a VTL Ruleset defined on Variables and the SDMX Components on which the Ruleset is applied. In fact, a VTL Ruleset is expressed by means of the values of the Variables (i.e. SDMX Concepts), i.e. assuming definite representations for them (e.g. ISOalpha-3 for country). If the Ruleset is applied to SDMX Components that have the same name of the Concept they refer to but different representations (e.g. ISO-alpha-2 for country), the Ruleset cannot work properly.
511 +It remains up to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]-[[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definer also the assurance of the consistency between a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Ruleset defined on Variables and the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] on which the Ruleset is applied. In fact, a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Ruleset is expressed by means of the values of the Variables (i.e. [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#2ecc71" %)Concepts(%%)), i.e. assuming definite [[representations>>doc:xwiki:Glossary.Representation.WebHome]] for them (e.g. ISOalpha-3 for country). If the Ruleset is applied to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Components>>doc:xwiki:Glossary.Component.WebHome]] that have the same name of the (% style="color:#2ecc71" %)Concept(%%) they refer to but different [[representations>>doc:xwiki:Glossary.Representation.WebHome]] (e.g. ISO-alpha-2 for country), the Ruleset cannot work properly.
516 516  
517 517  == 12.4 Mapping between SDMX and VTL Data Types ==
518 518  
519 519  === 12.4.1 VTL Data types ===
520 520  
521 -According to the VTL User Guide the possible operations in VTL depend on the data types of the artefacts. For example, numbers can be multiplied but text strings cannot. In the VTL Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
517 +According to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] User Guide the possible operations in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] depend on the data types of the [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]]. For example, numbers can be multiplied but text strings cannot. In the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations, the compliance between the operators and the data types of their operands is statically checked, i.e., violations result in compile-time errors.
522 522  
523 -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:
519 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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>>doc:xwiki:Glossary.Data set.WebHome]], [[Components>>doc:xwiki:Glossary.Component.WebHome]], Rulesets, etc.), which are the types of the compound structures. See below the diagram of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] data types, taken from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] User Manual:
524 524  
525 525  [[image:1747388434672-948.png]]
526 526  
... ... @@ -527,9 +527,9 @@
527 527  (% class="wikigeneratedid" id="HFigure222013VTLDataTypes" %)
528 528  **Figure 22 – VTL Data Types**
529 529  
530 -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.
526 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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.
531 531  
532 -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):
528 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] 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):
533 533  
534 534  [[image:1747388465321-274.png]]
535 535  
... ... @@ -537,25 +537,25 @@
537 537  
538 538  === 12.4.2 VTL basic scalar types and SDMX data types ===
539 539  
540 -The VTL assumes that a basic scalar type has a unique internal representation and can have more external representations.
536 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] assumes that a basic scalar type has a unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] and can have more external [[representations>>doc:xwiki:Glossary.Representation.WebHome]].
541 541  
542 -The internal representation is the format used within a VTL system to represent (and process) all the scalar values of a certain type. In principle, this format is hidden and not necessarily known by users. The external representations are instead the external formats of the values of a certain basic scalar type, i.e. the formats known by the users. For example, the internal representation of the dates can be an integer counting the days since a predefined date (e.g. from 01/01/4713 BC up to 31/12/5874897 AD like in Postgres) while two possible external representations are the formats YYYY-MMGG and MM-GG-YYYY (e.g. respectively 2010-12-31 and 12-31-2010).
538 +The internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is the format used within a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] system to represent (and process) all the scalar values of a certain type. In principle, this format is hidden and not necessarily known by users. The external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] are instead the external formats of the values of a certain basic scalar type, i.e. the formats known by the users. For example, the internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the dates can be an integer counting the days since a predefined date (e.g. from 01/01/4713 BC up to 31/12/5874897 AD like in Postgres) while two possible external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] are the formats YYYY-MMGG and MM-GG-YYYY (e.g. respectively 2010-12-31 and 12-31-2010).
543 543  
544 -The internal representation is the reference format that allows VTL to operate on more values of the same type (for example on more dates) even if such values have different external formats: these values are all converted to the unique internal representation so that they can be composed together (e.g. to find the more recent date, to find the time span between these dates and so on).
540 +The internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is the reference format that allows [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to operate on more values of the same type (for example on more dates) even if such values have different external formats: these values are all converted to the unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] so that they can be composed together (e.g. to find the more recent date, to find the time span between these dates and so on).
545 545  
546 -The VTL assumes that a unique internal representation exists for each basic scalar type but does not prescribe any particular format for it, leaving the VTL systems free to using they preferred or already existing internal format. By consequence, in VTL the basic scalar types are abstractions not associated to a specific format.
542 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] assumes that a unique internal [[representation>>doc:xwiki:Glossary.Representation.WebHome]] exists for each basic scalar type but does not prescribe any particular format for it, leaving the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] systems free to using they preferred or already existing internal format. By consequence, in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] the basic scalar types are abstractions not associated to a specific format.
547 547  
548 -SDMX data types are conceived instead to support the data exchange, therefore they do have a format, which is known by the users and correspond, in VTL terms, to external representations. Therefore, for each VTL basic scalar type there can be more SDMX data types (the latter are explained in the section "General Notes for Implementers" of this document and are actually much more numerous than the former).
544 +[[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types are conceived instead to support the data exchange, therefore they do have a format, which is known by the users and correspond, in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] terms, to external [[representations>>doc:xwiki:Glossary.Representation.WebHome]]. Therefore, for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type there can be more [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types (the latter are explained in the section "General Notes for Implementers" of this document and are actually much more numerous than the former).
549 549  
550 -The following paragraphs describe the mapping between the SDMX data types and the VTL basic scalar types. This mapping shall be presented in the two directions of possible conversion, i.e. from SDMX to VTL and vice-versa.
546 +The following paragraphs describe the mapping between the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types and the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types. This mapping shall be presented in the two directions of possible conversion, i.e. from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] and vice-versa.
551 551  
552 -The conversion from SDMX to VTL happens when an SDMX artefact acts as inputs of a VTL Transformation. As already said, in fact, at compile time the VTL needs to know the VTL type of the operands in order to check their compliance with the VTL operators and at runtime it must convert the values from their external (SDMX) representations to the corresponding internal (VTL) ones.
548 +The conversion from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] happens when an [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] acts as inputs of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation. As already said, in fact, at compile time the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] needs to know the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] type of the operands in order to check their compliance with the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operators and at runtime it must convert the values from their external ([[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) [[representations>>doc:xwiki:Glossary.Representation.WebHome]] to the corresponding internal ([[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]) ones.
553 553  
554 -The opposite conversion, i.e. from VTL to SDMX, happens when a VTL result, i.e. a VTL Data Set output of a Transformation, must become a SDMX artefact (or part of it). The values of the VTL result must be converted into the desired (SDMX) external representations (data types) of the SDMX artefact.
550 +The opposite conversion, i.e. from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], happens when a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] result, i.e. a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] [[Data Set>>doc:xwiki:Glossary.Data set.WebHome]] output of a Transformation, must become a [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (or part of it). The values of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] result must be converted into the desired ([[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]) external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] (data types) of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]].
555 555  
556 556  === 12.4.3 Mapping SDMX data types to VTL basic scalar types ===
557 557  
558 -The following table describes the default mapping for converting from the SDMX data types to the VTL basic scalar types.
554 +The following table describes the default mapping for converting from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types to the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types.
559 559  
560 560  (% style="width:823.294px" %)
561 561  |(% style="width:509px" %)**SDMX data type (BasicComponentDataType)**|(% style="width:312px" %)**Default VTL basic scalar type**
... ... @@ -591,7 +591,7 @@
591 591  Short
592 592  (corresponds to XML Schema xs:short datatype; between -32768 and -32767 (inclusive))
593 593  )))|(% style="width:312px" %)integer
594 -|(% 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
590 +|(% style="width:509px" %)[[Decimal>>doc:xwiki:Glossary.Decimals.WebHome]] (corresponds to XML Schema xs:decimal datatype; subset of real numbers that can be represented as [[decimals>>doc:xwiki:Glossary.Decimals.WebHome]])|(% style="width:312px" %)number
595 595  |(% style="width:509px" %)(((
596 596  Float
597 597  (corresponds to XML Schema xs:float datatype; patterned after the IEEE single-precision 32-bit floating point type)
... ... @@ -602,7 +602,7 @@
602 602  )))|(% style="width:312px" %)number
603 603  |(% style="width:509px" %)(((
604 604  Boolean
605 -(corresponds to the XML Schema xs:boolean datatype; support the mathematical concept of binary-valued logic: {true, false})
601 +(corresponds to the XML Schema xs:boolean datatype; support the mathematical (% style="color:#2ecc71" %)concept(%%) of binary-valued logic: {true, false})
606 606  )))|(% style="width:312px" %)boolean
607 607  
608 608  (% style="width:822.294px" %)
... ... @@ -616,15 +616,15 @@
616 616  )))|(% colspan="1" style="width:311px" %)integer
617 617  |(% colspan="2" style="width:507px" %)(((
618 618  InclusiveValueRange
619 -(decimal number within a closed interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
615 +([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number within a closed interval, whose bounds are specified in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[representation>>doc:xwiki:Glossary.Representation.WebHome]] by the [[facets>>doc:xwiki:Glossary.Facet.WebHome]] minValue and maxValue)
620 620  )))|(% colspan="1" style="width:311px" %)number
621 621  |(% colspan="2" style="width:507px" %)(((
622 622  ExclusiveValueRange
623 -(decimal number within an open interval, whose bounds are specified in the SDMX representation by the facets minValue and maxValue)
619 +([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number within an open interval, whose bounds are specified in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[representation>>doc:xwiki:Glossary.Representation.WebHome]] by the [[facets>>doc:xwiki:Glossary.Facet.WebHome]] minValue and maxValue)
624 624  )))|(% colspan="1" style="width:311px" %)number
625 625  |(% colspan="2" style="width:507px" %)(((
626 626  Incremental
627 -(decimal number the increased by a specific interval (defined by the interval facet), which is typically enforced outside of the XML validation)
623 +([[decimal>>doc:xwiki:Glossary.Decimals.WebHome]] number the increased by a specific interval (defined by the interval [[facet>>doc:xwiki:Glossary.Facet.WebHome]]), which is typically enforced outside of the XML validation)
628 628  )))|(% colspan="1" style="width:311px" %)number
629 629  |(% colspan="2" style="width:507px" %)(((
630 630  ObservationalTimePeriod
... ... @@ -681,19 +681,19 @@
681 681  )))|(% colspan="2" style="width:312px" %)date
682 682  |(% colspan="1" style="width:507px" %)(((
683 683  TimeRange
684 -(YYYY-MM-DD(Thh:mm:ss)?/<duration>)
680 +(YYYY-MM-DD(Thh:mm:ss)?/)
685 685  )))|(% colspan="2" style="width:312px" %)time
686 686  |(% colspan="1" style="width:507px" %)(((
687 687  Month
688 -(~-~-MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
684 +(MM; speicifies a month independent of a year; e.g. February is black history month in the United States)
689 689  )))|(% colspan="2" style="width:312px" %)string
690 690  |(% colspan="1" style="width:507px" %)(((
691 691  MonthDay
692 -(~-~-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)
688 +(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)
693 693  )))|(% colspan="2" style="width:312px" %)string
694 694  |(% colspan="1" style="width:507px" %)(((
695 695  Day
696 -(~-~--DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
692 +(-DD; specifies a day independent of a month or year; e.g. the 15^^th^^ is payday)
697 697  )))|(% colspan="2" style="width:312px" %)string
698 698  |(% colspan="1" style="width:507px" %)(((
699 699  Time
... ... @@ -711,11 +711,11 @@
711 711  (% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes" %)
712 712  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
713 713  
714 -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).
710 +When [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] takes in input [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]], it is assumed that a type conversion according to the table above always happens. In case a different [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type is desired, it can be achieved in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] program taking in input the default [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type above and applying to it the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] type conversion features (see the implicit and explicit type conversion and the "cast" operator in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Reference Manual).
715 715  
716 716  === 12.4.4 Mapping VTL basic scalar types to SDMX data types ===
717 717  
718 -The following table describes the default conversion from the VTL basic scalar types to the SDMX data types .
714 +The following table describes the default conversion from the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types to the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types .
719 719  
720 720  (% style="width:1073.29px" %)
721 721  |(% style="width:207px" %)(((
... ... @@ -727,13 +727,13 @@
727 727  |(% style="width:207px" %)Number|(% style="width:462px" %)Float|(% style="width:402px" %)Like XML (xs:float)
728 728  |(% style="width:207px" %)Integer|(% style="width:462px" %)Integer|(% style="width:402px" %)Like XML (xs:int)
729 729  |(% style="width:207px" %)Date|(% style="width:462px" %)DateTime|(% style="width:402px" %)YYYY-MM-DDT00:00:00Z
730 -|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)<date>/<date> (as defined above)
726 +|(% style="width:207px" %)Time|(% style="width:462px" %)StandardTimePeriod|(% style="width:402px" %)/ (as defined above)
731 731  |(% style="width:207px" %)time_period|(% style="width:462px" %)(((
732 732  ReportingTimePeriod
733 733  (StandardReportingPeriod)
734 734  )))|(% style="width:402px" %)(((
735 735  YYYY-Pppp
736 -(according to SDMX )
732 +(according to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] )
737 737  )))
738 738  |(% style="width:207px" %)Duration|(% style="width:462px" %)Duration|(% style="width:402px" %)(((
739 739  Like XML (xs:duration)
... ... @@ -744,9 +744,9 @@
744 744  (% class="wikigeneratedid" id="HFigure142013MappingsfromSDMXdatatypestoVTLBasicScalarTypes-1" %)
745 745  **Figure 14 – Mappings from SDMX data types to VTL Basic Scalar Types**
746 746  
747 -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).
743 +In case a different default conversion is desired, it can be achieved through the CustomTypeScheme and CustomType [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] information model).
748 748  
749 -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.
745 +The custom output formats can be specified by means of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] formatting mask described in the section "Type Conversion and Formatting Mask" of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Reference Manual. Such a section describes the masks for the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types "number", "integer", "date", "time", "time_period" and "duration" and gives examples. As for the types "string" and "boolean" the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] conventions are extended with some other special characters as described in the following table.
750 750  
751 751  (% style="width:713.294px" %)
752 752  |(% colspan="2" style="width:710px" %)VTL special characters for the formatting masks
... ... @@ -796,26 +796,26 @@
796 796  |\|(% style="width:486px" %)prefix for the special characters that must appear in the mask
797 797  |N|(% style="width:486px" %)fixed number of digits used in the preceding textual representation of the month or the day
798 798  
799 -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}}.
795 +The default conversion, either standard or customized, can be used to deduce automatically the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the [[components>>doc:xwiki:Glossary.Component.WebHome]] of the result of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformation. In alternative, the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of the resulting [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] can be given explicitly by providing its DataStructureDefinition. In other words, the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] specified in the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]], if available, overrides any default conversion{{footnote}}The representation given in the DSD should obviously be compatible with the VTL data type.{{/footnote}}.
800 800  
801 801  === 12.4.5 Null Values ===
802 802  
803 -In the conversions from SDMX to VTL it is assumed by default that a missing value in SDMX becomes a NULL in VTL. After the conversion, the NULLs can be manipulated through the proper VTL operators.
799 +In the conversions from [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] to [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] it is assumed by default that a missing value in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] becomes a NULL in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]]. After the conversion, the NULLs can be manipulated through the proper [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] operators.
804 804  
805 -On the other side, the VTL programs can produce in output NULL values for Measures and Attributes (Null values are not allowed in the Identifiers). In the conversion from VTL to SDMX, it is assumed that a NULL in VTL becomes a missing value in SDMX. In the conversion from VTL to SDMX, the default assumption can be overridden, separately for each VTL basic scalar type, by specifying which the value that represents the NULL in SDMX is. This can be specified in the attribute "nullValue" of the CustomType artefact (see also the section Transformations and Expressions of the SDMX information model). A CustomType belongs to a CustomTypeScheme, which can be referenced by one or more TransformationScheme (i.e. VTL programs). The overriding assumption is applied for all the SDMX Dataflows calculated in the TransformationScheme.
801 +On the other side, the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs can produce in output NULL values for [[Measures>>doc:xwiki:Glossary.Measure.WebHome]] and [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] (Null values are not allowed in the Identifiers). In the conversion from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], it is assumed that a NULL in [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] becomes a missing value in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]]. In the conversion from [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]], the default assumption can be overridden, separately for each [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type, by specifying which the value that represents the NULL in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] is. This can be specified in the [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] "nullValue" of the CustomType [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX information model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]). A CustomType belongs to a CustomTypeScheme, which can be referenced by one or more TransformationScheme (i.e. [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs). The overriding assumption is applied for all the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]] calculated in the TransformationScheme.
806 806  
807 807  === 12.4.6 Format of the literals used in VTL Transformations ===
808 808  
809 -The VTL programs can contain literals, i.e. specific values of certain data types written directly in the VTL definitions or expressions. The VTL does not prescribe a specific format for the literals and leave the specific VTL systems and the definers of VTL Transformations free of using their preferred formats.
805 +The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] programs can contain literals, i.e. specific values of certain data types written directly in the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] definitions or expressions. The [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] does not prescribe a specific format for the literals and leave the specific [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] systems and the definers of [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Transformations free of using their preferred formats.
810 810  
811 -Given this discretion, it is essential to know which are the external representations adopted for the literals in a VTL program, in order to interpret them correctly. For example, if the external format for the dates is YYYY-MM-DD the date literal 2010-0102 has the meaning of 2^^nd^^ January 2010, instead if the external format for the dates is YYYY-DD-MM the same literal has the meaning of 1^^st^^ February 2010.
807 +Given this discretion, it is essential to know which are the external [[representations>>doc:xwiki:Glossary.Representation.WebHome]] adopted for the literals in a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] program, in order to interpret them correctly. For example, if the external format for the dates is YYYY-MM-DD the date literal 2010-0102 has the meaning of 2^^nd^^ January 2010, instead if the external format for the dates is YYYY-DD-MM the same literal has the meaning of 1^^st^^ February 2010.
812 812  
813 -Hereinafter, i.e. in the SDMX implementation of the VTL, it is assumed that the literals are expressed according to the "default output format" of the table of the previous paragraph ("Mapping VTL basic scalar types to SDMX data types") unless otherwise specified.
809 +Hereinafter, i.e. in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] implementation of the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]], it is assumed that the literals are expressed according to the "default output format" of the table of the previous paragraph ("Mapping [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar types to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types") unless otherwise specified.
814 814  
815 -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).
811 +A different format can be specified in the [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] "vtlLiteralFormat" of the CustomType [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (see also the section Transformations and Expressions of the [[SDMX information model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]).
816 816  
817 -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.
813 +Like in the case of the conversion of NULLs described in the previous paragraph, the overriding assumption is applied, for a certain [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type, if a value is found for the vtlLiteralFormat [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] of the CustomType of such [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] basic scalar type. The overriding assumption is applied for all the literals of a related [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] TransformationScheme.
818 818  
819 -In case a literal is operand of a VTL Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
815 +In case a literal is operand of a [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] Cast operation, the format specified in the Cast overrides all the possible otherwise specified formats.
820 820  
821 821  {{putFootnotes/}}
SUZ.Methodology.Code.MethodologyClass[0]