Difference between revisions of "Concept Scheme V10"

From FMR Knowledge Base
Jump to navigation Jump to search
(→‎Structure Properties)
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[Category:SDMX Structures]]
+
[[Category:SDMX 2.1 Structures]]
 
=Overview=
 
=Overview=
−
A concept scheme is a container for [[Concepts|Concepts]]. A concept associates an identifier with a name and optional description. Their purpose is to provide other structures a semantic meaning.
+
A concept scheme is a container for [[Concepts V10|Concepts]] which are reusable definitions for statistical items such as frequency, currency, and reference area (country).  
  
−
Concepts may be referenced by multiple structures in SDMX, and therefore provide re-useable mechanism for giving meaning to structures.
+
Concepts may be referenced by multiple structures in SDMX, and therefore provide re-usable 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|Data Structure Definition]], each [[Dimension|Dimension]], [[Attribute|Attribute]] and [[Measure|Measure]] is given a specific [[Concepts|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.
+
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 V10|Data Structure Definition]], each [[Dimension|Dimension]], [[Attribute|Attribute]] and Measure is given a specific [[Concepts V10|Concept]]. The dimensions etc. do not have names or descriptions, instead they provide a reference to a Concept which gives this information. To get a human readable name for a Dimension, the referenced Concept must first be obtained.
  
 
==Structure Properties==
 
==Structure Properties==
Line 13: Line 13:
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Maintainable
 
