Changes for page 16 Annex 6: Worked Use Case

Last modified by Helena on 2025/09/10 11:19

From 3.1 to 2.1

From version 2.1

edited by Helena
on 2025/05/23 01:18

Change comment: There is no comment for this version

To version 1.1

edited by Artur
on 2025/04/21 12:12

Change comment: Imported from XAR

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Parent

@@ -1,1 +1,1 @@
--WebHome
++Methodology.SDMX 2\.1 User Guide.WebHome

Author

@@ -1,1 +1,1 @@
--xwiki:XWiki.helena
++xwiki:XWiki.arturkryazhev

Content

@@ -12,6 +12,7 @@
  This scenario is the dissemination of data and related reference metadata using SDMX web services. It shows how the data, reference metadata, and structural metadata are used to build a web dissemination system.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-1.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -33,6 +33,7 @@
  The following structural metadata and provisioning metadata is used in the scenario.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-2.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -42,26 +42,22 @@
  For the reasons of clarity a sub set of the contents of the Code Lists and Concept Schemes are used in this example, and only a few of the DSD Attributes are used.
--(% class="wikigeneratedid" id="HDimensions" %)
--**Dimensions**
++===== **Dimensions** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-3.jpeg]]** **
--(% class="wikigeneratedid" id="HAttributes" %)
--**Attributes**
++===== **Attributes** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-4.jpeg]]** **
--(% class="wikigeneratedid" id="HGroup" %)
--**Group**
++===== **Group** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-5.jpeg]]** **
--(% class="wikigeneratedid" id="HPrimaryMeasure" %)
--**Primary Measure**
++===== **Primary Measure** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-6.jpeg]]** **
@@ -70,6 +70,7 @@
  === 16.4.1 Create Data Base ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-7.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -79,19 +79,18 @@
  ===== Dimensions =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-8.jpeg||data-xwiki-image-style-alignment="center"]]
  Note that for brevity only the XML of the FREQ and TIME_PERIOD are shown in full.
--(% class="wikigeneratedid" id="HNotes" %)
--**Notes**
++===== **Notes** =====
 . 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.
 . This DSD is converted from version 2.0. The version 2.0 Concepts were standalone in the form  <Concept agencyID=”ECB” version=”1.0”/>
 . 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.
--(% class="wikigeneratedid" id="HGroup-1" %)
--**Group**
++===== **Group** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-9.jpeg]]** **
@@ -103,14 +103,15 @@
  ===== Attributes =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-10.jpeg||data-xwiki-image-style-alignment="center"]]
++(% style="text-align: center;" %)
  [[image:image-20250318221512-11.jpeg||data-xwiki-image-style-alignment="center"]]
  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.
--(% class="wikigeneratedid" id="HNotes-1" %)
--**Notes**
++===== **Notes** =====
 . The Attribute has a relationship to either a data set of one or more Dimensions as described in Chapter 4.
 . DECIMALS has a relationship to a Group with the Id of Group.
@@ -117,23 +117,22 @@
 . 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.
 . OBS_CONF has a relationship with the Primary Measure.
--(% class="wikigeneratedid" id="HMeasure" %)
--**Measure**
++===== **Measure** =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-12.jpeg||data-xwiki-image-style-alignment="center"]]
  A typical database schema that can be set up using this DSD is shown below.
--(% class="wikigeneratedid" id="HSeriesKeyTable" %)
--**Series Key Table**
++===== **Series Key Table** =====
++(% style="text-align: center;" %)
  [[image:image-20250318221902-34.png||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
  **{{id name="image_50"/}}Figure 50: Relational Table Structure created from a DSD Dimensions and Related Attributes**
--(% class="wikigeneratedid" id="HGroup201CGroup201DTable" %)
--**Group “Group” Table**
++===== **Group “Group” Table** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-13.jpeg]]** **
@@ -141,9 +141,9 @@
  (% style="text-align: center;" %)
  **{{id name="image_51"/}}Figure 51: Relational Table Structure created from a DSD Group and Related Attributes**
--(% class="wikigeneratedid" id="HObservation" %)
--**Observation**
++===== **Observation** =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-14.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -151,6 +151,7 @@
  === 16.4.2 Load Database ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-15.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -158,14 +158,15 @@
  The following is an extract from the SDMX dataset.
++(% style="text-align: center;" %)
  [[image:image-20250319123255-1.png||data-xwiki-image-style-alignment="center"]]
++(% style="text-align: center;" %)
  [[image:image-20250319123339-2.png||data-xwiki-image-style-alignment="center"]]
  Note that this is a sub set of the actual data message.
--(% class="wikigeneratedid" id="HNotes-2" %)
--**Notes**
++===== **Notes** =====
 . The reference to the DSD is given in the message header and given a local structureId
 . The local structureId (DSD) is referenced from the DataSet
@@ -175,18 +175,17 @@
  The diagrams below show the database content based on the schema created.
