Ontology engineering: Ontology alignment

38
Ontology Alignment Course “Ontology Engineering”

description

 

Transcript of Ontology engineering: Ontology alignment

Page 1: Ontology engineering: Ontology alignment

Ontology Alignment

Course “Ontology Engineering”

Page 2: Ontology engineering: Ontology alignment

Goals of the lecture

Understand why ontology alignment is done Know what constructs can be used to express

an alignment between two concepts Know what options there are to find mappings

2

Page 3: Ontology engineering: Ontology alignment

3

Agenda

Why ontology alignment? Alignment relations Alignment techniques

Page 4: Ontology engineering: Ontology alignment

4

Why is Ontology Alignment done?

Page 5: Ontology engineering: Ontology alignment

5

Interoperability problem II

A private company wants to participate in a marketplace

E.g. eBay: Home > Buy > Cameras & Photo > Digital Cameras >

Digital SLR > Nikon > D40

Needed: correspondences between entries of its catalogs and entries of a common catalog of a marketplace.

Page 6: Ontology engineering: Ontology alignment

Example use of vocabulary alignment

“Tokugawa”

SVCN period Edo

SVCN is local in-house ethnology thesaurus

AAT style/period Edo (Japanese period) Tokugawa

AAT is Getty’s Art & Architecture Thesaurus

Page 7: Ontology engineering: Ontology alignment

Alignment architecture for P2P

Page 8: Ontology engineering: Ontology alignment

8

Two kinds of interoperability

Syntactic interoperability– using data formats that you can share– XML family is the preferred option

Semantic interoperability– How to share meaning / concepts– Technology for finding and representing semantic

links

Page 9: Ontology engineering: Ontology alignment

9

Reusing vocabularies

Page 10: Ontology engineering: Ontology alignment

10

The myth of a unified vocabulary

There will always be multiple ontologies Partly overlapping In multiple languages Each with their own perspective

Page 11: Ontology engineering: Ontology alignment

11

Links between ontologies

“Ontology Alignment” / “Ontology Mapping”– use ontologies jointly by defining a limited set of

links– Benefit from knowledge encoded in the other

ontology– Enable access across applications/collections.– Partial by nature!

Page 12: Ontology engineering: Ontology alignment

12

Why ontology alignment?

Summary: There is no single ontology of the world People work with different viewpoints and

thus multiple conceptualizations But: these concepts often overlap Semantic relations between ontologies help

integrating information sources Currently seen as a major issue in

development of distributed (web) systems

Page 13: Ontology engineering: Ontology alignment

13

How do we represent the alignment between two concepts?

Page 14: Ontology engineering: Ontology alignment

14

Link types between concepts in different ontologies

Equality

owl:sameAs

Individual individual“Den Haag” = “The Hague”

Equivalence

owl:EquivalentClass

class class

wood-material = wood

Subclass

rdfs:subClassOf

class class

aat:Artist wn:Artist

Instance of

rdf:typeindividual class

tgn:Africa wn:Continent

Disjoint

owl:disjointWith

class class

aat:wood wn:plastic

Page 15: Ontology engineering: Ontology alignment

15

skos:mappingRelation- skos:closeMatch- skos:exactMatch- skos:broadMatch- skos:narrowMatch- skos:relatedMatch

Types of links between concepts in different thesauri

Page 16: Ontology engineering: Ontology alignment

SKOS mapping properties

16

- skos:closeMatch- symmetricProperty

- skos:exactMatch- subPropertyOf

skos:closeMatch- transitiveProperty- symmetric property

- skos:broadMatch- subPropertyOf

skos:broader- inverseOf

skos:narrowMatch

- skos:narrowMatch-subPropertyOf skos:narrower-inverseOf skos:broadMatch

-skos:relatedMatch-subPropertyOf skos:related-symmetric property

Page 17: Ontology engineering: Ontology alignment

17

Example: partial alignment between citations

Page 18: Ontology engineering: Ontology alignment

18

Example: alignment between XML Schemas

Page 19: Ontology engineering: Ontology alignment

19

Example: alignment between thesauri

Page 20: Ontology engineering: Ontology alignment

20

Links between properties: equivalentProperty subPropertyOf inverseOf

E.g. painterOf – creatorOf Trick: wn:hyponym subPropertyOf

rdfs:subClassOf

Types of links between properties in different ontologies

Page 21: Ontology engineering: Ontology alignment

21

Domain-specific links– Van Gogh (ULAN) born-in Groot-Zundert

