Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 6.2
edited by Helena
on 2025/05/16 12:28
Change comment: There is no comment for this version
To version 6.10
edited by Helena
on 2025/05/16 12:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,10 +26,8 @@
26 26  
27 27  The alias of an SDMX artefact can be its URN (Universal Resource Name), an abbreviation of its URN or another user-defined name.
28 28  
29 -In any case, the aliases used in the VTL Transformations have to be mapped to the
29 +In any case, the aliases used in the VTL Transformations have to be mapped to the SDMX artefacts through the VtlMappingScheme and VtlMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlMapping allows specifying the aliases to be used in the VTL Transformations, Rulesets{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}} or User Defined Operators{{footnote}}The VTLMappings are used also for User Defined Operators (UDO). Although UDOs are envisaged to be defined on generic operands, so that the specific artefacts to be manipulated are passed as parameters at their invocation, it is also possible that an UDO invokes directly some specific SDMX artefacts. These SDMX artefacts have to be mapped to the corresponding aliases used in the definition of the UDO through the VtlMappingScheme and VtlMapping classes as well.{{/footnote}} to reference SDMX artefacts. A VtlMappingScheme is a container for zero or more VtlMapping.
30 30  
31 -SDMX artefacts through the VtlMappingScheme and VtlMapping classes (see the section of the SDMX IM relevant to the VTL). A VtlMapping allows specifying the aliases to be used in the VTL Transformations, Rulesets{{footnote}}See also the section "VTL-DL Rulesets" in the VTL Reference Manual.{{/footnote}} or User Defined Operators{{footnote}}The VTLMappings are used also for User Defined Operators (UDO). Although UDOs are envisaged to be defined on generic operands, so that the specific artefacts to be manipulated are passed as parameters at their invocation, it is also possible that an UDO invokes directly some specific SDMX artefacts. These SDMX artefacts have to be mapped to the corresponding aliases used in the definition of the UDO through the VtlMappingScheme and VtlMapping classes as well.{{/footnote}} to reference SDMX artefacts. A VtlMappingScheme is a container for zero or more VtlMapping.
32 -
33 33  The correspondence between an alias and a SDMX artefact must be one-to-one, meaning that a generic alias identifies one and just one SDMX artefact while a SDMX artefact is identified by one and just one alias. In other words, within a VtlMappingScheme an artefact can have just one alias and different artefacts cannot have the same alias.
34 34  
35 35  The references through the URN and the abbreviated URN are described in the following paragraphs.
... ... @@ -200,7 +200,7 @@
200 200  
201 201  === 12.3.3 Mapping from SDMX to VTL data structures ===
202 202  
203 -**12.3.3.1 Basic Mapping**
201 +==== 12.3.3.1 Basic Mapping ====
204 204  
205 205  The main mapping method from SDMX to VTL is called **Basic **mapping. This is considered as the default mapping method and is applied unless a different method is specified through the VtlMappingScheme and VtlDataflowMapping classes. When transforming **from SDMX to VTL**, this method consists in leaving the components unchanged and maintaining their names and roles, according to the following table:
206 206  
... ... @@ -230,18 +230,11 @@
230 230  The SDMX structures that contain a MeasureDimension are mapped as described below (this mapping is equivalent to a pivoting operation):
231 231  
232 232  * A SDMX simple dimension becomes a VTL (simple) identifier and a SDMX TimeDimension becomes a VTL (time) identifier;
233 -* Each possible Code Cj of the SDMX MeasureDimension is mapped to a VTL Measure, having the same name as the SDMX Code (i.e. Cj); the VTL Measure Cj is a new VTL component even if the SDMX data structure has not such a
234 -
235 -Component;
236 -
231 +* Each possible Code Cj of the SDMX MeasureDimension is mapped to a VTL Measure, having the same name as the SDMX Code (i.e. Cj); the VTL Measure Cj is a new VTL component even if the SDMX data structure has not such a Component;
237 237  * The SDMX MeasureDimension is not mapped to VTL (it disappears in the VTL Data Structure);
238 238  * The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
239 239  * An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
240 -** If, according to the SDMX AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the SDMX DataAttribute becomes a VTL Attribute having the same name. This happens if the
241 -
242 -AttributeRelationship is not specified (i.e. the DataAttribute does not depend on any DimensionComponent and therefore is at data set level), or if it refers to a set (or a group) of dimensions which does not include the MeasureDimension;
243 -
244 -*
235 +** If, according to the SDMX AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the SDMX DataAttribute becomes a VTL Attribute having the same name. This happens if the AttributeRelationship is not specified (i.e. the DataAttribute does not depend on any DimensionComponent and therefore is at data set level), or if it refers to a set (or a group) of dimensions which does not include the MeasureDimension;
245 245  ** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators).
246 246  ** Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
247 247  
... ... @@ -264,10 +264,7 @@
264 264  At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
265 265  
266 266  * The set of SDMX observations having the same values for all the Dimensions except than the MeasureDimension become one multi-measure VTL Data Point, having one Measure for each Code Cj of the SDMX MeasureDimension;
267 -* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple)
268 -
269 -Identifiers, (time) Identifier and Attributes.
270 -
258 +* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple) Identifiers, (time) Identifier and Attributes.
271 271  * The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
272 272  * For the SDMX DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Attribute DA_Cj
273 273  
... ... @@ -360,7 +360,7 @@
360 360  The mapping table is the following:
361 361  
362 362  (% style="width:689.294px" %)
363 -|(% style="width:344px" %)VTL|(% style="width:341px" %)SDMX
351 +|(% style="width:344px" %)**VTL**|(% style="width:341px" %)**SDMX**
364 364  |(% style="width:344px" %)(Simple) Identifier|(% style="width:341px" %)Dimension
365 365  |(% style="width:344px" %)(Time) Identifier|(% style="width:341px" %)TimeDimension
366 366  |(% style="width:344px" %)Some Measures|(% style="width:341px" %)Measure
... ... @@ -420,26 +420,14 @@
420 420  
421 421  SDMX Dataflow having INDICATOR=//INDICATORvalue //and COUNTRY=// COUNTRYvalue//. For example, the VTL dataset ‘DF1(1.0.0)/POPULATION.USA’ would contain all the observations of DF1(1.0.0) having INDICATOR = POPULATION and COUNTRY = USA.
422 422  
423 -In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e.
411 +In order to obtain the data structure of these VTL Data Sets from the SDMX one, it is assumed that the SDMX DimensionComponents on which the mapping is based are dropped, i.e. not maintained in the VTL data structure; this is possible because their values are fixed for each one of the invoked VTL Data Sets{{footnote}}If these DimensionComponents would not be dropped, the various VTL Data Sets resulting from this kind of mapping would have non-matching values for the Identifiers corresponding to the mapping Dimensions (e.g. POPULATION and COUNTRY). As a consequence, taking into account that the typical binary VTL operations at dataset level (+, -, *, / and so on) are executed on the observations having matching values for the identifiers, it would not be possible to compose the resulting VTL datasets one another (e.g. it would not be possible to calculate the population ratio between USA and CANADA).{{/footnote}}. After that, the mapping method from SDMX to VTL specified for the Dataflow DF1(1.0.0) is applied (i.e. basic, pivot …).
424 424  
425 -basic, pivot …).
413 +In the example above, for all the datasets of the kind ‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
426 426  
427 -In the example above, for all the datasets of the kind
428 -
429 -‘DF1(1.0.0)///INDICATORvalue//.//COUNTRYvalue//’, the dimensions INDICATOR and COUNTRY would be dropped so that the data structure of all the resulting VTL Data Sets would have the identifier TIME_PERIOD only.
430 -
431 431  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:
432 432  
433 -‘DF1(1.0.0)/POPULATION.USA’ :=
417 +[[image:1747388275998-621.png]]
434 434  
435 -DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“USA” ];
436 -
437 -‘DF1(1.0.0)/POPULATION.CANADA’ :=
438 -
439 -DF1(1.0.0) [ sub INDICATOR=“POPULATION”, COUNTRY=“CANADA” ];
440 -
441 -… … …
442 -
443 443  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}}
444 444  
445 445  In the direction from SDMX to VTL it is allowed to omit the value of one or more
... ... @@ -450,10 +450,8 @@
450 450  
451 451  This is equivalent to the application of the VTL “sub” operator only to the identifier //INDICATOR//:
452 452  
453 -‘DF1(1.0.0)/POPULATION.’ :=
429 +[[image:1747388244829-693.png]]
454 454  
455 -DF1(1.0.0) [ sub INDICATOR=“POPULATION” ];
456 -
457 457  Therefore the VTL Data Set ‘DF1(1.0.0)/POPULATION.’ would have the identifiers COUNTRY and TIME_PERIOD.
458 458  
459 459  Heterogeneous invocations of the same Dataflow are allowed, i.e. omitting different
... ... @@ -479,54 +479,18 @@
479 479  
480 480  Some examples follow, for some specific values of INDICATOR and COUNTRY:
481 481  
482 -‘DF2(1.0.0)/GDPPERCAPITA.USA’ <- expression11; ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ <- expression12;
456 +[[image:1747388222879-916.png]]
483 483  
484 -… … …
458 +[[image:1747388206717-256.png]]
485 485  
486 -‘DF2(1.0.0)/POPGROWTH.USA’ <- expression21;
487 -
488 -‘DF2(1.0.0)/POPGROWTH.CANADA’ <- expression22;
489 -
490 -… … …
491 -
492 492  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:
493 493  
494 -VTL dataset INDICATOR value COUNTRY value
462 +[[image:1747388148322-387.png]]
495 495  
496 -‘DF2(1.0.0)/GDPPERCAPITA.USA’ GDPPERCAPITA USA
497 -
498 -‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ GDPPERCAPITA CANADA … … …
499 -
500 -‘DF2(1.0.0)/POPGROWTH.USA’ POPGROWTH USA
501 -
502 -‘DF2(1.0.0)/POPGROWTH.CANADA’ POPGROWTH CANADA
503 -
504 -… … …
505 -
506 506  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:
507 507  
508 -DF2bis_GDPPERCAPITA_USA := ‘DF2(1.0.0)/GDPPERCAPITA.USA’ [calc identifier INDICATOR := ”GDPPERCAPITA”, identifier COUNTRY := ”USA”];
466 +[[image:1747388179021-814.png]]
509 509  
510 -DF2bis_GDPPERCAPITA_CANADA := ‘DF2(1.0.0)/GDPPERCAPITA.CANADA’ [calc identifier INDICATOR:=”GDPPERCAPITA”, identifier COUNTRY:=”CANADA”]; … … …
511 -
512 -DF2bis_POPGROWTH_USA := ‘DF2(1.0.0)/POPGROWTH.USA’
513 -
514 -[calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”USA”];
515 -
516 -DF2bis_POPGROWTH_CANADA’ := ‘DF2(1.0.0)/POPGROWTH.CANADA’ [calc identifier INDICATOR := ”POPGROWTH”, identifier COUNTRY := ”CANADA”]; … … …
517 -
518 -DF2(1.0) <- UNION (DF2bis_GDPPERCAPITA_USA’,
519 -
520 -DF2bis_GDPPERCAPITA_CANADA’,
521 -
522 -… ,
523 -
524 -DF2bis_POPGROWTH_USA’,
525 -
526 -DF2bis_POPGROWTH_CANADA’
527 -
528 -…);
529 -
530 530  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
531 531  
532 532  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.
... ... @@ -540,37 +540,30 @@
540 540  With reference to the VTL “model for Variables and Value domains”, the following additional mappings have to be considered:
541 541  
542 542  (% style="width:1170.29px" %)
543 -|**VTL**|(% style="width:754px" %)**SDMX**
544 -|**Data Set Component**|(% style="width:754px" %)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}}
545 -|**Represented Variable**|(% style="width:754px" %)(((
481 +|(% style="width:392px" %)**VTL**|(% style="width:776px" %)**SDMX**
482 +|(% style="width:392px" %)**Data Set Component**|(% style="width:776px" %)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}}
483 +|(% style="width:392px" %)**Represented Variable**|(% style="width:776px" %)(((
546 546  **Concept** with a definite
547 547  
548 548  Representation
549 549  )))
550 -|**Value Domain**|(% style="width:754px" %)(((
551 -**Representation** (see the Structure
552 -
553 -Pattern in the Base Package)
488 +|(% style="width:392px" %)**Value Domain**|(% style="width:776px" %)(((
489 +**Representation** (see the Structure Pattern in the Base Package)
554 554  )))
555 -|**Enumerated Value Domain / Code List**|(% style="width:754px" %)**Codelist**
556 -|**Code**|(% style="width:754px" %)(((
491 +|(% style="width:392px" %)**Enumerated Value Domain / Code List**|(% style="width:776px" %)**Codelist**
492 +|(% style="width:392px" %)**Code**|(% style="width:776px" %)(((
557 557  **Code** (for enumerated
558 558  
559 559  DimensionComponent, Measure, DataAttribute)
560 560  )))
561 -|**Described Value Domain**|(% style="width:754px" %)(((
562 -non-enumerated** Representation**
563 -
564 -(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
497 +|(% style="width:392px" %)**Described Value Domain**|(% style="width:776px" %)(((
498 +non-enumerated** Representation **(having Facets / ExtendedFacets, see the Structure Pattern in the Base Package)
565 565  )))
566 -|**Value**|(% style="width:754px" %)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
567 -| |(% style="width:754px" %)(((
568 -to a valid **value **(for non-enumerated** **Representations)
569 -)))
570 -|**Value Domain Subset / Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
571 -|**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
572 -|**Described Value Domain Subset / Described Set**|(% style="width:754px" %)This abstraction does not exist in SDMX
573 -|**Set list**|(% style="width:754px" %)This abstraction does not exist in SDMX
500 +|(% style="width:392px" %)**Value**|(% style="width:776px" %)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)
501 +|(% style="width:392px" %)**Value Domain Subset / Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
502 +|(% style="width:392px" %)**Enumerated Value Domain Subset / Enumerated Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
503 +|(% style="width:392px" %)**Described Value Domain Subset / Described Set**|(% style="width:776px" %)This abstraction does not exist in SDMX
504 +|(% style="width:392px" %)**Set list**|(% style="width:776px" %)This abstraction does not exist in SDMX
574 574  
575 575  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).
576 576  
1747388148322-387.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
1747388179021-814.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +66.2 KB
Content
1747388206717-256.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +10.3 KB
Content
1747388222879-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +9.9 KB
Content
1747388244829-693.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +7.4 KB
Content
1747388275998-621.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +19.2 KB
Content