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
-
... ... @@ -331,7 +331,9 @@ 331 331 **master + satellite DSDs** 332 332 )))|**multiple, indep. DSDs** 333 333 |**within organization**|((( 334 -best for single-domain, single-purpose can be created on the fly from structured databases 334 +best for single-domain, single-purpose can be created on the 335 + 336 +fly from structured databases 335 335 )))|(% colspan="2" %)use if harmonization is important in covered domains or purposes or if such a set of DSDs is already available at international level|easier to do than master + satellite approach each domain/purpose can maintain DSDs independently can be created on the fly from structured databases 336 336 |**between national organizations**|(% colspan="4" %)the same applies as to the “within organization” scenario 337 337 |**Level of data exchange**|(% colspan="3" %)((( ... ... @@ -340,7 +340,9 @@ 340 340 **one DSD master + satellite DSDs** 341 341 )))|**multiple, indep. DSDs** 342 342 |**between int. organization and national organizations**|(% colspan="2" %)best for single domain, single purpose scenarios that are usually rather restricted with very clear specification of what needs to be exchanged|preferable over multiDSD approach in case of multi-domain and/or multi-purpose scenarios with highly correlated data flows for maintenance reasons|((( 343 -for multi-domain and/or multipurpose scenarios; only recommended if overlap of domains/purposes is minor (e.g. just w.r.t. cross-domain concepts) equivalent to multiple “one DSD” solutions, one for each domain / purpose 345 +for multi-domain and/or multipurpose scenarios; only recommended if overlap of domains/purposes is minor (e.g. just w.r.t. cross-domain concepts) 346 + 347 +equivalent to multiple “one DSD” solutions, one for each domain / purpose 344 344 ))) 345 345 |**between international organizations**|(% colspan="3" %)comparable to “national to international” scenario| 346 346 |**dissemination to public**|(% colspan="2" %)for single-domain, single-purpose cases in more complex cases this may be the preferable approach for data discovery tools (one data structure to find and access all data)|(% colspan="2" %)(((