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

Summary

Details

Page properties
Content
... ... @@ -389,19 +389,20 @@
389 389  
390 390  **Table 9. Minimum requirements for DSDs~*~***
391 391  
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
392 +(% style="width:1308.83px" %)
393 +|(% style="width:205px" %)**Question**|(% style="width:272px" %)**Concept**|(% style="width:178px" %)**COG**|(% style="width:270px" %)**Code list**|(% style="width:290px" %)**Time series**|(% style="width:221px" %)**Cross-section**
394 +|(% style="width:205px" %)Where?|(% style="width:272px" %)reference area|(% style="width:178px" %)X|(% style="width:270px" %)revision|(% colspan="2" rowspan="1" style="width:478px" %)mand. attribute or dimension
395 +|(% style="width:205px" %)What?|(% style="width:272px" %)“indicator”|(% style="width:178px" %)-|(% style="width:270px" %)domain|(% colspan="2" rowspan="1" style="width:478px" %)one or multiple dimensions
396 +|(% style="width:205px" %)How?|(% style="width:272px" %)unit of measure|(% style="width:178px" %)X|(% style="width:270px" %)development|(% colspan="2" rowspan="1" style="width:478px" %)mand. attribute or dimension
397 +|(% style="width:205px" %)How?|(% style="width:272px" %)unit multiplier|(% style="width:178px" %)X|(% style="width:270px" %)available|(% colspan="2" rowspan="1" style="width:478px" %)mandatory attribute
398 +|(% style="width:205px" %)How?|(% style="width:272px" %)decimals|(% style="width:178px" %)X|(% style="width:270px" %)available|(% colspan="2" rowspan="1" style="width:478px" %)mandatory attribute
399 +|(% style="width:205px" %)How?|(% style="width:272px" %)//adjustment//|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:290px" %)mand. att.|(% style="width:221px" %) not relevant
400 +|(% style="width:205px" %)When?|(% style="width:272px" %)time period|(% style="width:178px" %)X|(% style="width:270px" %)format|(% style="width:290px" %)dimension|(% style="width:221px" %)mand. att.
401 +|(% style="width:205px" %)When?|(% style="width:272px" %)time format|(% style="width:178px" %)X|(% style="width:270px" %)available|(% colspan="2" rowspan="1" style="width:478px" %)mandatory attribute
402 +|(% style="width:205px" %)When?|(% style="width:272px" %)time period – collection|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:290px" %)mand. att.|(% style="width:221px" %)cond. att.
403 +|(% style="width:205px" %)When?|(% style="width:272px" %)data update – last update|(% style="width:178px" %)X|(% style="width:270px" %)time stamp|(% colspan="2" rowspan="1" style="width:478px" %)mandatory attribute
404 +|(% style="width:205px" %)How often?|(% style="width:272px" %)//frequency//|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:290px" %)mand. att. or|(% style="width:221px" %)not relevant
405 +|(% style="width:205px" %)How much?|(% style="width:272px" %)observation value|(% style="width:178px" %)-|(% style="width:270px" %)numeric|(% colspan="2" rowspan="1" style="width:290px" %) 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  
... ... @@ -411,7 +411,7 @@
411 411  
412 412  |**Question**|**Concept**|**COG**|**Code list**|**TS**|**CS**|**Scenario**
413 413  |Who?|compiling agency|X|development|(((
414 -conditional (sibling)
415 +conditional (sibling)
415 415  )))|conditional (obs. level)|data provider different from data compiler
416 416  |Who?|(((
417 417  confidentiality status – observation
... ... @@ -502,42 +502,75 @@
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 -==== Figure 7. New DSD specification process ====
506 +(% class="wikigeneratedid" %)
507 +[[image:1768470705894-724.png]]
506 506  
509 +(% class="wikigeneratedid" id="HFigure7.NewDSDspecificationprocess" %)
510 +Figure 7. New DSD specification process
511 +
507 507  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.
508 508  
509 -==== Figure 8. Concept specification process ====
514 +(% class="wikigeneratedid" %)
515 +[[image:1768470729899-225.png]]
510 510  
517 +(% class="wikigeneratedid" id="HFigure8.Conceptspecificationprocess" %)
518 +Figure 8. Concept specification process
519 +
511 511  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.
512 512  
513 -==== Figure 9. DSD design options ====
522 +(% class="wikigeneratedid" %)
523 +[[image:1768470752201-691.png]]
514 514  
525 +(% class="wikigeneratedid" id="HFigure9.DSDdesignoptions" %)
526 +Figure 9. DSD design options
527 +
515 515  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.
516 516  
517 -==== Figure 10. Potential sources of concepts and definitions ====
530 +(% class="wikigeneratedid" %)
531 +[[image:1768470775109-874.png]]
518 518  
533 +(% class="wikigeneratedid" id="HFigure10.Potentialsourcesofconceptsanddefinitions" %)
534 +Figure 10. Potential sources of concepts and definitions
535 +
519 519  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.
520 520  
521 521  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.
522 522  
540 +[[image:1768470796725-270.png]]
523 523  
542 +(% class="wikigeneratedid" %)
543 +Figure 11. Possible concept roles
544 +
545 +(% class="wikigeneratedid" %)
546 +[[image:1768470829131-599.png]]
547 +
548 +(% class="wikigeneratedid" %)
549 +Figure 12. Possible attribute attachment levels
550 +
551 +(% class="wikigeneratedid" %)
552 +[[image:1768470860119-204.png]]
553 +
524 524  (% class="wikigeneratedid" id="HFigure13.Codelistspecificationprocess" %)
525 525  Figure 13. Code list specification process
526 526  
527 -
557 +(% class="wikigeneratedid" %)
528 528  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.
529 529  
560 +[[image:1768470878394-873.png]]
530 530  
531 531  (% class="wikigeneratedid" id="HFigure14.Priorityrankingofexistingcodelistsforreuse" %)
532 532  Figure 14. Priority ranking of existing code lists for reuse
533 533  
534 -
565 +(% class="wikigeneratedid" %)
535 535  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.
536 536  
568 +[[image:1768470896763-366.png]]
537 537  
538 538  (% class="wikigeneratedid" id="HFigure15.Aspectsofcodelistsuitability" %)
539 539  Figure 15. Aspects of code list suitability
540 540  
573 +(% class="wikigeneratedid" %)
574 +[[image:1768470911321-123.png]]
541 541  
542 542  (% class="wikigeneratedid" id="HFigure16.Codelistmodificationscenarios" %)
543 543  Figure 16. Code list modification scenarios
... ... @@ -550,8 +550,11 @@
550 550  
551 551  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.
552 552  
587 +[[image:1768471052577-528.png]]
588 +
553 553  Figure 17. DSD design process
554 554  
591 +[[image:1768470939545-136.png]]
555 555  
556 556  Figure 18. Checklist for DSD design process
557 557  
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
1768471052577-528.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +97.4 KB
Content
© Semantic R&D Group, 2026