<!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>Aligning Conference Ontologies with SUMO: A Report on Manual Alignment via WordNet</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniela SCHMIDT</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adam PEASE</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cassia TROJAHN</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Renata VIEIRA</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Infosys, Foothill Research Center</institution>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institut de Recherche en Informatique de Toulouse</institution>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Pontifical Catholic University of Rio Grande do Sul</institution>
          ,
          <country country="BR">Brazil</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper presents the process of manually establishing alignments between domain and foundational ontologies. The ontologies from the OAEI Conference track have been aligned to the SUMO foundational ontology. The Conference dataset is one of the most used dataset in ontology matching evaluation and has been extended in several versions. However, it lacks in alignments to foundational ontologies. As a complete manual alignment between SUMO and WordNet is available, we use such alignments as bridges to facilitate the matching task. In this paper we describe the constructing of such alignments and discuss the issues dealt with during the process, lessons learned and perspectives in the field.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>foundational ontologies</kwd>
        <kwd>ontology matching</kwd>
        <kwd>WordNet</kwd>
        <kwd>SUMO</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Foundational ontologies play a fundamental role in the construction and integration of
domain ontologies, providing a reference model that can be shared across domains. The
clarity in semantics and the rich formalization of foundational ontologies are important
requirements for ontology development in general [17,13], since it improves ontology
quality. They also act as semantic bridges supporting interoperability between domain
ontologies [15,13,18]. There are two approaches for the use of foundational ontologies
[28]. With a top-down approach, the foundational ontology is used as a reference for
deriving domain concepts, taking advantage of the knowledge and experience already
encoded in it. In a bottom-up approach, one usually matches an existing domain ontology
to the foundational ontology. The latter is more challenging since inconsistencies may
exist between domain and foundational ontologies and one has to deal with different
levels of abstraction in the matching process. This paper focus on the latter.</p>
      <p>
        This paper discusses the alignment of the Conference ontologies [35] to a
foundational ontology. The Conference dataset has been used in the Ontology Alignment
Evaluation Initiative (OAEI)1, which have been carried out over the last fifteen years. The
OAEI, however, still lacks matching tasks involving foundational ontologies. The choice
for aligning this OAEI dataset to a foundational ontology is motivated by the fact that
it has became one of the most used in matching evaluations [35]. This dataset has also
been extended with different proposals [
        <xref ref-type="bibr" rid="ref4">4,16</xref>
        ], and recently it is also covering complex
alignments [33].
      </p>
      <p>We present the process of establishing a consensual alignment between the
Conference ontologies and SUMO (Suggested Upper Merged Ontology) [19,21]. Matching
foundational and domain ontologies is far from being a trivial task and most approaches
still rely on manually or semi-automatic strategies. This has been corroborated in [31],
where manually classifying domain entities under foundational ontology concepts is
reported to be very difficult to do correctly. As knowledge on foundational ontologies is
highly specialized, it is important that such alignments consider the participation of
different experts in the area. The findings in [31] also point out the need for improving the
methodological process of manual integration of domain and foundational ontologies,
in accord with what has been stated in [13]. As a complete manual alignment between
SUMO and WordNet has been previously provided [20] and continually updated since
the original effort, we argue here that using these alignments as bridges to matching
domain ontologies to SUMO can facilitate the matching task.</p>
      <p>We have chosen SUMO for several reasons. It is the only formal ontology that has
a complete set of manually-performed correspondences to all 117,000 word senses in
WordNet. It is also one of the few ontologies that has a detailed formalization in an
expressive logical language. Most ontologies are still simple taxonomies and frame
systems, and so assessing the meaning of their terms requires human intuition based on term
names and relationships. SUMO includes a computational toolset [23] that allows users
to test the logical consistency of its definitions, which provides a guarantee of quality and
correctness than just testing type constraints. Lastly, SUMO is large and comprehensive
at roughly 20,000 terms and 80,000 hand-written logical axioms, exceeding the size of
other open source foundational ontologies by several orders of magnitude.</p>
      <p>In this paper we describe the design choices and methodology followed for
