+ All Categories
Home > Technology > Ontology Engineering: Ontology evaluation

Ontology Engineering: Ontology evaluation

Date post: 05-Dec-2014
Category:
Upload: guus-schreiber
View: 1,558 times
Download: 4 times
Share this document with a friend
Description:
 
22
Ontology evaluation Course “Ontology Engineering”
Transcript
Page 1: Ontology Engineering: Ontology evaluation

Ontology evaluation

Course “Ontology Engineering”

Page 2: Ontology Engineering: Ontology evaluation

2

OntoClean

• Guarino & Welty

• Method for rationalizing subclass hierarchies

• Meta-properties for characterizing classes:– Rigidity– Identity– Unity

• Are used to analyze an existing subsumption hierarchy

Page 3: Ontology Engineering: Ontology evaluation

3

Rigid class properties

• Are “essential” for all its instances– It must always hold, and not just accidentally

• Semi-rigid; essential for some of the instances

• Anti-rigid: not essential for all instances

• Classes intentionally defined on anti-rigid properties cannot be superclasses of classes defined on rigid properties

Page 4: Ontology Engineering: Ontology evaluation

4

Example of applying rigidity

Class Human

hasBodyWeight (rigid)

isFather (anti-rigid)

isFemale (semi-rigid)

hasGender (rigid)

Page 5: Ontology Engineering: Ontology evaluation

5

Identity

• Refers to the problem of being able to recognize objects of a certain class

• Identity criteria:– How do we recognize an object as belonging

to a class?– Should hold over time– How can one determine two instances are the

same or different?– Identity criteria are inherited over the

subsumption relation

Page 6: Ontology Engineering: Ontology evaluation

6

Example of identity criteria:

Class Human• Different bodies

Class Article• Citation information

Class GeographicalLocation- Latitude/longitude(/Altitude) coordinates

Page 7: Ontology Engineering: Ontology evaluation

7

Example of use of Identity

• Does the class TimeDuration (e.g. “1 hour”) subsume the class TimeInterval (e.g. 11:00-12:00 today)?

• Check identity: multiple instances of TimeInterval can be identified as the same instance of TimeDuration

• Compare this to the subsumption relation between Human and Female

Page 8: Ontology Engineering: Ontology evaluation

8

Unity

• How to determine something is a whole?• How to determine which are the parts?• Unit criteria:

– Criteria for essential parts– Criteria for conditions between the parts

• Guideline for analyzing subsumption hierarchies:– Wholes should not be subclasses of non-

wholes

Page 9: Ontology Engineering: Ontology evaluation

9

Examples of unity

• Is “water” a unity?– Not if it has no clear boundaries

• But the following are unities:– An ocean– A cup of water

• Applying the guideline:– Can “water” be a superclass of “ocean”?

Page 10: Ontology Engineering: Ontology evaluation

10

Ontological analysis of a subsumption hierarchy

• Identifying the “backbone”– Subclasses based on rigid properties– Can also help in comparing two hierarchies

• Discovering inconsistencies in hierarchies– List of common types of misuse of

subsumption

Page 11: Ontology Engineering: Ontology evaluation

11

Misuse of subsumption:instantiation• Some cases are easy:

– Asia in not a subclass of Continent, but an instance

– BillClinton is not a subclass of Human, but an instance of it.

• Consider the subclass hierarchy Human Mammal AnimalWhat is the relation between Species and

Human?

Page 12: Ontology Engineering: Ontology evaluation

Species

12

Page 13: Ontology Engineering: Ontology evaluation

13

Modelling issue:classes as instances

Aircraft-type

no-of-engines: integer >0

propulsion: {propeller, jet}

Fokker-70

instance of Aircraft-type

no-of-engines = 2

propulsion = jet

Aircraft

no-of-seats: positive integer

owner: Airline

Fokker-70

subclass of Aircraft

no-of-seats: 60-80

PH-851

instance of Fokker-70

no-of-seats = 65

owner = KLM

Page 14: Ontology Engineering: Ontology evaluation

14

Misuse of subsumption:part-whole

• Common error

• E.g. Engine is not a subclass of Car

• See part-of relations lecture

Page 15: Ontology Engineering: Ontology evaluation

15

Type restriction

• Is CarPart a superclass of Engine?– No, there are engines which are not car parts– Engine has rigid properties– Car parts have no rigid properties

=> CarPart cannot subsume Engine

Page 16: Ontology Engineering: Ontology evaluation

16

Polysemy

• Example confusion– This book is heavy– I liked this book

• Using a term in two different senses

• Cf. concept/term debate in thesauri

Page 17: Ontology Engineering: Ontology evaluation

17

Example “dirty” hierarchy

Page 18: Ontology Engineering: Ontology evaluation

18

Principles for backbone identification (Rector)1. Backbone should be a genuine tree2. Distinctions at one level of the subclass

hierarchy should have he same decomposition principle (“dimension”)

e.g. location

3. Self-standing concepts• Disjoint but open: no exhaustive enumeration

possible

4. Partitioning/refining concepts• Properties that carve up the subsumption space in

exhaustive disjoint partitions

Page 19: Ontology Engineering: Ontology evaluation

19

Example backbone analysis

Hormone

Steroid hormone

Cortisol

Protein Hormone

Insulin

ATPase

Substance

Enzyme

Protein

Steroid

Catalyst

Page 20: Ontology Engineering: Ontology evaluation

20

Backbone: physical/chemical structure

Substance

Protein

Insulin

ATPase

Steroid

Cortisol

Page 21: Ontology Engineering: Ontology evaluation

21

Roles: non-primitive types

PhysiologicalRole HormoneRole CatalystRole

Hormone = Substance AND playsRole HormoneRoleEnzyme = Protein AND playsRole CatalystRoleInsulin => playsRole HormoneRole

Page 22: Ontology Engineering: Ontology evaluation

22

Summary

• Construction of subclass hierarchies is error prone

• Techniques for normalization through ontological analysis exist

• Main advantage of normalized hierarchy is ease of understanding by others– Prevention of misunderstandings when

hierarchy is shared


Recommended