<!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>
      <journal-title-group>
        <journal-title>Pittsburgh, Pennsylvania, US
∗ Corresponding author.
† These authors contributed equally.
avi.shaked@cs.ox.ac.uk (A. Shaked); linikujp@gmail.com (A.Y. Lin)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Utilizing PROVE Tool to Evaluate Ontologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Avi Shaked</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Asiyah Yu Lin</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Oxford</institution>
          ,
          <addr-line>Oxford, Oxfordshire, OX1 3QD</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>OntoData Research and Solutions, LLC.</institution>
          ,
          <addr-line>Bethesda, Maryland, 20817</addr-line>
          ,
          <country country="US">United States of America</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>Ontology evaluation plays a crucial role in promoting the usability of ontology by ensuring it meets specific requirements. Evaluating an ontology is currently a complex task, typically involving manual and timeconsuming efforts. Furthermore, human experts based ontology evaluation is challenging, especially when ontologies become huge and in an iterative development process. PROVE tool is an open-source process modeling tool, aimed to promote computer-aided design and evaluation of process descriptions using coherent, multi-perspective representations. As a proof-of-concept, we utilized PROVE Tool to model and evaluate process descriptions of the Informed Consent Ontology (ICO). We found that a relatively low modeling effort using PROVE Tool can underpin effective evaluation and re-design of the ontology. It is promising to further develop PROVE Tool as a user-friendly ontology validation tool or vice versa, to use PROVE Tool to assist the ontology design, based on insights from rigorous conceptual process modeling.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;PROVE Tool</kwd>
        <kwd>ontology evaluation</kwd>
        <kwd>process modeling</kwd>
        <kwd>informed consent process 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Ontology evaluation can promote the quality of an ontology as well as contextualize and facilitate
its use in specific situations. Evaluating an ontology is a complex process, and often involves manual
and time-consuming efforts. To address the complexity of ontology evaluation, many ontology
evaluation frameworks have been developed. These frameworks provide structured methodologies,
criteria, and tools to assess the quality of an ontology across various dimensions, such as accuracy,
completeness, consistency, and relevance to a particular domain. The evaluation process can be
categorized into different approaches, including structural, functional, and usability evaluations.
Structural evaluation focuses on the internal consistency and logical coherence of the ontology's
structure, ensuring that relationships between concepts are accurately represented. Functional
evaluation, on the other hand, examines how well the ontology performs in specific tasks or
applications, such as information retrieval or data integration. Usability evaluation assesses the
ontology's ease of use, accessibility, and documentation, which are crucial for end-users and
developers [
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ].
      </p>
      <p>Ontology validation is a critical aspect of the ontology evaluation process. Validation focuses on
