+ All Categories
Home > Documents > Foundations of the Semantic Web: Ontology Engineering

Foundations of the Semantic Web: Ontology Engineering

Date post: 08-Jan-2016
Category:
Upload: yori
View: 19 times
Download: 0 times
Share this document with a friend
Description:
Foundations of the Semantic Web: Ontology Engineering. Building Ontologies 3 Ontology Patterns Parts and Wholes Alan Rector & colleagues Special acknowledgement to Jeremy Rogers & Chris Wroe. Parts & Wholes, containment, connection and adjacency – common sense merology. - PowerPoint PPT Presentation
Popular Tags:
28
1 Foundations of the Semantic Web: Ontology Engineering Building Ontologies 3 Ontology Patterns Parts and Wholes Alan Rector & colleagues Special acknowledgement to Jeremy Rogers & Chris Wroe
Transcript
Page 1: Foundations of the Semantic Web: Ontology Engineering

1

Foundations of the Semantic Web:Ontology Engineering

Building Ontologies 3Ontology PatternsParts and Wholes

Alan Rector & colleaguesSpecial acknowledgement to Jeremy Rogers & Chris Wroe

Page 2: Foundations of the Semantic Web: Ontology Engineering

2

Parts & Wholes, containment,connection and adjacency – common sense merology

• Standard lexical semantic versions motivated by historyMany philosophical versions motivated by topology– This version motivated primarily by anatomy and engineering

• Classic knowledge representation work is– Odell, J. J. (1994). "Six different kinds of composition." Journal of

Object Oriented Programming 5(8): 10-15.• A short readable summary

– Not complete nor completely up to date

– Winston, M., R. Chaffin, et al. (1987). "A taxonomy of part-whole relations." Cognitive Science 11: 417-444.

• Merology – the study of parts and wholes– A quick glance at Google…

Page 3: Foundations of the Semantic Web: Ontology Engineering

3

Before we startImplementation Pattern

• Transitive properties should have non-transitive children– isPartOf : transitive

isPartOfDirectly : non-transitive

• Split which is used in partial descriptions and complete definitions– Necessary conditions use non-transitive version– Definitions use transitive version

• Benefits– Allows more restrictions in domain/range constraints and cardinality

• Allows the hierarchy along that axis to be traced one step at a time• Allow a good approximation of pure trees

– Make the nontransitive subproperty functional» Transitive properties can (almost) never be functional

(by definition, a transitive property has more than one value in any non-trivial system)

• Constraints on transitive properties easily lead to unsatisfiability

Page 4: Foundations of the Semantic Web: Ontology Engineering

4

Parts & wholes:Some examples

• The leg is part of the chair

• The left side of the body is part of the body

• The liver cells are part of the liver

• The ignition of part of the electrical system of the car

• The goose is part of the flock

• Manchester is part of England

• Computer science is part of the University

Page 5: Foundations of the Semantic Web: Ontology Engineering

5

Five families of relations

• Partonomic– Parts and wholes

• The lid is part of the box– Constitution

• The box is made of cardboard– Membership

• The box is part of the shipment

• Nonpartonomic– Containment

• The gift is contained in the box– Connection/branching/Adjacency

• The box is connected to the container by a strap

Page 6: Foundations of the Semantic Web: Ontology Engineering

6

Some tests• True kinds of part-of are transitive and

A fault to the part is a fault in the whole– The finger nail is part of the finger is part of the hand is part of the upper extremity is

part of the body• Injury to the fingernail is injury to the body

– The tail-light is part of the electrical system is part of the car• A fault in the tail light is a fault in the car

• Some similar relations are not transitive– The foot of the goose is part of the goose but not part of the flock of geese

• Damage to the foot of the goose is not damage ot the flock of geese

• Containment is transitive but things contained are not necessarily parts– A fault (e.g. souring) to the milk contained in the bottle is not damage to the bottle

• Some kinds of part-whole relation are questionably transitive– Is the cell that is part of the finger a part of the body?

• Is damage to the cell that is part of the finger damage to the body?– Not necessarily, since the cells in my body die and regrow constantly

Page 7: Foundations of the Semantic Web: Ontology Engineering

7

Structural parts• The leg is a component of of the table

• Discrete• connected, • clear boundary, • specifically named• may be differently constituted• Can have metal legs on a wooden table or vice versa

• The left side is a subdivision of the table– ‘Side’, ‘Lobe’, ‘segment’, ‘region’,…

• Arbitrary, similarly constituted, • components typically fall into one or another subdivision;• defined in relation to something else; • sensible to talk about what fraction it is: half the table, a third of the table, etc.

Page 8: Foundations of the Semantic Web: Ontology Engineering

8

Propagates_via / transitive_across• Components of subdivisions are components of the whole, but

subdivisions of components are not subdivisions of the whole– A the left side of the steering wheel of the car is not a subdivision of

the car• and certainly not a subdivision of the left side of the car

– (at least not in the UK)

• No consistent name for this relation between properties– We shall call it propagates_via or transitive_across

