<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Improved explanations in the Protege OWL ontology editor</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Cilliers Pretorius</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>prtpie</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>@myuct.ac.za</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Meyer</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>tmeyer@cs.uct.ac.za</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Centre for Arti cial Intelligence Research</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Cape Town</institution>
          ,
          <country country="ZA">South Africa</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A logic-based reasoning system is a software system that generates conclusions that are consistent with a knowledge base (KB) or ontology. However, because the steps taken to generate a conclusion are usually hidden from the user, it cannot be guaranteed that the user accepts and acts upon the conclusion[3]. This leads to systems that provide explanations and justi cations as a key part of the system's design[5]. Novice and expert users greatly bene t from explanations[1].</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>C. Pretorius &amp; T. Meyer</p>
      <p>If a formal de nition or AnnotationProperty is added to the OWL
standards, then the de nition used in this paper will be changed to re ect the OWL
standards. Explanations are still invoked when the user clicks on the \Explain
inference" button that appears next to each axiom. Checkboxes are added to allow
the user to decide if annotated explanations should be displayed or keywords
expanded. Users are allowed to have the checkboxes checked in any combination. If
neither is checked, the output is exactly as the original Explanation Workbench
would produce.</p>
      <p>Keyword expansion is implemented as a single function. The function iterates
through the axiom and replaces every keyword with the equivalent expansion. It
returns the expanded axiom to the renderer to be displayed on the screen. If the
checkbox for explanatory annotations is checked, the method checks if the axiom
has any annotations attached to it. If there is at least one annotation, it iterates
over all annotations and checks if any annotation has the annotation property
\exp:Explanation". If this is true, the renderer will display the axiom (in its
original Manchester Syntax form) and append the explanatory annotation after
it. Note that this functionality requires the ontology creator to have de ned the
explanatory annotations beforehand.</p>
      <p>The source code of this extension of the Explanation Workbench can be
found and freely downloaded from the paper's GitHub repository3. It will require
Protege to be of use, which can be downloaded from protege.stanford.edu.
The More Readable Extension to the Explanation Workbench (MRE) is of
signi cant value to novice users since it allows them to more easily understand
description logics and the knowledge held by the ontology. It does not prohibit
the more rigid and formal notation, thereby bene ting expert users who might
prefer the more formal notation. It can allow all users to receive terminological
knowledge regarding the ontology with signi cantly greater ease and is therefore
of great bene t to users wanting to familiarise themselves with a new ontology.</p>
      <p>The next step in this research would be to create a tool to automatically
generate the explanatory annotations for axioms. This research could draw
inspiration from OWL Simpli ed English (OWLSE) and Attempto Controlled English
(ACE) to formulate the actual annotations. It might also look at Horridge's work
on justi cations to determine what axioms should get annotations if annotations
are prioritised to the most important axioms. Further research can also be done
to integrate the keyword expansion and the OWLSE and ACE syntaxes. This
can be integrated with user testing to evaluate the various attempts at natural
language expressions for OWL and the associated explanations.
3 https://github.com/Pietersielie/Explanation-Workbench-More-Readable-Extension
Improved explanations in the Protege OWL ontology editor</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Dhaliwal</surname>
            ,
            <given-names>J.S.:</given-names>
          </string-name>
          <article-title>An experimental investigation of the use of explanations provided by knowledge-based systems</article-title>
          .
          <source>Ph.D. thesis</source>
          , University of British Columbia (
          <year>1993</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sattler</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>The owl explanation workbench: A toolkit for working with justi cations for entailments in owl ontologies (</article-title>
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          :
          <article-title>Usability issues in knowledge representation systems</article-title>
          .
          <source>In: AAAI/IAAI</source>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          , et al.:
          <article-title>The protege project: a look back and a look forward</article-title>
          .
          <source>AI</source>
          matters
          <volume>1</volume>
          (
          <issue>4</issue>
          ),
          <volume>4</volume>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Teach</surname>
            ,
            <given-names>R.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shortli</surname>
            <given-names>e</given-names>
          </string-name>
          ,
          <string-name>
            <surname>E.H.</surname>
          </string-name>
          :
          <article-title>An analysis of physician attitudes regarding computerbased clinical consultation systems</article-title>
          .
          <source>Computers and Biomedical Research</source>
          <volume>14</volume>
          (
          <issue>6</issue>
          ),
          <volume>542</volume>
          {
          <fpage>558</fpage>
          (
          <year>1981</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>