constructing this bridged alignment. We discuss the main issues that the experts were faced
with during the process and the lessons learned and perspectives in the field. The rest of
this paper is organised as follows. Section 2 discusses the main related works on
matching domain and foundational level ontologies and the manual construction of alignments.
Section 3 describes the domain and foundational ontologies used here, together with
the alignments between SUMO and WordNet. Section 4 presents the methodology we
followed to match the domain ontologies to WordNet. Section 5 discusses the main
issues we have faced with and finally Section 6 concludes the paper and discusses future
directions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        Matching Domain Ontologies to Foundational Ontologies As reported in [14,13],
methodologies for constructing ontologies should not neglect the use of foundational
ontologies and should better address it in a top-down approach. In the absence of systematic
adoption of foundational ontologies within the domain ontology development process,
bottom-up approaches have to be applied instead. Matching domain and foundational
ontologies has been done mostly manually. In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], geoscience ontologies (GeoSciML and
SWEET – Semantic Web for Earth and Environmental Terminology) have been
manually aligned to DOLCE (Descriptive Ontology for Linguistic and Cognitive Engineering)
[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]2 and incompatibilities issues have been discussed. In [17], DOLCE has also been
manually aligned to a domain ontology describing services (OWL-S), in order to address
its conceptual ambiguity, poor axiomatization, loose design and narrow scope. In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
several schemata of FactForge (which enables SPARQL querying over the Linked Open
Data cloud) have been aligned to PROTON (PROTo ONtology) [32]3 in order to provide
a unified way to access the data. The alignments were created by knowledge engineers,
where equivalence and subclass relationships between DBPedia, Geonames and
Freebase were established to PROTON classes. They report the different strategies adopted
and how the ontologies had fit them (for instance, the fact that reference instances were
not included in the FactForge datasets and the need of using alternative strategies or
extending the dataset with the necessary instances). Contrary to us, they have modified the
original ontoloiges. Manually alignments have also been established between biomedical
ontologies and BFO (Basic Formal Ontology)4 [
        <xref ref-type="bibr" rid="ref1 ref10">10,1</xref>
        ], in [29]. Although many proposals
have focused on DOLCE, it lacks complete alignments to WordNet, as found in SUMO,
also it is several orders of magnitude smaller. PROTON and BFO are also limited, they
present formal axioms in an expressive logic but are small in size.
      </p>
      <p>
        While those proposals mainly generate manual alignments between foundational
and domain ontologies, one of the few automatic approaches is BLOOMS+ [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. It has
been used to automatically align PROTON to LOD datasets using as gold standard the
alignments provided in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. BLOOMS+ first uses Wikipedia to construct a set of
category hierarchy trees for each class in the source and target ontologies. It then determines
which classes to align using 1) similarity between classes based on their category
hierarchy trees; and 2) contextual similarity between these classes to support (or reject) an
alignment. BLOOMS+ significantly outperformed existing matchers in the task.
      </p>
      <p>
        More recently, an automatic approach for matching domain and foundational
ontologies has been proposed in [26]. It exploits existing alignments between WordNet and
foundational ontologies. The matching process is divided in two main steps. The first
step identifies the correct synset to the domain concept and the second one identifies the
correspondence the domain concept to a foundational concept. The approach has been
evaluated using DOLCE and domain ontologies from the OAEI conference data set5,
with the help of the alignments provided in [
        <xref ref-type="bibr" rid="ref9">9,20</xref>
        ]. This work has been further extended
in [27], where two similarity measures for synset disambiguation have been adopted: (1)
an adaptation of the Lesk measure and (2) word embeddings. The evaluation has been
also extended including DOLCE and SUMO ontologies and their alignments to WordNet
and three domain ontologies (SSN – Semantic Sensor Network ontology Core Ontology
for Robotics and Automation, and OAEI Conference). Here, we discuss the consensual
process of manually constructing the alignments between SUMO and OAEI Conference
dataset.
      </p>
      <p>
        Consensual Alignments While different ontology alignments have been constructed
