Skip to Content

Changes for page 9 Concept Roles

Last modified by Artur on 2025/09/10 11:19
From version 1.4
edited by Helena
on 2025/06/16 12:00
Change comment: There is no comment for this version
To version 1.1
edited by Helena
on 2025/06/16 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,18 +8,16 @@
8 8  
9 9  * **Frequency **– in a data set the content of this Component contains information on the frequency of the observation values.
10 10  * **Geography** – in a data set the content of this Component contains information on the geographic location of the observation values.
11 +*1. Information Model
11 11  
12 -== 9.2 Information Model ==
13 -
14 14  The Information Model for this is shown below:
15 15  
16 -[[image:1750064300151-855.png]]
17 17  
18 18  **Figure 19: Information Model Extract for Concept Role**
19 19  
20 20  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.
21 21  
22 -== 9.3 Technical Mechanism ==
20 +== 9.2 Technical Mechanism ==
23 23  
24 24  The mechanism for maintain and using concept roles is as follows:
25 25  
... ... @@ -29,21 +29,17 @@
29 29  1. There is no explicit indication on the Concept whether it is a 'role' concept.
30 30  1. Therefore, any concept in any concept scheme is capable of being a 'role' concept.
31 31  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'.
32 -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.
30 +
31 +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.
33 33  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.
33 +11. SDMX-ML Examples in a DSD
34 34  
35 -== 9.4 SDMX-ML Examples in a DSD ==
36 -
37 37  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':
38 38  
39 -[[image:1750064402123-572.png]]
40 -
41 41  Given this is the standard roles Concept Scheme, any application should interpret the above Dimension to have the role of Frequency.
42 42  
43 43  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.
44 44  
45 -[[image:1750064426747-767.png]]
46 -
47 47  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.
48 48  
49 49  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:
... ... @@ -54,7 +54,7 @@
54 54  
55 55  In order for these roles to be extensible and also to enable user communities to maintain community-specific roles, the roles are maintained in a controlled vocabulary which is implemented in SDMX as Concepts in a Concept Scheme. The Component optionally references this Concept if it is required to declare the role explicitly. Note that a Component can play more than one role and therefore multiple "role" concepts can be referenced.
56 56  
57 -== 9.5 SDMX standard roles Concept Scheme ==
51 +== 9.3 SDMX standard roles Concept Scheme ==
58 58  
59 59  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:
60 60  
1750064300151-855.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -42.8 KB
Content
1750064402123-572.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
1750064426747-767.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -25.2 KB
Content