• Also known as “right identities” – Not supported in most DLs or OWL directly

• Although an extension to FaCT to support it exists• Heavily used in medical ontologies (GRAIL and SNOMED-CT)

Page 9: Foundations of the Semantic Web: Ontology Engineering

9

No simple solution:Here’s one of several nasty kluges

• Component_of_table is defined as a component of table or any subdivision of table– Must do it for each concept

• A Schema rather than an axiom– No way to say “same as”– No variables in OWL

» or most DLs

• SCHEMA:Components_of_X isComponentOf someValuesFrom (X or (someValuesfrom isSubDivisionOf X))– Tedious to do with OilEd Expression editor

• Schemas to be built into new tools

Page 10: Foundations of the Semantic Web: Ontology Engineering

10

Functional parts• Structural parts form a contiguous whole

– May or may not contribute to functione.g. decorative parts, vestiges such as the human appendix, “spandrels”1,

accidental lumps and bumps

• The remote control is part of the projection system– May or may not be physically connected to it

• Part of a common function

• Biology examples:– The endocrine system

• The glands are not connected, but form part of a functioning system communicating via hormones and transmitters

• The blood-forming system– Bone marrow in various places, the spleen, etc.

1 See Stephen J Gould

Page 11: Foundations of the Semantic Web: Ontology Engineering

11

If something is both a structural and functional part…

• Must put in both restrictions explicitly– Can create a common child property but this gets

complicated with the different kinds of structural parts– Better to put syntactic sugar in tools

• But syntactic sugar has not arrived, so for this course you have to do it by hand!

– Coming Real Soon Now (RSN)

Page 12: Foundations of the Semantic Web: Ontology Engineering

12

So far we have • isPartOf

isStructuralPartOf isSubdivisionOf isComponentOf isFunctionalPartOf

• Many other varieties– Layers, surfaces, …

• Many other constraints, e.g.– Dimensions must match

• 3-D things can only be structural parts of 3-D things– boundaries have one less dimension than the things they bound

• surfaces bound volumes, lines bound areas– layers of subdivisions are subdivisions of layers of the whole

• the skin of the finger is a subdivision of the skin of the upper hand

• Can add isSubprocessOf –– similar to isComponentOf

Page 13: Foundations of the Semantic Web: Ontology Engineering

13

What about containment

– X isContainedIn Y isStructuralPartOf Z X isContainedIn Z

– Rigorous version needs analogous schema to subdivision• contained_in_X

contained_in someValuesFor (X or (someValuesFor is_structural_part_of X))

– Weak approximation• make contained_in a parent of is_structural_part

– Not right – implies all structural parts are contained in the whole

» A “kluge”

Page 14: Foundations of the Semantic Web: Ontology Engineering

14

Ontology PatternsThings are made of Stuff1

One of the primary dichotomies in all top ontologies • Can divide the world into

– discrete vs continuous– thing vs stuff– structures vs substances

• Very general – not just physical things– Ideas are things; thought is stuff– A book is a thing; text is stuff

• Whether we think of it as a physical book or the pattern/form– A game is a thing; playing a game is stuff

• You count things; you measure stuff

1 “Stuff” is Lenat & Guha’s term, Building Large Ontologies, other common terms are “substance”, “amount of matter”, “Generalised_substance”

Page 15: Foundations of the Semantic Web: Ontology Engineering

15

Things are made of Stuff (cont)

• Most languages make the distinction– Indo-European languages: Can (almost) only have

plurals of discrete things – or it signals a different meaning”

• “mass nouns” vs “count nouns”

• “paper” vs “papers”, “water” vs “waters”, etc.

• Many different labels by philosophers– “Thing” severely overloaded

• “Generalised_thing is_made_of Generalised_substance”“Discrete_entity isConstitutedOf Continuous_entity”

Page 16: Foundations of the Semantic Web: Ontology Engineering

16

Top Level Ontologies – Distinction

• Continuous_entity vs Discrete_entity– For physical things sometimes

“Amount_of_matter” vs “Physical_object”

• Discrete_entity hasConstituent Continuous_entityContinuous_entity isConstituentOf Discrete_entity

• Synonym– isMadeOf = hasConstituent = isConstitutedOf

• Examples– Table isMadeOf someValuesFrom Wood– Casing isMadeOf someValuesFrom Aluminium– Aluminium isConstituentOf someValuesFrom Casing

Page 17: Foundations of the Semantic Web: Ontology Engineering

17

Partonomic Variants

• Examples– Tables isConstitutedOf someValuesFrom Wood– Whiteboard isConstitutedOf someValuesFrom Plastic– Computer_casing isConstitutedOf someValuesFrom Aluminium

• Relations to other partonomic attributes– Not propagated across isComponentOf

• The computer is not made of aluminium– Often propagates across hasSubdivision

• Computer_casing isConstitutedOf Aluminium left_side isSubDivisionOf Computer_casing isConstitutedOf Aluminium

– If it were seriously different, we would probably call the left_side a component– However, context dependent. Holds in most biological contexts

