Semantic Web Systems Ontology Matching. Jacques Fleuriot School of Informatics

Similar documents
Semantic Web Systems Ontologies Jacques Fleuriot School of Informatics

Metadata. Considerations for digital libraries. Tefko Saracevic, Ph.D. Tefko Saracevic

Category Theory in Ontology Research: Concrete Gain from an Abstract Approach

What you have learned so far. Interoperability. Ontology heterogeneity. Being serious about the semantic web

In this Lecture you will Learn: Testing in Software Development Process. What is Software Testing. Static Testing vs.

Semantic Web Systems Introduction Jacques Fleuriot School of Informatics

4 KEY FACTORS FOR DATA QUALITY ON A DATA LAKE (OR: HOW TO AVOID THE DATA SWAMP) JOSH HERRITZ MIOSOFT CORPORATION MIOsoft Corporation.

Models versus Ontologies - What's the Difference and where does it Matter?

What are ontologies? Eva Blomqvist Some slides by Patrick Lambrix

So many Logics, so little time

Multi-agent and Semantic Web Systems: Representation

Software Testing and Maintenance

SOFTWARE PRODUCT QUALITY SOFTWARE ENGINEERING SOFTWARE QUALITY SOFTWARE QUALITIES - PRODUCT AND PROCESS SOFTWARE QUALITY - QUALITY COMPONENTS

Week 4. COMP62342 Sean Bechhofer, Uli Sattler

An Architecture for Semantic Enterprise Application Integration Standards

SOFTWARE ENGINEERING DESIGN I

Semantic Interoperability. Being serious about the Semantic Web

Developing Web-Based Applications Using Model Driven Architecture and Domain Specific Languages

UNIK Multiagent systems Lecture 3. Communication. Jonas Moen

Promoting Component Architectures in a Dysfunctional Organization

Where is the Semantics on the Semantic Web?

Ontology Matching with CIDER: Evaluation Report for the OAEI 2008

Domain Specific Search Engine for Students

Description Logics as Ontology Languages for Semantic Webs

Mathematical Logic Prof. Arindama Singh Department of Mathematics Indian Institute of Technology, Madras. Lecture - 37 Resolution Rules

SKOS. COMP62342 Sean Bechhofer

Semantic Web Systems Web Services Part 2 Jacques Fleuriot School of Informatics

Object-Oriented Analysis and Design Prof. Partha Pratim Das Department of Computer Science and Engineering Indian Institute of Technology-Kharagpur

Ontologies SKOS. COMP62342 Sean Bechhofer

Using Ontologies for Data and Semantic Integration

The Zachman Framework

Linked Open Data: a short introduction

Ontology Development. Qing He

LOGICAL OPERATOR USAGE IN STRUCTURAL MODELLING

Methods for requirements engineering

So, You Want to Test Your Compiler?

Agenda. More on the Unified Modeling Language. UML diagram types. Packages

Previously. Principles for Modern Processor. History 1. Fetch execute cycle Pipelining and others forms of parallelism Basic architecture

OWL 2 Profiles. An Introduction to Lightweight Ontology Languages. Markus Krötzsch University of Oxford. Reasoning Web 2012

Introduction to Programming Style

Web Services Annotation and Reasoning

3. XML Foundations; Introduction to Modeling

Requirements Validation and Negotiation

1 Achieving IND-CPA security

Theory and Algorithms Introduction: insertion sort, merge sort

Ontology Merging: on the confluence between theoretical and pragmatic approaches

Part 5. Verification and Validation

PECULIARITIES OF LINKED DATA PROCESSING IN SEMANTIC APPLICATIONS. Sergey Shcherbak, Ilona Galushka, Sergey Soloshich, Valeriy Zavgorodniy

Today s topic CS347. Results list clustering example. Why cluster documents. Clustering documents. Lecture 8 May 7, 2001 Prabhakar Raghavan

Losing Control: Controls, Risks, Governance, and Stewardship of Enterprise Data

Leveraging Data and Structure in Ontology Integration

A Case Study of Model-Based Testing

Towards Ontology Mapping: DL View or Graph View?

Adobe Graphics Software

Semantic Web. Ontology Engineering and Evaluation. Morteza Amini. Sharif University of Technology Fall 93-94

Recommended Practice for Software Requirements Specifications (IEEE)

Controlled vocabularies, taxonomies, and thesauruses (and ontologies)

An Ontology-Based Methodology for Integrating i* Variants

Lightweight Semantic Web Motivated Reasoning in Prolog

