Changes for page Guidelines for SDMX Data Structure Definitions
Last modified by Artur K. on 2026/05/29 14:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -502,25 +502,52 @@ 502 502 503 503 In case no (suitable) DSD is available, the actual process of specifying a new DSD is started. Figure 7 depicts this process (step 4.3. in Figure 1). It encompasses the specification of concepts, code lists, and data formats. All three specification steps include the identification of already existing artefacts that could be reused or modified to satisfy the requirements at hand and the definition of new artefacts in case no suitable artefacts are detected. Several iterations of steps 1 (specification of concepts; see Figure 8) and 2 (specification of code lists; see Figure°13) may be necessary, including revisions of the decision concerning the data structuring approach. Finally all artefacts defined in the previous steps are put together into a DSD. 504 504 505 -==== Figure 7. New DSD specification process ==== 505 +(% class="wikigeneratedid" %) 506 +[[image:1768470705894-724.png]] 506 506 508 +(% class="wikigeneratedid" id="HFigure7.NewDSDspecificationprocess" %) 509 +Figure 7. New DSD specification process 510 + 507 507 Figure 8 outlines step 4.3.1, the process of concept specification. It covers the decision on the structuring approach, the identification of relevant concepts and the assessment of their suitability, the definition of new concepts, concept roles, and attribute attachment levels. 508 508 509 -==== Figure 8. Concept specification process ==== 513 +(% class="wikigeneratedid" %) 514 +[[image:1768470729899-225.png]] 510 510 516 +(% class="wikigeneratedid" id="HFigure8.Conceptspecificationprocess" %) 517 +Figure 8. Concept specification process 518 + 511 511 Both, the decision on reuse of existing concepts as well as the definition of new ones, may lead back to a revision of the data structuring approach. For example, it could turn out that a certain concept needs to be broken down further which may lead from a “few composite dimensions” to a “many pure dimensions” approach. Figure 9 provides the design options involved in the decision on a data structuring approach. The options are defined in terms of the number of DSDs and the number of concepts (especially dimensions). The reasonability and feasibility of these options depend on the context of the present data exchange(s) as defined in the first step of the overall design process and on the content of the data exchange with respect to concepts. 512 512 513 -==== Figure 9. DSD design options ==== 521 +(% class="wikigeneratedid" %) 522 +[[image:1768470752201-691.png]] 514 514 524 +(% class="wikigeneratedid" id="HFigure9.DSDdesignoptions" %) 525 +Figure 9. DSD design options 526 + 515 515 In the second step of new DSD design, relevant existing concepts are identified. Figure 10 indicates potential sources of those concepts such as the SDMX COG for cross-domain concepts, global or other DSDs as already identified earlier in the process, and domain standards such as the UN's System of National Accounts Manual 2008 for domain-specific concepts. 516 516 517 -==== Figure 10. Potential sources of concepts and definitions ==== 529 +(% class="wikigeneratedid" %) 530 +[[image:1768470775109-874.png]] 518 518 532 +(% class="wikigeneratedid" id="HFigure10.Potentialsourcesofconceptsanddefinitions" %) 533 +Figure 10. Potential sources of concepts and definitions 534 + 519 519 The definition of new concepts (step 4.3.1.4.2.) is necessary if no (suitable) concept can be reused. It entails giving each concept a name, a code, and a definition. Further details about the usage of the concepts in the DSD are specified in steps 4.3.1.5. (concept roles), 4.3.1.6. (dimension groups), and 4.3.1.7. (attribute attachment levels). Figure 11 and 12 summarize the possible concept roles and attribute attachment levels. 520 520 521 521 The second step in the process of defining a new DSD is the specification of code lists for all coded concepts. All dimensions must be coded (with time being an exception to this rule); attributes may be coded. For uncoded concepts, a data format has to be specified. Existing formats may be reused or new ones defined. An example is the time format that is specified in the SDMX COG. Figure 13 illustrates the code list specification process. If no relevant and suitable code list exists, a new one will be defined or a partially suitable one will be adapted (see Figure 16). Suitable code lists can simply be reused via reference. 522 522 539 +[[image:1768470796725-270.png]] 523 523 541 +(% class="wikigeneratedid" %) 542 +Figure 11. Possible concept roles 543 + 544 +(% class="wikigeneratedid" %) 545 +[[image:1768470829131-599.png]] 546 + 547 +(% class="wikigeneratedid" %) 548 +Figure 12. Possible attribute attachment levels 549 + 550 + 524 524 (% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %) 525 525 Figure 13. Code list specification process 526 526
- 1768470705894-724.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.9 KB - Content
- 1768470729899-225.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +66.5 KB - Content
- 1768470752201-691.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.0 KB - Content
- 1768470775109-874.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.5 KB - Content
- 1768470796725-270.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.7 KB - Content
- 1768470829131-599.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.8 KB - Content