Difference between revisions of "Concept Scheme V10"

From FMR Knowledge Base
Jump to navigation Jump to search
(Created page with "Category:SDMX Structures [https://drive.google.com/file/d/1TvF1uhUkt7uQjcWNxuClBzi1y9ZQZC9i/view?usp=sharing Link to sdmx_2.1_Section2_Informations model] [https://drive...")
 
(→‎Structure Properties)
 
(68 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[Category:SDMX Structures]]
+
[[Category:SDMX 2.1 Structures]]
 +
=Overview=
 +
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).
  
−
[https://drive.google.com/file/d/1TvF1uhUkt7uQjcWNxuClBzi1y9ZQZC9i/view?usp=sharing Link to sdmx_2.1_Section2_Informations model]
+
Concepts may be referenced by multiple structures in SDMX, and therefore provide re-usable mechanism for giving meaning to structures.
−
 
 
−
[https://drive.google.com/file/d/1_2Sgr6GVyxK3Oy9NII_YR7yGGnq_RXhS/view?usp=sharing Link to sdmx_2.1_Section6_Technical Notes]
 
−
 
 
−
[https://lucid.app/users/login#/login Link to Lucid Charts]
 
−
 
 
−
 
 
−
=Overview=
 
  
 +
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 17: 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
−
| 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 - Codelist namespace
+
! scope=row style="text-align: left;"  | URN - ConceptScheme namespace
−
| <nowiki>urn:sdmx:org.sdmx.infomodel.codelist.Codelist</nowiki>
+
| <nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme</nowiki>
 
|-
 
|-
−
! scope=row style="text-align: left;"  | URN - Code namespace
+
! scope=row style="text-align: left;"  | URN - concept namespace
−
| <nowiki>urn:sdmx:org.sdmx.infomodel.codelist.Code</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==
  
−
Diagram to be done
+
[[File:Concept1.png|Concept Scheme|600px]]
 +
 
 +
=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.
  
−
==Usage==
+
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=
 
=Conventions=
−
<p><strong>'CL_' Codelist ID Prefix</strong></p>
+
'''Concept Scheme IDs'''
−
<p>
+
IDs are conventionally uppercase using underscores '_' as separators if required. Examples:
−
Codelist IDs are given a 'CL_' prefix to distinguish them from other structures. For instance: CL_FREQ, CL_REF_AREA, CL_AGE.
+
 
−
</p>
+
{| class="wikitable"
 +
|-
 +
! Agency !! Concept Scheme ID !! Description !! 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]
 +
|-
 +
| SDMX || CROSS_DOMAIN_CONCEPTS || SDMX Cross Domain Concept Scheme || [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0]
 +
|-
 +
|}
 +
[[URN V10|You can seem more examples and information on Identities in this article]].
 +
 
 +
=Flat Concept Schemes=
 +
<p>Flat Concept Schemes are simple lists of codes with no explicit or implied relationships or hierarchies.</p>
 +
 
 +
<p> Example: SDMX Cross Domain Concept Scheme</p>
 +
{| class="wikitable"
 +
|-
 +
! 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=
 +
<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>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>
  
−
<p><strong>Code ID Conventions</strong></p>
 
 
<p>
 
<p>
−
Codes can take any legal SDMX [[SDMX ID|ID]]. But there are several conventions that should be taken into account when choosing Code IDs:<br>
 
−
 
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
| <strong>Uppercase</strong> || By convention, Code ID's are in uppercase such as 'ABC'. Lower case Codes are valid (for example 'abc'), but care should be taken in their use to avoid confusion.
+
! 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
 
|-
 
|-
−
| <strong>'_Z' Code</strong> || The '_Z' code is conventionally used for the Undefined and Unknown classification.
+
| CONTACT_MAIL || Contact mail address || CONTACT
 
|-
 
|-
−
| <strong>'TOTAL' Code</strong> || The 'TOTAL' code represents the total or sum of the dimension. For a 'country' dimension, series with TOTAL would indicate the sum of observation values for all countries.
+
 
 
|}
 
|}
 
</p>
 
</p>
  
−
=Other - Dependent on the Structure)
+
<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 03: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"