Changes for page Guidelines for SDMX Data Structure Definitions

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 13 removed)
  • 1768470533088-795.png
  • 1768470575978-226.png
  • 1768470596130-305.png
  • 1768470611326-907.png
  • 1768470626558-321.png
  • 1768470646456-652.png
  • 1768470678965-391.png
  • 1768470705894-724.png
  • 1768470729899-225.png
  • 1768470752201-691.png
  • 1768470775109-874.png
  • 1768470796725-270.png
  • 1768470829131-599.png

Details

Page properties

Content

...	...	@@ -443,8 +443,10 @@
443	443	* //ID//: a unique identifier of the message
444	444	* //Test//: a Boolean attribute that indicates whether the message is for test purposes or not
445	445	* //Prepared//: the date the message was prepared
446		-* //Sender//: the identification of the organization that is transmitting the message (recommended: code from the agency code list in the SDMX COG)
	446	+* //Sender//: the identification of the organization that is transmitting the message
447	447
	448	+(recommended: code from the agency code list in the SDMX COG)
	449	+
448	448	From a business perspective, the inclusion of the //Name// element is highly recommended, as it can help to understand the purpose of the exchange message. Other header elements such as //Receiver// are optional.
449	449
450	450	= 6 STEP-BY-STEP GUIDE =
...	...	@@ -455,15 +455,13 @@
455	455
456	456	Figure 1 provides an overview of the overall process. As a first step, the context of the data exchange(s) that should be covered by the DSD(s) is defined in terms of purpose, domains, level of exchange, type of data, type of recipient, role of in data exchange, process pattern, and GSBPM phase (see Figure 2). Since reusing existing artefacts is one of the guiding principles, the second step identifies existing DSDs that may be reused (see Figure 3). In case relevant DSDs are available, their suitability in the present context is evaluated in step 3. Aspects to be taken into account are concept coverage, concept roles, attribute attachment levels, and code lists (see Figure 4). Step 4 is subject to the outcome of step 3. In case of a favorable assessment, the DSDs are simply reused. If the DSDs are partly suitable, modified versions can be derived. See section 2. for a summary of possible DSD modification scenarios. If the DSDs are not suitable or if no relevant DSDs are available at all, new DSDs will be defined as described in section 3. Finally, supporting artefacts such as data flow definitions and data provision agreements are defined (see Figure 5).
457	457
458		-(% class="wikigeneratedid" %)
459		-[[image:1768470533088-795.png]]
460	460
461	461	(% class="wikigeneratedid" id="HFigure1.OverviewoftheDSDdesignprocess" %)
462	462	Figure 1. Overview of the DSD design process
463	463
	464	+
464	464	Figure 2 summarizes the characteristics of the data exchange context that is defined in step 1. These characteristics affect the decision on the data structuring approach that is part of the process of defining the concepts of a new DSD (step 4.3. in Figure 1; see Figure 7 in section 2.).
465	465
466		-[[image:1768470575978-226.png]]
467	467
468	468	(% class="wikigeneratedid" id="HFigure2.Characteristicsofdataexchangecontext" %)
469	469	Figure 2. Characteristics of data exchange context
...	...	@@ -470,23 +470,20 @@
470	470
471	471	Figure 3 recaps the priorities given to different types of existing DSDs when searching for candidates for reuse in step 2. Global DSDs maintained by the SDMX consortium are ranked the highest. They can be found via the Global SDMX Registry.
472	472
473		-(% class="wikigeneratedid" %)
474		-[[image:1768470596130-305.png]]
475	475
476	476	(% class="wikigeneratedid" id="HFigure3.PriorityrankingofexistingDSDsforreuse" %)
477	477	Figure 3. Priority ranking of existing DSDs for reuse
478	478
	477	+
479	479	Figure 4 summarizes the aspects to be considered in the assessment of the suitability of existing DSDs in step 3. For a detailed description of the cases of partial unsuitability see section 2.1. above.
480	480
481		-(% class="wikigeneratedid" %)
482		-[[image:1768470626558-321.png]]
483	483
484	484	(% class="wikigeneratedid" id="HFigure4.AspectsofDSDsuitability" %)
485	485	Figure 4. Aspects of DSD suitability
486	486
	484	+
487	487	Figure 5 lists the most relevant artefacts required in addition to a DSD, its concept scheme, and code lists.
488	488
489		-[[image:1768470646456-652.png]]
490	490
491	491	Figure 5. Supporting artefacts
492	492
...	...	@@ -494,60 +494,31 @@
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]]
	494	+**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]]
	500	+==== 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]]
	504	+==== 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]]
	508	+==== 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]]
	512	+==== 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		-
551	551	(% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %)
552	552	Figure 13. Code list specification process
553	553

1768470533088-795.png

Author

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

Size

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

Content

1768470575978-226.png

Author

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

Size

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

Content

1768470596130-305.png

Author

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

Size

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

Content

1768470611326-907.png

Author

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

Size

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

Content

1768470626558-321.png

Author

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

Size

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

Content

1768470646456-652.png

Author

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

Size

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

Content

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