Page 18: Foundations of the Semantic Web: Ontology Engineering

18

Constituents have portions

• Casing isConstitutedOf someValuesfrom (Alloy hasPortion someValuesFrom Aluminium & hasPortion someValuesFrom Titanium)

Page 19: Foundations of the Semantic Web: Ontology Engineering

19

Portions can be reified to Proportions

• Casing isConstitutedOf someValuesFrom (Alloy hasProportion someValuesFrom (Proportion hasSubstance someValuesFrom Aluminium & hasRate 30%) & someValuesFrom (Proportion hasSubstance someValuesFrom Titanium & hasRate 30%))

• hasRate is a concrete property– Supported by OWL but not by current OilEd software

Page 20: Foundations of the Semantic Web: Ontology Engineering

20

So now we have

• isPartOf isStructuralPartOf isSubdivisionOf isComponentOf isFunctionalPartOf isConstituentOf isPortionOf

Page 21: Foundations of the Semantic Web: Ontology Engineering

21

Ontology Pattern:Use-Reciprocally and Inverses

• hasPart and isPartOf are inverses– Foot isPartOf someValuesFrom Leg

• Means “All feet are part of some leg”– Does not imply that “All legs have a part foot”

• In building parts databases, anatomy, and many other things we want to make a meta-statement that hasPart/isPartOf are to be used reciprocally– Whenever I say

“All X isPartOf someValuesFrom Y” also say “All Y hasPart someValuesFrom X”

– Actually should use isPartOfDirectly & hasPartDirectly• Tools with the ability to mark properties as “use reciprocally” coming RSN

Page 22: Foundations of the Semantic Web: Ontology Engineering

22

Multiples of Things at one level behave like substances at the next

• “Multiple” is non-standard – “Collection” is more usual but heavily over-loaded

• We treat “Multiple” as a special kind of collection– Also not like “Flock”

» A “Flock of Geese” is a discrete thing» A “Multiple of Cells” or a “Multiple of molecules” is a substance

• Multiples, like all collections, defined using allValuesFrom

• Examples– Tissue hasPortion someValuesFrom

Multiple isOf allValuesFrom Cell– Steel hasPortion someValuesFrom

Multiple isOf allValuesFrom Steel_atom– Bricks hasPortion someValuesfrom

Multiple isOf allValuesFrom Brick

Page 23: Foundations of the Semantic Web: Ontology Engineering

23

Example

• University owns Buildings madeOf Bricks– Bricks multipleOf Brick madeOf Clay– But we don’t say:

“The University owns buildings made of clay”

Page 24: Foundations of the Semantic Web: Ontology Engineering

24

We now have almost enough to describe the University

• Things & Processes including Acts

• Structures and Substances

• Multiples

• Agents Organisations People

• Selectors, Features & States

• Arbitrary relations

Page 25: Foundations of the Semantic Web: Ontology Engineering

25

Top Level Summary (1)

Independent / Self-Standing

Modifiers

  Intrinsic Properties / Selectors

Accidental ProprtiesFeature-state pairs

Page 26: Foundations of the Semantic Web: Ontology Engineering

26

Top Level Summary Continued Independent / Self-Standing Entities

Continuants/Endurants/

Things 

Occurrents/Perdurants/

Processes

Discrete/Thing/

Countable

Continuous/Substance/

Stuff

Discrete/Thing/

Countable

Continuous/Substance/

Stuff

Physical Non-physical/ Abstract

Physical Non-physical/ Abstract

Physical Non-physical/ Abstract

Physical Non-physical/ Abstract

PhysicalObject

ConceptPattern

PhysicalSubstance

Thought PhysicalProcess

Analysis/Problem solving

Activity Thinking

Page 27: Foundations of the Semantic Web: Ontology Engineering

27

Top Level Summary (cont)

Physical Discrete Entity/ Physical Countable

Physical Object

ContiguousConnected

AggregatesCollections of Physical Objects

Structures Lumps Multiples Collections

have subdivisions / regions have own dentity (not extensional)

have components

  treated as continuous

(substances);action on whole is action on all

its parts

Treated as discrete (things)

Page 28: Foundations of the Semantic Web: Ontology Engineering

28

From http://amos.indiana.edu/library/scripts/spandrel.html

• … Imagine a dome that is held up by four arches, the way it's done in cathedrals. When you do this you wind up with some leftover space between each arch. That's a spandrel. Nobody planned for that extra space to be there, but if you're going to put a dome on top of four arches, you  will always have it. Since it was there, people started painting angels in the leftover space, and it became one of the nicest parts of many cathedrals.

• Biologist Stephen J. Gould used the term "spandrel" to express something that happens in evolution all the time. He gave the example of the Irish Elk. It had enormous antlers. To hold up hose huge antlers it developed big spines on the vertebrae at its shoulders. This made a hump on the animal's back. The hump later became useful as a mating device--bigger humps were sexy. But the hump wasn't developed in order to attract mates. It was just a bi-product of having big antlers. Later on, since it was already there, it developed into other uses as well. That's a spandrel!  


Recommended