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

Summary

Details

Page properties
Content
... ... @@ -455,13 +455,15 @@
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]]
458 458  
459 459  (% class="wikigeneratedid" id="HFigure1.OverviewoftheDSDdesignprocess" %)
460 460  Figure 1. Overview of the DSD design process
461 461  
462 -
463 463  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.).
464 464  
466 +[[image:1768470575978-226.png]]
465 465  
466 466  (% class="wikigeneratedid" id="HFigure2.Characteristicsofdataexchangecontext" %)
467 467  Figure 2. Characteristics of data exchange context
... ... @@ -468,20 +468,23 @@
468 468  
469 469  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.
470 470  
473 +(% class="wikigeneratedid" %)
474 +[[image:1768470596130-305.png]]
471 471  
472 472  (% class="wikigeneratedid" id="HFigure3.PriorityrankingofexistingDSDsforreuse" %)
473 473  Figure 3. Priority ranking of existing DSDs for reuse
474 474  
475 -
476 476  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.
477 477  
481 +(% class="wikigeneratedid" %)
482 +[[image:1768470626558-321.png]]
478 478  
479 479  (% class="wikigeneratedid" id="HFigure4.AspectsofDSDsuitability" %)
480 480  Figure 4. Aspects of DSD suitability
481 481  
482 -
483 483  Figure 5 lists the most relevant artefacts required in addition to a DSD, its concept scheme, and code lists.
484 484  
489 +[[image:1768470646456-652.png]]
485 485  
486 486  Figure 5. Supporting artefacts
487 487  
... ... @@ -489,8 +489,10 @@
489 489  
490 490  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.
491 491  
492 -**Figure 6. DSD modification scenarios**
497 +[[image:1768470678965-391.png]]
493 493  
499 +Figure 6. DSD modification scenarios
500 +
494 494  == 6.3 Defining new DSDs ==
495 495  
496 496  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.
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
© Semantic R&D Group, 2026