Skip to Content

Changes for page Part VI. Samples

Last modified by Elena on 2025/09/10 11:19
From version 5.5
edited by Helena
on 2025/07/03 11:29
Change comment: There is no comment for this version
To version 5.2
edited by Helena
on 2025/07/03 11:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -91,7 +91,7 @@
91 91  
92 92  ## Geospatial##
93 93  
94 -**##geospatial geocomponents.xml##**
94 +**##geospatial geocomponents.xml ##**
95 95  
96 96  An example of the use of the "GeospatialInformation" representation type. The GeospatialInformation type can be assigned to a Dimension, DataAttribute, MetadataAttribute or a Measure in conjunction with the "GEO" role. Values of are included directly in data messages or metadata reports and must conform to the Geo Feature Set syntax defined in Section 6 of the Technical Specifications.
97 97  
... ... @@ -101,7 +101,7 @@
101 101  * The AREA attribute has the SDMX Concept Role "GEO" defined identifying it generally as a geospatial component following guidelines.
102 102  * The AREA attribute also carries a LocalRepresentation with textType="GeospatialInformation".
103 103  
104 -**##geospatial geographiccodelist.xml##**
104 +### geospatial geographiccodelist.xml ##
105 105  
106 106  An example of the definition of GeographicCodelists, a specialised form of code list introduced in SDMX 3.0. GeographicCodelists are used in the same was as simple code lists to assign a closed enumerated list of values to a component. The difference being that the definition of each GeoFeatureSetCode explicitly specifies the geospatial features to which it relates as a string expression using the Geo Feature Set syntax set out in Section 6 of the Technical Specifications. As with any other coded component, data sets only contain the codes and not the Feature Set information itself. Thus, GeoFeatureSetCodes act as pointers to the Geo Feature Set information held in the GeographicCodelist.
107 107  
... ... @@ -112,7 +112,7 @@
112 112  * Three illustrative GeoFeatureSetCodes have been defined with IDs "A1", "A2" and "A3".
113 113  * The GeoFeatureSetCode Value attribute specifies the geospatial features to which the code relates as a string expression. Note that the values shown are conceptual examples and are not syntactically valid Geo Feature Set expressions.
114 114  
115 -**##geospatial geogridcodelist.xml##**
115 +### geospatial geogridcodelist.xml ##
116 116  
117 117  An example of the definition of GeoGridCodelists, the second specialised form of codelist for modelling gridded geographies.
118 118  Like GeographicCodelists, GeoGridCodelists act in the same way as simple code lists to assign a closed enumerated list of values to a component.
... ... @@ -126,19 +126,19 @@
126 126  
127 127  ## VTL Transformations##
128 128  
129 -##**VTL Sample 1.xml**##
129 +### VTL Sample 1.xml ##
130 130  
131 131  Illustrates the use of VTL Rulesets to validate an SDMX dataflow. The validation process adds additional identifiers and measures to the resulting VTL dataset indicating, on a row by row basis the validation rule applied and the outcome in terms of a valid / invalid. If invalid, details of the error found and its severity are added.
132 132  
133 133  A second transformation takes the resulting dataset filtering out high-severity validation errors and persists the result back to a SDMX dataflow using VTL mappings.
134 134  
135 -##**VTL Sample 2.xml**##
135 +### VTL Sample 2.xml ##
136 136  
137 137  Illustrates aggregation of an SDMX dataflow using VTL hierarchical rulesets, filtering and user defined operators.
138 138  
139 139  After the initial aggregation, unaggregated observations removed are removed from the result dataset. A user defined operator is subsequently applied to calculate a percentage measure with the final persistent result mapped from VTL to a SDMX dataflow.
140 140  
141 -##**VTL Sample 3.xml**##
141 +### VTL Sample 3.xml ##
142 142  
143 143  Illustrates the calculation of a GDP per capita dataset from an input mapped SDMX dataflow containing GDP and population indicators on a country by country basis.
144 144  
... ... @@ -149,13 +149,13 @@
149 149  The Structure Specific Data message is characterised by the XML elements and attributes being derived from the data structure definition of the data set. This provides two main benefits:
150 150  
151 151  1. The message content is relatively compact.
152 -1. It is possible to use an XML schema to validate that the data set contains the correct values as defined by the data structure definition and any constraints attached to the dataflow, data structure definition or data provision agreement.
152 +2. It is possible to use an XML schema to validate that the data set contains the correct values as defined by the data structure definition and any constraints attached to the dataflow, data structure definition or data provision agreement.
153 153  
154 154  The samples therefore include both the Structure Specific Data XML, and a corresponding example validation schema XSD. Successful schema validation confirms that the XML is both a valid Structure Specific Data message, and the content is valid according to the SDMX structural metadata.
155 155  
156 156  == Aggregated Time Series with Simple Data Attributes ==
157 157  
158 -##**ECB EXR.xml**##
158 +### ECB EXR.xml ##
159 159  
160 160  Structure specific data message.
161 161  
... ... @@ -167,7 +167,7 @@
167 167  
168 168  Note that a structure specific namespace ns1 is defined using xsi:schemalocation to reference the validation schema location, in this case ECB_EXR_Dataflow.xsd.
169 169  
170 -**##ECB EXR Dataflow.xsd##**
170 +### ECB EXR Dataflow.xsd ##
171 171  
172 172  Structure-specific schema for validating the dataset.
173 173  
... ... @@ -177,7 +177,7 @@
177 177  
178 178  Complex attributes include those with multilingual text and arrays of values.
179 179  
180 -**##EXB EXR CA.xml##**
180 +### EXB EXR CA.xml ##
181 181  
182 182  Structure specific data message.
183 183  
... ... @@ -193,7 +193,7 @@
193 193  
194 194  Note that a structure specific namespace ns1 is defined using xsi:schemalocation to reference the validation schema location, in this case ECB_EXR_Dataflow.xsd.
195 195  
196 -##**ECB EXR CA Dataflow.xsd**##
196 +### ECB EXR CA Dataflow.xsd ##
197 197  
198 198  Structure specific schema for validating the dataset.
199 199  
... ... @@ -201,7 +201,7 @@
201 201  
202 202  Complex types based on the abstract dsd:CompType are defined for each complex attribute.
203 203  
204 -##**ECB EXR CA DSD.xml**##
204 +### ECB EXR CA DSD.xml ##
205 205  
206 206  Structure message describing the Data Structure Definition for the above dataflow illustrating, in particular, the definition of complex attributes:
207 207