from manual analysis, involving a different number of experts and resulting in different
2http://www.loa.istc.cnr.it/old/DOLCE.html
3http://ontotext.com/proton
4https://github.com/bfo-ontology/BFO/wiki
5http://oaei.ontologymatching.org/2017/conference/index.html
levels of agreement, the focus has mostly been on describing the resulting alignment
rather than on the details of the manual process. Guidelines for constructing alignments
are in fact scarce in the field, though there are more general discussions on the qualities of
a good benchmark in other research fields [
        <xref ref-type="bibr" rid="ref6">30,6</xref>
        ]. It may be obvious that the fundamental
problem of aligning ontologies is determining what is the meaning of the terms that are
candidates for alignment. If the meaning is implicit, and one must resort to the domain
knowledge of human matchers, then only an automatic suggestion is feasible. This is
even more required when dealing with foundational ontologies.
      </p>
      <p>
        Construction of alignments in general follows different strategies, including starting
the alignment generation from scratch, relying on a set of initial alignments for gathering
additional ones, and creating a reference from validating and selecting a set of
correspondences from automatically generated correspondences from a number of matching
systems. In the first category, the creation of the first reference alignment of the
Conference dataset dates back to 2008, when the track organizers created a reference alignment
for all possible pairs of five of the conference ontologies. The reference alignments were
based on the majority opinion of three evaluators and were discussed during a
consensus workshop. This dataset has evolved over the years, as described in [35], with the
feedback from the OAEI participants and has been revised in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. They re-examined the
dataset with a focus on the degree of agreement between the reference alignments and the
opinion of experts. With the aim of studying the way different raters evaluate
correspondences, in [34] experiments in manual evaluation have been carried out using a set of
correspondences generated by different matchers between different vocabularies. Five raters
evaluated alignments and talked through their decisions using the think aloud method.
Their analysis showed which variables can be controlled to affect the level of agreement,
including the correspondence relations, the evaluation guidelines and the background of
the raters. That work refers as well to the different levels of agreements between
annotators reported in the literature. While a perfect agreement between raters is reported in
the Very Large Crosslingual dataset in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] reported a quite different observation
when establishing owl:sameAs relationships in the LOD. These aspects have also been
discussed in [31] for the task of integrating foundational and domain ontologies.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Ontologies and WordNet Alignments</title>
      <sec id="sec-3-1">
        <title>3.1. Foundational and Domain Ontologies 3.1.1. SUMO</title>
        <p>SUMO [19]67 (Suggested Upper Merged Ontology) is a comprehensive ontology that
includes general concepts and their definitions as well as a number of integrated
domain ontologies. It totals approximately 20,000 terms and 80,000 logical axioms. It is
defined in a higher-order logic, which supports mathematical statements about modality,
belief, likelihood and temporal qualification. It is this expressiveness of the logic used
that provides unambiguous formal definitions of terms, without recourse to human
interpretation. SUMO includes an associated tool set called Sigma [23] that is used to test</p>
        <sec id="sec-3-1-1">
          <title>6http://www.ontologyportal.org</title>
        </sec>
        <sec id="sec-3-1-2">
          <title>7https://github.com/ontologyportal/sumo</title>
          <p>
            and extend the ontology and deploy it for applications involving automated inference.
It includes automatic translators to the following languages: TPTP (for first order logic
with equality) [24,25], TFF0 (for first order logic with arithmetic) [22] and THF [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ] (for
classical higher-order logic) used by major classes of automatic theorem provers.
          </p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.1.2. OAEI Conference Dataset</title>
        <p>
          The Conference dataset8 has been used to evaluate nearly all matching systems
