Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 3.6
edited by Helena
on 2025/05/20 12:09
Change comment: There is no comment for this version
To version 3.7
edited by Helena
on 2025/05/20 12:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,6 +20,8 @@
20 20  
21 21  === {{id name="_Toc370990"/}}4.3.1 Class Diagram ===
22 22  
23 +[[image:1747732337979-971.png]]
24 +
23 23  **Figure 15 Class diagram of the Codelist**
24 24  
25 25  === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram ===
... ... @@ -72,6 +72,8 @@
72 72  
73 73  === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance ===
74 74  
77 +[[image:1747732287949-594.png]]
78 +
75 75  **Figure 16 Class diagram of the Concept Scheme**
76 76  
77 77  === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram ===
... ... @@ -107,6 +107,7 @@
107 107  
108 108  === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship ===
109 109  
114 +[[image:1747732242162-856.png]]
110 110  
111 111  **Figure 17: Relationship class diagram of the Concept Scheme**
112 112  
... ... @@ -114,10 +114,8 @@
114 114  
115 115  ==== 4.4.4.1 Narrative ====
116 116  
117 -The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the
122 +The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
118 118  
119 -MetadataStructureDefinition.
120 -
121 121  The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a
122 122  
123 123  MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
1747732242162-856.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +21.8 KB
Content
1747732287949-594.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +42.4 KB
Content
1747732337979-971.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +39.3 KB
Content