DOCSLIB.ORG

Gellish a Generic Extensible Ontological Language

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Gellish a Generic Extensible Ontological Language Gellish A Generic Extensible Ontological Language - Design and Application of a Universal Data Structure - Cover illustration: Museum: Boymans van Beuningen, Rotterdam, The Netherlands Pieter Brueghel de Oude, The Tower of Babel (Genesis 11:1-9) At first everyone spoke the same language… Then people said: “Let's build a city with a tower that reaches to the sky! We'll become famous.” But the LORD said: “Come on! Let's confuse them by making them speak different languages, then they won't be able to understand each other…” So the people had to stop building the city… That is why the city was called Babel (confusing) -because there the LORD confused the language of the whole world… Nederlandse vertaling: Ooit werd er op de hele aarde één enkele taal gesproken… De mensen zeiden: laten we een stad bouwen met een toren die tot in de hemel reikt. Dat zal ons beroemd maken… Maar God dacht: …laten wij …spraakverwarring onder hen teweegbrengen, zodat ze elkaar niet meer verstaan… en de bouw van de stad werd gestaakt… Zo komt het dat die stad Babel (verwarring) heet, want daar bracht God verwarring in de taal die op de hele aarde gesproken werd… Gellish A Generic Extensible Ontological Language - Design and Application of a Universal Data Structure - Proefschrift ter verkrijging van de graad van doctor aan de Technische Universiteit Delft, op gezag van de Rector Magnificus prof.dr.ir. J.T. Fokkema, in het openbaar te verdedigen ten overstaan van een commissie, door het College voor Promoties aangewezen, op woensdag 14 september 2005 te 10.30 uur door Andries Simon Hendrik Paul VAN RENSSEN werktuigkundig ingenieur geboren te Utrecht Dit proefschrift is goedgekeurd door de promotor: Prof.dr.ir. J.L.G. Dietz Samenstelling promotiecommissie: Rector Magnificus, voorzitter Prof.dr.ir. J.L.G. Dietz, Technische Universiteit Delft, promotor Prof.dr. J.S. Dhillon, Technische Universiteit Delft Prof.dr.ir. P.A. Kroes, Technische Universiteit Delft Prof.dr. R.A. Meersman, Vrije Universiteit, Brussel, België Prof.dr.ir. A.W.M. Meijers, Technische Universiteit Delft Prof.dr. B. Smith, State University of New York at Buffalo, United States of America Ir. G.J. van Luijk, Technische Universiteit Delft, voormalig directeur Shell Global Solutions International Published and distributed by: DUP Science DUP Science is an imprint of Delft University Press P.O. Box 98 2600 MG Delft The Netherlands Telephone: +31 15 278 5678 Telefax: +31 15 278 5706 E-mail: [email protected] ISBN 90-407-2597-4 Keywords: ontology, data modeling, standardization, product modeling, language, engineering, dictionary, taxonomy, data exchange, data storage, application interface Copyright © 2005 by A.S.H.P. van Renssen All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the author. Printed in The Netherlands Table of content Table of content Samenvatting ..........................................................................................................................IX Summary.............................................................................................................................. XIX Nomenclature.................................................................................................................... XXIX 1 Introduction....................................................................................................................... 1 1.1 Objectives and approach...............................................................................................................1 1.2 Related initiatives.........................................................................................................................5 2 Philosophical perspective ............................................................................................... 13 2.1 Ontological models.....................................................................................................................13 2.2 Language independent ontologies and the unique identification of anything............................13 2.2.1 Synonyms and Homonyms.............................................................................................17 2.3 Integration of ontologies ............................................................................................................18 2.3.1 The solvability of the classification and ontology integration problem .........................21 2.3.2 The position of individual things in the ontology ..........................................................23 2.4 Summary of basic concepts........................................................................................................24 2.4.1 Presentation and scope ...................................................................................................24 2.4.2 Basic semantic concepts: Standardized types of relationships.......................................24 2.4.3 Definition of additional semantic concepts ....................................................................33 2.4.4 Individual things and Kinds of things (concepts)...........................................................36 2.4.5 Specialization hierarchy .................................................................................................40 2.4.6 The Upper ontology........................................................................................................44 2.4.7 Discriminating aspect for specialization.........................................................................44 2.4.8 Requirements for high quality definitions......................................................................46 2.4.9 Discriminating aspects used for prime specialization ....................................................47 3 Details of the Gellish language....................................................................................... 51 3.1 Language definition versus language usage...............................................................................51 3.2 Phenomena – Totalities and aspects ...........................................................................................53 3.2.1 A specialization hierarchy of phenomena ......................................................................53 3.2.2 Totalities.........................................................................................................................55 3.2.3 Phenomena as nodes in a semantic network...................................................................58 3.2.4 The existence of totalities...............................................................................................58 3.2.5 Aspects ...........................................................................................................................59 3.2.5.1 An ontology of number ...............................................................................................62 3.2.5.2 Mathematical operations and functions .....................................................................63 3.2.5.3 Ontology of space.......................................................................................................64 3.3 Facts and their dynamics – Ordinary facts and Occurrences......................................................64 3.3.1 Atomic facts ...................................................................................................................64 3.3.2 Expression of facts by relations between things.............................................................66 3.3.3 Elementary facts and roles in relations...........................................................................69 3.3.4 Complex facts, messages, product models and templates ..............................................71 3.3.5 Ordinary facts (static facts) ............................................................................................73 3.3.6 Occurrences as dynamic facts.........................................................................................75 3.3.7 The relationship between ordinary facts and occurrences - to be and to become ..........77 3.3.8 Functions, roles and occurrences....................................................................................79 3.3.8.1 What is a function?.....................................................................................................79 3.3.8.2 The term function used to indicate a subtype of occurrence ......................................80 3.3.8.3 The term function used as a reference to a totality in a role......................................82 3.3.8.4 The term function used to indicate a subtype of role..................................................83 3.3.8.5 The term function used to indicate an expression of a correlation ............................85 3.3.8.6 The term function used to indicate a mathematical equation.....................................86 V Table of content 3.3.8.7 Functional decomposition – decomposition of functions (occurrences) ....................88 3.3.9 The ontology of kinds of relations .................................................................................88 3.3.9.1 Relations between individual things...........................................................................90 3.3.9.2 Relations between kinds of things – expression of knowledge ...................................93
Load more