Oleksandr Kuzomin, Bohdan Tkachenko

Linked Data: Standard s convergence

Curtin University School of Design. Internet Usability Design 391. Chapter 1 Introduction to Usability Design. By Joel Day

Semantic reasoning for dynamic knowledge bases. Lionel Médini M2IA Knowledge Dynamics 2018

Lecture 8 May 7, Prabhakar Raghavan

Design of Embedded Systems

Paradigms of computer programming

Data Management Glossary

Functional Languages. Hwansoo Han

Tania Tudorache Stanford University. - Ontolog forum invited talk04. October 2007

Natasha Noy Stanford University USA

Using Travelling Salesman Problem Algorithms to. Plan the Most Time-efficient Route for Robots

New Approach to Graph Databases

Lecture Telecooperation. D. Fensel Leopold-Franzens- Universität Innsbruck

Planning the Repackaging Project

Semantic Web. Ontology Engineering and Evaluation. Morteza Amini. Sharif University of Technology Fall 95-96

Tabs with Oracle Apex Application Express

COMP718: Ontologies and Knowledge Bases

From Strings to Things

CS115 - Module 1. Cameron Morland. Fall Cameron Morland CS115 - Module 1

Building the NNEW Weather Ontology

Instances and Classes. SOFTWARE ENGINEERING Christopher A. Welty David A. Ferrucci. 24 Summer 1999 intelligence

GDPR & FOSS. Marc Jones CIPP/US, CISSP Compliance Engineer & In-House Counsel

14.1 Encoding for different models of computation

CMSC 132: OBJECT-ORIENTED PROGRAMMING II

Reducing the costs of rework. Coping with change. Software prototyping. Ways to Cope with change. Benefits of prototyping

The Application Research of Semantic Web Technology and Clickstream Data Mart in Tourism Electronic Commerce Website Bo Liu

! Use of formal notations. ! in software system descriptions. ! for a broad range of effects. ! and varying levels of use. !

1: Introduction to Object (1)

Applying Experiences with Declarative Codifications of Software Architectures on COD

Taxonomies and controlled vocabularies best practices for metadata

Coding and Unit Testing! The Coding Phase! Coding vs. Code! Coding! Overall Coding Language Trends!

Content Enrichment. An essential strategic capability for every publisher. Enriched content. Delivered.

Introduction to R programming a SciLife Lab course

An Introduction to Software Architecture

Performance Evaluation of Semantic Registries: OWLJessKB and instancestore

Introduction to R programming a SciLife Lab course

Semantics of programming languages

Semantic Web in a Constrained Environment

Relational inductive biases, deep learning, and graph networks

Topics on Web Services COMP6017

Transcription:

Semantic Web Systems Ontology Matching Jacques Fleuriot School of Informatics

In the previous lecture l Ontological Engineering There s no such thing as the correct way to model a domain. Ontology development should be an iterative process. l Methodologies for developing ontologies METHONTOLOGY. On-To-Knowledge. NeOn Methodology. and many more 2

In this lecture l Ontological mismatch: Inevitable and desirable l Different kinds of matching: Mapping, merging, alignment, translation. l Different approaches to matching: Traditional vs dynamic. 3

Ontological Mismatch 4

Ontologies l A notion of relevant knowledge is highly subjective: which parts of the world it is important to talk about. how to segregate and organise the world. what terms to use. l Ontologies are designed by individuals: central control is impossible and undesirable. 5

Ontologies l Therefore, ontologies are user- and domainspecific representations of knowledge. l Ontologies represent only what is in their domain, otherwise they are too large. l Even within a domain, there is an enormous (unlimited?) number of ways of representing knowledge. Mismatch is common 6

Ontologies l But what is mismatch? Your ontology does not fully agree with someone with whom you wish to communicate. Your ontology does not suitably reflect a physical world. etc., l Occasionally, there will be a correct version. l Generally, this is completely subjective. 7

Ontologies l But ontological differences are desirable and essential: freedom of expression. ability to adapt to task. changing environment. l Even direct contradictions can be desirable. Is a tomato a fruit or a vegetable? l The crucial task is managing these differences. 8

Ontologies Ontology Mismatch is Good! We just need to know how to deal with it 9

Ontology Mismatch l Ontology mismatch occurs when your ontology does not accurately match your world: Other agents with different ontologies. Physical world. l Often, this causes no problems e.g. a robot can interact with the world even though it cannot fully represent it. l Sometimes it leads to serious problems. 10