developed [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] and it is quite a challenging dataset in the field [35]. This dataset is composed
of 16 ontologies on the conference organization domain and simple reference alignments
between 7 of these ontologies. They cover different aspects of the domain and are
classified in three categories: i) Web (conference series and its web pages), ii) Tool (software
tool for conference organisation support), and iii) Insider (experience of people with
personal participation in conference organisation). Here, we used the 7 ontologies for which
the reference alignments are available. Table 1 presents the classification of the
ontologies and their number of concepts. Although they differ in DL expressivity, this was not
taken into account in our manual alignment methodology.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.2. SUMO to WordNet Alignment</title>
        <p>In alignment between SUMO and WordNet, for each identified correspondence, the
synset of WordNet is augmented with three pieces of information: (i) a prefix (&amp;%) that
indicates that the term is taken from SUMO; (ii) the SUMO concept; and (iii) a suffix
indicating the kind of relation. The suffix ‘=’ indicates that the correspondence relation
is synonymy. ‘+’ indicates that the concept is a hypernym of the associated synset. The
instantiation relation is indicated by the suffix ‘@’. An example of the structure of a
correspondence representing a synonymy relation can be seen below. In the example,
“02761392 06 n 03 automaton 0 robot 0 golem” corresponds to the synset. The gloss
is defined as “a mechanism that can move automatically”, the prefix “&amp;%” indicates
that the term is taken from SUMO. “Device” corresponds to the SUMO concept and the
signal “+” is the suffix indicating the hyponymy relation.</p>
        <p>02761392 06 n 03 automaton 0 robot 0 golem a mechanism that can move automatically
&amp;%Device+</p>
        <sec id="sec-3-3-1">
          <title>8http://oaei.ontologymatching.org/2016/conference/index.html</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Alignment Methodology</title>
      <p>This section describes the overall methodology we have followed to create the
consensual alignment between SUMO and the domain ontologies. As stated above, this process
relies on the existing alignment between SUMO and WordNet. We consider these
previous alignments as correct so the aim here is to identify the right WordNet synset to the
domain concepts. Also, we have reduced the problem to the first-level concepts of the
hierarchies from the domain ontologies. This has resulted in 70 first-level domain concepts
(Table 1). For each first level concept of the domain ontology, a foundational specific
concept is associated. The cost of doing manual alignment with first level concepts is
smaller, as it is reduced to the number of concepts at the first level.</p>
      <p>Four evaluators have been involved in the task of aligning the 70 top-level
domain concepts to the WordNet synsets. The evaluators are researchers, therefore all have
common-sense knowledge about conferences (the domain ontology), they have
background in Computer Science and are well acquainted with ontology matching. One of
the evaluators is the creator of the SUMO ontology.</p>
      <p>The overall methodology is articulated in the following two steps: i) Individually
generating the alignments between domain concepts and WordNet synsets; ii)
Collaboratively validating the set of found correspondences. Next we detail each step.</p>
      <sec id="sec-4-1">
        <title>4.1. Individual Generation of Correspondences</title>
        <p>In this first step, each evaluator aligned each of 70 domain concepts to WordNet synsets.