Recommended publications
  • Data Warehouse: an Integrated Decision Support Database Whose Content Is Derived from the Various Operational Databases
    1 www.onlineeducation.bharatsevaksamaj.net www.bssskillmission.in DATABASE MANAGEMENT Topic Objective: At the end of this topic student will be able to: Understand the Contrasting basic concepts Understand the Database Server and Database Specified Understand the USER Clause Definition/Overview: Data: Stored representations of objects and events that have meaning and importance in the users environment. Information: Data that have been processed in such a way that they can increase the knowledge of the person who uses it. Metadata: Data that describes the properties or characteristics of end-user data and the context of that data. Database application: An application program (or set of related programs) that is used to perform a series of database activities (create, read, update, and delete) on behalf of database users. WWW.BSSVE.IN Data warehouse: An integrated decision support database whose content is derived from the various operational databases. Constraint: A rule that cannot be violated by database users. Database: An organized collection of logically related data. Entity: A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data. Database management system: A software system that is used to create, maintain, and provide controlled access to user databases. www.bsscommunitycollege.in www.bssnewgeneration.in www.bsslifeskillscollege.in 2 www.onlineeducation.bharatsevaksamaj.net www.bssskillmission.in Data dependence; data independence: With data dependence, data descriptions are included with the application programs that use the data, while with data independence the data descriptions are separated from the application programs. Data warehouse; data mining: A data warehouse is an integrated decision support database, while data mining (described in the topic introduction) is the process of extracting useful information from databases.
    [Show full text]
  • Bi-Directional Transformation Between Normalized Systems Elements and Domain Ontologies in OWL
    Bi-directional Transformation between Normalized Systems Elements and Domain Ontologies in OWL Marek Suchanek´ 1 a, Herwig Mannaert2, Peter Uhnak´ 3 b and Robert Pergl1 c 1Faculty of Information Technology, Czech Technical University in Prague, Thakurova´ 9, Prague, Czech Republic 2Normalized Systems Institute, University of Antwerp, Prinsstraat 13, Antwerp, Belgium 3NSX bvba, Wetenschapspark Universiteit Antwerpen, Galileilaan 15, 2845 Niel, Belgium Keywords: Ontology, Normalized Systems, Transformation, Model-driven Development, Ontology Engineering, Software Modelling. Abstract: Knowledge representation in OWL ontologies gained a lot of popularity with the development of Big Data, Artificial Intelligence, Semantic Web, and Linked Open Data. OWL ontologies are very versatile, and there are many tools for analysis, design, documentation, and mapping. They can capture concepts and categories, their properties and relations. Normalized Systems (NS) provide a way of code generation from a model of so-called NS Elements resulting in an information system with proven evolvability. The model used in NS contains domain-specific knowledge that can be represented in an OWL ontology. This work clarifies the potential advantages of having OWL representation of the NS model, discusses the design of a bi-directional transformation between NS models and domain ontologies in OWL, and describes its implementation. It shows how the resulting ontology enables further work on the analytical level and leverages the system design. Moreover, due to the fact that NS metamodel is metacircular, the transformation can generate ontology of NS metamodel itself. It is expected that the results of this work will help with the design of larger real-world applications as well as the metamodel and that the transformation tool will be further extended with additional features which we proposed.
    [Show full text]
  • A Survey and Classification of Controlled Natural Languages
    A Survey and Classification of Controlled Natural Languages ∗ Tobias Kuhn ETH Zurich and University of Zurich What is here called controlled natural language (CNL) has traditionally been given many different names. Especially during the last four decades, a wide variety of such languages have been designed. They are applied to improve communication among humans, to improve translation, or to provide natural and intuitive representations for formal notations. Despite the apparent differences, it seems sensible to put all these languages under the same umbrella. To bring order to the variety of languages, a general classification scheme is presented here. A comprehensive survey of existing English-based CNLs is given, listing and describing 100 languages from 1930 until today. Classification of these languages reveals that they form a single scattered cloud filling the conceptual space between natural languages such as English on the one end and formal languages such as propositional logic on the other. The goal of this article is to provide a common terminology and a common model for CNL, to contribute to the understanding of their general nature, to provide a starting point for researchers interested in the area, and to help developers to make design decisions. 1. Introduction Controlled, processable, simplified, technical, structured,andbasic are just a few examples of attributes given to constructed languages of the type to be discussed here. We will call them controlled natural languages (CNL) or simply controlled languages.Basic English, Caterpillar Fundamental English, SBVR Structured English, and Attempto Controlled English are some examples; many more will be presented herein. This article investigates the nature of such languages, provides a general classification scheme, and explores existing approaches.
    [Show full text]
  • A Conceptual Framework for Constructing Distributed Object Libraries Using Gellish
    A Conceptual Framework for Constructing Distributed Object Libraries using Gellish Master's Thesis in Computer Science Michael Rudi Henrichs [email protected] Parallel and Distributed Systems group Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology June 1, 2009 Student Michael Rudi Henrichs Studentnumber: 9327103 Oranjelaan 8 2264 CW Leidschendam [email protected] MSc Presentation June 2, 2009 at 14:00 Lipkenszaal (LB 01.150), Faculty EWI, Mekelweg 4, Delft Committee Chair: Prof. Dr. Ir. H.J. Sips [email protected] Member: Dr. Ir. D.H.J. Epema [email protected] Member: Ir. N.W. Roest [email protected] Supervisor: Dr. K. van der Meer [email protected] Idoro B.V. Zonnebloem 52 2317 LM Leiden The Netherlands Parallel and Distributed Systems group Department of Software Technology Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology Mekelweg 4 2826 CD Delft The Netherlands www.ewi.tudelft.nl Sponsors: This master's thesis was typeset with MiKTEX 2.7, edited on TEXnicCenter 1 beta 7.50. Illustrations and diagrams were created using Microsoft Visio 2003 and Corel Paint Shop Pro 12.0. All running on an Acer Aspire 6930. Copyright c 2009 by Michael Henrichs, Idoro B.V. Cover photo and design by Michael Henrichs c 2009 http:nnphoto.lemantle.com All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the author.
    [Show full text]
  • A Pattern-Based Approach to Ontology-Supported Semantic Data Integration
    A pattern-based approach to ontology-supported semantic data integration Andreas A. Jordan Wolfgang Mayer Georg Grossmann Markus Stumptner Advanced Computing Research Centre University of South Australia, Mawson Lakes Boulevard, Mawson Lakes, South Australia 5095, Email: [email protected] Email: (wolfgang.mayer|georg.grossmann)@unisa.edu.au, [email protected] Abstract RSM2, ISO 159263 and Gellish4 standards are all used to represent information about engineering assets and Interoperability between information systems is associated maintenance information. However, there rapidly becoming an increasingly difficult issue, in exists considerable variation in the scope and level of particular where data is to be exchanged with exter- detail present in each standard, and where the infor- nal entities. Although standard naming conventions mation content covered by different standards over- and forms of representation have been established, laps, their vocabulary and representation used vary significant discrepancies remain between different im- considerably. Furthermore, standards like ISO 15926 plementations of the same standards and between dif- are large yet offer little guidance on how to represent ferent standards within the same domain. Further- particular asset information in its generic data struc- more, current approaches for bridging such hetero- tures. Heterogeneities arising from continued evolu- geneities are incomplete or do not scale well to real- tion of standards have further exacerbated the prob- world problems. lem. As a consequence, tool vendors formally support We present a pragmatic approach to interoperabil- the standard, yet their implementations do not inter- ity, where ontologies are leveraged to annotate proto- operate due to different use of the same standard or typical information fragments in order to facilitate varying assumptions about the required and optional automated transformation between fragments in dif- information held in each system.
    [Show full text]
  • Chapter 2: Database System Concepts and Architecture Define
    Chapter 2: Database System Concepts and Architecture define: data model - set of concepts that can be used to describe the structure of a database data types, relationships and constraints set of basic operations - retrievals and updates specify behavior - set of valid user-defined operations categories: high-level (conceptual data model) - provides concepts the way a user perceives data - entity - real world object or concept to be represented in db - attribute - some property of the entity - relationship - represents and interaction among entities representational (implementation data model) - hide some details of how data is stored, but can be implemented directly - record-based models like relational are representational low-level (physical data model) - provides details of how data is stored - record formats - record orderings - access path (for efficient search) schemas and instances: database schema - description of the data (meta-data) defined at design time each object in schema is a schema construct EX: look at TOY example - top notation represents schema schema constructs: cust ID; order #; etc. database state - the data in the database at any particular time - also called set of instances an instance of data is filled when database is populated/updated EX: cust name is a schema construct; George Grant is an instance of cust name difference between schema and state - at design time, schema is defined and state is the empty state - state changes each time data is inserted or updated, schema remains the same Three-schema architecture
    [Show full text]
  • Geographic Information Services
    Note: In order to continue to make this intellectual content available to the public, the National Transportation Library (NTL) copied the contents of this document from its original HTML file. The link to the original HTML file, which was last accessed on 2020-07-29, is https://ntlrepository.blob.core.windows.net/lib/4000/4200/4256/report.html NTL has preserved this content as it was presented in the HTML file, and has checked this document to ensure as complete a representation as possible. Questions about this file can be directed through the NTL Ask a Librarian service at: https://transportation.libanswers.com/form.php?queue_id=1810 _____________________________________________________________________________________ Geographic Information Services ON THE RESULTS OF A WORKSHOP ON GENERIC DATA MODEL FOR LINEAR REFERENCING SYSTEMS Authored by Workshop Participants with Alan Vonderohe (Principal Investigator Supported by The National Cooperative Highway Research Program Project) PREFACE The first draft of this report was prepared from notes and other materials developed during the workshop, audio tape recordings of the workshop sessions, and follow-up discussions with workshop participants. All participants were given the opportunity to review the first draft and provide responses. These responses were assimilated to identify both consensus revisions to the first draft and significant points of contention. The responders were informed of these results and asked to provide their opinions on each of the points of contention. The responders were also asked to provide measures of the relative importance of their positions on each of the points of contention (i.e., "critical", "strong preference", "weak preference"). The revised model presented in this second draft is true to the model as developed during the workshop and to the revisions on which there was consensus.
    [Show full text]
  • Data Models for Home Services
    __________________________________________PROCEEDING OF THE 13TH CONFERENCE OF FRUCT ASSOCIATION Data Models for Home Services Vadym Kramar, Markku Korhonen, Yury Sergeev Oulu University of Applied Sciences, School of Engineering Raahe, Finland {vadym.kramar, markku.korhonen, yury.sergeev}@oamk.fi Abstract An ultimate penetration of communication technologies allowing web access has enriched a conception of smart homes with new paradigms of home services. Modern home services range far beyond such notions as Home Automation or Use of Internet. The services expose their ubiquitous nature by being integrated into smart environments, and provisioned through a variety of end-user devices. Computational intelligence require a use of knowledge technologies, and within a given domain, such requirement as a compliance with modern web architecture is essential. This is where Semantic Web technologies excel. A given work presents an overview of important terms, vocabularies, and data models that may be utilised in data and knowledge engineering with respect to home services. Index Terms: Context, Data engineering, Data models, Knowledge engineering, Semantic Web, Smart homes, Ubiquitous computing. I. INTRODUCTION In recent years, a use of Semantic Web technologies to build a giant information space has shown certain benefits. Rapid development of Web 3.0 and a use of its principle in web applications is the best evidence of such benefits. A traditional database design in still and will be widely used in web applications. One of the most important reason for that is a vast number of databases developed over years and used in a variety of applications varying from simple web services to enterprise portals. In accordance to Forrester Research though a growing number of document, or knowledge bases, such as NoSQL is not a hype anymore [1].
    [Show full text]
  • Integrating Fuzzy Logic in Ontologies
    INTEGRATING FUZZY LOGIC IN ONTOLOGIES Silvia Calegari and Davide Ciucci Dipartimento di Informatica, Sistemistica e Comunicazione, Universita` degli Studi di Milano Bicocca, via Bicocca degli Arcimboldi 8, 20126 Milano, Italy Keywords: Concept modifiers, fuzzy logics, fuzzy ontologies, membership modifiers, KAON, ontology editor. Abstract: Ontologies have proved to be very useful in sharing concepts across applications in an unambiguous way. Nowadays, in ontology-based applications information is often vague and imprecise. This is a well-known problem especially for semantics-based applications, such as e-commerce, knowledge management, web por- tals, etc. In computer-aided reasoning, the predominant paradigm to manage vague knowledge is fuzzy set theory. This paper presents an enrichment of classical computational ontologies with fuzzy logic to create fuzzy ontologies. So, it is a step towards facing the nuances of natural languages with ontologies. Our pro- posal is developed in the KAON ontology editor, that allows to handle ontology concepts in an high-level environment. 1 INTRODUCTION A possible solution to handle uncertain data and, hence, to tackle these problems, is to incorporate fuzzy logic into ontologies. The aim of fuzzy set An ontology is a formal conceptualization of a partic- theory (Klir and Yuan, 1995) introduced by L. A. ular domain of interest shared among heterogeneous Zadeh (Zadeh, 1965) is to describe vague concepts applications. It consists of entities, attributes, rela- through a generalized notion of set, according to tionships and axioms to provide a common under- which an object may belong to a certain degree (typ- standing of the real world (Lammari and Mtais, 2004; ically a real number from the interval [0,1]) to a set.
    [Show full text]
  • Ontology Transformation: from Requirements to Conceptual Model*
    Justas Trinkunas, Olegas Vasilecas Ontology Transformation: from Requirements to .. SCIeNTIfIC PAPeRS, UNIVeRSITy of Latvia, 2009. Vol. 751 COMPUTER SCIENCE AND Information TECHNOLOGIES 52–64 P. Ontology Transformation: from Requirements to Conceptual Model* Justas Trinkunas1 and Olegas Vasilecas2, 3 1 Information Systems Research Laboratory, Faculty of Fundamental Sciences, Vilnius Gediminas Technical University, Sauletekio al. 11, LT-10223 Vilnius-40, Lithuania, [email protected] 2 Information Systems Research Laboratory, Faculty of Fundamental Sciences, Vilnius Gediminas Technical University, Sauletekio al. 11, LT-10223 Vilnius-40, Lithuania, [email protected] 3 Department of Computer Science, Faculty of Natural Sciences, Klaipeda University, Herkaus Manto 84, LT-92294 Klaipeda, [email protected] Information systems are increasingly complex, especially in the enormous growth of the volume of data, different structures, different technologies, and the evolving requirements of the users. Consequently, current applications require an enormous effort of design and development. The fast-changing requirements are the main problem in creating and/or modifying conceptual data models. To improve this process, we proposed to reuse already existing knowledge for conceptual modelling. In the paper, we have analysed reusable knowledge models. We present our method for creating conceptual models from various knowledge models. Keywords: transformation, ontology, data modelling. 1 Introduction Most of information systems analysts have at least once considered how many times they have to analyse the same problems, create and design the same things. Most of them ask, is it possible to reuse already existing knowledge? Our answer is yes. We believe that knowledge can and should be reused for information systems development.
    [Show full text]
  • A Framework for GIS-T Data Sharing
    Portland State University PDXScholar Center for Urban Studies Publications and Reports Center for Urban Studies 6-2000 A Framework for GIS-T Data Sharing Kenneth Dueker Portland State University J. Allison Butler Follow this and additional works at: https://pdxscholar.library.pdx.edu/cus_pubs Part of the Transportation Commons, and the Urban Studies and Planning Commons Let us know how access to this document benefits ou.y Citation Details Dueker, Kenneth and Butler, J. Allison, "A Framework for GIS-T Data Sharing" (2000). Center for Urban Studies Publications and Reports. 13. https://pdxscholar.library.pdx.edu/cus_pubs/13 This Working Paper is brought to you for free and open access. It has been accepted for inclusion in Center for Urban Studies Publications and Reports by an authorized administrator of PDXScholar. Please contact us if we can make this document more accessible: [email protected]. A Framework for GIS-T Data Sharing Kenneth J. Dueker Portland State University J. Allison Butler Hamilton County Tennessee December 1999 (Revised June 2000) Submitted to Transportation Research Part C: Emerging Technologies Center for Urban Studies Portland State University Portland OR 97207-0751 www.upa.pdx.edu/cus/ Abstract This paper develops a framework and principles for sharing of transportation data. The framework is intended to clarify roles among participants, data producers, data integrators, and data users. The principles are intended to provide guidance for the participants. Both the framework and the principles are based on an enterprise GIS-T data model that defines relations among transportation data elements. The data model guards against ambiguities and provides a basis for the development of the framework and principles for sharing of transportation data.
    [Show full text]
  • A CASE STUDY EXAMINATION DATA MODELLING in PRACTICE Paul
    A CASE STUDY EXAMINATION DATA MODELLING IN PRACTICE Paul Groves A report submitted in partial fulfilment of the requirements of the degree of Master of Commerce (Honours) to the University of New South Wales 1988 CERTIFICATION "I hereby declare that this submission is my own work and that, to the best of my knowledge and belief, it contains no material previously published or written by another person nor material which to a substantial extent has been accepted for the award of any other degree or diploma of a University or any other institute of higher learning, except where due acknowledgement is made in the text." ABSTRACT Data modelling for analysis and data base design is increasingly being viewed as a critical phase in the systems development process. This report is a comparative analysis of data modelling theory and practice. It investigates the nature of data and examines several data modelling methododologies. Current international standards for the conceptual data model are reviewed and based on this a reference framework is defined. This framework is used to compare four contemporary data modelling theories. Field testing of three of the methods is conducted, two case studies from a commercial environment and one from an academic setting. The case studies are conducted on a descriptive research basis. Results from the case studies confirm that data modelling represents a technique of growing impor­ tance in the systems development process. Increasing resources applied to the practice of relational database should ensure ensure ongoing theoretical interest and development. Although in the for­ mative stages of implementation and use, binary data modelling was seen to have achieved notable sucess in enhancing communication between project participants and in increasing user participation.
    [Show full text]