<!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>Assessing Candidate Ontologies for Reuse</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Reham Alharbi</string-name>
          <email>r.alharbi@liverpool.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Liverpool</institution>
          ,
          <addr-line>Liverpool L69 3BX</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <fpage>65</fpage>
      <lpage>72</lpage>
      <abstract>
        <p>Ontology reuse is a complex process that requires the support of methodologies and tools to minimise errors and keep the ontologies consistent. Although many e orts have investigated ontology reuse for di erent tasks and purposes, this body of work does not seem to translate to practice. The goal of this research is a comprehensive \Ontology Reusability Assessment", that builds on and extends the current state of the art. In this paper, we describe this overall aim and two preliminary results: 1) a community questionnaire to gain an insight on the gap between theory and practice, and 2) a case study to see if it is possible to identify similar functional requirements across di erent domains.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Ontologies are explicit speci cations of conceptualised domains shared by a
community of users, and play a signi cant role in conceptual data modelling and
AI [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In the context of ontology engineering, reusing existing knowledge
models is largely recognised as a key factor in the development of ontologies that are
both cost-e ective and of higher quality, by reusing components that have
previously and independently been validated [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Despite this, ontology reuse does
not seem a consolidated practice [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]: for instance, an analysis of 377 biomedical
ontologies in BioPortal1 concluded that reuse was very limited (&lt;5%) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        From state of the art reviewed, it is clear that some ontologies are reused more
than others, possibly because they documented when compared with others [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
One of the aspects a ecting the reusability of an ontology is the perception of its
quality with respect to some evaluation criteria. However, although much work
has addressed the evaluation of the quality of ontologies from the perspective of
reuse, there are no de nitive principles and practices, and especially, there is no
practical mechanism for providing developers with a qualitative and quantitative
assessment of reusability.
      </p>
      <p>The PhD research presented in this paper, currently in its second year, aims
to develop a comprehensive framework for assessing ontologies for reuse,
capturing the requirements for reusing an ontology, identifying the modalities of reuse,
the ontology features, and any additional information that ontology engineers
need to be aware of when selecting a candidate ontology to reuse.</p>
      <p>To achieve this objective, we analysed state of the art in a top-down and
bottom-up manner: we reviewed the current literature on the theory of ontology</p>
      <sec id="sec-1-1">
        <title>1 https://www.bioontology.org/</title>
        <p>reuse, whilst we compiled a questionnaire aimed at ontology practitioners to
identify mismatches between theory and common practices.</p>
        <p>
          In parallel with the questionnaire, we also started investigating how
ontological requirements can help determine whether an ontology can be reused for
a given purpose. Competency questions (CQs), the natural language questions
outlining the scope of knowledge represented by an ontology and assisting in its
development and maintenance [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ], are often seen as a way of expressing
functional ontological requirements that can be used to promote ontology reuse and
that facilitate the identi cation of patterns that implement such requirements [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
Our approach aims to contribute a qualitative estimator of the reusability of a
given design pattern. We illustrate this through a case study that developes an
ontology for the role game Dungeons and Dragons (DnD)2. In the case study we
objectively assess the similarity between the DnD ontological requirements and
those of candidate ontologies to reuse or of design patterns that could be reused.
        </p>
        <p>This paper reports our preliminary results on these two directions of
research. We start by de ning the problem statement Section 2. In Section 3 we
discuss state of the art on how ontology engineers/developers make use of known
de nitions and measures in reuse. We present the methodology Section 4, the
questionnaire and its preliminary results in Section 5, and in Section 6 we present
the case study assessing the similarity between ontological requirements. Finally,
in Section 7 we conclude and discuss future research directions.
2</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Problem statement</title>
      <p>
        Ontology reuse is one of the fundamental phases in all ontology design
methodologies, and it is deemed as crucial because it allows developing ontologies by
saving e ort and by reusing ontological fragments that have been independently
validated [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. However, a number of reasons can hamper the e ective reuse of
existing ontologies:
      </p>
      <p>
        (i) possible de ciencies in the ontology's documentation make it di cult to
nd all the ontologies suitable for reuse [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]; (ii) the lack of a standard way to
verify the accuracy of CQs against an ontology typically results in
misconceptions in determining the reusability of a candidate ontology [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]; (iii) the lack of
standardisation in designing an ontology through reuse can introduce future
errors, for example, by failing to keep track of changes in the reused ontologies [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ];
(iv) insu cient information about the requirements that ontology engineers aim
to satisfy when assessing candidate ontologies for reuse [
        <xref ref-type="bibr" rid="ref11 ref8">11,8</xref>
        ]. The current PhD
research aims to answer the following main research question: "RQ 1: To what
extent and what methods can suppport ontology developers assess qualitatively
or quantitatively the reusability of an ontology? " This research question can be
further decomposed in the following subsidiary questions:
RQ 1.1: Why ontology developers do not reuse existing ontologies?
RQ 1.2: When is an ontology good for reuse from the community point of view?
RQ 1.3: What methods can be used to assess the reusability of an ontology?
      </p>
      <sec id="sec-2-1">
        <title>2 A fantasy tabletop role-playing game, https://dnd.wizards.com/</title>
        <p>RQ 1.4: To what extent identifying similar requirements could indicate the
reusability of a target ontology?
RQ 1.5: What are the linguistic features in the requirements that can indicate
ontology reusability?</p>
        <p>These research questions lead to the de nition of the following four objectives
that this research aims to address:
A 1: Identify the reasons that hamper reuse (RQ 1.1)
A 2: Develop methods for reusing an ontology by identifying: the requirements
for reusing an ontology (RQ 1.1), and the ontology features and additional
information that ontology engineers need to know to make an informed
decision (RQ 1.3, RQ 1.4).</p>
        <p>A 3: Develop mechanisms to assess the reusability of an ontology against the
requirements identi ed and summarise them into an assessment metric (RQ
1.1, RQ 1.2).</p>
        <p>A 4: Evaluate the proposed methodology and metrics with the community to
estimate the prospective level of uptake (RQ 1).</p>
        <p>From reviewing the extensive state of the art on ontology reuse, we have
established that reuse is based on the ability to determine the scope and the purpose
for which an ontology is built. Therefore, we start our investigation from the
analysis of the role that CQs play to express ontology requirements, and we
investigate whether the semantic similarity between CQs can be used as an
indicator of reusability of a candidate ontology, which could be used to determine
an initial set of reusable ontologies to be selected by ontology developers.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Related work</title>
      <p>
        In selecting the literature to review to investigate our research questions we
also included ontology evaluation papers, as the quality of an ontology is an
in uential factor in determining whether to reuse an ontology. The literature
review provides us with a set of widely used metrics and techniques that determine
the ontology quality from di erent perspectives, even though these e orts are
not always explicitly tailored to the task of ontology reuse. Furthermore, whilst
several metrics have been proposed to support ontology reuse, few e orts have
attempted to assess how ontology reuse theories a ect development practices [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ],
which is the aim of this research.
      </p>
      <p>
        The assessment method we aim to develop as part of this PhD combines
these metrics to understand the thinking behind ontology selection and reuse,
with a particular interest in the practical way of assessing the reusability of
an ontology. Our assessment metric is based on the combination of four main
aspects: schema metrics, instance metrics, community and social metrics, and
documentation metrics:
Schema metrics [
        <xref ref-type="bibr" rid="ref13 ref19 ref21">21,19,13</xref>
        ]: pertain to the quality of the design of the ontology
schema.This can be assessed by indicating the richness, width, depth, and
inheritance of an ontology schema.
Instance Metrics [
        <xref ref-type="bibr" rid="ref13 ref19 ref21">21,19,13</xref>
        ]: evaluate the way an ontology is populated. The
placement and distribution of instance data can indicate the e ectiveness of
the ontology design and the knowledge represented by the ontology.
Metrics related to Community and Social aspects [
        <xref ref-type="bibr" rid="ref11 ref20">11,20</xref>
        ]: capture the
several social and community aspects that can a ect the quality of an
ontology in the evaluation process.
      </p>
      <p>
        Metrics Related to Documentation [
        <xref ref-type="bibr" rid="ref11 ref20 ref7">11,7,20</xref>
        ]: determine whether an
ontology includes some speci cation of the requirements, for instance the
Ontology Requirement Speci cation Document or CQs.
      </p>
      <p>In addition to identifying these metrics, we also used the literature review to
guide us in preparing a questionnaire aimed at ontology practitioners that
validates the importance of the identi ed measures in common practices.</p>
      <p>
        The literature review also includes studies that investigate functional
ontological requirements [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and how these are represented by means of CQs, since
these fundamental in de ning the scope of an ontology. For example, an
analytical study presented by [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] included a list of 30 methodologies to build ontologies
that start by de ning CQs.
      </p>
      <p>
        The purposes of many studies of ontological functional requirements can be
categorised into: (i) ontology evaluation, by evaluating CQs over an ontology
to check whether knowledge is entailed [
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ], or measuring the quality and
accuracy of the knowledge encoded in the ontology [
        <xref ref-type="bibr" rid="ref15 ref3">15,3</xref>
        ]. (ii) ontology veri cation,
by comparing an ontology against the ontological requirements to ensure that
an ontology is built correctly [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. (iii) methodology de nition, by de ning a
methodology that could consistently drive the ontology engineers in developing
an ontology from scratch. This by using a goal modelling approach (Tropos
process) to capture, model and reason CQs [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. (iv) analysis of CQs, by analysing
the structure of CQs and proposing some popular linguistic patterns that can
be reused to specify requirements [
        <xref ref-type="bibr" rid="ref10 ref15 ref23 ref3">10,23,15,3</xref>
        ]. (v) CQs formalisation, by
automatically fromulating CQs in a controlled natural language based on CQs
patterns [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and producing a glossary of terms for each domain [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
      </p>
      <p>
        All these studies can improve the requirement speci cation activity by
identifying possible problems in the de nition of requirements [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Our contribution
proposes the assessment of the similarity between requirements to decide on the
reusability of an ontology.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Methodology</title>
      <p>This section introduces the di erent methodologies used for investigating the
main research question, and its sub-questions.</p>
      <p>RQ 1.1 3 has been addressed by a systematic review to determine the
challenges to ontology reuse. We have then validated the identi ed challenges with a
qualitative study through an online questionnaire aimed at ontology developers
(Section 5), that assesses the extent to which these challenges hamper reuse, and</p>
      <sec id="sec-4-1">
        <title>3 Why ontology developers do not reuse existing ontologies?</title>
        <p>
          therefore addresses both RQ 1.2 4 and RQ 1.3 5. Based on the survey's initial
analysis, we recognised the importance of ontological requirements, and added
two further sub-questions: RQ 1.4 6 and RQ 1.5 7, whose aim investigates the
feasibility of (semi-) automatic similarity assessment of requirements. We conduct
a case study (Section 6) that develops a Dungeons and Dragons (DnD)ontology
covering the di erent characters and the possible relationships between the
resources of the game. The ontology development is divided in three phases, and is
described in Section 6: 1) analysis of the DnD requirements by identifying
concepts and relationships that are relevant in the domain; 2) implementation of
the requirements using CLaRO [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], a template-based Controlled Natural
Language resource to author CQs; and 3) identi cation of similar requirements in
the CORAL curated data set [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] of ontological requirements. In order to assess
the similarity between requirements and CQs we adopted the BERTSimilarity
method [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], that allows us to compute the similarity between complete
requirements, taking into account their grammatical structure. Wordnet was also used
to account for entity and propriety synonyms.
        </p>
        <p>The overall assessment mechanism(RQ 1) is meant as a summary of the
measures for reusing an ontology. It is intended to be a visual graphical summary
for all reasons that justify why an ontology can be reused, and thus a visual
representation of the ontology reusability with respect to the requirements de ned
by an ontology developer.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>The reuse questionnaire</title>
      <p>The review of state of the art has highlighted the existence of a gap between
theory and practice. However, it is not clear what are the barriers to a more
extensive uptake of the practice: it is essential, therefore, to go back to the
community, and elicit the information directly from ontology developers.</p>
      <p>We designed an online questionnaire to understand how ontologists and
knowledge engineers in di erent domains search for, evaluate, and select an
ontology for reuse. The questionnaire was disseminated during the period March to
November 2020 through personal contacts, and relevant mailing lists and
conferences (e.g. the 19th International Semantic Web Conference). In total, 54 eligible
respondents participated in this study, but we excluded respondents who classed
themselves as having no ontology engineering experience.</p>
      <p>The analysis of the answers to the questionnaire is intended to inform how
each metric contributes to the assessment mechanism, based on how much the
respondents consider a given metric when deciding whether to reuse an ontology.
4 When is an ontology good for reuse from the community point of view?</p>
      <sec id="sec-5-1">
        <title>5 What methods can be used to assess the reusability of an ontology?</title>
      </sec>
      <sec id="sec-5-2">
        <title>6 To what extent identifying similar requirements could indicate the reusability of a</title>
        <p>target ontology?</p>
      </sec>
      <sec id="sec-5-3">
        <title>7 What are the linguistic features in the requirements that can indicateontology</title>
        <p>reusability?
The initial ndings can be accessed here 8. The results are still being analysed;
however, it is worth noting that a large proportion of respondents (95%)
indicates that they are likely or very likely to consider any ontology documentation,
including CQs, when deciding reuse. These results are the basis for the DnD
case study, presented in Sectionn 6.
6</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Case Study: Developing Dungeon and Dragons through reuse</title>
      <p>
        CQs are often used as a starting point in the ontology development process and
capture the functional requirements of the ontology. It is, therefore plausible to
consider rst the reuse of ontologies that have similar functional requirements
to the ontology being developed. In order to verify this hypothesis, we devised
an experiment where we develop an ontology for the role game Dungeons and
Dragons (DnD) 9 using the NeOn methodology [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] and reusing other ontologies
from disparate domains do not bear an immediate similarity with the DnD one.
The underlying idea is that there could be ontologies that cover di erent domains
from the one of the ontology being designed, but that could still provide terms
or patterns that can be reused because their semantics are similar to those in
the domain of interest. For instance, the notion of a boss in an organisation can
be considered similar to the one of a dungeon master in the game.
      </p>
      <p>
        Therefore, we aim to assess whether the similarity between requirements can
be used as an indicator of the reusability of an ontology. We verify this
hypothesis by desining a case study, where we use the Corpus of Ontological
Requirements Annotated with Lexico-syntactic patterns, CORAL [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], as a repository
of requirements to be matched. CORAL is an openly available corpus of 834
ontological requirements extracted from ontologies modelling di erent domains,
including video games, buildings and terrains and business organisation. We
chose to model DnD because its rules and roles in the games are potentially
similar to the requirements in CORAL.
      </p>
      <p>
        We worked with a domain expert and we identi ed 45 CQs for DnD, which
then were analysed through natural language processing to the main terms of
interest, using the vocabulary agnostic patterns proposed by [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. We then tested
those terms against CORAL, and we identi ed ve candidate ontologies to reuse
(SAREF4ENV, OneM2M, SAREF, SAREF4BLD and OntoDT) [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] with 38
requirements matching the DnD CQs. The remaining 7 CQs from DnD remained
unmatched. We then applied question relevance methods, investigated by the
question answering community, to detect duplicate CQs and measure the
similarity between requirements 10.
8
https://ralharbi9.wixsite.com/reham-alharbi?uid=b3768c75-e033-45c8-88ae8b6fb426f701
      </p>
      <sec id="sec-6-1">
        <title>9 https://dnd.wizards.com/articles/features/basicrules</title>
        <p>10 https://medium.com/@drcjudelhi/bert-
ne-tuning-on-quora-question-pairsb48277787285</p>
        <p>The underlying hypothesis in this case study is that the similarity scores
between requirements can indicate the reusability of the part of the ontology
modelling the requirement. For example, in DnD, we ask, "What does a
campaign have?". The corresponding requirement in CLARO is "An organisation
has users", and we notice that one is a generalised form of the other(that
indicate an implicit relationship). We use WordNet (a large lexical database of
English) and apply the Wu-Palmer Similarity 11 to asses how similar the word
senses of the terms used in the requirements are and the relative position of
Synsets in the hypernym tree. This shows that some terms in CLARO are more
general than the ones in DnD, and therefore we could reuse the pattern used to
de ne the corresponding CQs in CLARO in DnD.</p>
        <p>The ability to start selecting and identi ng the relevant ontologies by analysing
requirements has a clear potential and is worht exploring further. Applying this
methodology to ontology repositories like BioPortal could enable ontology
developers to identify ontologies to reuse or to model some of their requrements.
7</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Conclusion and Future work</title>
      <p>We argued that despite the many community e orts, and reuse being a key
step in ontology development, the practice is not yet widespread. Therefore this
PhD research aims to identify the barriers to a more extensive uptake of the
practice and proposes an \Ontology Reusability Assessment" to provide an
objective assessment to guide the reuse of an ontology. As part of this e ort we
sought feedback from the community through an online questionnaireaimed at
understanding how ontologists and knowledge engineers select an ontology to
reuse.</p>
      <p>From an initial analysis of the responses we identi ed that the ability to
analyse and match CQs is a potential good indicator of the reusability of an
ontology. Choosing the reuse of a candidate ontology by exploring the similarity
between a set of given requirements and those documenting existing ontologies
could facilitate and support their reuse. As a next step, we aim to identify
linguistic features in the requirements that can be an indication of whether
an ontology could be reused. The proposed mechanism for reuse will be then
presented back to the community for evaluation. An evaluation study including
expert ontologist and community members will ensure that the reuse assessment
is both practical and relevant.
11 https://wordnet.princeton.edu/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bezerra</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Freitas</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Verifying description logic ontologies based on competency questions and unit testing</article-title>
          . pp.
          <volume>159</volume>
          {
          <issue>164</issue>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bezerra</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Freitas</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santana</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Evaluating ontologies with competency questions</article-title>
          .
          <source>vol. 3</source>
          , pp.
          <volume>284</volume>
          {
          <issue>285</issue>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bezerra</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santana</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Freitas</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Cqchecker: a tool to check ontologies in owl-dl using competency questions written in controlled natural language 12(2), 4 (</article-title>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Cuenca</given-names>
            <surname>Grau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Horrocks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Kazakov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Sattler</surname>
          </string-name>
          ,
          <string-name>
            <surname>U.</surname>
          </string-name>
          :
          <source>Modular reuse of ontologies: Theory and practice 31</source>
          ,
          <volume>273</volume>
          {
          <fpage>318</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Devlin</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chang</surname>
            ,
            <given-names>M.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toutanova</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Bert: Pre-training of deep bidirectional transformers for language understanding (</article-title>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Fernandez-Izquierdo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poveda-Villalon</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garc</surname>
            a-Castro,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Coral: a corpus of ontological requirements annotated with lexico-syntactic patterns</article-title>
          . pp.
          <volume>443</volume>
          {
          <issue>458</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Fernandez-Lopez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          : Methodological guidelines for reusing
          <source>general ontologies 86</source>
          ,
          <volume>242</volume>
          {
          <fpage>275</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Fernandez-Lopez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poveda-Villalon</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Why are ontologies not reused across the same domain</article-title>
          ?
          <source>Journal of Web Semantics</source>
          <volume>57</volume>
          ,
          <issue>100492</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kamdar</surname>
            ,
            <given-names>M.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tudorache</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>A systematic analysis of term reuse and term overlap across biomedical ontologies</article-title>
          .
          <source>Semantic web 8(6)</source>
          ,
          <volume>853</volume>
          {
          <fpage>871</fpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Keet</surname>
            ,
            <given-names>C.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mahlaza</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antia</surname>
            ,
            <given-names>M.J.:</given-names>
          </string-name>
          <article-title>Claro: a controlled language for authoring competency questions</article-title>
          . pp.
          <volume>3</volume>
          {
          <issue>15</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Matentzoglu</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malone</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mungall</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevens</surname>
          </string-name>
          , R.:
          <article-title>Miro: guidelines for minimum information for the reporting of an ontology</article-title>
          .
          <source>Journal of biomedical semantics 9(1)</source>
          ,
          <volume>6</volume>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          , et al.:
          <article-title>Ontology development 101: A guide to creating your rst ontology (</article-title>
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahn</surname>
          </string-name>
          , J.:
          <article-title>Ontology selection ranking model for knowledge reuse 38(5</article-title>
          ),
          <volume>5133</volume>
          {
          <fpage>5144</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Poveda-Villalon</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Reusing ontology design patterns in a context ontology network</article-title>
          . pp.
          <volume>35</volume>
          {
          <issue>52</issue>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Ren</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parvizi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mellish</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>J.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Van Deemter</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevens</surname>
          </string-name>
          , R.:
          <article-title>Towards competency question-driven ontology authoring</article-title>
          . pp.
          <volume>752</volume>
          {
          <issue>767</issue>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Soares</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Towards ontology-driven information systems: Guidelines to the creation of new methodologies to build ontologies (</article-title>
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          :
          <article-title>NeOn Methodology for building ontology networks: specication, scheduling and reuse</article-title>
          .
          <source>Ph.D. thesis</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>First attempt towards a standard glossary of ontology engineering terminology</article-title>
          . pp.
          <volume>1</volume>
          {
          <issue>16</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Supekar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Characterizing quality of knowledge on semantic web</article-title>
          . pp.
          <volume>472</volume>
          {
          <issue>478</issue>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Talebpour</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sykora</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jackson</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The role of community and social metrics in ontology evaluation: An interview study of ontology reuse</article-title>
          . pp.
          <volume>119</volume>
          {
          <issue>127</issue>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Tartir</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arpinar</surname>
            ,
            <given-names>I.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moore</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aleman-Meza</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Ontoqa: Metric-based ontology quality analysis (</article-title>
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Wisniewski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lawrynowicz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A tagger for glossary of terms extraction from ontology competency questions</article-title>
          . pp.
          <volume>181</volume>
          {
          <issue>185</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Wisniewski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Potoniec</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lawrynowicz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keet</surname>
            ,
            <given-names>C.M.:</given-names>
          </string-name>
          <article-title>Analysis of ontology competency questions and their formalizations in sparql-owl 59</article-title>
          <issue>, 100534</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>