Difference between revisions of "Data Structure Definition V10"

From FMR Knowledge Base
Jump to navigation Jump to search
(Context within the SDMX 2.1 Information Model)
(Context within the SDMX 2.1 Information Model)
Line 27: Line 27:
 
==Context within the SDMX 2.1 Information Model==
 
==Context within the SDMX 2.1 Information Model==
 
::[[File:SDMX_Information_Model_-_Core_Artefacts_-_DSD.png|600px|frameless]]
 
::[[File:SDMX_Information_Model_-_Core_Artefacts_-_DSD.png|600px|frameless]]
<p>The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how Codelists and Codes fit in.</p>
+
<p>The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how the Data Structure Definition relates to other structures.</p>
  
 
<p>Codelists can be referenced directly by Data Structure Definitions (DSD), or indirectly through Concepts to explictly define the set of legal values for enumerated Dimensions or Attributes.</p>
 
<p>Codelists can be referenced directly by Data Structure Definitions (DSD), or indirectly through Concepts to explictly define the set of legal values for enumerated Dimensions or Attributes.</p>

Revision as of 04:45, 19 December 2019

Overview

An SDMX Data Structure Definition (DSD) describes the structure of a dataset in terms of its dimensions, attributes and measures.

Structure Properties

Structure Type Standard SDMX Structural Metadata Artefact
Maintainable Yes
Identifiable Yes
Item Scheme No
SDMX Information Model Versions 1.0, 2.0, 2.1
Concept ID DSD

Context within the SDMX 2.1 Information Model

SDMX Information Model - Core Artefacts - DSD.png

The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how the Data Structure Definition relates to other structures.

Codelists can be referenced directly by Data Structure Definitions (DSD), or indirectly through Concepts to explictly define the set of legal values for enumerated Dimensions or Attributes.

Usage

SDMX Codelists are lists of classification codes used principally for defining the set of allowed values for enumerated Components in Data Structure Definitions (DSDs) or Metadata Structure Definitions which describe Reference Metadata.

Each code is a separate Item so must have an ID and a Name, but can also have an optional Description. While Code IDs must be unique within a Codelist, the same Code ID may be safely used in other Codelists. For instance: The code 'A' may be used in a Frequency Codelist to represent 'Annual', but also appear in an Industry Codelist to represent 'Agriculture'.