(TGN) – Derain (ULAN) related-to Fauve (AAT))– Wandelkaart Pyreneeën RANDO.07 Haute-

Ariège - Vicdessos (Pied à Terre) related to Pyrénées (TGN)

– Part-of relations

Types of links between concepts in different ontologies

Page 22: Ontology engineering: Ontology alignment

22

Alignment Techniques

Page 23: Ontology engineering: Ontology alignment

23

Alignment tools Input: two ontologies, each consisting of a set

of discrete entities• HTML table headers• XML elements• Classes• Properties

Output: relationships holding between these entities (equivalence, subsumption, etc.) + confidence measure.

Cardinality (e.g., 1:1, 1:m)

Page 24: Ontology engineering: Ontology alignment

24

Alignment techniques Syntax: comparison of characters of the terms

– Measures of syntactic distance– Language processing

• E.g. Tokenization, single/plural,

Relate to lexical resource– Relate terms to place in WordNet hierarchy

Taxonomy comparison– Look for common parents/children in taxonomy

Instance based mapping– Two classes are similar if their instances are similar.

Page 25: Ontology engineering: Ontology alignment

String-based techniques (1)

Exact string match Prefix

– takes as input two strings and checks whether the first string starts with the second one

– net = network; but also hot = hotel Suffix

– takes as input two strings and checks whether the first string ends with the second one

– ID = PID; but also word = sword

Page 26: Ontology engineering: Ontology alignment

String-based techniques (2)

Edit distance– takes as input two strings and calculates the

number of edition operations, (e.g., insertions, deletions, substitutions) of characters

– required to transform one string into another, normalized by length of the maximum string

– EditDistance ( NKN , Nikon ) = 0.4 (2/5)

Page 27: Ontology engineering: Ontology alignment

Language-based techniques

Tokenization– parses names into tokens by recognizing punctuation, cases– Hands-Free Kits => hands, free, kits

Lemmatization– analyses morphologically tokens in order to find all their possible

basic forms– Kits => Kit

Elimination– discards “empty” tokens that are articles, prepositions,

conjunctions . . .– a, the, by, type of, their, from

Page 28: Ontology engineering: Ontology alignment

Linguistic techniquesusing WordNet senses

A subClassOf B if A is a hyponym of B– Pine subClassOf Tree

A hasPart B if A is a holonym of B– Europe hasPart Greece

A = B if they are synonyms– Quantity = Amount

A disjoint B if they are antonyms or ar siblings in the same part of hierarchy– Pine disjoint Oak

Page 29: Ontology engineering: Ontology alignment

Linguistic techniques: gloss-based

WordNet gloss comparison– The number of the same words occurring in both

input glosses increases the similarity value. – The equivalence relation is returned if the

resulting similarity value exceeds a given threshold

– Maltese dog is a breed of toy dogs having a long straight silky white coat Afghan hound is a tall graceful breed of hound with a long silky coat

Page 30: Ontology engineering: Ontology alignment

Structural technique: taxonomy comparison

Page 31: Ontology engineering: Ontology alignment

31

Techniques for Part-of Relations

Phrase (Hearst) patterns:

add <part> to <whole><whole> is made of <part><part> gives the <whole> its<whole>-containing <part><whole> consists of <part>

Page 32: Ontology engineering: Ontology alignment

Overview of alignment techniques

Page 33: Ontology engineering: Ontology alignment

33

Alignment issues (1)

Nature of the input– Underlying data models– Schema-level vs. Instance-level– Example: Link WordNet to Wikipedia

Interpretation of the output– Approximate vs. exact– Graded vs. absolute confidence

Performance varies> semi-automatic alignment.

Page 34: Ontology engineering: Ontology alignment

Involving the human in alignment evaluation

Page 35: Ontology engineering: Ontology alignment

35

Evaluation of alignments

Judging individual alignments– Precision

Comparison to a reference alignment– Recall– Precision?

Comparing the logical consequences of the models

End-to-end evaluation

Page 36: Ontology engineering: Ontology alignment

The intrinsic fuzziness of alignment

Page 37: Ontology engineering: Ontology alignment

37

WordNet

AAT

Page 38: Ontology engineering: Ontology alignment

38

Literature / acknowledgment

Some slides from this lecture are based on a tutorial of Pavel Shvaiko and Jerome Euzenathttp://dit.unitn.it/~accord/Presentations/

ESWC'05-MatchingHandOuts.pdf

Some slides are from Antoine Isaac (STICH)