ensuring that an ontology faithfully represents the intended domain. It involves verifying that the
ontology's structure, concepts, relationships, and rules are correct, coherent, and logically consistent.
This step is essential for guaranteeing that the ontology can be reliably used in applications such as
data integration, semantic search, and knowledge management. Some tools like reasoners (e.g.,
Pellet, HermiT) and ontology editors (e.g., Protégé) provide functionalities to validate ontologies.
Most of the ontology validation work involves human expert review to ensure that the ontology
correctly captures the domain knowledge. Experts can provide insights into whether the ontology’s
concepts and relationships are properly modeled and relevant to the domain. The common practice
of a human expert to re-examine and validate ontology development typically involves visualizing
the ontology's structure. This is done by creating diagrams that illustrate the classes and their
relationships as defined in the ontology. These diagrams serve as a crucial tool for understanding
and verifying how well the ontology models the designated domain. The expert then compares this
diagrammatic representation to use case scenarios, ensuring that the ontology captures the necessary
concepts and relationships relevant to the specific application. This manual process is
timeconsuming, error-prone and has additional challenges with respect to scalability, and efficiency,
particularly in iterative development of an ontology. Computer-aided conceptual modeling can
provide additional discipline and rigor to the manual, validation process.</p>
      <p>
        PROVE Tool is an open-source process modelling tool, driven by a metamodel [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. It codifies a
pertinent process design domain framework [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which has previously been established as effective
in underpinning the evaluation of process descriptions in research [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. PROVE Tool allows
generating metamodel-compliant conceptual models of processes. It is designed to assist in the
design and analysis of process descriptions [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The tool provides an environment where users can
create detailed process models. These models describe the activities and artifacts involved in various
processes as well as their hierarchical arrangement and flow. One of the primary features of PROVE
Tool is its ability to verify process models based on its metamodel of the process. The tool allows its
users to check for logical consistency, ensuring that the processes are free from errors such as
unreachable states, incorrect scope of process hierarchy or contradictions. It also allows to check
that the process designs fulfil specified requirements to ensure they provide intended results, in the
form of artifacts and related achievements.
      </p>
      <p>
        In what follows, we describe our proof of concept using PROVE Tool to validate that the design
of the Informed Consent Ontology (ICO) [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ]. The significance of this work to the conceptual
modeling field is the demonstration of how conceptual modeling – particularly domain specific
conceptual modeling – can underpin rigorous validation of formal ontologies. Further automation of
the approach can significantly contribute to ontology evaluation.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. PROVE Tool validation of the Informed Consent process</title>
      <p>
        Informed consent is a fundamental ethical and legal requirement in many fields, especially in
research involving human participants, clinical trials, and medical treatments. It ensures that
individuals are fully aware of and understand the nature, purpose, risks, benefits, and alternatives of
a procedure or study before agreeing to participate. The ICO has modeled pertinent informed consent
processes, including: giving a subject adequate information of the study, providing adequate
opportunity for the subject to consider all options, ensuring that the subject has comprehended this
information, obtaining the subject’s voluntary agreement to participate and to continuingly provide
information as the subject or situation requires, and archiving the signed documents for possible
future usage [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The ICO modeling follows the Basic Formal Ontology based approach. Particularly,
the “planned process” defined in the Ontology for Biomedical Investigation is the top-level class for
the entire informed consent framework.
      </p>
      <p>
        Using PROVE Tool, processes of the Informed Consent Ontology – as shown in Figure 4 of [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]–
were re-modeled and illustrated as diagrams, as shown in Figure 1. Through this modeling process,
the human experts were able to quickly identify some deficiencies in the ontological modeling (of
ICO): 1) Informed consent form states are not explicitly defined. Specifically, this does not force
“Informed consent form approval” to occur before “Informed consent process” (as the artifact
required for the latter – “Informed consent form” – is already available as the output of another
process – “Informed consent form design”); 2) “Signed informed consent form” is an artifact in a
specific state. This can be improved by attributing a state to the previously designed and approved
artifact, and the process scope can be communicated using this; 3) There are no expectations stated
from the various activities within “Informed consent process,” as indicated by the lack of an outgoing
arrow the in lower diagram in Figure 1.
      </p>
      <p>Figure 2 shows the potential improvement of the informed consent processes, based on our
PROVE Tool analysis. Different states of the informed consent form after each specific process can
be explicitly identified, such as “designed informed consent form”, “approved informed consent
form” and “signed informed consent form” as the output of the “Informed consent form design,”
“Informed consent form approval” and “Informed consent process” processes respectively.</p>
      <p>Furthermore, PROVE Tool can also provide the interaction of the completed implementation of a
specific process by marking an artifact’s status as “achieved”. Figure 3 shows the “designed” state
of the informed consent form marked in green once the “status achieved” being clicked. This green
highlighted status is automatically shown in various PROVE Tool representations (in the user
interface).</p>
    </sec>
    <sec id="sec-3">
      <title>3. Conclusion and future work</title>
      <p>Ontologies play a significant role in our understanding of domains as well as in depicting desired
behavior of systems in those domains. The validation of ontologies remains a labor intensive, error
prone task. Here, for the first time, we utilized PROVE Tool to validate an ontology by rigorous,
metamodel-based conceptual modeling of its processes. This proof-of-concept, computer-aided
validation of the Informed Consent Ontology (ICO) shows the benefit of PROVE Tool’s multiple
graphical representations and perspectives in designing and evaluating the ontology. Specifically,
the tool aids the human experts to quickly validate the ontological model using multiple, coherent
diagrams. It is therefore promising to further develop PROVE Tool’s capabilities as a user-friendly
ontology validation tool or vice versa, using PROVE Tool to assist ontology design, particularly in
process-centered ontologies that can benefit from the tool’s ability to effectively capture and analyze
process models.</p>
      <p>Future work can further extend the tool to align the underlying metamodel with the Basic Formal
Ontology based planned process modeling, and to evaluate other ontologies using the tool. Currently
the modeling of an ontology using PROVE Tool is performed manually. We plan to automate this
modeling, e.g., by automatic transformation of OWL or RDF files into PROVE models and vice versa,
which will facilitate ontology validation and re-design.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>R.S.I. Wilson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.S.</given-names>
            <surname>Goonetillake</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.A.</given-names>
            <surname>Indika</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ginige</surname>
          </string-name>
          ,
          <article-title>A conceptual model for ontology quality assessment</article-title>
          ,
          <source>Semantic Web</source>
          <volume>14</volume>
          (
          <year>2023</year>
          )
          <fpage>1051</fpage>
          -
          <lpage>1097</lpage>
          . https://doi.org/10.3233/SW-233393.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Amith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.A.</given-names>
            <surname>Lossio-Ventura</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Tao, Assessing the practice of biomedical ontology evaluation: Gaps and opportunities</article-title>
          ,
          <source>J Biomed Inform</source>
          <volume>80</volume>
          (
          <year>2018</year>
          )
          <fpage>1</fpage>
          -
          <lpage>13</lpage>
          . https://doi.org/10.1016/j.jbi.
          <year>2018</year>
          .
          <volume>02</volume>
          .010.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Shaked</surname>
          </string-name>
          , PROVE Tool:
          <article-title>A tool for designing and analyzing process descriptions</article-title>
          ,
          <source>Software Impacts</source>
          <volume>12</volume>
          (
          <year>2022</year>
          )
          <article-title>100234</article-title>
          . https://doi.org/10.1016/j.simpa.
          <year>2022</year>
          .
          <volume>100234</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Shaked</surname>
          </string-name>
          , Y. Reich,
          <article-title>Designing development processes related to system of systems using a modeling framework</article-title>
          ,
          <source>Systems Engineering</source>
          <volume>22</volume>
          (
          <year>2019</year>
          )
          <fpage>561</fpage>
          -
          <lpage>575</lpage>
          . https://doi.org/10.1002/sys.21512.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Shaked</surname>
          </string-name>
          , Y. Reich,
          <article-title>Improving Process Descriptions in Research by Model-Based Analysis</article-title>
          ,
          <source>IEEE Systems Journal</source>
          <volume>15</volume>
          (
          <year>2021</year>
          )
          <fpage>435</fpage>
          -
          <lpage>444</lpage>
          . https://doi.org/10.1109/JSYST.
          <year>2020</year>
          .
          <volume>2990488</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A.</given-names>
            <surname>Shaked</surname>
          </string-name>
          , Y. Reich,
          <article-title>DESIGNING A MODEL-BASED, MULTI-PERSPECTIVE PROCESS DESIGN ENVIRONMENT</article-title>
          ,
          <source>Proc. Des. Soc</source>
          .
          <volume>1</volume>
          (
          <year>2021</year>
          )
          <fpage>1103</fpage>
          -
          <lpage>1112</lpage>
          . https://doi.org/10.1017/pds.
          <year>2021</year>
          .
          <volume>110</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Harris</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Manion</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Eisenhauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Shi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Karnovsky</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <article-title>Development of a BFO-Based Informed Consent Ontology (ICO)</article-title>
          , in: 2014. https://www.semanticscholar.org/paper/Development-of
          <article-title>-a-BFO-Based-</article-title>
          <string-name>
            <surname>Informed-Consent-(ICO</surname>
          </string-name>
          )
          <article-title>- Lin-Harris/4e6062732cf49b6081322ae1ebd14dbc4ee3e841 (accessed August 19,</article-title>
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>E.E.</given-names>
            <surname>Umberfield</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.H.</given-names>
            <surname>Fenton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Stansbury</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ford</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Crist</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.L.R.</given-names>
            <surname>Kardia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.K.</given-names>
            <surname>Thomer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.R.</given-names>
            <surname>Harris</surname>
          </string-name>
          ,
          <article-title>Lessons Learned for Identifying and Annotating Permissions in Clinical Consent Forms</article-title>
          ,
          <source>Appl Clin Inform</source>
          <volume>12</volume>
          (
          <year>2021</year>
          )
          <fpage>429</fpage>
          -
          <lpage>435</lpage>
          . https://doi.org/10.1055/s-0041-1730032.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>