Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 1.15
edited by Helena K.
on 2026/01/15 12:48
Change comment: There is no comment for this version
To version 1.19
edited by Helena K.
on 2026/01/15 12:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -443,10 +443,8 @@
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
446 +* //Sender//: the identification of the organization that is transmitting the message (recommended: code from the agency code list in the SDMX COG)
447 447  
448 -(recommended: code from the agency code list in the SDMX COG)
449 -
450 450  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.
451 451  
452 452  = 6 STEP-BY-STEP GUIDE =
... ... @@ -457,13 +457,15 @@
457 457  
458 458  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).
459 459  
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 -
465 465  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.).
466 466  
466 +[[image:1768470575978-226.png]]
467 467  
468 468  (% class="wikigeneratedid" id="HFigure2.Characteristicsofdataexchangecontext" %)
469 469  Figure 2. Characteristics of data exchange context
... ... @@ -470,20 +470,23 @@
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]]
473 473  
474 474  (% class="wikigeneratedid" id="HFigure3.PriorityrankingofexistingDSDsforreuse" %)
475 475  Figure 3. Priority ranking of existing DSDs for reuse
476 476  
477 -
478 478  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.
479 479  
481 +(% class="wikigeneratedid" %)
482 +[[image:1768470626558-321.png]]
480 480  
481 481  (% class="wikigeneratedid" id="HFigure4.AspectsofDSDsuitability" %)
482 482  Figure 4. Aspects of DSD suitability
483 483  
484 -
485 485  Figure 5 lists the most relevant artefacts required in addition to a DSD, its concept scheme, and code lists.
486 486  
489 +[[image:1768470646456-652.png]]
487 487  
488 488  Figure 5. Supporting artefacts
489 489  
... ... @@ -491,31 +491,60 @@
491 491  
492 492  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.
493 493  
494 -**Figure 6. DSD modification scenarios**
497 +[[image:1768470678965-391.png]]
495 495  
499 +Figure 6. DSD modification scenarios
500 +
496 496  == 6.3 Defining new DSDs ==
497 497  
498 498  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.
499 499  
500 -==== Figure 7. New DSD specification process ====
505 +(% class="wikigeneratedid" %)
506 +[[image:1768470705894-724.png]]
501 501  
508 +(% class="wikigeneratedid" id="HFigure7.NewDSDspecificationprocess" %)
509 +Figure 7. New DSD specification process
510 +
502 502  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.
503 503  
504 -==== Figure 8. Concept specification process ====
513 +(% class="wikigeneratedid" %)
514 +[[image:1768470729899-225.png]]
505 505  
516 +(% class="wikigeneratedid" id="HFigure8.Conceptspecificationprocess" %)
517 +Figure 8. Concept specification process
518 +
506 506  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.
507 507  
508 -==== Figure 9. DSD design options ====
521 +(% class="wikigeneratedid" %)
522 +[[image:1768470752201-691.png]]
509 509  
524 +(% class="wikigeneratedid" id="HFigure9.DSDdesignoptions" %)
525 +Figure 9. DSD design options
526 +
510 510  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.
511 511  
512 -==== Figure 10. Potential sources of concepts and definitions ====
529 +(% class="wikigeneratedid" %)
530 +[[image:1768470775109-874.png]]
513 513  
532 +(% class="wikigeneratedid" id="HFigure10.Potentialsourcesofconceptsanddefinitions" %)
533 +Figure 10. Potential sources of concepts and definitions
534 +
514 514  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.
515 515  
516 516  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.
517 517  
539 +[[image:1768470796725-270.png]]
518 518  
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 +
519 519  (% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %)
520 520  Figure 13. Code list specification process
521 521  
1768470533088-795.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
1768470575978-226.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +95.8 KB
Content
1768470596130-305.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +44.4 KB
Content
1768470611326-907.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1768470626558-321.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1768470646456-652.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +32.7 KB
Content
1768470678965-391.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +117.9 KB
Content
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
© Semantic R&D Group, 2026