SDMX 5 Modelling a statistical domain

UN/FAO - Erik van IngenAbuja, Nigeria, 13-14 May 2015

•Agree on exchange needs

•Define the Concept Scheme

•Code the Concept Scheme

•Define a DSD Matrix

•Optimise the DSD Matrix

•Create SDMX Artefacts

agree on data exchange needs

list Dataflows to be covered by SDMX

One Dataflow per data exchange need (e.g. transmission table)

define the Concept Scheme

list all Concepts needed in any Dataflow

place all of the Concepts required in a single Concept Scheme

code the Concepts

add default representations to Concepts drawing on existing:

cross-domain Code Lists

existing shared Code Lists

new Code Lists based on existing classifications

new Code Lists following the SDMX coding guidelines

define a DSD Matrix

put the Dataflows in relation to the Concept Scheme:

which Concept is used in which Dataflow?

DSD Matrix

optimise the DSD Matrix

One DSD for each Dataflow with only the Dimensions needed for the respective

Dataflow

A single DSD covering both Dataflows, where the code

reported for Dimensions not needed are fixed to a single

code for use with that specific Dataflow

Option 1

option 2

optimise the DSD Matrix

fill blanks in the matrix with default codes as far as possible from statistical perspective

to reduce the number of DSDs, you may fix a Dimension to a single Code value for use in a Dataflow

generic example

create SDMX Artefacts

Derive DSDs from the matrix

1 Concept Scheme

1 DSD for each set of dimensionality

1 Dataflow per exchange need

1 Cube Region Constraint per Dataflow

DSD matrix in context

architectural scenarios

thank you