To that extent, each domain concept and the corresponding WordNet synsets, resulting
from searching in WordNet for the term associated to the domain concept, were listed
to the evaluators. In the absence of entries in WordNet for the terms, a head modifier
strategy has been applied (i.e., WrittenPaper is a Paper). Only one concept had not
corresponding entry in WordNet (sigkdd#Sponzor9). In order to help the evaluator to
understand the context of the domain concept, their sub-concepts were also presented. As the
domain ontologies are equipped with very few comments or labels, we have completed
the description of the concept using the definitions from the Cambridge Dictionary10.
However, we are aware that the found definitions may not reflect the exact semantic of
the concept. Each evaluator then was asked to select the right WordNet synset for each
domain concept. The evaluators were instructed to select one option for each domain
concept, however, in some cases more than one sense was selected. This happens
because the domain concept was not clear enough, or the senses available in WordNet were
very general. Evaluators were also invited to comment their decisions. Table 2 shows a
fragment of the spreadsheet for the domain concept cmt#Conference.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Validating the Correspondences</title>
        <p>After the individual annotation of each domain concept with the WordNet synset, the
annotators were able to see the annotations of each other and identify the conflicts. Based
on the views on the other annotators (and their comments), each one was able to change
their initial annotations. For those conflicts where the comments were not enough for</p>
        <sec id="sec-4-2-1">
          <title>9http://oaei.ontologymatching.org/2018/conference/data/sigkdd.owl 10http://dictionary.cambridge.org/us/</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>During the process of alignment construction, several difficulties arose for interpreting
the real meaning that the concept represents in the domain ontology. For instance, the
concepts Bid and Preference (Table 3) in cmt ontology had no description clarifying
its use, and no sub or super concepts which could be used to clarify their meaning. In
these cases, the evaluators discussed and considered the proper meaning according to
their own interpretation of the domain, however, such cases may interfere with the
quality of the resulting reference alignment because there is no objective standard for what
the meaning, and therefore the correct mapping must be. We have only the consensus
guess about intended meaning among human evaluators. In addition, some concepts
rep11https://github.com/danielasch/ReferenceAlignment
resented in the ontology present other kind of problems such as doubts regarding
ontology elements’ adequacy, for example, the concept ReviewRating in edas ontology,
which according to the discussion raised by the evaluators, a rating could be a
relationship between a thing, an agent and a rating value. In the same way, the concept Deadline
in sigkdd ontology could be a relationship between the conference and a date. They are
however defined in those ontologies as concepts, rather than relationships.</p>
      <p>In other cases, sub-concepts are different from first-level concepts and
therefore they represent different information, as the concept Event in ConfOf ontology.
Some of their sub-concepts Social event/Banquet, Working event/Conference,
Working event/Workshop are in line with the main concept, however others such as
Administrative event/Camera Ready event seems out of the context. In fact, it
should not be a Process at all but a deadline for doing something (submitting a version
of a paper, for instance).</p>
      <p>In contrast, one can examine a SUMO definition of a term such as FormalMeeting12
and see that it is necessarily a Meeting that is not a SocialParty, that it must be
temporally preceded by a Planning that has the result of creating the meeting, as well
as constraints that other events like a Resolution to be considered such, may only
occur at a FormalMeeting. Something like a modern dictionary, but with the definitions
expressed in logic, rather than human language, so that a machine can perform
computation (and consistency checking) with those definitions. The cases described above
consist of ontological representation problems commonly present in lightweight
ontologies, and hinder the reuse and reliability of the represented knowledge. In addition, they
highlight the importance of advancing in research that uses top-level ontologies to give
more formalization to domain ontologies.</p>
      <p>The challenges in aligning the OAEI ontologies should highlight two elements that
are lacking in the majority of most of current ontology practice. The first element is the
degree of reuse. Ontologies that are created from scratch suffer from the fact that their
terms have only a small number of relationships to other terms. The point of having an
ontology is to have a shared meaning among its users. When domain ontologies are
created in isolation, rather than as extensions to widely used comprehensive ontologies they
miss an opportunity for sharing common meaning. Modern software development, for
example in Java or Python, means reusing vast amounts of existing code, such as
extensive language libraries and other packages like web servers, databases, device drivers etc.
Ontology development needs to follow the same practice to achieve the same efficiency
of process as procedural software development.</p>
      <p>A second element is the expressivity of definitions. If, as with several of the OAEI
ontologies, one must guess at the intended meaning of a term only by its name, then there
isn’t much chance for shared meaning amongst its users. Each user will just be making
a guess. If each term has only a set of binary relationships to other terms then it should
still be clear that issues like mutual constraints on values and boundary cases are left
unformalized and also at risk of being in conflict among its users. Additionally, without
a computational formalization of such constraints, the computer will not be able to test
or enforce them. Comments in natural language, no matter how extensive or precise, will
not overcome the need for computational definitions, and our experience in this matching
effort has been that comments are often not even present, and rarely extensive or precise.</p>
      <p>12http://sigma.ontologyportal.org:8080/sigma/Browse.jsp?lang=EnglishLanguage&amp;
flang=SUO-KIF&amp;kb=SUMO&amp;term=FormalMeeting</p>
      <p>In our work, we were not engaged in correcting the ontologies, since they are part of
public datasets. However we consider that a discussion about the problems identified is
necessary. Perhaps more robust alignment processes would inherently require
modifications in target domain ontologies but also certainly a more detailed formalization. Given
the paucity of definitions, we are limited primarily to linguistically-based matches and
use of WordNet is a suitable choice for assisting with this sort of match.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusions</title>
      <p>This paper has discussed the alignment between domain ontologies from the Conference
domain and SUMO. One of the main issues experts have been faced concerns the lack of
formal definitions associated to rich terminological layers (comments and labels) helping
to understand the precise semantics of each concept. We claim that domain ontologies
should rather be developed on the top of such ontologies. This work is a first step toward
the construction of a dataset involving foundational ontologies that can serve to
evaluation systems in the context of OAEI campaigns. These alignments can also be explored
as semantic bridges in domain ontology matching.
[13] C. Keet. The use of foundational ontologies in ontology development: An empirical assessment. In</p>
      <p>Proceedings of the 8th Extended Semantic Web Conference, pages 321–335, 2011.
[14] Z. Khan and C. Keet. ONSET: Automated Foundational Ontology Selection and Explanation. In
Proceedings of the 18th International Conference on Knowledge Engineering and Knowledge Management,
pages 237–251, 2012.
[15] V. Mascardi, A. Locoro, and P. Rosso. Automatic Ontology Matching via Upper Ontologies: A
Systematic Evaluation. IEEE Trans. on Knowl. and Data Eng., 22(5):609–623, 2010.
[16] Christian Meilicke, Raul Garcia-Castro, Fred Freitas, Willem Robert van Hage, Elena Montiel-Ponsoda,
Ryan Ribeiro de Azevedo, Heiner Stuckenschmidt, Ondrej Sva´b-Zamazal, Vojtech Sva´tek, Andrei
Tamilin, Ca´ssia Trojahn, and Shenghui Wang. Multifarm: A benchmark for multilingual matching. JWS,
15:62–68, 2012.
[17] P. Mika, D. Oberle, A. Gangemi, and M. Sabou. Foundations for Service Ontologies: Aligning OWL-S
to DOLCE. In Proceedings of the 13th Conference on World Wide Web, pages 563–572, 2004.
[18] Julio Cesar Nardi, Ricardo de Almeida Falbo, and Joa˜o Paulo A. Almeida. Foundational ontologies
for semantic integration in EAI: A systematic literature review. In Proceedings of the 12th IFIP WG
Conference on e-Business, e-Services, and e-Society, I3E, pages 238–249, 2013.
[19] I. Niles and A. Pease. Towards a Standard Upper Ontology. In Conference on Formal Ontology in</p>
      <p>Information Systems, pages 2–9, 2001.
[20] I. Niles and A. Pease. Linking Lexicons and Ontologies: Mapping WordNet to the Suggested Upper
Merged Ontology. In Proceedings of the Inter. Conference on Knowledge Engineering, pages 412–416,
2003.
[21] Adam Pease. Ontology: A Practical Guide. Articulate Software Press, Angwin, CA, 2011.
[22] Adam Pease. Arithmetic and inference in a large theory (extended abstract). In 4th Conference on</p>
      <p>Artificial Intelligence and Theorem Proving, 2019.
[23] Adam Pease and Christoph Benzmu¨ ller. Sigma: An Integrated Development Environment for Logical</p>
      <p>Theories. AI Communications, 26:9–97, 2013.
[24] Adam Pease and Stephan Schulz. Knowledge Engineering for Large Ontologies with Sigma KEE 3.0.</p>
      <p>In The International Joint Conference on Automated Reasoning, 2014.
[25] Adam Pease, Geoff Sutcliffe, Nick Siegel, and Steven Trac. Large Theory Reasoning with SUMO at
CASC. AI Communications, Special issue on Practical Aspects of Automated Reasoning, 23(2-3):137–
144, 2010.
[26] D. Schmidt, R. Basso, C. Trojahn, and R. Vieira. Matching Domain and Top-level Ontologies via</p>
      <p>OntoWordNet. In Workshop on Ontology Matching, pages 1–2, 2017.
[27] D. Schmidt, R. Basso, C. Trojahn, and R. Vieira. Matching domain and top-level ontologies exploring
word sense disambiguation and word embedding. In Emerging Topics in Semantic Technologies [best
papers from the workshops at ISWC 2018], pages 27–38, 2018.
[28] S. Semy, M. Pulvermacher, and L. Obrst. Toward the use of an upper ontology for U.S. government and
U.S. military domains: An evaluation. Technical report, MTR 04B0000063, The MITRE Corporation,
2004.
[29] V. Silva, M. Campos, J. Silva, and M. Cavalcanti. An Approach for the Alignment of Biomedical</p>
      <p>Ontologies based on Foundational Ontologies. Information and Data Management, 2(3):557–572, 2011.
[30] Susan Elliott Sim, Steve Easterbrook, and Richard C. Holt. Using benchmarking to advance research:
A challenge to software engineering. In Proceedings of the 25th International Conference on Software
Engineering, pages 74–83, 2003.
[31] R. Stevens, P. Lord, J. Malone, and N. Matentzoglu. Measuring expert performance at manually
classifying domain entities under upper ontology classes. Journal of Web Semantics, 2018.
[32] I. Terziev, A. Kiryakov, and D. Manov. Base Upper-level Ontology (BULO) Guidance. Deliverable
1.8.1, sekt project, 2005.
[33] E´lodie Thie´blin, Ollivier Haemmerle´, Nathalie Hernandez, and Ca´ssia Trojahn. Task-oriented complex
ontology alignment: Two alignment evaluation sets. In Proceedings of the 15th Extended Semantic Web
Conference, pages 655–670, 2018.
[34] Anna Tordai, Jacco van Ossenbruggen, Guus Schreiber, and Bob Wielinga. Let’s agree to disagree:
On the evaluation of vocabulary alignment. In Proceedings of the 6th International Conference on
Knowledge Capture, pages 65–72, 2011.
[35] Ondrˇej Zamazal and Vojteˇch Sva´tek. The Ten-Year OntoFarm and its Fertilization within the
OntoSphere. Web Semantics: Science, Services and Agents on the World Wide Web, 43:46–53, March 2017.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Arp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          , and
          <string-name>
            <given-names>A.</given-names>
            <surname>Spear</surname>
          </string-name>
          .
          <article-title>Building Ontologies with Basic Formal Ontology</article-title>
          . MIT Press,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Benzmu</surname>
          </string-name>
          <article-title>¨ller and Adam Pease. Progress in Automating higher-order ontology reasoning</article-title>
          . In Boris Konev, Renate Schmidt, and Stephan Schulz, editors,
          <source>Proceedings of the Workshop on Practical Aspects of Automated Reasoning. Edinburgh</source>
          , UK,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>B.</given-names>
            <surname>Brodaric</surname>
          </string-name>
          and
          <string-name>
            <surname>F. Probst. DOLCE ROCKS</surname>
          </string-name>
          :
          <article-title>Integrating Geoscience Ontologies with DOLCE</article-title>
          .
          <source>In Semantic Scientific Knowledge Integration</source>
          , pages
          <fpage>3</fpage>
          -
          <lpage>8</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Michelle</given-names>
            <surname>Cheatham</surname>
          </string-name>
          and
          <string-name>
            <given-names>Pascal</given-names>
            <surname>Hitzler</surname>
          </string-name>
          .
          <source>Conference v2</source>
          .
          <article-title>0: An uncertain version of the oaei conference benchmark</article-title>
          .
          <source>In International Semantic Web Conference</source>
          , pages
          <fpage>33</fpage>
          -
          <lpage>48</lpage>
          . Springer,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Damova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kiryakov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ivanov Simov</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Petrov</surname>
          </string-name>
          .
          <article-title>Mapping the central LOD ontologies to PROTON upper-level ontology</article-title>
          .
          <source>In Workshop on Ontology Matching</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A</given-names>
            <surname>Dekhtyar</surname>
          </string-name>
          and
          <string-name>
            <given-names>J Huffman</given-names>
            <surname>Hayes</surname>
          </string-name>
          .
          <article-title>Good benchmarks are hard to find: Toward the benchmark for information retrieval applications in software engineering</article-title>
          .
          <source>In Proceedings of the 22th International Conference on Software Maintenance</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7] Je´roˆme Euzenat, Alfio Ferrara, Laura Hollink, Antoine Isaac, Cliff Joslyn, Ve´ronique Malaise´,
          <string-name>
            <surname>Christian</surname>
            <given-names>Meilicke</given-names>
          </string-name>
          , Andriy Nikolov, Juan Pane, Marta Sabou, Franc¸ois Scharffe, Pavel Shvaiko, Vassilis Spiliopoulos, Heiner Stuckenschmidt, Ondrej Sva´
          <article-title>b-</article-title>
          <string-name>
            <surname>Zamazal</surname>
          </string-name>
          , Vojtech Sva´tek, Ca´ssia Trojahn dos Santos,
          <article-title>George A</article-title>
          .
          <string-name>
            <surname>Vouros</surname>
            , and
            <given-names>Shenghui</given-names>
          </string-name>
          <string-name>
            <surname>Wang</surname>
          </string-name>
          .
          <article-title>Results of the ontology alignment evaluation initiative 2009</article-title>
          .
          <source>In Proceedings of the 4th International Workshop on Ontology Matching</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Masolo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Oltramari</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Schneider</surname>
          </string-name>
          .
          <article-title>Sweetening Ontologies with DOLCE</article-title>
          .
          <source>In 13th Conference on Knowledge Engineering and Knowledge Management</source>
          , pages
          <fpage>166</fpage>
          -
          <lpage>181</lpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Navigli</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Velardi</surname>
          </string-name>
          .
          <article-title>The OntoWordNet Project: Extension and Axiomatization of Conceptual Relations in WordNet</article-title>
          , pages
          <fpage>820</fpage>
          -
          <lpage>838</lpage>
          .
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>P.</given-names>
            <surname>Grenon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Goldberg</surname>
          </string-name>
          . Biodynamic Ontology:
          <article-title>Applying BFO in the Biomedical Domain</article-title>
          .
          <source>In Stud. Health Technol. Inform</source>
          , pages
          <fpage>20</fpage>
          -
          <lpage>38</lpage>
          . IOS Press,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Harry</surname>
            <given-names>Halpin</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Patrick J.</given-names>
            <surname>Hayes</surname>
          </string-name>
          ,
          <string-name>
            <surname>James P. McCusker</surname>
          </string-name>
          ,
          <string-name>
            <surname>Deborah L. McGuinness</surname>
          </string-name>
          , and
          <string-name>
            <surname>Henry</surname>
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Thompson</surname>
          </string-name>
          .
          <article-title>When owl:sameas isn't the same: An analysis of identity in linked data</article-title>
          .
          <source>In Proceedings of the 9th International Semantic Web Conference</source>
          , pages
          <fpage>305</fpage>
          -
          <lpage>320</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>P.</given-names>
            <surname>Jain</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Yeh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Verma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Vasquez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Damova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Hitzler</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Sheth</surname>
          </string-name>
          .
          <article-title>Contextual Ontology Alignment of LOD with an Upper Ontology: A Case Study with PROTON</article-title>
          .
          <source>In Proceedings of the 8th Extended Semantic Web Conference</source>
          , pages
          <fpage>80</fpage>
          -
          <lpage>92</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>