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

Summary

Details

Page properties
Content
... ... @@ -389,19 +389,19 @@
389 389  
390 390  **Table 9. Minimum requirements for DSDs~*~***
391 391  
392 -|**Question**|**Concept**|**COG**|**Code list**|**Time series Cross-section**
393 -|Where?|reference area|X|revision|mand. attribute or dimension
394 -|What?|“indicator”|-|domain|one or multiple dimensions
395 -|How?|unit of measure|X|development|mand. attribute or dimension
396 -|How?|unit multiplier|X|available|mandatory attribute
397 -|How?|decimals|X|available|mandatory attribute
398 -|How?|//adjustment//|X|development|mand. att. not relevant
399 -|When?|time period|X|format|dimension mand. att.
400 -|When?|time format|X|available|mandatory attribute
401 -|When?|time period – collection|X|development|mand. att. cond. att.
402 -|When?|data update – last update|X|time stamp|mandatory attribute
403 -|How often?|//frequency//|X|available|mand. att. or not relevant
404 -|(% colspan="2" %)How much? observation value|-|numeric|dimension measure
392 +|(% style="width:205px" %)**Question**|(% style="width:272px" %)**Concept**|(% style="width:178px" %)**COG**|(% style="width:270px" %)**Code list**|(% style="width:690px" %)**Time series Cross-section**
393 +|(% style="width:205px" %)Where?|(% style="width:272px" %)reference area|(% style="width:178px" %)X|(% style="width:270px" %)revision|(% style="width:690px" %)mand. attribute or dimension
394 +|(% style="width:205px" %)What?|(% style="width:272px" %)“indicator”|(% style="width:178px" %)-|(% style="width:270px" %)domain|(% style="width:690px" %)one or multiple dimensions
395 +|(% style="width:205px" %)How?|(% style="width:272px" %)unit of measure|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:690px" %)mand. attribute or dimension
396 +|(% style="width:205px" %)How?|(% style="width:272px" %)unit multiplier|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mandatory attribute
397 +|(% style="width:205px" %)How?|(% style="width:272px" %)decimals|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mandatory attribute
398 +|(% style="width:205px" %)How?|(% style="width:272px" %)//adjustment//|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:690px" %)mand. att. not relevant
399 +|(% style="width:205px" %)When?|(% style="width:272px" %)time period|(% style="width:178px" %)X|(% style="width:270px" %)format|(% style="width:690px" %)dimension mand. att.
400 +|(% style="width:205px" %)When?|(% style="width:272px" %)time format|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mandatory attribute
401 +|(% style="width:205px" %)When?|(% style="width:272px" %)time period – collection|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:690px" %)mand. att. cond. att.
402 +|(% style="width:205px" %)When?|(% style="width:272px" %)data update – last update|(% style="width:178px" %)X|(% style="width:270px" %)time stamp|(% style="width:690px" %)mandatory attribute
403 +|(% style="width:205px" %)How often?|(% style="width:272px" %)//frequency//|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mand. att. or not relevant
404 +|(% colspan="2" style="width:477px" %)How much? observation value|(% style="width:178px" %)-|(% style="width:270px" %)numeric|(% style="width:690px" %)dimension measure
405 405  
406 406  ~*~*Concepts in //italics// are only relevant for time series DSDs. An “X” in the COG column means the concept is defined in the COG. Code list “development” means that the SWG will develop a code list to be recommended in the COG; “revision” means that the code list is recommended by the COG and under revision by the SWG; “format” means that a format is defined by another concept; “text”, “time stamp”, and “numeric” provide data types used for uncoded concepts.
407 407  
... ... @@ -409,25 +409,19 @@
409 409  
410 410  **Table 10. Suggested additional concepts for certain scenarios~*~***
411 411  
412 -|**Question**|**Concept**|**COG**|**Code list**|**TS CS**|**Scenario**
412 +|**Question**|**Concept**|**COG**|**Code list**|**TS**|**CS**|**Scenario**
413 413  |Who?|compiling agency|X|development|(((
414 -conditional conditional
415 -
416 - (sibling) (obs. level)
417 -)))|data provider different from data compiler
414 +conditional (sibling)
415 +)))|conditional (obs. level)|data provider different from data compiler
418 418  |Who?|(((
419 -confidentiality
420 -
421 -status – observation
422 -)))|X|available|mandatory (obs. level)|except dissemination
423 -|How?|observation status|X|available|conditional (obs. level)|except orig. collection
417 +confidentiality status – observation
418 +)))|X|available|(% colspan="2" rowspan="1" %)mandatory (obs. level)|except dissemination
419 +|How?|observation status|X|available|(% colspan="2" rowspan="1" %)conditional (obs. level)|except orig. collection
424 424  |How much?|(((
425 -//observation pre-//
421 +//observation pre-break value//
422 +)))|-|numeric|cond. (obs.)|not relevant|except orig. collection
423 +|What and how?|//time series title//|X|text|cond. (TS)|not relevant|dissemination
426 426  
427 -//break value//
428 -)))|-|numeric|cond. (obs.) not relevant|except orig. collection
429 -|What and how?|//time series title//|X|text|cond. (TS) not relevant|dissemination
430 -
431 431  ~** The legend of Table 9 applies to Table 10 as well. The suggested attachment level of attributes (if any) is provided in parentheses in the TS (time series) or CS (cross-section) columns. In case an attribute does not vary at that level in a certain use case, it should be attached at the highest possible level.
432 432  
433 433  == 5.2 Attribute attachment levels and definition of groups ==
... ... @@ -449,10 +449,8 @@
449 449  * //ID//: a unique identifier of the message
450 450  * //Test//: a Boolean attribute that indicates whether the message is for test purposes or not
451 451  * //Prepared//: the date the message was prepared
452 -* //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)
453 453  
454 -(recommended: code from the agency code list in the SDMX COG)
455 -
456 456  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.
457 457  
458 458  = 6 STEP-BY-STEP GUIDE =
... ... @@ -463,13 +463,15 @@
463 463  
464 464  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).
465 465  
458 +(% class="wikigeneratedid" %)
459 +[[image:1768470533088-795.png]]
466 466  
467 467  (% class="wikigeneratedid" id="HFigure1.OverviewoftheDSDdesignprocess" %)
468 468  Figure 1. Overview of the DSD design process
469 469  
470 -
471 471  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.).
472 472  
466 +[[image:1768470575978-226.png]]
473 473  
474 474  (% class="wikigeneratedid" id="HFigure2.Characteristicsofdataexchangecontext" %)
475 475  Figure 2. Characteristics of data exchange context
... ... @@ -476,20 +476,23 @@
476 476  
477 477  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.
478 478  
473 +(% class="wikigeneratedid" %)
474 +[[image:1768470596130-305.png]]
479 479  
480 480  (% class="wikigeneratedid" id="HFigure3.PriorityrankingofexistingDSDsforreuse" %)
481 481  Figure 3. Priority ranking of existing DSDs for reuse
482 482  
483 -
484 484  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.
485 485  
481 +(% class="wikigeneratedid" %)
482 +[[image:1768470626558-321.png]]
486 486  
487 487  (% class="wikigeneratedid" id="HFigure4.AspectsofDSDsuitability" %)
488 488  Figure 4. Aspects of DSD suitability
489 489  
490 -
491 491  Figure 5 lists the most relevant artefacts required in addition to a DSD, its concept scheme, and code lists.
492 492  
489 +[[image:1768470646456-652.png]]
493 493  
494 494  Figure 5. Supporting artefacts
495 495  
... ... @@ -497,48 +497,83 @@
497 497  
498 498  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.
499 499  
500 -**Figure 6. DSD modification scenarios**
497 +[[image:1768470678965-391.png]]
501 501  
499 +Figure 6. DSD modification scenarios
500 +
502 502  == 6.3 Defining new DSDs ==
503 503  
504 504  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.
505 505  
506 -==== Figure 7. New DSD specification process ====
505 +(% class="wikigeneratedid" %)
506 +[[image:1768470705894-724.png]]
507 507  
508 +(% class="wikigeneratedid" id="HFigure7.NewDSDspecificationprocess" %)
509 +Figure 7. New DSD specification process
510 +
508 508  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.
509 509  
510 -==== Figure 8. Concept specification process ====
513 +(% class="wikigeneratedid" %)
514 +[[image:1768470729899-225.png]]
511 511  
516 +(% class="wikigeneratedid" id="HFigure8.Conceptspecificationprocess" %)
517 +Figure 8. Concept specification process
518 +
512 512  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.
513 513  
514 -==== Figure 9. DSD design options ====
521 +(% class="wikigeneratedid" %)
522 +[[image:1768470752201-691.png]]
515 515  
524 +(% class="wikigeneratedid" id="HFigure9.DSDdesignoptions" %)
525 +Figure 9. DSD design options
526 +
516 516  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.
517 517  
518 -==== Figure 10. Potential sources of concepts and definitions ====
529 +(% class="wikigeneratedid" %)
530 +[[image:1768470775109-874.png]]
519 519  
532 +(% class="wikigeneratedid" id="HFigure10.Potentialsourcesofconceptsanddefinitions" %)
533 +Figure 10. Potential sources of concepts and definitions
534 +
520 520  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.
521 521  
522 522  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.
523 523  
539 +[[image:1768470796725-270.png]]
524 524  
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 +
525 525  (% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %)
526 526  Figure 13. Code list specification process
527 527  
528 -
556 +(% class="wikigeneratedid" %)
529 529  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.
530 530  
559 +[[image:1768470878394-873.png]]
531 531  
532 532  (% class="wikigeneratedid" id="HFigure14.Priorityrankingofexistingcodelistsforreuse" %)
533 533  Figure 14. Priority ranking of existing code lists for reuse
534 534  
535 -
564 +(% class="wikigeneratedid" %)
536 536  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.
537 537  
567 +[[image:1768470896763-366.png]]
538 538  
539 539  (% class="wikigeneratedid" id="HFigure15.Aspectsofcodelistsuitability" %)
540 540  Figure 15. Aspects of code list suitability
541 541  
572 +(% class="wikigeneratedid" %)
573 +[[image:1768470911321-123.png]]
542 542  
543 543  (% class="wikigeneratedid" id="HFigure16.Codelistmodificationscenarios" %)
544 544  Figure 16. Code list modification scenarios
... ... @@ -551,8 +551,10 @@
551 551  
552 552  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.
553 553  
586 +
554 554  Figure 17. DSD design process
555 555  
589 +[[image:1768470939545-136.png]]
556 556  
557 557  Figure 18. Checklist for DSD design process
558 558  
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
1768470860119-204.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +37.9 KB
Content
1768470878394-873.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +49.7 KB
Content
1768470896763-366.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
1768470911321-123.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +49.2 KB
Content
1768470939545-136.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +143.4 KB
Content
© Semantic R&D Group, 2026