Difference between revisions of "Concept Scheme V10"

From FMR Knowledge Base
Jump to navigation Jump to search
Line 39: Line 39:
 
Concepts are referenced directly by Data Structure Definitions (DSD). Concepts can also be linked to Codelists to explicitly define the set of legal values for enumerated Dimensions or Attributes.
 
Concepts are referenced directly by Data Structure Definitions (DSD). Concepts can also be linked to Codelists to explicitly define the set of legal values for enumerated Dimensions or Attributes.
  
==Usage==
+
=Usage=
 
[[Concepts|Concepts]] are used by Dimensions, Attributes, Measures, and Metadata Attributes to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.
 
[[Concepts|Concepts]] are used by Dimensions, Attributes, Measures, and Metadata Attributes to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.
  
Line 54: Line 54:
 
'''Using standardised Concepts wherever possible is good practice because it enables harmonisation of statistics i.e. it’s easy to compare statistics produced by different organisations if referenced concepts mean the same thing.'''
 
'''Using standardised Concepts wherever possible is good practice because it enables harmonisation of statistics i.e. it’s easy to compare statistics produced by different organisations if referenced concepts mean the same thing.'''
  
==Conventions==
+
=Conventions=
 
'''Concept Scheme IDs'''
 
'''Concept Scheme IDs'''
 
IDs are conventionally uppercase using underscores '_' as separators if required. Examples:
 
IDs are conventionally uppercase using underscores '_' as separators if required. Examples:
Line 72: Line 72:
 
[[URN|You can seem more examples and information on Identities in this article]].
 
[[URN|You can seem more examples and information on Identities in this article]].
  
=Flat Codelists=
+
=Flat Concept Schemes=
<p>Flat Codelists are simple lists of codes with no explicit or implied relationships or hierarchies.</p>
+
<p>Flat Concept Schemes are simple lists of codes with no explicit or implied relationships or hierarchies.</p>
  
 
<p> Example: CL_FREQUENCY Codelist</p>
 
<p> Example: CL_FREQUENCY Codelist</p>

Revision as of 05:01, 10 February 2021

Overview

A concept scheme is a container for Concepts. A concept associates an identifier with a name and optional description. Their purpose is to provide other structures a semantic meaning.

Concepts may be referenced by multiple structures in SDMX, and therefore provide re-useable mechanism for giving meaning to structures.

A Data Structure Definition (DSD) provides a good example of how Concepts are used as to create a DSD. When defining a Data Structure Definition, each Dimension, Attribute and Measure is given a specific Concept. The dimensions etc do not have names or descriptions, instead they provide a reference to a Concept which gives this information. In order to get a human readable name for a Dimension, the referenced Concept must first be obtained.

Structure Properties

Structure Type Standard SDMX Structural Metadata Artefact
Maintainable Yes
Identifiable Yes
Item Scheme Yes
SDMX Information Model Versions 1.0, 2.0, 2.1
URN - ConceptScheme namespace urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme
URN - concept namespace urn:sdmx:org.sdmx.infomodel.concept.Concept

Context within the SDMX 2.1 Information Model

Concept1.png

The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how Concepts Schemes and Concepts fit in.

Concepts are referenced directly by Data Structure Definitions (DSD). Concepts can also be linked to Codelists to explicitly define the set of legal values for enumerated Dimensions or Attributes.

Usage

Concepts are used by Dimensions, Attributes, Measures, and Metadata Attributes to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.

The SDMX Cross Domain Concept Scheme provides a range of standardised Concepts maintained by the SDMX Statistical Working Group (SWG) and can be viewed on the Global Registry site https://registry.sdmx.org/items/conceptscheme.html.

An extract is shown below.

Concept2A.PNG

Note that the concept Civil Status has been coded and references the Codelist CIVIL_STATUS, viewing that Codelist displays valid codes.

Concept3.PNG

Using standardised Concepts wherever possible is good practice because it enables harmonisation of statistics i.e. it’s easy to compare statistics produced by different organisations if referenced concepts mean the same thing.

Conventions

Concept Scheme IDs IDs are conventionally uppercase using underscores '_' as separators if required. Examples:

Agency Concept Scheme ID Description SDMX-ML
ESTAT CS_NA List of concepts for National Accounts DSDs SDMX-ML
UIS CS_BOP Balance of Payments Concept Scheme SDMX-ML
IMF CS_EDUC_UOE EDUC_UOE Concept Scheme SDMX-ML
SDMX CROSS_DOMAIN_CONCEPTS SDMX Gross Domain Concept Scheme SDMX-ML

You can seem more examples and information on Identities in this article.

Flat Concept Schemes

Flat Concept Schemes are simple lists of codes with no explicit or implied relationships or hierarchies.

Example: CL_FREQUENCY Codelist

Code ID Code Name
A Annual
S Half-yearly, semester
Q Quarterly
M Monthly
W Weekly
D Daily
B Daily - Business Week
N Minutely

Example: CL_ADJUSTMENT Codelist with descriptions

Code ID Code Name Code Description
K Calendar component Synonyms: Calendar effects; calendar factors
X Seasonal component Synonyms: Seasonal effects; seasonal factors
M Seasonal and calendar components Synonyms: Seasonal and calendar effects; seasonal and calendar factors
I Irregular component Synonym: Irregular effects
N Neither seasonally adjusted nor calendar adjusted data Synonyms: Raw data; unadjusted data

Example: CL_ADJUSTMENT Codelist with multi-lingual names and descriptions

Code ID Locale Code Name Code Description
K en Calendar component Synonyms: Calendar effects; calendar factors
K fr Composant de calendrier Synonymes: effets de calendrier; facteurs de calendrier
X en Seasonal component Synonyms: Seasonal effects; seasonal factors
X fr Composant saisonnier Synonymes: effets saisonniers; facteurs saisonniers
M en Seasonal and calendar components Synonyms: Seasonal and calendar effects; seasonal and calendar factors
M fr Composants saisonniers et calendaires Synonymes: effets saisonniers et calendaires; facteurs saisonniers et calendaires
I en Irregular component Synonym: Irregular effects
I fr Composant irrégulier Synonyme: effets irréguliers
N en Neither seasonally adjusted nor calendar adjusted data Synonyms: Raw data; unadjusted data
N fr Ni données désaisonnalisées ni données désaisonnalisées Synonymes: données brutes; données non ajustées