Skip to Content

Changes for page 8 Hierarchy

Last modified by Artur on 2025/09/10 11:19
From version 4.2
edited by Helena
on 2025/05/15 10:53
Change comment: There is no comment for this version
To version 6.2
edited by Helena
on 2025/05/16 23:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,17 +4,17 @@
4 4  
5 5  == 8.1 Scope ==
6 6  
7 -The Codelist described in the section on structural definitions supports a simple hierarchy of Codes and restricts any child Code to having just one parent Code. Whilst this structure is useful for supporting the needs of the DataStructureDefinition and the
7 +The Codelist described in the section on structural definitions supports a simple [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] of [[Codes>>doc:xwiki:Glossary.Code.WebHome]] and restricts any child [[Code>>doc:xwiki:Glossary.Code.WebHome]] to having just one parent [[Code>>doc:xwiki:Glossary.Code.WebHome]]. Whilst this structure is useful for supporting the needs of the DataStructureDefinition and the
8 8  
9 -MetadataStructureDefinition, it may not be sufficient for supporting the more complex associations between codes that are often found in coding schemes such as a classification scheme. Often, the Codelist used in a DataStructureDefinition is derived from a more complex coding scheme. Access to such a coding scheme can aid applications, such as OLAP applications or data visualisation systems, to give more views of the data than would be possible with the simple Codelist used in the DataStructureDefinition. A Hierarchy may be linked to an IndentifiableArtefact, in order to assist
9 +MetadataStructureDefinition, it may not be sufficient for supporting the more complex associations between [[codes>>doc:xwiki:Glossary.Code.WebHome]] that are often found in coding schemes such as a classification scheme. Often, the Codelist used in a DataStructureDefinition is derived from a more complex coding scheme. Access to such a coding scheme can aid applications, such as OLAP applications or data visualisation systems, to give more views of the data than would be possible with the simple Codelist used in the DataStructureDefinition. A [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] may be linked to an IndentifiableArtefact, in order to assist
10 10  
11 -Note that a Hierarchy is not necessarily a balanced tree. A balanced tree is where levels are pre-defined and fixed, (i.e. a level always has the same set of codes, and any code has a fixed parent and child relationship to other codes). A statistical classification is an example of a balanced tree, and the support for a balanced hierarchy is a subset, and special case, of hierarchies.
11 +Note that a [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] is not necessarily a balanced tree. A balanced tree is where (% style="color:#2ecc71" %)levels(%%) are pre-defined and fixed, (i.e. a (% style="color:#2ecc71" %)level(%%) always has the same set of [[codes>>doc:xwiki:Glossary.Code.WebHome]], and any [[code>>doc:xwiki:Glossary.Code.WebHome]] has a fixed parent and child relationship to other [[codes>>doc:xwiki:Glossary.Code.WebHome]]). A statistical classification is an example of a balanced tree, and the support for a balanced [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] is a subset, and special case, of hierarchies.
12 12  
13 -The principal features of the Hierarchy are:
13 +The principal features of the [[Hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] are:
14 14  
15 -1. A child code can have more than one parent.
16 -1. There can be more than one code that has no parent (i.e. more than one “root node”).
17 -1. The levels in a hierarchy can be explicitly defined or they can be implicit: i.e. they exist only as parent/child relationships in the coding structure.
15 +1. A child [[code>>doc:xwiki:Glossary.Code.WebHome]] can have more than one parent.
16 +1. There can be more than one [[code>>doc:xwiki:Glossary.Code.WebHome]] that has no parent (i.e. more than one “root node”).
17 +1. The (% style="color:#2ecc71" %)levels(%%) in a [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] can be explicitly defined or they can be implicit: i.e. they exist only as parent/child relationships in the coding structure.
18 18  1. Hierarchies may be associated to the structures they refer to, via the HierarchyAssociation.
19 19  
20 20  == 8.2 Inheritance ==
... ... @@ -71,7 +71,6 @@
71 71  |**Class**|**Feature**|(% style="width:683px" %)**Description**
72 72  |Hierarchy|(((
73 73  Inherits from:
74 -
75 75  //MaintainableArtefact//
76 76  )))|(% style="width:683px" %)A classification structure arranged in levels of detail from the broadest to the most detailed level.
77 77  | |hasFormalLevels|(% style="width:683px" %)(((
... ... @@ -82,7 +82,6 @@
82 82  | |+level|(% style="width:683px" %)Association to the top Level in the Hierarchy.
83 83  |Level|(((
84 84  Inherits from
85 -
86 86  //NameableArtefact//
87 87  )))|(% style="width:683px" %)(((
88 88  In a “level based” hierarchy this describes a group of Codes which are characterised by homogeneous coding, and where the parent of each Code in the group is at the same higher level of the Hierarchy.
... ... @@ -102,7 +102,6 @@
102 102  |Codelist| |(% style="width:683px" %)The Code list containing the Code.
103 103  |HierarchyAssociation|(((
104 104  Inherits from:
105 -
106 106  //MaintainableArtefact//
107 107  )))|(% style="width:683px" %)An association between an Identifiable Artefact and a Hierarchy, within a specific context.
108 108  | |+contextObject|(% style="width:683px" %)The context within which the association is performed.