Changes for page Guidelines for SDMX Data Structure Definitions

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 12 removed)
  • 1768470678965-391.png
  • 1768470705894-724.png
  • 1768470729899-225.png
  • 1768470752201-691.png
  • 1768470775109-874.png
  • 1768470796725-270.png
  • 1768470829131-599.png
  • 1768470860119-204.png
  • 1768470878394-873.png
  • 1768470896763-366.png
  • 1768470911321-123.png
  • 1768470939545-136.png

Details

Page properties

Content

...	...	@@ -494,83 +494,48 @@
494	494
495	495	Figure 6 briefly recapitulates the actions that can be taken to overcome partial unsuitability of DSDs. As far as possible, existing artefacts should be reused in this case. This means that even if a DSD cannot be reused as a whole, concepts and code lists from that DSD can be included in the new DSD by reference.
496	496
497		-[[image:1768470678965-391.png]]
	497	+**Figure 6. DSD modification scenarios**
498	498
499		-Figure 6. DSD modification scenarios
500		-
501	501	== 6.3 Defining new DSDs ==
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		-(% class="wikigeneratedid" %)
506		-[[image:1768470705894-724.png]]
	503	+==== Figure 7. New DSD specification process ====
507	507
508		-(% class="wikigeneratedid" id="HFigure7.NewDSDspecificationprocess" %)
509		-Figure 7. New DSD specification process
510		-
511	511	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.
512	512
513		-(% class="wikigeneratedid" %)
514		-[[image:1768470729899-225.png]]
	507	+==== Figure 8. Concept specification process ====
515	515
516		-(% class="wikigeneratedid" id="HFigure8.Conceptspecificationprocess" %)
517		-Figure 8. Concept specification process
518		-
519	519	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.
520	520
521		-(% class="wikigeneratedid" %)
522		-[[image:1768470752201-691.png]]
	511	+==== Figure 9. DSD design options ====
523	523
524		-(% class="wikigeneratedid" id="HFigure9.DSDdesignoptions" %)
525		-Figure 9. DSD design options
526		-
527	527	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.
528	528
529		-(% class="wikigeneratedid" %)
530		-[[image:1768470775109-874.png]]
	515	+==== Figure 10. Potential sources of concepts and definitions ====
531	531
532		-(% class="wikigeneratedid" id="HFigure10.Potentialsourcesofconceptsanddefinitions" %)
533		-Figure 10. Potential sources of concepts and definitions
534		-
535	535	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.
536	536
537	537	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.
538	538
539		-[[image:1768470796725-270.png]]
540	540
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		-(% class="wikigeneratedid" %)
551		-[[image:1768470860119-204.png]]
552		-
553	553	(% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %)
554	554	Figure 13. Code list specification process
555	555
556		-(% class="wikigeneratedid" %)
	525	+
557	557	Figure 14 recaps the priorities given to different types of existing code lists when searching for candidates for reuse (step 4.3.2.1.). Code lists recommended by the SDMX COG (and maintained by the SDMX consortium) are ranked the highest.
558	558
559		-[[image:1768470878394-873.png]]
560	560
561	561	(% class="wikigeneratedid" id="HFigure14.Priorityrankingofexistingcodelistsforreuse" %)
562	562	Figure 14. Priority ranking of existing code lists for reuse
563	563
564		-(% class="wikigeneratedid" %)
	532	+
565	565	Figure 15 summarizes the aspects to be considered in the evaluation of the suitability of existing code lists (step 4.3.2.2.). Figure 16 summarizes the scenarios of adapting existing code lists that do not fully meet the specified needs (step 4.3.2.3.2). For a detailed description of the cases of partial unsuitability see section 2.1. above.
566	566
567		-[[image:1768470896763-366.png]]
568	568
569	569	(% class="wikigeneratedid" id="HFigure15.Aspectsofcodelistsuitability" %)
570	570	Figure 15. Aspects of code list suitability
571	571
572		-(% class="wikigeneratedid" %)
573		-[[image:1768470911321-123.png]]
574	574
575	575	(% class="wikigeneratedid" id="HFigure16.Codelistmodificationscenarios" %)
576	576	Figure 16. Code list modification scenarios
...	...	@@ -583,10 +583,8 @@
583	583
584	584	Figure 17 provides an overview of all steps in the DSD design process as described in the previous subsections 1. to 3. Figure 18 compiles those steps into a checklist for DSD designers to help them make sure all aspects are considered.
585	585
586		-
587	587	Figure 17. DSD design process
588	588
589		-[[image:1768470939545-136.png]]
590	590
591	591	Figure 18. Checklist for DSD design process
592	592

1768470678965-391.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-117.9 KB

Content

1768470705894-724.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-23.9 KB

Content

1768470729899-225.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-66.5 KB

Content

1768470752201-691.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-38.0 KB

Content

1768470775109-874.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-36.5 KB

Content

1768470796725-270.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-30.7 KB

Content

1768470829131-599.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-30.8 KB

Content

1768470860119-204.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-37.9 KB

Content

1768470878394-873.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-49.7 KB

Content

1768470896763-366.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-29.9 KB

Content

1768470911321-123.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-49.2 KB

Content

1768470939545-136.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-143.4 KB

Content