<!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>Ontologies Guidelines and Evaluation of Ontologies Mapping Tools and Algorithms</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ian Harrow</string-name>
          <email>ian.harrow@pistoiaalliance.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Romacker</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrea Splendiani</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Negru</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Peter Woollard</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Scott Markel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yasmin Alam-Faruque</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Koch</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Erfan Younesi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>James Malone</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ernesto Jimenez-Rui</string-name>
          <email>Ernesto.Jimenez-Ruiz@cs.ox.ac.uk</email>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Pistoia Alliance Ontologies Mapping Project, Pistoia Alliance Inc.</institution>
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The Pistoia Alliance Ontologies Mapping project1 was set up to find or create better tools or services for mapping between ontologies in the same domain and to establish best practices for ontology management in the Life Sciences. It was selected by the Pistoia Alliance Operations Team for development of a formal business case following proposal of the idea through the Pistoia Alliance Ideas Portfolio Platform (IP3)2. 1http://www.pistoiaalliance.org/projects/ontologies-mapping 2https://www.qmarkets.org/live/pistoia/home 3https://pistoiaalliance.atlassian.net/wiki/display/PUB/Ontologies+Map ping+Resources</p>
      </abstract>
      <kwd-group>
        <kwd>Ontologies</kwd>
        <kwd>Mapping</kwd>
        <kwd>Guidelines</kwd>
        <kwd>Tool</kwd>
        <kwd>Algorithm</kwd>
        <kwd>Evaluation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
    </sec>
    <sec id="sec-2">
      <title>2. Ontologies Guidelines</title>
      <p>The project has delivered a set of guidelines for best practice which
build on existing standards. In the poster we will show how these
guidelines can be used as a "checklist" to support the application and
mapping of source ontologies in the disease and phenotype domain.
These guidelines are accessible on a public wiki3.
An important output of this project was to specify the requirements for
an Ontologies Mapping (OM) Tool. Three major aspects of the user
requirements comprised of:-1) User interface; 2) Framework, including
ontology matching algorithms and 3) Import and export of mappings.
The detailed requirements were used to establish that OM tools already
exist which substantially meet them. Therefore, we developed a formal
process to define and submit a request for information (RFI) from
existing ontologies mapping tool providers to enable their evaluation.
In the poster we will summarise our findings from evaluation of seven
ontologies mapping tools from academic and commercial providers.
The RFI materials are also accessible on the public wiki3.</p>
    </sec>
    <sec id="sec-3">
      <title>4. Evaluation of Ontology Matching Algorithms for Disease and</title>
    </sec>
    <sec id="sec-4">
      <title>Phenotype</title>
      <p>A critical component of any Ontologies Mapping tool is the embedded
ontology matching algorithm. Therefore, the Pistoia Alliance
Ontologies Mapping Project supported the development and evaluation
of ontology matching algorithms through sponsorship and organisation
of the new Disease and Phenotype track for OM-20164 at ISWC 20165.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Future Plans for an Ontologies Mapping service</title>
      <p>The Ontologies Mapping project has defined the business requirements
for an ontologies mapping service, which use an ontologies matching
algorithm in the service workflow. We are also conducting a
questionnaire to survey Pistoia Alliance members to understand the
likely demand for such a service to help us to determine whether it
should be implemented in future.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>