We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byElena Lovegrove
Modified over 2 years ago
Ontology - Introduction ONTOBRAS-2013 The Industrial Application of Ontology: Driven by a foundational ontology Real World Foundational Ontology
© 2013 BORO Solutions Abstract The aim of the tutorial is to provide a practical introduction for researchers and practitioners to potential for the use of foundational ontologies in industrial applications, based upon an actual application. The tutorial will be based upon industrial work currently being done using the BORO foundational methodology; an ontology-based systems (and data) re-engineering and modernisation approach. It will start with an introduction to ontology, particularly foundational ontologies. It will then introduce the BORO ontology. Using these introductions as a basis, it will walk through a number of illustrative examples of how the BORO methodology has been used to re-engineer data in an industrial context.
© 2013 BORO Solutions Structure of the tutorial A series of modules: BORO Top Ontology Introduction BORO Standards BORO BDM Introduction Case Studies 3
© 2013 BORO Solutions BORO Top Ontology Introduction - Topics A brief history of ontology The BORO Top Ontology Basis For Choosing The Right Top Ontology Methodological Themes 4
A Brief History Of Ontology
© 2013 BORO Solutions A brief history of ontology History of the word the word ontology is from the Greek ν, genitive ντος: of being (part. of ε ναι: to be) and -λογία: science, study, theory While the etymology is Greek, the oldest extant record of the word itself is the Latin form ontologia, which appeared in 1661, in the work Ogdoas Scholastica by Jacob Lorhard (Lorhardus) and in 1631 in the Lexicon Philosophicum by Rudolph Göckel (Goclenius). By this stage, it is regarded as forming the basic subject matter of metaphysics 6
© 2013 BORO Solutions Ontology – as philosophy Origins ontology as a mode of analysis is generally thought to have originated in early Greece and occupied most famously Aristotle, who created the first system of ontology in the form of an ontology of substances – often represented pictorially in the tree of Porphyry 7
© 2013 BORO Solutions Ontology in the 1960s and 1970s Connection with Ontology and Reality recognised from the start the issue is ontology, or the question of what exists. (Mealy 1967. p. 525) for some time now my work has concerned the representation of information in computers. The work has involved such things as file organizations, indexes, hierarchical structures, network structures, relational models, and so on. After a while it dawned on me that these are all just maps, being poor artificial approximations of some real underlying terrain. (William Kent 1978, Data And Reality: Basic Assumptions in Data Processing Reconsidered) Resulting view codified / standardised in the early 80s ANSI-SPARC - Griethuysen, J.v. ISO/TC97/SC5/WG3-N695 - Concepts and Terminology for the Conceptual Schema and the Information Base., ANSI, New York, NY, 1982 8
© 2013 BORO Solutions Defining ontology – in philosophy 20th Century views Quine claimed that the question ontology asks can be stated in three words What is there? and the answer in one everything not only that, everyone will accept this answer as true though there remains room for disagreement over cases. (On What There Is) Mealy refers to this essay of Quines Jonathon Lowe has a more technical definition an ontology is the set of things whose existence is acknowledged by a particular theory or system of thought. (E. J. Lowe, The Oxford Companion to Philosophy) Note the thing/object turn. 9
© 2013 BORO Solutions Defining ontology - in enterprise systems Enterprise systems can be seen as theories of their domains (Naur 1985) Recasting the philosophical description in these terms Enterprise System ontology: The set of things whose existence is acknowledged by a particular enterprise system A common way of characterizing this acknowledgment relationship is as one of ontic commitment. (Quine 1969) Naur, P, Programming as Theory Building, Microprocessing and Microprogramming, 15, (1985), 254-261 Quine, WV, Ontological relativity, and other essays, Columbia University Press, New York, 1969 10
© 2013 BORO Solutions Ontology as an engineering artefact For the ontology to be useful, to be an engineering artefact, we need to describe it In AI, the term ontology tends to be used to refer to the description (the engineering artefact), rather than what the engineering artefact describes One can then characterise the way it is described (independently of what or how it describes) An ontology consists of a specific vocabulary, plus a set of explicit assumptions in the form of a first-order logical theory, where vocabulary words appear as unary or binary predicate names One can then develop ontology languages that enforce these ways of describing if one wishes to do reasoning, then it makes sense to take this route 11
© 2013 BORO Solutions Two aspects Ontology and the real world what things exists? Ontology as an engineering artefact how is the description artefact structured? What language is used? Both aspects need to be formalised For enterprise systems, formalising the first aspect is important for semantic interoperability, it is essential no amount of work on the second aspect, by itself, can get to the heart of semantic interoperability 12
© 2013 BORO Solutions Two Aspects in Context 13 Domain Representation
The BORO Top Ontology Why you need to make metaphysical choices
© 2013 BORO Solutions The BORO Top Ontology It is helpful if the top ontology is comprehensive if it lists all the kinds of things that exist 15
© 2013 BORO Solutions Top Ontology features It is a categorical ontology. It categorises every kind of thing into ontological categories; Things Classes tuples The prime distinction between these categories is their criterion of identity: Things = 4D extension Classes = instances tuples = objects in places Practically, the categories need to be disjoint to avoid clashes of identity. 16
© 2013 BORO Solutions Ontology as a technical discipline Criteria of Identity are clearly technical. 4D objects are also technical hopefully, this illustrates that this kind of work involves what we earlier called rational reconstruction Criteria of identity are part of a bigger picture – technically called metaphysical choices the reason for the name is that the choice seems to be independent from any empirical checks on the real world however, it looks as if the choice you make can affect how easy it is to build your ontology – so it is worth getting right Brief overview of the metaphysical choices 17
© 2013 BORO Solutions Metaphysical choices A partial list of choices extensionalism versus non-extensionalism – I – Universals extensionalism versus non-extensionalism – II – Particulars Second Order Universals perdurantism versus endurantism presentism versus eternalism absolute versus relative space, time and space-time modally extended versus unextended individuals materialism and non-materialism topology of time – branching or linear. Include or exclude abstract individuals 18
© 2013 BORO Solutions Some references for metaphysical choices Focusing on choices for ontological engineering: Partridge, C. (2002). LADSEB-CNR - Technical report 06/02 - Note: A Couple of Meta-Ontological Choices for Ontological Architectures. Padova, LADSEB CNR, Italy Recap of (2002) paper above. Borgo, S., A. Gangemi, N. Guarino, C. Masolo, and A. Oltramari. (2002). WonderWeb Deliverable D15 Ontology RoadMap. The WonderWeb Library of Foundational Ontologies and the DOLCE ontology. p. 11 - 4 ROADMAP OF MAJOR ONTOLOGICAL CHOICES Salim K. Semy, Mary K. Pulvermacher, Leo J. Obrst. (2004). Toward the Use of an Upper Ontology for U.S. Government and U.S. Military Domains: An Evaluation. DOCUMENT NUMBER MTR 04B0000063, MITRE TECHNICAL REPORT p. 3-10 Table 2. Ontological Choices Summary. Guidelines for Developing Ontological Architectures in Modelling and Simulation (Book Chapter): Authors: Chris Partridge, Andy Mitchell, and Sergio de Cesare. Chapter 2 in Ontology, Epistemology, and Teleology for Modeling and Simulation: Philosophical Foundations for Intelligent M&S Applications. Series: Intelligent Systems Reference Library, Vol. 44. Andreas Tolk, (Editor). ISBN 978-3-642-31139-0. Publisher: Springer. Will find a discussion of these choices in any introductory textbook on metaphysics. 19
© 2013 BORO Solutions BOROs choices Extensionalism – I – Universals Extensionalism – II – Individuals Higher order universals Perdurantism Eternalism Relative space-time Modally unextended individuals Materialism Topology of time –linear Exclude abstract individuals 20
© 2013 BORO Solutions Making metaphysical choices They are not independent, so need to be made consistently For example, it is difficult to be extensional and include abstract objects, which typically have no extension Choices need to reflect the enterprise system ontologys (engineering) goals 21
Basis For Choosing The Right Top Ontology
© 2013 BORO Solutions Basis for making the choices We call these types of sophistication Based upon the notion of what makes a good scientific theory – so have a pedigree Normally list six characteristics generality. The degree by which the scope of the types in the improved model can be increased without the loss of information simplicity. The degree by which the model can be made less complex explanatory power. The ability of the improved model to give increased meaning fruitfulness. The degree to which the improved model can meet currently unspecified requirements or is easily extendable to do so objectivity. The ability of the model to provide a more objective (shared) understanding of the world : in particular, to index a thing to its mode of existence as opposed to its mode of representation and/or application precision. The ability of the improved model to give a more precise picture of the business object These types are closely inter-related In our experience, the result is the identification of very general (highly re-usable) business patterns 23
Methodological Themes Ways of explaining what is happening in the ontological analysis process 24
© 2013 BORO Solutions Methodological Themes (A slightly arbitrary selection) All have the similar underlying theme; change can lead to improvements Opaque Vision Things are not what they seem to be; we need to (re-)educate our current vision Paradigm Shift Reorganise the internal structure – see things in a (radically) new way Shift to a new technology (e.g. from pen and paper to computing) needs a corresponding conceptual shift. Refactoring Internal reorganisation can lead to substantially better knowledgebase Rational Reconstruction Improvements in in clarity and exactness These all offer support for a revisionary rather than a descriptive approach. A top ontology is a mechanism for delivering these kinds of changes.
© 2013 BORO Solutions Opaque Vision 26 Now... that should clear up a few things around here transparent vision No need for a top ontology opaque vision Useful to have a top ontology
© 2013 BORO Solutions From code to ontological refactoring 27 Code refactoring is a "disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior", undertaken in order to improve some of the nonfunctional attributes of the software. Advantages include improved code readability and reduced complexity to improve the maintainability of the source code, as well as a more expressive internal architecture or object model to improve extensibility. Ontology refactoring is a "disciplined technique for restructuring an existing body of knowledge, altering its internal structure without changing its external behavior", undertaken in order to improve some of the nonfunctional features of the knowledgebase. Advantages include improved readability and reduced complexity to improve maintainability, as well as a more expressive internal architecture or model to improve extensibility.
© 2013 BORO Solutions Paradigm Shift (Kuhn) Kuhn claims that the major scientific revolutions were conceptual rather than empirical shifts. They were about looking at the existing empirical data in a new way. He used the gestalt pictures as an analogy.
© 2013 BORO Solutions Carnaps Rational Reconstruction 'Rational reconstruction (rationale Nachkonstruktion) was the underlying motivation of his first major book, Der logische Aufbau der Welt. "This holds especially for the problems that are posed, and for the essential features of the method which was employed. The main problem concerns the possibility of the rational reconstruction of the concepts of all fields of knowledge on the basis of concepts that refer to the immediately given. By rational reconstruction is here meant the searching out of new definitions for old concepts. The old concepts did not ordinarily originate by way of deliberate formulation, but in more or less unreflected and spontaneous development. The new definitions should be superior to the old in clarity and exactness, and, above all, should fit into a systematic structure of concepts. Such a clarification of concepts, nowadays frequently called explication, still seems to me one of the most important tasks of philosophy, especially if it is concerned with the main categories of human thought." 1928, Der logische Aufbau der Welt, Berlin-Schlachtensee: Weltkreis-Verlag, 2nd ed. Hamburg: Felix Meiner, 1961 This evolved into explication: The task of making more exact a vague or not quite exact concept used in everyday life or in an earlier stage of scientific or logical development, or rather of replacing it by a newly constructed, more exact concept, belongs among the most important tasks of logical analysis and logical construction. We call this the task of explicating, or of giving an explication for, the earlier concept... (Carnap 1947, 8-9.) 1947, Meaning and Necessity, Chicago: University of Chicago Press, 2nd ed. 1956 29
© 2013 BORO Solutions Summary An ontology is the set of things whose existence is acknowledged by a particular theory or system of thought. A top ontology should set the architecture for the overall ontology; One way it can do this is by providing a categorical breakdown of the things that exist. Another way is by making the major ontological choices The BORO top ontology uses these categories based upon their criterion of identity: Things = 4D extension Classes = instances tuples = objects in places It explicitly makes the major ontological choices. 31
Ontolog: Database And Ontology Mini-Series Data and process revisited: ontology driving a paradigm shift in the development of business application systems.
Chapter 7 System Models.
Ontology From Wikipedia, the free encyclopedia In philosophy, ontology (from the Greek oν, genitive oντος: of being (part. of εiναι: to be) and –λογία:
System Components as a litmus test for your ontological architecture Ontology for Big Systems & Systems Engineering Ontology Summit 2012 Session-11 Thu.
Lecture 6: Software Design (Part I) Dr Valentina Plekhanova University of Sunderland, UK
LOGIC AND ONTOLOGY Both logic and ontology are important areas of philosophy covering large, diverse, and active research projects. These two areas overlap.
PROGRAMMING LANGUAGES The Study of Programming Languages.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 29Slide 1 Configuration management l Managing the products of system change l Objectives.
Limitations of the relational model 1. 2 Overview application areas for which the relational model is inadequate - reasons drawbacks of relational DBMSs.
1 Science as a Process Chapter 1 Section 2. 2 Objectives Explain how science is different from other forms of human endeavor. Identify the steps that.
Copyright: SIPC From Ontology to Data Model: Choices and Design Decisions Matthew West Reference Data Architecture and Standards Manager Shell International.
Executional Architecture Lecture Conceptual vs execution Conceptual Architecture Execution Architecture Component Connector Domain-level responsibilities.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Fundamentals, Design, and Implementation, 9/e Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques.
Conceptual modelling. Overview - what is the aim of the article? ”We build conceptual models in our heads to solve problems in our everyday life”… ”By.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Lecture 5: Requirements Engineering Dr Valentina Plekhanova University of Sunderland, UK
1 CS 385 Fall 2006 Chapter 1 AI: Early History and Applications.
This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the design, communication,
© 2011 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary. Towards a Model-Based Characterization of Data and Services Integration Paul.
Chapter 1 Introduction to Databases 1. Chapter 1 - Objectives Some common uses of database systems. Characteristics of file-based systems. Problems with.
Conceptual / semantic modelling
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
Maria Daskalaki Center for Cultural Informatics Institute of Computer Science Foundation for Research and Technology – Hellas Nuremberg Philosophy.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
1 Knowledge Representation Introduction KR and Logic.
Jane Reid, BSc/IT DB, QMUL, 7/1/02 1 Lecture plan Outline of DB design process Entity-relationship model –Entities and attributes –Relationships.
Modeling Main issues: What do we want to build How do we write this down.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
2 1 Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Relational Database and Data Modeling
Ontology Development in the Sciences Some Fundamental Considerations Ontolytics LLC Topics: Possible uses of ontologies Ontologies vs. terminologies.
Author: Graeme C. Simsion and Graham C. Witt Chapter 12 Physical Database Design.
Science and Technology Norwegian University of NTNU Rolv Bræk, January Introduction to Systems Engineering by Rolv Bræk NTNU.
1 A Conceptual Framework of Data Mining Y.Y. Yao Department of Computer Science, University of Regina Regina, Sask., Canada S4S 0A2
Ontological Resources and Top-Level Ontologies Nicola Guarino LADSEB-CNR, Padova, Italy
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS.
The Relational Model and Normalization (1)
Domain-Specific Software Engineering Alex Adamec.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
14% of the exam 24 questions 1 Carol Pattyn 6/18/13.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Ontology Development Kenneth Baclawski Northeastern University Harvard Medical School.
Chapter 4 Project Management.
Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
Business Domain Modelling Principles Theory and Practice HYPERCUBE Ltd 7 CURTAIN RD, LONDON EC2A 3LT Mike Bennett, Hypercube Ltd.
1 Chapter 1 Introduction to Databases Transparencies.
© 2017 SlidePlayer.com Inc. All rights reserved.