Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/23 22:08
Change comment: There is no comment for this version
To version 11.1
edited by Artur
on 2025/07/14 10:19
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Tags
... ... @@ -1,0 +1,1 @@
1 +Attribute|Attribute relationship|Category|Category scheme|Code|Code list|Concept|Concept scheme|Data provider|Data provider scheme|Data set|Data source|Data structure definition|Dataflow|Decimals|Dimension|Measure|Metadata repository|Metadata structure definition|Provision agreement|Reference metadata|SDMX Registry|SDMX-ML|Series key|Statistical data and metadata exchange|Structural metadata|Title
Content
... ... @@ -6,7 +6,7 @@
6 6  
7 7  The scope of this Chapter is to show the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] interactions with the Registry, database, and [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] for the use case scenario outlined in Chapter 3. The scenario is repeated below.
8 8  
9 -The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] examples used are (% style="color:#e74c3c" %)version(%%) 2.1.
9 +The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] examples used are version 2.1.
10 10  
11 11  == 16.2 Scenario ==
12 12  
... ... @@ -25,7 +25,7 @@
25 25  |3|(% style="width:670px" %)These choices are logical choices, built from the [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] selections.
26 26  |5|(% style="width:670px" %)The logical choice is formatted as an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data query. This is passed to the Data Base which responds with an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
27 27  |6|(% style="width:670px" %)[[Reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] relevant to the data returned is retrieved from a [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]].
28 -|7|(% style="width:670px" %)The data and metadata are passed to a visualization tool to display the data in tables, charts, graphs, (% style="color:#e74c3c" %)maps(%%) etc. Often a download is offered in various formats. The download options often include also the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or MSD.
28 +|7|(% style="width:670px" %)The data and metadata are passed to a visualization tool to display the data in tables, charts, graphs, maps etc. Often a download is offered in various formats. The download options often include also the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or MSD.
29 29  
30 30  == 16.3 Structural Metadata ==
31 31  
... ... @@ -75,7 +75,8 @@
75 75  (% style="text-align: center;" %)
76 76  **{{id name="image_49"/}}Figure 49: User Case - Create Database Tables from DSD**
77 77  
78 -The following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] is extracted from the Registry using the REST query http:~/~/[ ws-entry-point]/DataStructure_ECB/ECB_EXR1
78 +The following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] is extracted from the Registry using the REST query
79 +http:~/~/[ ws-entry-point]/DataStructure_ECB/ECB_EXR1
79 79  
80 80  (% class="wikigeneratedid" id="HDimensions" %)
81 81  **Dimensions**
... ... @@ -87,9 +87,9 @@
87 87  (% class="wikigeneratedid" id="HNotes" %)
88 88  **Notes**
89 89  
90 -1. A Dimension can state its position in the key, but the actual sequence is defined by the sequence in the <DimensionList> i.e. the inferred sequence in the <DimensionList> takes precedence over the value of the position attribute.
91 -1. This DSD is converted from version 2.0. The version 2.0 Concepts were standalone in the form  <Concept agencyID=”ECB” version=”1.0”/>
92 -1. The standalone concept is not supported in 2.1 and any standalone concept is placed in a Concept Scheme with the Id “STANDALONE_CONCEPT_SCHEME” of the version corresponding to the version of the original standalone concept.
91 +1. A [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can state its position in the key, but the actual sequence is defined by the sequence in the i.e. the inferred sequence in the  takes precedence over the value of the position attribute.
92 +1. This [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is converted from version 2.0. The version 2.0 [[Concepts>>doc:sdmx:Glossary.Concept.WebHome]] were standalone in the form  <[[Concept>>doc:sdmx:Glossary.Concept.WebHome]] agencyID=”ECB” version=”1.0”/>
93 +1. The standalone [[concept>>doc:sdmx:Glossary.Concept.WebHome]] is not supported in 2.1 and any standalone [[concept>>doc:sdmx:Glossary.Concept.WebHome]] is placed in a [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] with the Id “STANDALONE_CONCEPT_SCHEME” of the version corresponding to the version of the original standalone [[concept>>doc:sdmx:Glossary.Concept.WebHome]].
93 93  
94 94  (% class="wikigeneratedid" id="HGroup-1" %)
95 95  **Group**
... ... @@ -99,8 +99,8 @@
99 99  
100 100  **Notes:**
101 101  
102 -1. A Group in version 2.1 plays the same role as it does in version 2.0 except that it does not group Series in the data set. The Group in version 2.1 is used solely as a mechanism to attach Attributes in the data set.
103 -1. The Group in version 2.1 is retained for compatibility with version 2.0 and for avoiding repetition in the new Attribute Relationship construct which is introduced in version 2.1.
103 +1. A Group in version 2.1 plays the same role as it does in version 2.0 except that it does not group Series in the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. The Group in version 2.1 is used solely as a mechanism to attach [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
104 +1. The Group in version 2.1 is retained for compatibility with version 2.0 and for avoiding repetition in the new [[Attribute Relationship>>doc:sdmx:Glossary.Attribute relationship.WebHome]] construct which is introduced in version 2.1.
104 104  
105 105  (% class="wikigeneratedid" id="HAttributes" %)
106 106  **Attributes**
... ... @@ -109,15 +109,15 @@
109 109  
110 110  [[image:image-20250318221512-11.jpeg||data-xwiki-image-style-alignment="center"]]
111 111  
112 -Note that for brevity only the XML of the DECIMALS (relationship to a group) COLLECTION (relationship to a set of Dimensions) and OBS_CONF (relationship to the Primary Measure) are shown in full.
113 +Note that for brevity only the XML of the [[DECIMALS>>doc:sdmx:Glossary.Decimals.WebHome]] (relationship to a group) COLLECTION (relationship to a set of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]) and OBS_CONF (relationship to the Primary [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]) are shown in full.
113 113  
114 114  (% class="wikigeneratedid" id="HNotes-1" %)
115 115  **Notes**
116 116  
117 -1. The Attribute has a relationship to either a data set of one or more Dimensions as described in Chapter 4.
118 -1. DECIMALS has a relationship to a Group with the Id of Group.
119 -1. COLLECTION has a relationship to a set of Dimensions – in this case this is, in reality, the series key as this has been converted from version 2.0. It is possible for an attribute to have a relationship with just one, a few, or all of the Dimensions.
120 -1. OBS_CONF has a relationship with the Primary Measure.
118 +1. The [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has a relationship to either a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] of one or more [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] as described in Chapter 4.
119 +1. [[DECIMALS>>doc:sdmx:Glossary.Decimals.WebHome]] has a relationship to a Group with the Id of Group.
120 +1. COLLECTION has a relationship to a set of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] – in this case this is, in reality, the [[series key>>doc:sdmx:Glossary.Series key.WebHome]] as this has been converted from version 2.0. It is possible for an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] to have a relationship with just one, a few, or all of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]].
121 +1. OBS_CONF has a relationship with the Primary [[Measure>>doc:sdmx:Glossary.Measure.WebHome]].
121 121  
122 122  (% class="wikigeneratedid" id="HMeasure" %)
123 123  **Measure**
... ... @@ -124,7 +124,7 @@
124 124  
125 125  [[image:image-20250318221512-12.jpeg||data-xwiki-image-style-alignment="center"]]
126 126  
127 -A typical database schema that can be set up using this DSD is shown below.
128 +A typical database schema that can be set up using this [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is shown below.
128 128  
129 129  (% class="wikigeneratedid" id="HSeriesKeyTable" %)
130 130  **Series Key Table**
... ... @@ -158,7 +158,7 @@
158 158  (% style="text-align: center;" %)
159 159  **{{id name="image_53"/}}Figure 53: Loading an SDMX Dataset into a Database **
160 160  
161 -The following is an extract from the SDMX dataset.
162 +The following is an extract from the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
162 162  
163 163  [[image:image-20250319123255-1.png||data-xwiki-image-style-alignment="center"]]
164 164  
... ... @@ -169,11 +169,11 @@
169 169  (% class="wikigeneratedid" id="HNotes-2" %)
170 170  **Notes**
171 171  
172 -1. The reference to the DSD is given in the message header and given a local structureId
173 -1. The local structureId (DSD) is referenced from the DataSet
173 +1. The reference to the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is given in the message header and given a local structureId
174 +1. The local structureId ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]) is referenced from the [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]
174 174  1. A Group does not contain Series in version 2.1: it is used solely to declare attributes
175 -1. The first <Obs> in the first <Series> has an OBS_VALUE of “NaN”. This is an XML expression that declared a value of “not a number”, thus allowing a “missing value” to be declared.
176 -1. A dataset can contain observations from different frequencies.
176 +1. The first in the first has an OBS_VALUE of “NaN”. This is an XML expression that declared a value of “not a number”, thus allowing a “missing value” to be declared.
177 +1. A [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] can contain observations from different frequencies.
177 177  
178 178  The diagrams below show the database content based on the schema created.
179 179  
... ... @@ -201,7 +201,7 @@
201 201  
202 202  [[image:image-20250318221512-19.jpeg||data-xwiki-image-style-alignment="center"]]
203 203  
204 -The SDMX web service of the database can now be searched for in the Registry.
205 +The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web service of the database can now be searched for in the Registry.
205 205  
206 206  === 16.4.4 Retrieve and Visualise Category Scheme and Dataflows ===
207 207  
... ... @@ -210,7 +210,7 @@
210 210  (% style="text-align: center;" %)
211 211  **{{id name="image_54"/}}Figure 54: Building a Search Screen from Structural Metadata**
212 212  
213 -The following REST query will return the Category Scheme and Categorisations that reference any of the Categories in the scheme.
214 +The following REST query will return the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] and Categorisations that reference any of the [[Categories>>doc:sdmx:Glossary.Category.WebHome]] in the scheme.
214 214  
215 215  [[http:~~/~~/ ~[ws-entry-point~]/categoryscheme/ECB/SDW_ECONOMIC_CONCEPTS/1.0?references=parents>>http:// [ws-entry-point]/categoryscheme/ECB/SDW_ECONOMIC_CONCEPTS/1.0?references=parents||rel="noopener noreferrer" target="_blank"]]
216 216  
... ... @@ -218,11 +218,11 @@
218 218  
219 219  [[image:image-20250318221512-22.jpeg||data-xwiki-image-style-alignment="center"]]
220 220  
221 -The application will now retrieve the Dataflows in the list of Categorisations – in this case there is only one – effective exchange rates.
222 +The application will now retrieve the [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] in the list of Categorisations – in this case there is only one – effective exchange rates.
222 222  
223 -The following REST query will return the dataflow.
224 +The following REST query will return the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
224 224  
225 -[[http:~~/~~/ ~[ws-entry-point~]/dataflow/ECB/2034482/1.0>>http:// [ws-entry-point]/dataflow/ECB/2034482/1.0||rel="noopener noreferrer" target="_blank"]]
226 +[[http:~~/~~/ ~[ws-entry-point~]/dataflow/ECB/2034482/1.0>>http://[ws-entry-point]/dataflow/ECB/2034482/1.0||rel="noopener noreferrer" target="_blank"]]
226 226  
227 227  [[image:image-20250318221512-23.jpeg||data-xwiki-image-style-alignment="center"]]
228 228  
... ... @@ -230,9 +230,9 @@
230 230  
231 231  1. Query application queries the Registry for the Provision Agreement.
232 232  1. Query application queries the Registry for data Registrations.
233 -1. If there is a data source registered then the dataflow is displayed and can be selected.
234 +1. If there is a [[data source>>doc:sdmx:Glossary.Data source.WebHome]] registered then the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] is displayed and can be selected.
234 234  
235 -The following REST query will return any provision agreements referenced from the dataflow
236 +The following REST query will return any [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] referenced from the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]
236 236  
237 237  [[http:~~/~~/~[ws-entry-point~]/dataflow/ECB/2034482/1.0?references=provisionagreement>>http://[ws-entry-point]/dataflow/ECB/2034482/1.0?references=provisionagreement||rel="noopener noreferrer" target="_blank"]]
238 238  
... ... @@ -241,22 +241,24 @@
241 241  (% class="wikigeneratedid" id="HNotes-3" %)
242 242  **Notes**
243 243  
244 -~1. The <URN> contains the same identification information as the individual attributes in the <Ref> tag in the context of the <Dataflow> and <Structure> tags (the <Dataflow> identifies that the <Structure> is a DataStructure).
245 +~1. The contains the same identification information as the individual [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the tag in the context of the <Dataflow> and tags (the <Dataflow> identifies that the is a DataStructure).
245 245  
246 -The following REST query will return the Data Provider Scheme that contains the Data Provider connected to the Provision Agreement. Note that this is not necessary in order to query for the data unless the Data Provider contains information required by the query application (such as the name of the Data Provider).
247 +The following REST query will return the [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]] that contains the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] connected to the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]. Note that this is not necessary in order to query for the data unless the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] contains information required by the query application (such as the name of the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]).
247 247  
248 -[[http:~~/~~/~[ws-entry-point~]/dataprovider/ECB>>http://[ws-entry-point]/dataprovider/ECB||rel="noopener noreferrer" target="_blank"]]
249 +[[http:~~/~~/~[ws-entry-point~]/dataprovider/ECB>>http:// [ws-entry-point]/dataprovider/ECB||rel="noopener noreferrer" target="_blank"]]
249 249  
250 250  (% class="wikigeneratedid" id="HNotes-4" %)
251 251  **Notes**
252 252  
253 -~1. As an Agency can have only one Data Provider Scheme and this has a mandatory Id of DATA_PROVIDER_SCHEME and must be version 1.0 there is no need to specify any other parameters to the REST query.
254 +1.
254 254  
255 -This returns the following as part of the Data Provider Scheme.
256 +As an Agency can have only one [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]] and this has a mandatory Id of DATA_PROVIDER_SCHEME and must be (% style="color:#e74c3c" %)version(%%) 1.0 there is no need to specify any other parameters to the REST query.
256 256  
258 +This returns the following as part of the [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]].
259 +
257 257  [[image:image-20250318221512-25.jpeg||data-xwiki-image-style-alignment="center"]]
258 258  
259 -The following Registry query will return the REST data source referenced in a Registration for the Provision Agreement
262 +The following Registry query will return the REST [[data source>>doc:sdmx:Glossary.Data source.WebHome]] referenced in a Registration for the Provision Agreement
260 260  
261 261  [[image:image-20250318221512-26.jpeg||data-xwiki-image-style-alignment="center"]]
262 262  
... ... @@ -268,7 +268,7 @@
268 268  
269 269  [[http:~~/~~/~[ws-entry-point~] /~[RESTParameters~]>>http://[ws-entry-point] /[RESTParameters||rel="noopener noreferrer" target="_blank"]]]
270 270  
271 -Where [ws-entry-point] is the URL of the SDMX web service and [RESTParameters] are the query parameters.
274 +Where [ws-entry-point] is the URL of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web service and [RESTParameters] are the query parameters.
272 272  
273 273  The application can now visualize the information it has retrieved from the Registry in a way that is meaningful to the user. An example visualization is shown below.
274 274  
... ... @@ -277,13 +277,13 @@
277 277  (% style="text-align: center;" %)
278 278  **{{id name="image_55"/}}Figure 55: Example Query Screen Built from SDMX Category Scheme and Dataflows**
279 279  
280 -The user will select the Category and this then shows the Dataflows that are available and which have data available for query (i.e. there is a Registration). There can be many such Dataflows but in this example there is only one.
283 +The user will select the [[Category>>doc:sdmx:Glossary.Category.WebHome]] and this then shows the [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] that are available and which have data available for query (i.e. there is a Registration). There can be many such [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] but in this example there is only one.
281 281  
282 282  === 16.4.5 Build Dimension Selection and Logical Query ===
283 283  
284 284  [[image:image-20250318221512-29.jpeg||data-xwiki-image-style-alignment="center"]]
285 285  
286 -Clicking on the Dataflow will cause the query application to query the Registry for the DSD associated to the Dataflow. The Dimensions and the relevant codes associated with the Dimensions are then shown for detailed data selections.
289 +Clicking on the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] will cause the query application to query the Registry for the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] associated to the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. The [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] and the relevant [[codes>>doc:sdmx:Glossary.Code.WebHome]] associated with the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] are then shown for detailed data selections.
287 287  
288 288  [[image:image-20250318221512-30.jpeg||data-xwiki-image-style-alignment="center"]]
289 289  
... ... @@ -290,13 +290,13 @@
290 290  (% style="text-align: center;" %)
291 291  **{{id name="image_56"/}}Figure 56: Selection Screen build from SDMX DSD**
292 292  
293 -The user can click on each of the Dimensions and the relevant code selections are displayed. Note that in the example above the application is assumed to have queries for all the keys so that it can process them in order to grey-out the Dimension selections for which there is no data. These are greyed-out based on the current selections in the other Dimensions. This shows the importance of content constraints in a web dissemination system, as they can be used to guide the user to make only the selections that will return data. The same result can be achieved if these constraints are available for query (e.g. in a Registry), but this is a less effective way of processing if the contenrts of the database are dynamic.
296 +The user can click on each of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] and the relevant [[code>>doc:sdmx:Glossary.Code.WebHome]] selections are displayed. Note that in the example above the application is assumed to have queries for all the keys so that it can process them in order to grey-out the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] selections for which there is no data. These are greyed-out based on the current selections in the other [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. This shows the importance of content [[constraints>>path:/xwiki/wiki/sdmx/get/Methodology/SDMX%202.1%20User%20Guide/6%20Data%20and%20Structure%20Query?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=doc&reference=Glossary.Constraint.WebHome&typed=true]] in a web dissemination system, as they can be used to guide the user to make only the selections that will return data. The same result can be achieved if these [[constraints>>path:/xwiki/wiki/sdmx/get/Methodology/SDMX%202.1%20User%20Guide/6%20Data%20and%20Structure%20Query?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=doc&reference=Glossary.Constraint.WebHome&typed=true]] are available for query (e.g. in a Registry), but this is a less effective way of processing if the contenrts of the database are dynamic.
294 294  
295 295  === 16.4.6 Query Database ===
296 296  
297 297  [[image:image-20250318221512-31.jpeg||data-xwiki-image-style-alignment="center"]]
298 298  
299 -The logical query of the user is converted to an SDMX query and sent to the Data Web Service of the data publisher. The Data Web Service may also query the Metadata Repository in order to return both data and related metadata to the user application. The Data Web Service may also require structural metadata (DSD and MSD and related Code Lists and Concepts) from the structural metadata repository, in this example this an SDMX Registry.
302 +The logical query of the user is converted to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] query and sent to the Data Web Service of the data publisher. The Data Web Service may also query the [[Metadata Repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] in order to return both data and related metadata to the user application. The Data Web Service may also require [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] and related [[Code Lists>>doc:sdmx:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%)) from the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository, in this example this an [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]].
300 300  
301 301  (% class="wikigeneratedid" id="HDataQueryLogicalSelections" %)
302 302  **Data Query Logical Selections**
... ... @@ -319,7 +319,7 @@
319 319  
320 320  [[image:image-20250318221512-32.jpeg||data-xwiki-image-style-alignment="center" height="310" width="346"]]
321 321  
322 -The returned data and metadata can be presented to the user in many ways – tables, graphs, charts, maps etc. SDMX does not support visualization directly but it is possible to define roles for a Dimension and Attribute in the DSD. For instance, it is possible to assign a role of “Geography” or “Title” or “Measure Unit” etc. which will aid a data visualization service to present this information in a meaningful way to the user.
325 +The returned data and metadata can be presented to the user in many ways – tables, graphs, charts, maps etc. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] does not support visualization directly but it is possible to define roles for a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] and [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. For instance, it is possible to assign a role of “Geography” or “[[Title>>doc:sdmx:Glossary.Title.WebHome]]” or “[[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Unit” etc. which will aid a data visualization service to present this information in a meaningful way to the user.
323 323  
324 324  [[image:image-20250318221512-33.jpeg||data-xwiki-image-style-alignment="center"]]
325 325  
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,0 @@
1 -17
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,0 +1,1 @@
1 +17