--(% class="wikigeneratedid" id="HSeriesKeyTable-1" %)
--**Series Key Table**
++===== **Series Key Table** =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-16.jpeg||data-xwiki-image-style-alignment="center"]]
--(% class="wikigeneratedid" id="HGroupTable" %)
--**Group Table**
++===== **Group Table** =====
++(% style="text-align: center;" %)
  [[image:image-20250318221512-17.jpeg||data-xwiki-image-style-alignment="center"]]
--(% class="wikigeneratedid" id="HObservationTable" %)
--**Observation Table**
++===== **Observation Table** =====
  (% style="text-align: center;" %)
  [[image:image-20250318221512-18.jpeg]]** **
@@ -197,6 +197,7 @@
  The following registration is submitted to the Registry.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-19.jpeg||data-xwiki-image-style-alignment="center"]]
  The SDMX web service of the database can now be searched for in the Registry.
@@ -203,6 +203,7 @@
  === 16.4.4 Retrieve and Visualise Category Scheme and Dataflows ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-20.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -212,8 +212,10 @@
  [[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"]]
++(% style="text-align: center;" %)
  [[image:image-20250318221512-21.jpeg||data-xwiki-image-style-alignment="center"]]
++(% style="text-align: center;" %)
  [[image:image-20250318221512-22.jpeg||data-xwiki-image-style-alignment="center"]]
  The application will now retrieve the Dataflows in the list of Categorisations – in this case there is only one – effective exchange rates.
@@ -222,6 +222,7 @@
  [[http:~~/~~/ ~[ws-entry-point~]/dataflow/ECB/2034482/1.0>>http:// [ws-entry-point]/dataflow/ECB/2034482/1.0||rel="noopener noreferrer" target="_blank"]]
++(% style="text-align: center;" %)
  [[image:image-20250318221512-23.jpeg||data-xwiki-image-style-alignment="center"]]
  The actual choreography of the query application is dependent upon the implementation but the following is assumed for this example.
@@ -234,10 +234,10 @@
  [[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"]]
++(% style="text-align: center;" %)
  [[image:image-20250318221512-24.jpeg||data-xwiki-image-style-alignment="center"]]
--(% class="wikigeneratedid" id="HNotes-3" %)
--**Notes**
++===== **Notes** =====
  ~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,21 +245,23 @@
  [[http:~~/~~/~[ws-entry-point~]/dataprovider/ECB>>http://[ws-entry-point]/dataprovider/ECB||rel="noopener noreferrer" target="_blank"]]
--(% class="wikigeneratedid" id="HNotes-4" %)
--**Notes**
++===== **Notes** =====
  ~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.
  This returns the following as part of the Data Provider Scheme.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-25.jpeg||data-xwiki-image-style-alignment="center"]]
  The following Registry query will return the REST data source referenced in a Registration for the Provision Agreement
++(% style="text-align: center;" %)
  [[image:image-20250318221512-26.jpeg||data-xwiki-image-style-alignment="center"]]
  The response from this query is:
++(% style="text-align: center;" %)
  [[image:image-20250318221512-27.jpeg||data-xwiki-image-style-alignment="center"]]
  The query application now has the details of the web service to call when making a query, and it also knows that the query expected uses the REST interface.
@@ -270,6 +270,7 @@
  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.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-28.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -279,10 +279,12 @@
  === 16.4.5 Build Dimension Selection and Logical Query ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-29.jpeg||data-xwiki-image-style-alignment="center"]]
  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.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-30.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)
@@ -292,12 +292,12 @@
  === 16.4.6 Query Database ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-31.jpeg||data-xwiki-image-style-alignment="center"]]
  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.
--(% class="wikigeneratedid" id="HDataQueryLogicalSelections" %)
--**Data Query Logical Selections**
++===== **Data Query Logical Selections** =====
  (% style="width:551.446px" %)
  |(% style="width:261px" %)**Dimension**|(% style="width:286px" %)**Values**
@@ -308,17 +308,18 @@
  |(% style="width:261px" %)EXR_SUFFIX|(% style="width:286px" %)A
  |(% style="width:261px" %)Time|(% style="width:286px" %)Jan 2008-Dec 2010
--(% class="wikigeneratedid" id="HRESTQuery" %)
--**REST Query**
++===== **REST Query** =====
  [[http:~~/~~/ws-entry-point/data/2034482/M.Z26+Z28.EUR+CZK+DKK.DFC0+EN00+A /ECB?startPeriod=2008-01&endPeriod=2010-12&detail=dataonly>>http://ws-entry-point/data/2034482/M.Z26+Z28.EUR+CZK+DKK.DFC0+EN00+A /ECB?startPeriod=2008-01&endPeriod=2010-12&detail=dataonly||rel="noopener noreferrer" target="_blank"]]
  === 16.4.7 Visualise the Resultant Data Set ===
++(% style="text-align: center;" %)
  [[image:image-20250318221512-32.jpeg||data-xwiki-image-style-alignment="center" height="310" width="346"]]
  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.
++(% style="text-align: center;" %)
  [[image:image-20250318221512-33.jpeg||data-xwiki-image-style-alignment="center"]]
  (% style="text-align: center;" %)