Semantic Mapping of Clinical Model Data to Biomedical Terminologies to Facilitate Interoperability

Total Page:16

File Type:pdf, Size:1020Kb

Semantic Mapping of Clinical Model Data to Biomedical Terminologies to Facilitate Interoperability SEMANTIC MAPPING OF CLINICAL MODEL DATA TO BIOMEDICAL TERMINOLOGIES TO FACILITATE INTEROPERABILITY A thesis submitted to the University of Manchester for the degree of Doctor of Philosophy in the Faculty of Engineering and Physical Sciences 2008 By Rahil Qamar School of Computer Science Contents Abstract 17 Declaration 19 Copyright 20 Dedication 21 Acknowledgments 22 1 Introduction 24 1.1 The task of semantic interoperability . 25 1.2 The Research Agenda . 26 1.2.1 Research Objective . 27 1.2.2 Research Aim . 29 1.2.3 Research Question . 30 1.2.4 Research Contributions . 30 1.2.5 Significance of the Research . 31 1.2.6 The Research Programme . 32 1.3 Vocabulary and Notations . 35 1.4 Thesis Outline . 36 1.5 List of Publications . 37 2 Clinical Data Models and Terminologies 39 2.1 Why is the medical domain particularly complex? . 40 2.2 Problems facing interoperability standards . 42 2.3 Benefits of standardised data in health care . 43 2.4 Clinical Data Models . 44 2.4.1 Need for Structured Clinical Data Models . 45 2 2.4.2 Examples of Data Models . 46 2.4.2.1 The openEHR Archetype Models . 46 2.4.2.2 HL7 CDA documents . 47 2.4.3 History of openEHR Archetypes . 49 2.4.3.1 Archetype Modeling Features . 50 2.4.3.2 Purpose of Archetypes . 51 2.4.3.3 Reasons for selecting Archetypes . 52 2.4.3.4 Term Binding in Archetypes . 53 2.5 The openEHR Information Model . 54 2.5.1 The openEHR ENTRY submodel . 55 2.5.1.1 The Observation subclass . 57 2.5.1.2 Structure and Syntax of Archetype Models . 58 2.5.1.3 Archetype Example . 60 2.6 Clinical Terminologies . 63 2.6.1 Need for Clinical Terminologies . 64 2.6.2 Problems with clinical terminologies and their use . 65 2.6.3 Examples of Terminologies . 66 2.6.3.1 LOINC . 66 2.6.3.2 GALEN . 67 2.6.3.3 SNOMED CT . 68 2.6.4 History of SNOMED CT . 69 2.6.4.1 Reasons for selecting SNOMED CT . 71 2.6.4.2 The SNOMED CT Concept Hierarchies . 72 2.6.4.3 SNOMED CT Core Model . 74 2.6.4.4 SNOMED Pre and Post Coordination . 76 2.7 Critical Comparison with Comparable Models . 77 2.7.1 Terminology Comparison: SNOMED versus GALEN . 77 2.7.2 Data Model Comparison: Archetypes versus HL7 . 79 2.7.3 Additional Vocabulary . 82 2.8 Summary . 83 3 Related Work 84 3.1 Mapping from Data Source to Terminologies . 85 3.1.1 Projects using Medical narratives and free text . 85 3.1.1.1 RELMA . 85 3.1.1.2 MedLEE . 85 3 3.1.1.3 Comparative Overview . 87 3.1.2 Projects using Databases . 88 3.1.2.1 MediClass . 88 3.1.2.2 Comparative Overview . 88 3.1.3 Projects using Ontologies . 89 3.1.3.1 BioPAX . 89 3.1.3.2 Anchor-PROMPT . 89 3.1.3.3 Comparative Overview . 89 3.1.4 Projects using Clinical Data Models . 90 3.1.4.1 Ocean Terminology Service . 90 3.1.4.2 Comparative Overview of OTS . 90 3.1.4.3 HL7 Terminfo . 92 3.1.4.4 Critical Overview of Terminfo . 94 3.2 Other Recent Efforts . 94 3.2.1 SNOMED CT Subsets . 95 3.2.2 Code Binding Interface . 95 3.3 Summary . 97 4 The MoST Methodology and System 98 4.1 Background . 99 4.2 The MoST Methodology . 100 4.3 The MoST System: Semi-automated Term Finding and Mapping 101 4.3.1 The Four Archetypes used in Development . 103 4.3.2 The Preparation Step . 103 4.3.3 Tier 1: Automated Term Finding Process . 104 4.3.3.1 Step 1: Context Independent Methods . 105 4.3.3.2 Step 2: Context Dependent Methods . 108 4.3.3.3 Step 3: Filtering Process . 110 4.3.3.4 Step 3a: Filtering Rules . 111 4.3.4 Tier 2: Assisted Manual Data Mapping Process . 117 4.4 Summary . 119 5 Evaluation I: Quantitative Analysis 120 5.1 Evaluation Criteria . 121 5.2 Evaluation Methodology . 122 5.2.1 The Four Evaluation Archetypes . 123 4 5.3 Statistical Measures for Evaluation . 125 5.3.1 Sensitivity and Specificity . 126 5.3.2 Mapping Coverage . 129 5.3.3 Trust Score . 131 5.3.4 Inter-rater Reliability . 132 5.4 Summary of Evaluation Data Results . 133 5.5 Evaluation Phase 1: Comparative Quantitative Analysis . 134 5.5.1 Comparison of Sensitivity and Specificity . 135 5.5.2 Comparison of Coverage Rating . 136 5.5.3 Comparison of Trust Score . 138 5.5.4 Comparison of Inter-rater reliability . 140 5.6 Evaluation Phase 2: Comparative Data Analysis . 141 5.7 Summary . 141 6 Evaluation II: Qualitative Analysis 143 6.1 Issues with the Evaluation Archetypes and SNOMED . 144 6.1.1 The Histology Pap Archetype . 144 6.1.1.1 Issues with the Histology Pap archetype . 145 6.1.1.2 SNOMED Issues with Histology Pap Archetype . 149 6.1.2 The Tendon Babinski Archetype . 150 6.1.2.1 Issues with the Tendon Babinski archetype . 151 6.1.2.2 SNOMED Issues with Tendon babinski archetype 156 6.1.3 The Visual Acuity Archetype . 164 6.1.3.1 Issues with the Visual acuity archetype . 165 6.1.3.2 SNOMED Issues with Visual acuity archetype . 168 6.1.4 The Body Weight Archetype . 170 6.1.4.1 Issues with the Body weight archetype . 171 6.1.4.2 SNOMED Issues with Body weight archetype . 172 6.2 Revising the Histology pap archetype as a gold standard . 173 6.2.1 Summary of changes to Histology Pap archetype . 175 6.2.2 Evaluation of revised Histology Pap Archetype . 175 6.3 Summary . 177 7 General Issues, Criteria and Guidelines 178 7.1 Integration Issues and Modeling Criteria . 179 7.1.1 Issues Integrating the Archetype and SNOMED Model . 179 5 7.1.1.1 Different Modeling Techniques . 180 7.1.1.2 Data categorisation to reflect intended semantics 180 7.1.1.3 Semantic results as against lexical results . 181 7.1.1.4 Context information . 182 7.1.2 Issues with Archetype Models . 184 7.1.2.1 Categorisation of Archetypes . 184 7.1.2.2 Specific and General Content . 187 7.1.2.3 Context Information . 188 7.1.2.4 Naming Conventions . 190 7.1.3 Issues with the SNOMED CT Terminology Model . 191 7.1.3.1 Concept Categorisation . 192 7.1.3.2 Internal use of category names . 194 7.1.3.3 Disjoint Axioms . 194 7.1.3.4 Post-coordinated concepts . 197 7.2 Data Modeling Guidelines . 198 7.2.1 General Archetype Modeling Guidelines . 199 7.2.2 Observation Archetype Model Guidelines . 200 7.2.3 Procedure Archetype Model Guidelines . 201 7.3 Terminology Guidelines . 202 7.3.1 General Terminology Modeling Guidelines . 203 7.3.2 Concepts inclusion in SNOMED . 204 7.4 Summary . 206 8 Future Work and Conclusion 207 8.1 Summary of Research Work . 207 8.2 Implications for Archetypes and SNOMED CT . 209 8.3 Future Work . 211 8.3.1 Specific-to-general approach . 211 8.3.2 Inclusion of ancestor archetype fragments . 211 8.3.3 Inclusion of SNOMED grandchildren concepts . 213 8.3.4 Filtering based on SNOMED Concept Model . 213 8.3.5 Post-coordinated results . 214 8.3.6 Extending testing to HL7 CDA . 216 8.4 Conclusion . 216 Bibliography 218 6 A EXTRA TABLES AND FIGURES 228 A.1 HL7 Reference Information Model . 228 A.2 HL7 Clinical Document Architecture . 228 B EVALUATION DETAILS 231 B.1 Description of Evaluators . 231 B.2 First Phase Evaluation Process . 232 B.3 Phase 1 of Evaluation: Fleiss’ Kappa Inter-rater Reliability . 237 B.4 Phase 2 of Evaluation: Comparative Data Analysis . 243 B.5 Evaluation Results Sheet for the Archetypes . 253 7 List of Tables 2.1 Characteristics of Conventional versus Clinical Data Warehouses (Taken from [72]). ............................... 41 2.2 The nineteen SNOMED CT Concept hierarchies. 72 2.3 The eight most relevant SNOMED CT Concept Hierarchies. Note: The Context dependent category has been changed to Situation with explicit context since the July 2006 release. 73 3.1 Value set constraints using SNOMED CT for some of the major classes of the Act and Entity RIM classes. NOTE: ≤ implies ‘the class and any of its subtypes’ (Taken from [64]). 93 4.1 Total number of SNOMED (SCT) codes that were returned by MoST before and after the filtering process. 112 4.2 Total number of SNOMED (SCT) codes that were retained at the end of application of Rule 2 for the Autopsy archetype. 115 4.3 Total number of SNOMED (SCT) codes that were retained at the end of application of Rule 3 for the Autopsy archetype. 116 5.1 Symbols used to measure degree of reflexes in the tendon babinski archetype and the corresponding lexical annotations. 125 5.2 Example scores of the two SNOMED codes for the archetype fragment ‘cervical smear’, to illustrate the application of Criteria 1 and 2. Scores are between 0 and 10, and have been assigned by 5 experts. 130 5.3 Summary of.
Recommended publications
  • The Semantic Web - ISWC 2004
    Lecture Notes in Computer Science 3298 The Semantic Web - ISWC 2004 Third International Semantic Web Conference, Hiroshima, Japan, November 7-11, 2004. Proceedings Bearbeitet von Sheila A. McIlraith, Dimitris Plexousakis, Frank van Harmelen 1. Auflage 2004. Taschenbuch. xxxv, 844 S. Paperback ISBN 978 3 540 23798 3 Format (B x L): 15,5 x 23,5 cm Gewicht: 970 g Weitere Fachgebiete > EDV, Informatik > Datenbanken, Informationssicherheit, Geschäftssoftware > Datenkompression, Dokumentaustauschformate schnell und portofrei erhältlich bei Die Online-Fachbuchhandlung beck-shop.de ist spezialisiert auf Fachbücher, insbesondere Recht, Steuern und Wirtschaft. Im Sortiment finden Sie alle Medien (Bücher, Zeitschriften, CDs, eBooks, etc.) aller Verlage. Ergänzt wird das Programm durch Services wie Neuerscheinungsdienst oder Zusammenstellungen von Büchern zu Sonderpreisen. Der Shop führt mehr als 8 Millionen Produkte. Preface The 3rd International Semantic Web Conference (ISWC 2004) was held Novem- ber 7–11, 2004 in Hiroshima, Japan. If it is true what the proverb says: “Once by accident, twice by habit, three times by tradition,” then this third ISWC did indeed firmly establish a tradition. After the overwhelming interest in last year’s conference at Sanibel Island, Florida, this year’s conference showed that the Semantic Web is not just a one-day wonder, but has established itself firmly on the research agenda. At a time when special interest meetings with a Seman- tic Web theme are springing up at major conferences in numerous areas (ACL, VLDB, ECAI, AAAI, ECML, WWW, to name but a few), the ISWC series has established itself as the primary venue for Semantic Web research. Response to the call for papers for the conference continued to be strong.
    [Show full text]
  • Trombert-Paviot, Alan Rector, Robert Baud, Pieter
    HIMJ: Reviewed articles The development of CCAM: The new French coding system of clinical HIMJ HOME procedures Beatrice Trombert-Paviot, Alan Rector, Robert Baud, Pieter CONTENTS Zanstra, Caroline Martin, Egbert van der Haring, Lucienne Clavel and Jean Marie Rodrigues GUIDELINES Abstract MISSION A new French coding system of clinical procedures, the Classification Commune Des Actes Medicaux (CCAM), has been developed at the turn of the millennium (between 1996 and CONTACT US 2001). Two methodologies were used: a traditional domain- experts consensus method, and an artificial-intelligence-based semantic representation. An economic evaluation of clinical procedures was also undertaken for the rating for fee-for- service payment. We present the methodologies used and stress how the European Union research project, ‘European Consortium, Generalised Architecture for Languages, Encyclopaedias and Nomenclatures in Medicine’ (GALEN), facilitated the sharing and maintaining of consistent medical knowledge. This country case study highlights the significant cost to individual countries in developing their own HIMAA classifications in isolation. It also demonstrates the benefits of Locked Bag 2045 North Ryde, NSW contributing to international efforts such as GALEN that enable Australia 1670 harmonisation, yet still allow for diversity. ABN 54 008 451 910 Key words : Artificial intelligence; coding system; clinical procedures; terminology; GALEN Introduction Following an Act passed in the National Assembly and issued in January 1993, the Ministry
    [Show full text]
  • Ontologies and the Semantic Web
    Ontologies and the Semantic Web Ian Horrocks <[email protected]> Information Management Group School of Computer Science University of Manchester The Semantic Web Today’s Web • Distributed hypertext/hypermedia • Information accessed via (keyword based) search and browse • Browser tools render information for human consumption What is the Semantic Web? • Web was “invented” by Tim Berners-Lee (amongst others), a physicist working at CERN • His vision of the Web was much more ambitious than the reality of the existing (syntactic) Web: “… a set of connected applications … forming a consistent logical web of data …” “… an extension of the current web in which information is given well-defined meaning, better enabling computers and people to work in cooperation …” • This vision of the Web has become known as the Semantic Web Hard Work using “Syntactic Web” Find images of Peter Patel-Schneider, Frank van Harmelen and Alan Rector… Rev. Alan M. Gates, Associate Rector of the Church of the Holy Spirit, Lake Forest, Illinois Impossible (?) using “Syntactic Web” • Complex queries involving background knowledge – Find information about “animals that use sonar but are neither bats nor dolphins” , e.g., Barn Owl • Locating information in data repositories – Travel enquiries – Prices of goods and services – Results of human genome experiments • Finding and using “web services” – Given a DNA sequence, identify its genes, determine the proteins they can produce, and hence the biological processes they control • Delegating complex tasks to web “agents” – Book me a holiday next weekend somewhere warm, not too far away, and where they speak either French or English What is the Problem? Consider a typical web page: • Markup consists of: – rendering information (e.g., font size and colour) – Hyper-links to related content • Semantic content is accessible to humans, but not (easily) to computers… What is the (Proposed) Solution? • Add semantic annotations to web resources Dr.
    [Show full text]
  • Knowledge Driven Software and “Fractal Tailoring”: Ontologies in Development Environments for Clinical Systems
    Knowledge Driven Software and “Fractal Tailoring”: Ontologies in development environments for clinical systems Alan RECTOR School of Computer Science, University of Manchester, UK Abstract. Ontologies have been highly successful in applications involving annotation and data fusion. However, ontologies as the core of “Knowledge Driven Architectures” have not achieved the same influence as “Model Driven Architectures”, despite the fact that many biomedical applications require features that seem achievable only via ontological technologies – composition of descriptions, automatic classification and inference, and management of combinatorial explosions in many contexts. Our group adopted Knowledge Driven Architectures based on ontologies to address these problems in the early 1990s. In this paper we discuss first the use cases and requirements and then some of the requirements for more effective use of Knowledge Driven Architectures today: clearer separation of language and formal ontology, integration with contingent knowledge, richer and better distinguished annotations, higher order representations, integration with data models, and improved auxiliary structures to allow easy access and browsing by users. Keywords. Ontology based systems, Model driven architecture, OWL Citation. Rector A; Knowledge driven software and “fractal tailoring”: Ontologies in development environments for clinical systems. 2010; Formal Ontology in Information Systems (FOIS 2010): IOS Press; 17-30. 1. Introduction In the past fifteen years, the notion of “ontology” has gone from being an obscure “O” word to almost a synonym for “good”. Everybody thinks, and is often told, that they need ontologies. At the same time ontologies have, on the one hand, become dissociated from other forms of knowledge representation and, on the other hand, been taken by some to be all of knowledge representation.
    [Show full text]
  • Analysing Syntactic Regularities and Irregularities in SNOMED-CT Eleni Mikroyannidi*, Robert Stevens, Luigi Iannone and Alan Rector
    Mikroyannidi et al. Journal of Biomedical Semantics 2012, 3:8 http://www.jbiomedsem.com/content/3/1/8 JOURNAL OF BIOMEDICAL SEMANTICS RESEARCH Open Access Analysing Syntactic Regularities and Irregularities in SNOMED-CT Eleni Mikroyannidi*, Robert Stevens, Luigi Iannone and Alan Rector Abstract Motivation: In this paper we demonstrate the usage of RIO; a framework for detecting syntactic regularities using cluster analysis of the entities in the signature of an ontology. Quality assurance in ontologies is vital for their use in real applications, as well as a complex and difficult task. It is also important to have such methods and tools when the ontology lacks documentation and the user cannot consult the ontology developers to understand its construction. One aspect of quality assurance is checking how well an ontology complies with established ‘coding standards’; is the ontology regular in how descriptions of different types of entities are axiomatised? Is there a similar way to describe them and are there any corner cases that are not covered by a pattern? Detection of regularities and irregularities in axiom patterns should provide ontology authors and quality inspectors with a level of abstraction such that compliance to coding standards can be automated. However, there is a lack of such reverse ontology engineering methods and tools. Results: RIO framework allows regularities to be detected in an OWL ontology, i.e. repetitive structures in the axioms of an ontology. We describe the use of standard machine learning approaches to make clusters of similar entities and generalise over their axioms to find regularities. This abstraction allows matches to, and deviations from, an ontology’s patterns to be shown.
    [Show full text]
  • Ontologies and the Semantic Web
    Ontologies and the Semantic Web Ian Horrocks <[email protected]> Information Management Group School of Computer Science University of Manchester The Semantic Web Today’s Web • Distributed hypertext/hypermedia • Information accessed via (keyword based) search and browse • Browser tools render information for human consumption What is the Semantic Web? • Web was “invented” by Tim Berners-Lee (amongst others), a physicist working at CERN • His vision of the Web was much more ambitious than the reality of the existing (syntactic) Web: “… a set of connected applications … forming a consistent logical web of data …” “… an extension of the current web in which information is given well-defined meaning, better enabling computers and people to work in cooperation …” • This vision of the Web has become known as the Semantic Web Hard Work using “Syntactic Web” Find images of Peter Patel-Schneider, Frank van Harmelen and Alan Rector… Rev. Alan M. Gates, Associate Rector of the Church of the Holy Spirit, Lake Forest, Illinois Impossible (?) using “Syntactic Web” • Complex queries involving background knowledge – Find information about “animals that use sonar but are neither bats nor dolphins” , e.g., Barn Owl • Locating information in data repositories – Travel enquiries – Prices of goods and services – Results of human genome experiments • Finding and using “web services” – Given a DNA sequence, identify its genes, determine the proteins they can produce, and hence the biological processes they control • Delegating complex tasks to web “agents” – Book me a holiday next weekend somewhere warm, not too far away, and where they speak either French or English What is the Problem? Consider a typical web page: • Markup consists of: – rendering information (e.g., font size and colour) – Hyper-links to related content • Semantic content is accessible to humans, but not (easily) to computers… What is the (Proposed) Solution? • Add semantic annotations to web resources Dr.
    [Show full text]
  • Thesis Submitted to the University of Manchester for the Degree of Doctor of Philosophy in the Faculty of Medicine
    Structured Methods of Information Management for Medical Records A thesis submitted to the University of Manchester for the degree of Doctor of Philosophy in the Faculty of Medicine 1993 William Anthony Nowlan Table of Contents Structured Methods of Information Management for Medical Records 1 Table of Contents 2 List of Figures 8 Abstract 9 Declaration 11 Acknowledgements 12 The Author 13 1 Purpose and Introduction 14 1.1 The purpose of this thesis 14 1.2 Motivations for the work 14 1.2.1 Research on clinical information systems: PEN&PAD 14 1.2.2 Characteristics of clinical information systems 15 1.3 What is to be represented: the shared medical model 15 1.3.1 An example: thinking about ‘stroke’ 16 1.3.2 Medical limits on what can be modelled 16 1.4 Scope of the work in this thesis: the limits on context and modelling 17 1.5 Organisation of the thesis 17 2 Coding and Classification Schemes 18 2.1 The changing task: the move from populations to patients 18 2.2 Current methods: nomenclatures and classifications 19 2.2.1 Nomenclatures. 19 2.2.2 Classifications 19 2.2.3 Classification rules 20 2.3 An exemplar classification: the International Classification of Diseases (ICD) 20 2.3.1 History of the International Classification of Diseases 20 2.3.2 The organisation of ICD-9 21 2.3.3 Classification principles within ICD-9 23 2.3.4 Goal-orientation 24 2.3.5 The use of the classification structure: abstraction 24 2.3.6 Extending the coverage of a classification and the ‘combinatorial explosion’ 25 2 Contents 3 2.4 Multiaxial nomenclatures and classifications: SNOMED 26 2.4.1 Organisation of SNOMED 26 2.4.2 SNOMED coding of terms 27 2.4.3 Sense and nonsense in SNOMED 28 2.5 The structure within SNOMED fascicles 28 2.5.1 Abstraction in SNOMED 29 2.5.2 Relationships between topographical concepts in the SNOMED topography fascicle 31 2.6 SNOMED enhancements.
    [Show full text]
  • An Introduction to OWL
    An Introduction to OWL Sean Bechhofer School of Computer Science University of Manchester, UK http://www.cs.manchester.ac.uk OWL: Web Ontology Language • OWL is an ontology language designed for the Semantic Web – It provides a rich collection of operators for forming concept descriptions – It is a W3C standard, promoting interoperation and sharing between applications – It has been designed to be compatible with existing web standards • In this talk, we’ll see some of the motivation behind OWL and some details of the language Introduction to the Semantic Web Tutorial Towards a Semantic Web • The Web was made possible through established standards – TCP/IP for transporting bits down a wire – HTTP & HTML for transporting and rendering hyperlinked text • Applications able to exploit this common infrastructure – Result is the WWW as we know it • 1st generation web mostly handwritten HTML pages • 2nd generation (current) web often machine generated/active – Both intended for direct human processing/interaction • In next generation web, resources should be more accessible to automated processes – To be achieved via semantic markup – Metadata annotations that describe content/function Introduction to the Semantic Web Tutorial What’s the Problem? • Consider a typical web page • Markup consists of: – rendering information (e.g., font size and colour) – Hyper-links to related content • Semantic content is accessible to humans but not (easily) to computers… • Requires (at least) NL understanding Introduction to the Semantic Web Tutorial A Semantic
    [Show full text]
  • OWL 2 Web Ontology Language Primer (Second Edition) W3C Recommendation 11 December 2012
    OWL 2 Web Ontology Language Primer (Second Edition) W3C Recommendation 11 December 2012 OWL 2 Web Ontology Language Primer (Second Edition) W3C Recommendation 11 December 2012 This version: http://www.w3.org/TR/2012/REC-owl2-primer-20121211/ Latest version (series 2): http://www.w3.org/TR/owl2-primer/ Latest Recommendation: http://www.w3.org/TR/owl-primer Previous version: http://www.w3.org/TR/2012/PER-owl2-primer-20121018/ Editors: Pascal Hitzler, Wright State University Markus Krötzsch, University of Oxford Bijan Parsia, University of Manchester Peter F. Patel-Schneider, Nuance Communications Sebastian Rudolph, FZI Research Center for Information Technology Please refer to the errata for this document, which may include some normative corrections. A color-coded version of this document showing changes made since the previous version is also available. This document is also available in these non-normative formats: PDF version. See also translations. Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines, a running example showing how OWL 2 can be used to represent first simple information and then more complex information, how OWL 2 manages ontologies, and finally the distinctions between the various sublanguages of OWL 2.
    [Show full text]
  • Proceedings Ontology Matching 2009
    Ontology Matching OM-2009 Papers from the ISWC Workshop Introduction Ontology matching is a key interoperability enabler for the Semantic Web, as well as a useful tactic in some classical data integration tasks. It takes the ontologies as input and determines as output an alignment, that is, a set of correspondences between the semantically related entities of those ontologies. These correspondences can be used for various tasks, such as ontology merging and data translation. Thus, matching ontologies enables the knowledge and data expressed in the matched ontologies to interoperate. The workshop has three goals: • To bring together leaders from academia, industry and user institutions to assess how academic advances are addressing real-world requirements. The workshop will strive to improve academic awareness of industrial and final user needs, and therefore, direct research towards those needs. Simul- taneously, the workshop will serve to inform industry and user represen- tatives about existing research efforts that may meet their requirements. The workshop will also investigate how the ontology matching technology is going to evolve. • To conduct an extensive and rigorous evaluation of ontology matching approaches through the OAEI (Ontology Alignment Evaluation Initiative) 2009 campaign, http://oaei.ontologymatching.org/2009. This year's OAEI campaign introduces two new tracks about oriented alignments and about instance matching (a timely topic for the linked data community). Therefore, the ontology matching evaluation initiative itself will provide a solid ground for discussion of how well the current approaches are meeting business needs. • To examine similarities and differences from database schema matching, which has received decades of attention but is just beginning to transition to mainstream tools.
    [Show full text]
  • A Practical Introduction to Protégé OWL
    A Practical Introduction to Protégé OWL Session 1: Primitive Classes Nick Drummond, Matthew Horridge, Olivier Dameron, Alan Rector, Hai Wang Overview (morning) ‣ Tutorial Aims ‣ OWL Language Overview ‣ Language constructs ‣ Primitive Pizzas ‣ Creating a class hierarchy ‣ Basic relations ‣ Basic Reasoning ‣ Class consistency ‣ Your first defined class ‣ Q&A © 2006, The University of Manchester 2 Overview (afternoon) ‣ Formal Semantics of OWL ‣ Harder but more fun ‣ Advanced Reasoning ‣ Defined Classes ‣ Using a reasoner for computing a classification ‣ Common Mistakes ‣ Q&A © 2006, The University of Manchester 3 Aims of this morning ‣ Make OWL (DL) more approachable ‣ Get you used to the tool ‣ Give you a taste for the afternoon session © 2006, The University of Manchester 4 Exposing OWL © 2006, The University of Manchester 5 What is OWL? ‣ OWL is the Web Ontology Language ‣ It’s part of the Semantic Web framework ‣ It’s a standard © 2006, The University of Manchester 6 OWL has explicit formal semantics Can therefore be used to capture knowledge in a machine interpretable way © 2006, The University of Manchester 7 OWL helps us... ‣ Describe something, rather than just name it ‣ Class (BlueThing) does not mean anything ‣ Class (BlueThing complete owl:Thing restriction (hasColour someValuesFrom (Blue))) has an agreed meaning to any program accepting OWL semantics © 2006, The University of Manchester What is the Semantic Web? ‣ A vision of a computer-understandable web ‣ Distributed knowledge and data in reusable form ‣ XML, RDF(S), OWL just
    [Show full text]
  • Barry Smith PUBLICATIONS June 11, 2021
    Barry Smith PUBLICATIONS June 11, 2021 Google scholar PubMed PhilPapers Researchgate Semantic Scholar ORCID / Scopus / dblp / ResearcherID / Microsoft Academic Books Edited Conference Proceedings Journal Special Issues Refereed Articles in Scholarly Journals Non-Refereed Articles in Scholarly Journals Chapters in Books Papers in Refereed Conference Proceedings Preprints Reports Posters and Abstracts Databases and Ontologies Letters to the Editor Articles in Dictionaries and Encyclopedias Translations Bibliographies Reviews and Review Articles BOOKS 1. Barry Smith (ed.), Structure and Gestalt: Philosophy and Literature in Austria- Hungary and Her Successor States, Amsterdam: John Benjamins, 1981, x + 348pp. Reviews: P. M. Simons, Conceptus, 17 (1983), 131–134. J. Shearmur, Free Life, 3/2 (1983), 16–17. W. Stock, “Österreichische Philosophie”, Philosophischer Literaturanzeiger, 37 (1984), 93–96. R. Cardinal, Explorations in Knowledge, 2 (1985), 68–69. 2. Barry Smith (ed.), Parts and Moments. Studies in Logic and Formal Ontology, Munich: Philosophia, 1982, reprinted 2001, 564pp. Reviews: V. Muñoz Delgado, Estudios Filosoficos, (1982) 38, 611–613. I. Niiniluoto, Zentralblatt für Mathematik, (1983) 489, 15–16. D. P. Henry, History and Philosophy of Logic, (1983) 4, 228–229. F. G. Asenjo, Rivista Latinoamericana de Filosofía, (1983) 9, 174–177. U. Charpa, “Neues zur Lehre von den Ganzen und Teilen”, Philosophische Rundschau, 1/2 (1984), 52–59. J.M. Salanskis, “Parties, Moments et Modalités”, Critique, 443 (1984), 290–296. BARRY SMITH - LIST OF PUBLICATIONS PAGE 2 R. Sokolowski, Review of Metaphysics, 38 (1984), 140–142. B. Schuwey, Philosophy and Phenomenological Research, 45 (1985), 474–476. G. Berger, Noûs, (1986) 20, 115–121. J. Woleński, “Czeski i momenty”, Studia Filozoficzne, 1–2/242–243 (1986), 191–195.
    [Show full text]