Let’s look at the following use case: a museum have been using a hierarchy of classes for many years to categorize the items in their collection. They have used the hierarchy only internally. Recently, they started thinking of publishing their collection online. They want to publish their hierarchy as well, not only so that other people can work with their metadata, but also to allow other people to link to and reuse their hierarchy. At this point, however, they realized that the meaning of some of their classes was unclear. Multiple interpretations of the same class were possible. They want this to be fixed before they publish the hierarchy, and decided to use OntoClean. The image below shows the original hierarchy.
Research Report, 3 pages max.
- Characterize each class in terms of the OntoClean properties “rigidity”, “identity” and “unity”. I.e., is the class rigid; does the class represent a unity; does the class have an identity criterion, If yes, which one?
- Re-construct the hierarchy based on this analysis.
- Construct an OWL specification of the backbone of the hierarchy.
Remarks & tips
- Start with reading the OntoClean articles carefully.
- Study in particular classes with multiple parents.
- Insert only new classes if really needed.
- Identity and unity criteria are often difficult to formulate precisely, but that does not prevent an object to have identity/unity.
- Step 1: either an image clearly showing the rigidity/identity/unity of all classes in the hierarchy or an enumeration of all classes, specifying their rigidity/identity/unity.
- Step 1: an explanation of your rationale for step 1. This can be short.
- Step 2: an image of your new hierarchy
- Step 3: OWL specification file
Friday 16 November, 23:59 CET