Skip to Content

Changes for page 9 Concept Roles

Last modified by Helena on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/16 00:15
Change comment: There is no comment for this version
To version 4.2
edited by Helena
on 2025/05/16 12:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -37,42 +37,20 @@
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 -**<str:Dimension id="FREQ">**
40 +[[image:1747386659499-933.png]]
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 -
46 46  Given this is the standard roles Concept Scheme, any application should interpret the above Dimension to have the role of Frequency.
47 47  
48 48  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.
49 49  
50 -**<str:Dimension id="FREQ">**
46 +[[image:1747386677366-237.png]]
51 51  
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 -
62 62  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.
63 63  
64 64  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:
65 65  
66 -**<str:Dimension id="FREQ">**
52 +[[image:1747386694309-599.png]]
67 67  
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 -
76 76  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.
77 77  
78 78  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.
1747386659499-933.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +10.2 KB
Content
1747386677366-237.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +23.1 KB
Content
1747386694309-599.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +23.2 KB
Content