BioHealth Informatics Group QA of Ontologies OWL Tutorial December 6 th 2005.

Slides:



Advertisements
Similar presentations
Author: Graeme C. Simsion and Graham C. Witt Chapter 12 Physical Database Design.
Advertisements

Lectures on File Management
How do we know when we know. Outline  What is Research  Measurement  Method Types  Statistical Reasoning  Issues in Human Factors.
Embrace the Elephant A few provocative questions….
Techniques for Proving the Completeness of a Proof System Hongseok Yang Seoul National University Cristiano Calcagno Imperial College.
Introducing Formal Methods, Module 1, Version 1.1, Oct., Formal Specification and Analytical Verification L 5.
Testing and Quality Assurance
1 Inductive Equivalence of Logic Programs Chiaki Sakama Wakayama University Katsumi Inoue National Institute of Informatics ILP
Hoare’s Correctness Triplets Dijkstra’s Predicate Transformers
Rigorous Software Development CSCI-GA Instructor: Thomas Wies Spring 2012 Lecture 11.
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
Inference Tasks and Computational Semantics. Key Concepts Inference tasks Syntactic versus semantic approach to logic Soundness & completeness Decidability.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
ISBN Chapter 3 Describing Syntax and Semantics.
Copyright © 2006 Addison-Wesley. All rights reserved. 3.5 Dynamic Semantics Meanings of expressions, statements, and program units Static semantics – type.
1 Semantic Description of Programming languages. 2 Static versus Dynamic Semantics n Static Semantics represents legal forms of programs that cannot be.
CS 355 – Programming Languages
BioHealth Informatics Group Domenico’s Conclusion Ontologies are the basic infrastructures for modern interoperable information systems and are the groundwork.
Chapter 6: Design of Expert Systems
Knowledge Representation & Reasoning.  Introduction How can we formalize our knowledge about the world so that:  We can reason about it?  We can do.
Midterm Review Evaluation & Research Concepts Proposals & Research Design Measurement Sampling Survey methods.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
CS 330 Programming Languages 09 / 18 / 2007 Instructor: Michael Eckmann.
Tools for Developing and Using DAML-Based Ontologies and Documents Richard Fikes Deborah McGuinness Sheila McIlraith Jessica Jenkins Son Cao Tran Gleb.
CS 330 Programming Languages 09 / 16 / 2008 Instructor: Michael Eckmann.
Formal methods Basic concepts. Introduction  Just as models, formal methods is a complement to other specification methods.  Standard is model-based.
Describing Syntax and Semantics
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
Data Management: Documentation & Metadata Types of Documentation.
Classroom Assessment A Practical Guide for Educators by Craig A
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Reliability and Validity what is measured and how well.
MEASUREMENT CHARACTERISTICS Error & Confidence Reliability, Validity, & Usability.
1 Program Correctness CIS 375 Bruce R. Maxim UM-Dearborn.
1 Chapter 7 Propositional and Predicate Logic. 2 Chapter 7 Contents (1) l What is Logic? l Logical Operators l Translating between English and Logic l.
CS 4100 Artificial Intelligence Prof. C. Hafner Class Notes Jan 19, 2012.
Ontology Repositories: Discussions and Perspectives Mathieu d’Aquin KMi, the Open University, UK
Formal Models in AGI Research Pei Wang Temple University Philadelphia, USA.
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Dr. Shazzad Hosain Department of EECS North South Universtiy Lecture 04 – Part A Knowledge Representation and Reasoning.
ISBN Chapter 3 Describing Semantics -Attribute Grammars -Dynamic Semantics.
CS 363 Comparative Programming Languages Semantics.
1 Berendt: Advanced databases, first semester 2011, 1 Advanced databases – Inferring new knowledge.
Ontological Engineering 101 DAML + OIL Workshop February
Copyright © Cengage Learning. All rights reserved. 8 Introduction to Statistical Inferences.
3.2 Semantics. 2 Semantics Attribute Grammars The Meanings of Programs: Semantics Sebesta Chapter 3.
ISBN Chapter 3 Describing Semantics.
Chapter 3 Part II Describing Syntax and Semantics.
CSE Winter 2008 Introduction to Program Verification January 31 proofs through simplification.
Today’s Topics Introduction to Proofs Rules of Inference Rules of Equivalence.
1 Quality Attributes of Requirements Documents Lecture # 25.
Research Methodology and Methods of Social Inquiry Nov 8, 2011 Assessing Measurement Reliability & Validity.
An Axiomatic Basis for Computer Programming Robert Stewart.
DISCRETE COMPUTATIONAL STRUCTURES CSE 2353 Fall 2010 Most slides modified from Discrete Mathematical Structures: Theory and Applications by D.S. Malik.
Chapter 2.11 Program Validation. Reliable System = Reliable Hardware AND Reliable Software AND Compatible Hardware and Software.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
CSC3315 (Spring 2009)1 CSC 3315 Languages & Compilers Hamid Harroud School of Science and Engineering, Akhawayn University
C HAPTER 3 Describing Syntax and Semantics. D YNAMIC S EMANTICS Describing syntax is relatively simple There is no single widely acceptable notation or.
Using OWL 2 For Product Modeling David Leal Caesar Systems April 2009 Henson Graves Lockheed Martin Aeronautics.
© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.
SNOMED CT Data Quality and Data Repair Dr Jeremy Rogers IHTSDO Consultant Terminologist Principal Terminology Specialists NHS HSCIC IHTSDO ImpSIG, Amsterdam,
1 Ontological Foundations For SysML Henson Graves September 2010.
© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.
1 Modeling Formalism (Modeling Language Foundations) System Modeling Assessment & Roadmap Working Group Meeting – SE DSIG Reston – March, 2016 Yves BERNARD.
Spring 2017 Program Analysis and Verification
Software Verification and Validation
EA C461 – Artificial Intelligence Logical Agent
Logical architecture refinement
Department of Computer Science Abdul Wali Khan University Mardan
ONTOMERGE Ontology translations by merging ontologies Paper: Ontology Translation on the Semantic Web by Dejing Dou, Drew McDermott and Peishen Qi 2003.
Presentation transcript:

BioHealth Informatics Group QA of Ontologies OWL Tutorial December 6 th 2005

BioHealth Informatics Group The GIGO Problem Logic may be necessary But it is not sufficient Can not validate all possible inferences in advance Instead must prove: Reasoner is sound Axioms are correct Induction does the rest

BioHealth Informatics Group Barriers to Ontology QA ►Absolute Measures ►No ‘Gold Standard’ ►Mutual cross validation only as good as the parts ►Manual checking error-prone ►and can’t measure HOW error prone because of (1) ►Comparitive Measures ►Better than worse does not imply good ►Relative Measures ►Provides unequivocal evidence of improvement ►But not of proximity to goal ►Falling error detection rate does not imply none exist

BioHealth Informatics Group Types of Axiom Quality Philosophical Rigour Ontological commitment Content correctness Fitness for purpose

BioHealth Informatics Group Philosophical Rigour ►2500 years of research ►Theories of time, mereonomy, containment ►Often FOL, so not computable ►Similar upper level ontologies ►DOLCE, BFO ►But not 100% agreement: Realist vs Cognitivist

BioHealth Informatics Group Ontological commitment ►Formally specified semantic equivalence ►Logical transformation to canonical form ►Semantically equivalent but no logical transform ►‘Fixation of femur by means of inserting pins’ ►‘Insertion of pins to fixate the femur’ ►Metamodel rules/commitments ►Arbitrary choice of preferred form ►Conventions to be applied throughout ontology ►And by all applications that use it

BioHealth Informatics Group Content correctness ►Metadata Provenance, lexical annotations etc ►Truth ►‘Structure of labial vein’ is-a ‘Superficial vein of face’ ►Completeness – ambiguity and omission ►Thymus secretes Thymosin; Thymosin is-a Hormone …but omits Thymus is-a endocrine gland ►Conciseness ►Redundant inclusion of inferrable axioms ►Consistency – contradictory, duplicated, circular ►endocrine surgery vs endocrine surgeons ►Traumatic unilateral amputation Unilateral traumatic amputation

BioHealth Informatics Group Fitness for Purpose ►Best theories no guarantee of usability or utility ►Lab experiences no predictor of field behaviour ►All for nothing, if user can’t use it ►Interrater variability

BioHealth Informatics Group Fitness for Purpose: Inter-rater variability XXXXXXXXXX XXXXXXXXXXXXXX XXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXX XXXXXX XXXXXXXXXXXX XXXXXXXXXXXX XXXXXXXXXXXX Headcloth Cloth Scarf Model Person Woman Adults Standing Background Brown Blue Chemise Dress Tunics Clothes Suitcase Luggage Attache case Brass Instrument French Horn Horn Tuba

BioHealth Informatics Group Fitness for Purpose: Inter-rater variability ►Miscoding ►Code meaning is inappropriate to thing being described ►Instrument definitely not a french horn ►Missed coding ►Not coding something that could be coded ►No code for the table/platform ►Overcoding ►Code meaning is more detailed than justified ►Can the gender really be determined? ►Undercoding ►Code meaning is less detailed than justified ►Brass Instument vs Tuba

BioHealth Informatics Group Fitness for Purpose What ontological properties.. ►Increase usablility and utility? ►Are a prerequisite for them? ►Decrease usability or utility?

BioHealth Informatics Group Ontology QA How much quality do we need? Perfection is unattainable Trade-offs between quality and… Performance Cost Maintainability Usability Acceptance Utility

BioHealth Informatics Group Need for CQI, not final QA Assure the p rocess not the product Use/Test cases & exemplars REVIEW Explore consequences APPLY QI Algorithm DEVISE QI Algorithm ASSESS Identify problems