Concept Scheme V11 - Revision history

Vmurrell: /* Structure Properties */

2022-09-05T08:29:28Z

‎Structure Properties

Vmurrell: /* Structure Properties */

2022-09-05T08:27:45Z

‎Structure Properties

Vmurrell: /* Conventions */

2022-08-30T08:57:51Z

‎Conventions

Vmurrell: /* Usage */

2022-08-30T08:57:33Z

‎Usage

Vmurrell: /* Overview */

2022-08-30T08:56:58Z

‎Overview

Vmurrell: /* Context within the SDMX 2.1 Information Model */

2022-08-22T09:14:10Z

‎Context within the SDMX 2.1 Information Model

Vmurrell: Created page with "Category:SDMX 3.0 Structures =Overview= A concept scheme is a container for Concepts which are reusable definitions for statistical items such as frequency, c..."

2022-08-17T15:40:09Z

Created page with "Category:SDMX 3.0 Structures =Overview= A concept scheme is a container for Concepts which are reusable definitions for statistical items such as frequency, c..."

New page

[[Category:SDMX 3.0 Structures]]
=Overview=
A concept scheme is a container for [[Concepts|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|Data Structure Definition]], each [[Dimension|Dimension]], [[Attribute|Attribute]] and 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. To get a human readable name for a Dimension, the referenced Concept must first be obtained.

==Structure Properties==
{| class="wikitable"
! scope=row style="text-align: left;" | Structure Type
| Standard SDMX Structural Metadata Artefact
|-
! scope=row style="text-align: left;" | Maintainable
| [[Maintainable|Yes]]
|-
! scope=row style="text-align: left;" | Identifiable
| [[Identifiable|Yes]]
|-
! scope=row style="text-align: left;" | Item Scheme
| [[Item_Scheme|Yes]]
|-
! scope=row style="text-align: left;" | SDMX Information Model Versions
| 1.0, 2.0, 2.1, 3.0
|-
! scope=row style="text-align: left;" | URN - ConceptScheme namespace
| <nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme</nowiki>
|-
! scope=row style="text-align: left;" | URN - concept namespace
| <nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept</nowiki>
|}

==Context within the SDMX 2.1 Information Model==

[[File:Concept1.png|Concept Scheme|600px]]

=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, 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:

{| 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|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
{| 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=
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:


{| class="wikitable"
|-
! 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.

@@ Line 31: / Line 31: @@
 |}
-==Context within the SDMX 2.1 Information Model==
+==Context within the SDMX 3.0 Information Model==
-[[File:Concept1.png|Concept Scheme|600px]]
+[[File:SDMX3ConceptScheme.png|Concept Scheme|600px]]
 =Usage=

@@ Line 19: / Line 19: @@
 |-
 ! scope=row style="text-align: left;"  | Item Scheme
-| [[Item_Scheme V11||Yes]]
+| [[Item_Scheme V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | SDMX Information Model Versions

@@ Line 53: / Line 53: @@
 |-
 |}
-[[URN|You can seem more examples and information on Identities in this article]].
+[[URN V11|You can seem more examples and information on Identities in this article]].
 =Flat Concept Schemes=

@@ Line 36: / Line 36: @@
 =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, and any structure using the Concept will inherit the default representation.
+[[Concepts V11|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.

@@ Line 1: / Line 1: @@
 [[Category:SDMX 3.0 Structures]]
 =Overview=
-A concept scheme is a container for [[Concepts|Concepts]] which are reusable definitions for statistical items such as frequency, currency, and reference area (country).
+A concept scheme is a container for [[Concepts V11|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|Data Structure Definition]], each [[Dimension|Dimension]], [[Attribute|Attribute]] and 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. 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_or_Metadata_Structure_Definition|Data Structure Definition]], each [[Dimension|Dimension]], [[Attribute|Attribute]] and Measure is given a specific [[Concepts V11|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==
@@ Line 13: / Line 13: @@
 |-
 ! scope=row style="text-align: left;"  | Maintainable
-| [[Maintainable|Yes]]
+| [[Maintainable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Identifiable
-| [[Identifiable|Yes]]
+| [[Identifiable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Item Scheme