Borges, The Analytical Language of John Wilkins In a certain Chinese Encyclopaedia it is written that animals are divided into: 1. those that belong to the Emperor, 2. embalmed ones, 3. those that are trained, 4. suckling pigs, 5. mermaids, 6. fabulous ones, 7. stray dogs, 8. those included in the present classification, 9. those that tremble as if they were mad, 10. innumerable ones, 11. those drawn with a very fine camelhair brush, 12. others, 13. those that have just broken a flower vase, 14. those that from a long way off look like flies. http://www.alamut.com/subj/artiface/language/johnwilkins.html 11

The Problem of Meaning Text l Meaning is subjective, context-dependent, vague, l Good ontologies are hard to build; perfect ontologies are impossible to build. l Ontologies are often built quickly by many different people, and maintained and extended haphazardly. l Ontology matching (in the purest sense) will never work! 12

Good enough matching l Achieving perfect matching is impossible in all but tiny domains: not always clear what perfect matching is. l We need to perform matching that is good enough to adequately meet our needs, for example, to allow successful communication. It may be necessary to only match parts of the ontologies. l The more similar the ontologies are, the easier matching them will be. 13

Structural and Semantic matching l It has long been an implicit assumption that what needs to be matched is words. Essentially, this is what you are concerned with when you match class hierarchies. l This ignores the possibility that it may be the representation itself that may be wrong. This needs to be considered when you are matching structured (e.g. first-order) terms. l Matching of complex ontologies requires both. 14

What do we want to match? l Anything in the ontology: from simple hierarchies. to first-order relations, functions, axioms, planning rules, etc. l The more complex your ontology is, the harder the matching is! 15

What do we want to match? 16

What do we want to match? l The more complex ontological objects are (classes, frames, relations, functions, axioms, rules ), the more complex the matching must be. l But ontologies are often very large: If they are large enough, even very simple ontologies are hard to match. l Even matching class hierarchies only is a hard and unsolved problem! 17

Different kinds of matching 18

Different kinds of matching Mapping the most common task: the task of relating the vocabulary of two ontologies that share the same domain of discourse in such a way that the mathematical structure of ontological signatures and their intended interpretations, as specified by the ontological axioms, are respected Kalfoglou and Schorlemmer (2003) l Mapping is usually pairwise between individual ontologies. l Many ontologies can be mapped to a single ontology (more scalable but less flexible). l Can be done between ontology clusters. 19

Different kinds of matching Different but related ontologies 20

Different kinds of matching Result of mapping the two ontologies 21

Different kinds of matching Merging creating a single new ontology: the act of building a new ontology by unifying several ontologies into a single one Hameed et al, 2003 Much less common for agent interaction, but useful in other areas, e.g. database integration. Generally thought not to be scalable: one monolithic information source is not feasible due to unresolvable inconsistencies between them Mitra et al, 2000 22

Different kinds of matching One possible result of merging the two ontologies 23

Different kinds of matching Alignment a more complete form of mapping: the sources must be made consistent and coherent with one another but kept separately Noy and Musen, 2000 l It involves mapping concepts and relations to indicate equivalence. l It is applied to full ontologies. l A special case of mapping? 24

Different kinds of matching Translation an implementation of the mapping process: whilst ontology mapping defines a collection of functions that specify which concepts and relations correspond to which other concepts and relations, ontology translation is the application of these mapping functions to the sentences based on one ontology into the other Kalfoglou and Schorlemmer, 2003 After mapping, your ontology remains unchanged; after translation, your ontology is different. 25

Different kinds of matching One possible result of translating one of the ontologies 26

Traditional vs dynamic matching 27

Traditional matching l Assume full knowledge of both (all) ontologies. l Assume ontologies are just class hierarchies. l Match both (all) ontologies. l Ignore time concerns: this is a slow process and is done offline. l Much research on this: some successes but still huge difficulties. 28

Dynamic matching l Assume full knowledge of one ontology but very limited knowledge of other ontology (or world): e.g. agent in multi-agent systems, robot in world l Ontologies can be up to first-order or beyond. l Match only when necessary, and only what is necessary. l Matching is done during interaction and is time critical. l Much less research: some encouraging early results, but much still to do! 29

What do we want to match? l Traditional approach: some need for these ontologies to be aligned is identified: e.g. companies merging, need for frequent interactions between particular agents. l Dynamic approach: some kind of failure has occurred because the ontologies are mismatched: e.g. agents not understanding one another, robots bumping into walls. 30

