Changes for page Guidelines for SDMX Data Structure Definitions
Last modified by Artur K. on 2026/05/29 14:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -389,19 +389,19 @@ 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 dimension394 -| (% style="width:205px" %)What?|(% style="width:272px" %)“indicator”|(% style="width:178px" %)-|(% style="width:270px" %)domain|(% style="width:690px" %)one or multiple dimensions395 -| (% style="width:205px" %)How?|(% style="width:272px" %)unit of measure|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:690px" %)mand. attribute or dimension396 -| (% style="width:205px" %)How?|(% style="width:272px" %)unit multiplier|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mandatory attribute397 -| (% style="width:205px" %)How?|(% style="width:272px" %)decimals|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mandatory attribute398 -| (% style="width:205px" %)How?|(% style="width:272px" %)//adjustment//|(% style="width:178px" %)X|(% style="width:270px" %)development|(% style="width:690px" %)mand. att. not relevant399 -| (% 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 attribute401 -| (% 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 attribute403 -| (% style="width:205px" %)How often?|(% style="width:272px" %)//frequency//|(% style="width:178px" %)X|(% style="width:270px" %)available|(% style="width:690px" %)mand. att. or not relevant404 -|(% colspan="2" style="width:477px"%)How much? observation value|(% style="width:178px" %)-|(% style="width:270px" %)numeric|(% style="width:690px" %)dimension measure392 +|**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 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,19 +409,25 @@ 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 (sibling) 415 -)))|conditional (obs. level)|data provider different from data compiler 414 +conditional conditional 415 + 416 + (sibling) (obs. level) 417 +)))|data provider different from data compiler 416 416 |Who?|((( 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 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 420 420 |How much?|((( 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 425 +//observation pre-// 424 424 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 + 425 425 ~** 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. 426 426 427 427 == 5.2 Attribute attachment levels and definition of groups == ... ... @@ -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)452 +* //Sender//: the identification of the organization that is transmitting the message 447 447 454 +(recommended: code from the agency code list in the SDMX COG) 455 + 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 =