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

Summary

Details

Page properties
Content
... ... @@ -80,9 +80,9 @@
80 80  
81 81  For example, by using the URN, the VTL Transformation that sums two SDMX Dataflows DF1 and DF2 and assigns the result to a third persistent Dataflow DFR, assuming that DF1, DF2 and DFR are the maintainedobject-id of the three Dataflows, that their version is 1.0.0 and their Agency is AG, would be written as{{footnote}}Since these references to SDMX objects include non-permitted characters as per the VTL ID notation, they need to be included between single quotes, according to the VTL rules for irregular names.{{/footnote}}:
82 82  
83 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85 ->(% style="font-size:16px" %) 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
83 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' <-
84 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
85 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
86 86  
87 87  === 12.2.3 Abbreviation of the URN ===
88 88  
... ... @@ -97,7 +97,8 @@
97 97  ** "codelist" for the class Codelist.
98 98  * The class-name can be omitted as it can be deduced from the VTL invocation. In particular, starting from the VTL class of the invoked artefact (e.g. dataset, component, identifier, measure, attribute, variable, valuedomain), which is known given the syntax of the invoking VTL operator{{footnote}}For the syntax of the VTL operators see the VTL Reference Manual{{/footnote}}, the SDMX class can be deduced from the mapping rules between VTL and SDMX (see the section "Mapping between VTL and SDMX" hereinafter){{footnote}}In case the invoked artefact is a VTL component, which can be invoked only within the invocation of a VTL data set (SDMX Dataflow), the specific SDMX class-name (e.g. Dimension, TimeDimension, Measure or DataAttribute) can be deduced from the data structure of the SDMX Dataflow, which the component belongs to.{{/footnote}}.
99 99  * If the agency-id is not specified, it is assumed by default equal to the agency-id of the TransformationScheme, UserDefinedOperatorScheme or RulesetScheme from which the artefact is invoked. For example, the agencyid can be omitted if it is the same as the invoking TransformationScheme and cannot be omitted if the artefact comes from another agency{{footnote}}If the Agency is composite (for example AgencyA.Dept1.Unit2), the agency is considered different even if only part of the composite name is different (for example AgencyA.Dept1.Unit3 is a different Agency than the previous one). Moreover the agency-id cannot be omitted in part (i.e., if a TransformationScheme owned by AgencyA.Dept1.Unit2 references an artefact coming from AgencyA.Dept1.Unit3, the specification of the agency-id becomes mandatory and must be complete, without omitting the possibly equal parts like AgencyA.Dept1){{/footnote}}. Take also into account that, according to the VTL consistency rules, the agency of the result of a Transformation must be the same as its TransformationScheme, therefore the agency-id can be omitted for all the results (left part of Transformation statements).
100 -* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted: o if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
100 +* As for the maintainedobject-id, this is essential in some cases while in other cases it can be omitted:
101 +** if the referenced artefact is a Dataflow, which is a maintainable class, the maintainedobject-id is the dataflow-id and obviously cannot be omitted;
101 101  ** if the referenced artefact is a Dimension, TimeDimension, Measure, DataAttribute, which are not maintainable and belong to the DataStructure maintainable class, the maintainedobject-id is the dataStructure-id and can be omitted, given that these components are always invoked within the invocation of a Dataflow, whose dataStructure-id can be deduced from the SDMX structural definitions;
102 102  ** if the referenced artefact is a Concept, which is not maintainable and belong to the ConceptScheme maintainable class, the maintained object is the conceptScheme-id and cannot be omitted;
103 103  ** if the referenced artefact is a Codelist, which is a maintainable class, the maintainedobject-id is the codelist-id and obviously cannot be omitted.
... ... @@ -109,51 +109,47 @@
109 109  
110 110  For example, the full formulation that uses the complete URN shown at the end of the previous paragraph:
111 111  
112 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
113 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DFR(1.0.0)' :=
114 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
115 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
113 113  
114 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF1(1.0.0)' +
115 -
116 -'urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=AG:DF2(1.0.0)'
117 -
118 118  by omitting all the non-essential parts would become simply:
119 119  
120 -DFR := DF1 + DF2
119 +> DFR  : =  DF1 + DF2
121 121  
122 122  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}}:
123 123  
124 -'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
123 +> 'urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AG:CL_FREQ(1.0.0)'
125 125  
126 126  if the Codelist is referenced from a RulesetScheme belonging to the agency AG, omitting all the optional parts, the abbreviated reference would become simply^^19^^:
127 127  
128 -CL_FREQ
127 +> CL_FREQ
129 129  
130 130  As for the references to the components, it can be enough to specify the componentId, given that the dataStructure-Id can be omitted. An example of non-abbreviated reference, if the data structure is DST1 and the component is SECTOR, is the following:
131 131  
132 -'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S
131 +> 'urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=AG:DST1(1.0.0).S ECTOR'
133 133  
134 -ECTOR'
135 -
136 136  The corresponding fully abbreviated reference, if made from a TransformationScheme belonging to AG, would become simply:
137 137  
138 -SECTOR
135 +> SECTOR
139 139  
140 140  For example, the Transformation for renaming the component SECTOR of the Dataflow DF1 into SEC can be written as{{footnote}}The result DFR(1.0.0) is be equal to DF1(1.0.0) save that the component SECTOR is called SEC{{/footnote}}:
141 141  
142 -'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
139 +> 'DFR(1.0.0)' := 'DF1(1.0.0)' [rename SECTOR to SEC]
143 143  
144 144  In the references to the Concepts, which can exist for example in the definition of the VTL Rulesets, at least the conceptScheme-id and the concept-id must be specified.
145 145  
146 146  An example of non-abbreviated reference, if the conceptScheme-id is CS1 and the concept-id is SECTOR, is the following:
147 147  
148 -'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
145 +> 'urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=AG:CS1(1.0.0).SECTOR'
149 149  
150 150  The corresponding fully abbreviated reference, if made from a RulesetScheme belonging to AG, would become simply:
151 151  
152 -CS1(1.0.0).SECTOR
149 +> CS1(1.0.0).SECTOR
153 153  
154 154  The Codes and in general all the Values can be written without any other specification, for example, the transformation to check if the values of the measures of the Dataflow DF1 are between 0 and 25000 can be written like follows:
155 155  
156 -'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
153 +> 'DFR(1.0.0)' := between ( 'DF1(1.0.0)', 0, 25000 )
157 157  
158 158  The artefact (Component, Concept, Codelist …) which the Values are referred to can be deduced from the context in which the reference is made, taking also into account the VTL syntax. In the Transformation above, for example, the values 0 and 2500 are compared to the values of the measures of DF1(1.0.0).
159 159  
... ... @@ -209,11 +209,12 @@
209 209  
210 210  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:
211 211  
212 -|**SDMX**|**VTL**
213 -|Dimension|(Simple) Identifier
214 -|TimeDimension|(Time) Identifier
215 -|Measure|Measure
216 -|DataAttribute|Attribute
209 +(% style="width:468.294px" %)
210 +|(% style="width:196px" %)**SDMX**|(% style="width:269px" %)**VTL**
211 +|(% style="width:196px" %)Dimension|(% style="width:269px" %)(Simple) Identifier
212 +|(% style="width:196px" %)TimeDimension|(% style="width:269px" %)(Time) Identifier
213 +|(% style="width:196px" %)Measure|(% style="width:269px" %)Measure
214 +|(% style="width:196px" %)DataAttribute|(% style="width:269px" %)Attribute
217 217  
218 218  The SDMX DataAttributes, in VTL they are all considered "at data point / observation level" (i.e. dependent on all the VTL Identifiers), because VTL does not have the SDMX AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, dimension or set or group of dimensions, whole data set).
219 219