What is the aim of matching? Traditional approach: Complete alignment between ontologies. No possibility of misunderstandings between agent using these ontologies. Dynamic approach: The mismatch that was leading to the observed failure is fixed so that that particular failure no longer occurs. Different failures are always possible. 31

Ontology consistency l After mapping or alignment, ontologies have not changed, so no consistency problems are introduced (though they may exist already). l After merging or translation, changes are introduced, so new inconsistencies may arise. l If changes are purely semantic (e.g. exchanging one word for an equivalent one), there should be no problems. If the meaning is changed, this could be harder. 32

Traditional matching: how does it work? l Find correspondences between nodes: R = {,,, }. l Relationships between nodes are expressed as: <ID ij, n 1i, n 2j, R ij >. l For each node n 1 i Ont 1,find the strongest semantic relationship R holding with n 2 j Ont 2. l The overall match is determined by maximising the strongest semantic relationship across all nodes. 33

Traditional matching: how does it work? Sometimes the structure of the hierarchy is considered Example from the S-Match system (Shvaiko, 2004) Images 1? Europe 1 Europe 2 =? Pictures Wine and Cheese 2 3 3 4 Austria Italy? 4 Italy 5 Austria < ID 22, 2, 2, = > < ID 21, 2, 1, > < ID 22, 2, 2, = > < ID 24, 2, 4, > 34

Traditional matching: how does it work? Source: Euzenat and Shvaiko, 2007 35

Traditional matching: Ontology Alignment Evaluation Initiative l Tests run annually at the Ontology Matching workshop. l Systems must fully align sets of two large ontologies written in OWL-DL and RDF/XML. l Points are given for correct matches and taken away for incorrect matches. l Each system can choose which streams they wish to enter. l Only results are evaluated timing is not considered. 36

Traditional matching: Ontology Alignment Evaluation Initiative Source: Dragisic et al 2014 37

Dynamic matching l Hope that our ontology will work. l Only take action when it doesn t. l Use the failure to help us identify what went wrong. l Fix the ontology so as to avoid that particular problem. l Keep going and hope for the best. 38

Dynamic matching: advantages l Makes the problem more tractable Only small parts of the ontology are matched. Failure-drive. l This means it can: be performed online. match complex ontologies (up to first order or even further). work in extremely complex environments (e.g. the real world) (theoretically). l Focuses on an ontology s failure to accurately reflect some world so, flexible: can match to Other ontologies. Real world (e.g. robotics). Any other environment in which behaviour can be observed and feedback obtained. 39

Dynamic matching: what it requires l Ability to observe failure. l Possibly, an oracle, which will provide some information about the world, e.g. In a Multi-Agent System: the agent you are trying to communicate with will provide answers to yes/no/don t know queries plus instantiations of predicates. In robotics: the physical world, which provides testable feedback (but may be more limited in scope and harder to interpret). Human user? l Ability to reason about which parts of the ontology are likely to be at fault. l Ability to alter the ontology accordingly. l Ability to test changes through further interaction with the world. 40

Summary: ontology mismatch l Ontology mismatch is inevitable. l And brings advantages. l We do not want everyone to have to use the same ontology. l Ontology mismatch is often not a problem. l And we want to ignore it if it isn t. 41

Summary: repairing mismatches The way this is tackled depends on the situation: l How complete a solution do you need? l What are you trying to match the ontology to? l How large and complex is your ontology? l How quickly do you need a solution? 42

Summary: traditional vs dynamic matching l Traditional matching is where most of the research is currently focussed and is important But is completely unusable in many contexts. l Dynamic matching is more flexible and solves problems traditional matching ignores But can only fix small parts of ontologies. 43

What can we hope to achieve? l Perfect matching is impossible because of the complexities of language and representation. l Sometimes it is not even clear what this means. Instead, we need good enough matching so agents understand one enough sufficiently for their current purposes. so robots can interact successfully with a dynamic and complex world. 44

How close are we to achieving this? l Quite far! Traditional matching has been important for a few years (e.g. OM workshop now 10 years old) Dynamic matching is still not widely studied. l Is the ability of the Semantic Web to take off dependent on this problem being solved to a reasonable degree? l Robotics can (sometimes) fare better because it is easier to control the environment But this is a big limitation: real world extremely complex. 45

Reading Shvaiko, P., & Euzenat, J. (2013). Ontology matching: state of the art and future challenges. Knowledge and Data Engineering, IEEE Transactions on, 25(1), 158-176. 46

Task Create two simple hierarchies and try matching, merging and translating them. 47