<!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>Document-centric work ow: a framework for ontology development</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Aisha Blfgeh</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>Phillip Lord</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Computing and Information Technology, King Abdulaziz University</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>School of Computing Science</institution>
          ,
          <addr-line>Newcastle University</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Ontologies are widely used in the eld of health-care and life sciences, because of their capability to adapt with such a complex and heterogeneous information. Therefore, the process of ontology construction is important especially with such complex and potentially changeable knowledge; also cooperation between domain specialists and ontology developers is essential, which will improve the reliability and robustness of the ontology overtime. However, tools used by ontology developers are less understood by the domain specialists who use di erent formalisms and tools to represent and manipulate their data. As developing ontologies is a collaborative process between di erent specialities with a variety of tools, it is challenging the integration of the di erent mindsets in dealing with knowledge in order to develop robust ontologies. Therefore, incorporating those tools into one framework to develop ontologies is a promising mechanism to interact directly with specialists through their preferred tools.In this research, we are proposing a document-centric work ow centred around the use of English and standard o ce tooling which should ease the interaction between a domain specialist and an ontologist. There are two popular tools that most biologists tend to use in managing their data; Excel spreadsheet and Word document. Hence, the proposed work which has been done so far is facilitating the use of these two applications. This work ow using Word documents is illustrated in Figure 1. First, the framework is started by the biologists creating an Excel spreadsheet and formatting their sheet as they preferred using all Excel facilities. This spreadsheet is then digested into an ontology by a developer using a programming textual environment of Tawny-OWL [1]. Any modi cations to the spreadsheet is possible as it remains as a part of the ontology's source code. The second framework is started when ontologists generate a literate ontology using Lentic package for documentation3 which can be transformed into Word documents, which biologists can then read and edit using Microsoft Word facilities. The biologists are not required to understand any ontological statements or scripts as the source code is embedded within the text and we have the choice to show or hide it. Also, the ontology developers can incorporate all changes to the text and ontological statements as needed. In this case, an arbitrary and frequently transformation of documents will be performed using Tawny-OWL, as well as 3 http://homepages.cs.ncl.ac.uk/phillip.lord/lentic/lenticular.html</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        maintaining the original les as part of the ontology source code. Similar
approaches such as CLCE (Common Logic Controlled English) 4 and Intermediate
representation [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] also facilitate using English language to increase readability
of the source code. Nonetheless, we produce more readable and also editable
document which can be commented and updated in a normal and more familiar
environment for the biologists and users but still need ontologists to recast any
changes in the source code according to the updated document.
In this study, we designed a framework for developing ontologies which is centred
around the use of Excel spreadsheet and Word document to cooperate with
nonontological specialists who are satis ed to interact with text environment rather
4 http://www.jfsowa.com/clce/specs.htm
than a complex ontology development environment. We can successfully generate
Word versions of a literate ontology.
      </p>
      <p>We are now moving toward the testing phase; one aim of this poster is to
approach life sciences community to help in appraising our methodology of
constructing ontologies. In this early stage of the study, we would like to encourage
intrested SWAT4LS' participants (biologists and developers) to test and
evaluate our proposed framework. This engagement will be bene cal to improve the
interaction activities between di erent specialities' users.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Lord</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>The Semantic Web takes Wing: Programming Ontologies with TawnyOWL</article-title>
          .
          <source>OWLED 2013 (March</source>
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Rector</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zanstra</surname>
            ,
            <given-names>P.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solomon</surname>
            ,
            <given-names>W.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rogers</surname>
            ,
            <given-names>J.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baud</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ceusters</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Claassen</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirby</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodrigues</surname>
            ,
            <given-names>J.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mori</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          , der
          <string-name>
            <surname>Haring</surname>
            ,
            <given-names>E.J.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wagner</surname>
          </string-name>
          , J.:
          <article-title>Reconciling users' needs and formal requirements: issues in developing a reusable ontology for medicine</article-title>
          .
          <source>IEEE Transactions on Information Technology in Biomedicine</source>
          <volume>2</volume>
          (
          <issue>4</issue>
          ) (
          <year>Dec 1998</year>
          )
          <volume>229</volume>
          {
          <fpage>242</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>