! scope=row style="text-align: left;"  | Maintainable
−
| [[Maintainable|Yes]]
+
| [[Maintainable_V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Identifiable
 
! scope=row style="text-align: left;"  | Identifiable
−
| [[Identifiable|Yes]]
+
| [[Identifiable V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Item Scheme
 
! scope=row style="text-align: left;"  | Item Scheme
−
| [[Item_Scheme|Yes]]
+
| [[Item_Scheme_V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
−
| 1.0, 2.0, 2.1
+
| 2.0, 2.1
 
|-
 
|-
 
! scope=row style="text-align: left;"  | URN - ConceptScheme namespace
 
! scope=row style="text-align: left;"  | URN - ConceptScheme namespace
Line 28: Line 28:
 
|-
 
|-
 
! scope=row style="text-align: left;"  | URN - concept namespace
 
! scope=row style="text-align: left;"  | URN - concept namespace
−
| <nowiki>urn:sdmx:org.sdmx.infomodel.concept.Concept</nowiki>
+
| <nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept</nowiki>
 
|}
 
|}
  
 
==Context within the SDMX 2.1 Information Model==
 
==Context within the SDMX 2.1 Information Model==
  
−
[[File:Concept1.png|900px]]
+
[[File:Concept1.png|Concept Scheme|600px]]
  
−
The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how Concepts Schemes and Concepts fit in.
+
=Usage=
−
 
+
[[Concepts V10|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, and any structure using the Concept will inherit the default representation.
−
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|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.
 
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.
+
=Conventions=
−
 
 
−
[[File:Concept2A.PNG|900px]]
 
−
 
 
−
Note that the concept '''Civil Status''' has been coded and references the Codelist '''CIVIL_STATUS''', viewing that Codelist displays valid codes.
 
−
 
 
−
[[File:Concept3.PNG|900px]]
 
−
 
 
−
'''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'''
 
'''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 62: Line 48:
 
! Agency !! Concept Scheme ID !! Description !! SDMX-ML
 
! Agency !! Concept Scheme ID !! Description !! SDMX-ML
 
|-
 
|-
−
| ESTAT || CS_NA || List of concepts for National Accounts DSDs || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/ESTAT/CS_NA/1.12 SDMX-ML]
+
| ESTAT || CS_NA || ESA 2010 - Transmission programme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/ESTAT/CS_NA/1.12 SDMX-ML]
 
|-
 
|-
−
| UIS || CS_BOP || Balance of Payments Concept Scheme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/IMF/CS_BOP/1.14 SDMX-ML]
+
| SDMX || CROSS_DOMAIN_CONCEPTS || SDMX Cross Domain Concept Scheme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0]
 
|-
 
|-
−
| IMF || CS_EDUC_UOE || EDUC_UOE Concept Scheme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/UIS/CS_EDUC_UOE/1.0 SDMX-ML]
 
−
|-
 
−
| SDMX || CROSS_DOMAIN_CONCEPTS || SDMX Gross Domain Concept Scheme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX-ML]
 
 
|}
 
|}
−
[[URN|You can seem more examples and information on Identities in this article]].
+
[[URN V10|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: SDMX Cross Domain Concept Scheme</p>
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Code ID !! Code Name
+
! Code ID !! Code Name !! Description
−
|-
 
−
| A || Annual
 
−
|-
 
−
| S || Half-yearly, semester
 
 
|-
 
|-
−
| Q || Quarterly
+
| ACC_CONV || Accounting conventions || Practical procedures, standards and other aspects used when compiling data from diverse so...
 
|-
 
|-
−
| M || Monthly
+
| ACCURACY || Accuracy || Closeness of computations or estimates to the unknown exact or true values that the statistics w...
 
|-
 
|-
−
| W || Weekly
+
| ACTION_TYPE || Action type || Behaviour to be undertaken by a system processing the information contained in a SDMX mess...
 
|-
 
|-
−
| D || Daily
+
| AGE || Age || Length of time that an entity has lived or existed.
 
|-
 
|-
−
| B || Daily - Business Week
+
| CIVIL_STATUS || Civil status || Legal, conjugal status of each individual in relation to the marriage laws or customs of the countr...
 
|-
 
|-
−
| N || Minutely
 
 
|}
 
|}
 +
=Concept Schemes with Simple Hierarchies=
 +
<p>SDMX allows simple hierarchies to be defined within flat Concept Schemes by making a code the parent of codes that logically sit under it in the hierarchy.</p>
  
−
<p> Example: CL_ADJUSTMENT Codelist with descriptions</p>
+
<p>Imagine a Concept Scheme including a Concept 'CONTACT' containing individual codes for details such as Name, Address, and Email etc. A simple hierarchy for CONTACT can be created by setting CONTACT as the parent for each of the Contact detail codes:</p>
−
{| class="wikitable"
 
−
|-
 
−
! 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
 
−
|}
 
  
−
<p> Example: CL_ADJUSTMENT Codelist with multi-lingual names and descriptions</p>
+
<p>
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Code ID !! Locale || Code Name !! Code Description
+
! Code ID !! Code Name !! Parent
 
|-
 
|-
−
| K || en || Calendar component || Synonyms: Calendar effects; calendar factors
+
| CONTACT || Contact || (none)
 
|-
 
|-
−
| K || fr || Composant de calendrier || Synonymes: effets de calendrier; facteurs de calendrier
+
| CONTACT_NAME || Contact name || CONTACT
 
|-
 
|-
−
| X || en || Seasonal component || Synonyms: Seasonal effects; seasonal factors
+
| CONTACT_EMAIL || Contact email address || CONTACT
 
|-
 
|-
−
| X || fr || Composant saisonnier || Synonymes: effets saisonniers; facteurs saisonniers
+
| CONTACT_ORGANISATION || Contact organisation || CONTACT
 
|-
 
|-
−
| M || en || Seasonal and calendar components || Synonyms: Seasonal and calendar effects; seasonal and calendar factors
+
| CONTACT_PHONE || Contact phone number || CONTACT
 
|-
 
|-
−
| M || fr || Composants saisonniers et calendaires || Synonymes: effets saisonniers et calendaires; facteurs saisonniers et calendaires
+
| CONTACT_MAIL || Contact mail address || CONTACT
 
|-
 
|-
−
| 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
 
 
|}
 
|}
 +
</p>
 +
 +
<p>Other than acting as a parent, CONTACT behaves as a normal code allowing series for CONTACT or any of the individual details.</p>
 +
<p>A Code can only have one parent meaning that it can only appear once in a simple Concept Scheme hierarchy.

Latest revision as of 02:12, 28 March 2024

Overview

A concept scheme is a container for Concepts which are reusable definitions for statistical items such as frequency, currency, and reference area (country).

Concepts may be referenced by multiple structures in SDMX, and therefore provide re-usable 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. 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 2.0, 2.1
URN - ConceptScheme namespace urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme
URN - concept namespace urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept

Context within the SDMX 2.1 Information Model

Concept Scheme

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, and 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.

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 ESA 2010 - Transmission programme SDMX-ML
SDMX CROSS_DOMAIN_CONCEPTS SDMX Cross Domain Concept Scheme [1]

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: SDMX Cross Domain Concept Scheme

Code ID Code Name Description
ACC_CONV Accounting conventions Practical procedures, standards and other aspects used when compiling data from diverse so...
ACCURACY Accuracy Closeness of computations or estimates to the unknown exact or true values that the statistics w...
ACTION_TYPE Action type Behaviour to be undertaken by a system processing the information contained in a SDMX mess...
AGE Age Length of time that an entity has lived or existed.
CIVIL_STATUS Civil status Legal, conjugal status of each individual in relation to the marriage laws or customs of the countr...

Concept Schemes with Simple Hierarchies

SDMX allows simple hierarchies to be defined within flat Concept Schemes by making a code the parent of codes that logically sit under it in the hierarchy.

Imagine a Concept Scheme including a Concept 'CONTACT' containing individual codes for details such as Name, Address, and Email etc. A simple hierarchy for CONTACT can be created by setting CONTACT as the parent for each of the Contact detail codes:

Code ID Code Name Parent
CONTACT Contact (none)
CONTACT_NAME Contact name CONTACT
CONTACT_EMAIL Contact email address CONTACT
CONTACT_ORGANISATION Contact organisation CONTACT
CONTACT_PHONE Contact phone number CONTACT
CONTACT_MAIL Contact mail address CONTACT

Other than acting as a parent, CONTACT behaves as a normal code allowing series for CONTACT or any of the individual details.

A Code can only have one parent meaning that it can only appear once in a simple Concept Scheme hierarchy.

Retrieved from "https://fmrwiki.sdmxcloud.org/index.php?title=Concept_Scheme_V10&oldid=7466"