Skip to Content

Changes for page 9 Concept Roles

Last modified by Helena on 2025/09/10 11:19
From version 4.3
edited by Helena
on 2025/05/16 12:12
Change comment: There is no comment for this version
To version 2.2
edited by Helena
on 2025/05/15 15:48
Change comment: Changed document title to [9 Concept Roles].

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,4 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += 9 Concept Roles =
4 4  
5 5  == 9.1 Overview ==
6 6  
... ... @@ -15,8 +15,7 @@
15 15  
16 16  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_2a51ef88.jpg||height="296" width="557"]]
17 17  
18 -(% class="wikigeneratedid" id="HFigure19:InformationModelExtractforConceptRole" %)
19 -**Figure 19: Information Model Extract for Concept Role**
16 +==== Figure 19: Information Model Extract for Concept Role ====
20 20  
21 21  It is possible to specify zero or more concept roles for a Dimension, Measure and Data Attribute. The Time Dimension has explicitly defined roles and cannot be further specified with additional concept roles.
22 22  
... ... @@ -29,7 +29,10 @@
29 29  1. The concept scheme that contains the "role" concepts can contain concepts that do not play a role.
30 30  1. There is no explicit indication on the Concept whether it is a 'role' concept.
31 31  1. Therefore, any concept in any concept scheme is capable of being a 'role' concept.
32 -1. It is the responsibility of Agencies to ensure their community knows which concepts in which concept schemes play a 'role' and the significance and interpretation of this role. In other words, such concepts must be known by applications, there is no technical mechanism that can inform an application on how to process such a 'role'.
29 +1. It is the responsibility of Agencies to ensure their community knows which concepts in which concept schemes play a 'role' and the significance and interpretation of this role. In other words, such concepts must be known by applications, there is no technical mechanism that can inform an application on how to process such a
30 +
31 +'role'.
32 +
33 33  1. If the concept referenced in the Concept Identity in a DSD component (Dimension, Measure Dimension, Attribute) is contained in the concept scheme containing concept roles then the DSD component could play the role implied by the concept, if this is understood by the processing application.
34 34  1. If the concept referenced in the Concept Identity in a DSD component (Dimension, Measure Dimension, Attribute) is not contained in the concept scheme containing concept roles, and the DSD component is playing a role, then the concept role is identified by the Concept Role in the schema.
35 35  
... ... @@ -37,20 +37,42 @@
37 37  
38 38  The standard roles Concept Scheme, is still a normal Concept Scheme, thus it may be used also for the concept identity of a Component, e.g., the 'FREQ':
39 39  
40 -[[image:1747386659499-933.png]]
40 +**<str:Dimension id="FREQ">**
41 41  
42 +**<str:ConceptIdentity>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=**
43 +
44 +**SDMX:CONCEPT_ROLES(1.0.0).FREQ</str:ConceptIdentity> </str:Dimension>**
45 +
42 42  Given this is the standard roles Concept Scheme, any application should interpret the above Dimension to have the role of Frequency.
43 43  
44 44  Using a Concept Scheme that is not the standard roles Concept Scheme where it is required to assign a role using the standard roles Concept Scheme. Again, FREQ is chosen as the example.
45 45  
46 -[[image:1747386677366-237.png]]
50 +**<str:Dimension id="FREQ">**
47 47  
52 +**<str:ConceptIdentity>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=**
53 +
54 +**SDMX:CONCEPTS(1.0.0).FREQ</str:ConceptIdentity>**
55 +
56 +**<str:ConceptRole>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=**
57 +
58 +**SDMX:CONCEPT_ROLES(1.0.0).FREQ</str:ConceptRole>**
59 +
60 +**</str:Dimension>**
61 +
48 48  This explicitly states that this Dimension is playing a role identified by the FREQ concept in the standard roles Concept Scheme. Again, the application must interpret this as a Frequency role.
49 49  
50 50  In other cases where a role from a non-standard roles Concept Scheme is used, then the application has to know how to interpret the provided roles, e.g., like in the case below:
51 51  
52 -[[image:1747386694309-599.png]]
66 +**<str:Dimension id="FREQ">**
53 53  
68 +**<str:ConceptIdentity>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=**
69 +
70 +**SDMX:CONCEPTS(1.0.0).FREQ</str:ConceptIdentity>**
71 +
72 +**<str:ConceptRole>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=**
73 +
74 +**SDMX:MY_CONCEPT_ROLES(1.0.0).FREQ</str:ConceptRole> </str:Dimension>**
75 +
54 54  This is all that is required for interoperability within a community. Having a standard roles Concept Scheme, maintained by the SDMX SWG, allows the SDMX community to have a common understanding of the roles, while also being able to extend the roles in bilateral (or multilateral) agreements, by maintaining their own roles Concept Scheme. This will then ensure there is interoperability between systems that understand the use of these concepts.
55 55  
56 56  Note that each of the Components (Data Attribute, Measure, Dimension, Time Dimension) has a mandatory identity association (Concept Identity) and if this Concept also identifies the role then it must be interpreted accordingly.
... ... @@ -61,14 +61,13 @@
61 61  
62 62  As of SDMX 3.0, there is a predefined Concept Scheme, with a set of Concepts that are considered the standard roles for SDMX. Beyond that, a user is free to add other roles, using custom Concept Schemes. This predefined Concept Scheme is the result of the SWG guidelines for Concept Roles, plus that for Measure, and includes the following Concepts:
63 63  
64 -(% style="width:1183.29px" %)
65 -|COMMENT|Comment|(% style="width:723px" %)Descriptive text which can be attached to data or metadata.
66 -|ENTITY|Entity|(% style="width:723px" %)Describes the subject of the data set (e.g., a country).
67 -|FLAG|Flag|(% style="width:723px" %)Coded attribute in a data set that represents qualitative information for the cell or partial key (e.g. series) value.
68 -|FREQ|Frequency|(% style="width:723px" %)Time interval at which the source data are collected.
69 -|GEO|Geographical|(% style="width:723px" %)Geographic area to which the measured statistical phenomenon relates.
70 -|OPERATION|Statistical operation|(% style="width:723px" %)Signifies statistical operations have been done on the observations.
71 -|VARIABLE|Variable|(% style="width:723px" %)Characteristic of a unit being observed that may assume more than one of a set of values to which a numerical measure or a category from a classification can be assigned.
72 -|MEASURE|Measure|(% style="width:723px" %)Used for emulating the functionality of the deprecated MeasureDimension.
73 -|GEO_FEATU RE_SET|Geographical Feature Set|(% style="width:723px" %)Georeferencing information to describe the location or the shape of a statistical unit, recognizable object or geographical area.
74 -|PRIMARY|Primary Measure|(% style="width:723px" %)Used for backwards compatibility with SDMX 2.1 and back, or when the “Primary Measure” concept is needed.
86 +|COMMENT|Comment|Descriptive text which can be attached to data or metadata.
87 +|ENTITY|Entity|Describes the subject of the data set (e.g., a country).
88 +|FLAG|Flag|Coded attribute in a data set that represents qualitative information for the cell or partial key (e.g. series) value.
89 +|FREQ|Frequency|Time interval at which the source data are collected.
90 +|GEO|Geographical|Geographic area to which the measured statistical phenomenon relates.
91 +|OPERATION|Statistical operation|Signifies statistical operations have been done on the observations.
92 +|VARIABLE|Variable|Characteristic of a unit being observed that may assume more than one of a set of values to which a numerical measure or a category from a classification can be assigned.
93 +|MEASURE|Measure|Used for emulating the functionality of the deprecated MeasureDimension.
94 +|GEO_FEATU RE_SET|Geographical Feature Set|Georeferencing information to describe the location or the shape of a statistical unit, recognizable object or geographical area.
95 +|PRIMARY|Primary Measure|Used for backwards compatibility with SDMX 2.1 and back, or when the “Primary Measure” concept is needed.
1747386659499-933.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -10.2 KB
Content
1747386677366-237.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -23.1 KB
Content
1747386694309-599.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_2a51ef88.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -81.5 KB
Content