<!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>Ontology Verification Using Contexts</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Aviv Segev and Avigdor Gal Technion - Israel Institute of Technology</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Ontologies have become the de-facto modeling tool of choice, used in a variety of applications and prominently in the Semantic Web. Their design and maintenance, nevertheless, have been and still are a daunting task. As a result, ontologies quickly become underspecified. Therefore, if ontologies do not evolve, the semantic infrastructure of the information system can no longer support the changing needs of the organization. In this work we provide a model to semi-automatically support relationship evolution in an ontology using contexts. We propose to use (machine-generated) contexts as a mechanism for quantifying relationships among concepts. To do so we compare the contexts that are associated with the ontology constructs. On a conceptual level, we introduce an ontology verification model, a quantified model for automatically assessing the validity of relationships in an ontology. We motivate our work with examples from the field of eGovernment applications. To support our model with an empirical analysis, we provide a mapping of an ontology operator for defining relationships into context relationships, using real-world traces of RSS.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>
        Ontologies have become the de-facto modeling tool of choice, used
in a variety of applications and prominently in Semantic Web
applications. For example, ontologies can be used in discovering Web
services [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Ontology design, nevertheless, has been and still is a
daunting task. It requires collaboration of domain experts with
ontology engineers, which may consume many organizational resources
in terms of both time and monetary units. Once the ontology is
designed, evolving it becomes difficult due to the need for availability
of domain experts on the one hand, and costs related with hiring
ontology engineers on the other hand. To illustrate this point, consider
an eGovernment application, for which an ontology was designed
and tailored by an ontology engineer. Once the ontology is installed,
changes in the real world require a renewed collaboration of civil
servants with ontology engineers to reflect such changes in the
ontology. A typical outcome of such difficulties is that ontologies quickly
become underspecified. New concepts are introduced in the domain
while others become obsolete. Also, shifts of focus in the application
domain require the refinement of a concept into a hierarchy of
concepts, while in other cases hierarchies should be collapsed. Meeting
these challenges requires ontologies to evolve or else the semantic
infrastructure of the information system can no longer support the
changing needs of the organization.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] we introduced a model for compensating for ontology
underspecification using a combination of ontologies with contexts.
Contexts were defined to be first class objects [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and will be formally
presented later in this work. As an example, a context can be defined
to be a set of words, possibly associated with weights that represent
the relevance of a word to a document. Ontologies and contexts are
both used to model different perspectives of a domain (views).
Ontologies represent shared models of a domain and contexts are local
views of a domain. We also promote an orthogonal classification in
which ontologies are considered a result of a manual effort of
modeling a domain, while contexts are system generated models [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
Ontologies and contexts are joined together, as formally described in
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In a nutshell, each concept in an ontology is represented by a
name and a context. In this model, contexts serve as an easy-to-use
“semantic glue,” in which underspecifications are compensated for
with a syntactic, machine generated context, which highlights the
intentions of a local designer when using a specific ontology concept,
possibly differently from the way it is semantically captured in the
ontology using relationships.
      </p>
      <p>In this work we provide a model and an example of an algorithm
to semi-automatically support relationship evolution in an ontology
using contexts. The main motivation for this work stems from the
difficulty in supporting ontology evolution. Specifically, this problem
was raised within the framework of TerreGov, a European
eGovernment project. In this project, ontologies serve as the driving force
behind the application and thus affect government processes and
Web services, among other things. Therefore, we propose to use
(machine-generated) contexts as a mechanism for quantifying
relationships among concepts. Specifically, given an ontology operator
(e.g., link subclass, representing the knowledge that an instance of
one concept is included in an instance of another) and operands (e.g.,
two concepts or classes), we aim at quantifying the extent to which
this relationship is valid. We do so by comparing the contexts that are
associated with the operands. We believe that such a solution would
significantly assist in the support of ontology design and evolution.</p>
      <p>The main contribution of this work is thus twofold. On a
conceptual level, we introduce an ontology verification model, a quantified
model for automatically assessing the validity of relationships in an
ontology. On an algorithmic level, we provide an example of a
mapping of ontology operator for defining relationships into context
relationships. We motivate our work with examples from the
eGovernment domain. However, due to the absence of large scale data sets for
this domain, we support our model with an empirical analysis using
real-world traces of RSS data.</p>
      <p>The rest of the paper is organized as follows. We start with
preliminaries, formally defining ontologies and contexts in Section 2.
In Section 3 we introduce the ontology verification model, followed
by an example of a mapping of the ontology verification problem to
contexts in Section 4. We conclude with related work in Section 5
and a short summary in Section 6.</p>
    </sec>
    <sec id="sec-2">
      <title>ONTOLOGIES AND CONTEXTS</title>
      <p>
        Banerjee [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] defined a root class as an object that represents
anything from a simple number to a complex entity. An edge between
a node and a child node in a class represents an IS-A relationship.
Objects that belong to a class are called instances of that class. A
class describes the form (instance variables) of its instances and the
operations (methods) applicable to its instances.
      </p>
      <p>
        According to Gruber [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], an ontology is an explicit specification of
a domain conceptualization. Several models for ontologies exist; we
follow here that presented in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. In the discussion below, we assume
reader familiarity with basic concepts in conceptual modeling.
      </p>
      <p>We define a context C = {hcij , wij i}j i as a set of finite sets
of descriptors cij from a domain D with appropriate weights wij ,
representing the importance of cij . For example, a context C may be
a set of words (hence, D is a set of all possible character
combinations) defining a document Doc, and the weights could represent the
relevance of a descriptor to Doc. In classic Information Retrieval,
hcij , wij i may represent the fact that the word cij is repeated wij
times in Doc.</p>
      <p>
        The context of a class is defined as a set of contexts describing
instances that belong to this class. Documents are not instances but
represent them. Following [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], we define a class context CCL of a
class CL to be the union of its instance contexts.
      </p>
      <p>
        Segev and Gal [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] aimed at formalizing the inter-relationships
between an ontology, a manually generated domain model, and
contexts, partial and automatically generated local views. According to
their work, a context can belong to multiple context sets, which in
turn can converge to different ontology concepts. Thus, one context
can belong to several ontology concepts simultaneously. The
appropriate interpretation of a context leads to its relevance to different
given concepts.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>ONTOLOGY VERIFICATION USING</title>
    </sec>
    <sec id="sec-4">
      <title>CONTEXTS</title>
      <p>
        Ontology verification is the process by which semantic relationships
are identified. We term this process verification, since we assume
an ontology exists and may need to evolve. Therefore, semantic
relationships in an ontology need to be continuously monitored and
if necessary, revised. Here we follow the work of [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] on ontology
changes and assume a given closed set of operators OT , to be
applied on a set of operands OD, taken from the set of all ontology
elements. As an example, a change operator may be the disjoint
operator, resulting in the creation of a semantic relationship called
“disjoint” between two classes, given to it as operands.
      </p>
      <p>
        Figure 1 provides a pictorial representation of the process.
Formally, ontology verification is a function OV : OT ×OD∗ → [
        <xref ref-type="bibr" rid="ref1">0, 1</xref>
        ].
Ontology verification is given as input a hypothesis regarding the
possible operator to be applied to one or more operands and returns
a level of certainty μ regarding the truth in this hypothesis. A
certainty of 1 indicates full certainty in the hypothesis, while a certainty
of 0 means that the hypothesis is definitely incorrect. In Figure 1, the
ontology verification function determines that the disjointedness of
classes CL1 and CL2 has a certainty level of 0.9. An example of
the use of the model can be a user who would like to analyze a local
government concept relationship. The user could supply a set of
documents representing two concepts and could receive a verification
level based on this representative set of documents.
      </p>
      <p>Q
Operator Operand
Disjoint CL1, CL2</p>
      <sec id="sec-4-1">
        <title>Ontology</title>
      </sec>
      <sec id="sec-4-2">
        <title>Verification</title>
        <p>
          Certainty Level
0.9
Having introduced ontology verification, we now focus on the details
of change operators. Noy and Klein [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] describe a set of 22 ontology
change operators and their impact on ontology elements (both classes
and instances) using ontology relations defined in [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. We take one
of their ontology change operators and use it as an example.
        </p>
        <p>
          Our experiences are based on data from the RSS news data trace.
In this data trace, data were originally partitioned to topics with no
ontological relationships. The RSS trace was collected during August
2005 from the CNN Web site. We chose 10 news topic categories for
the data, when each RSS news header or news descriptor constitutes
a datum. We generated a context for each datum and each class using
an automatic context extraction algorithm [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. The number of context
descriptors generated from each datum was set to 10. The data size
used for RSS varied from 73 to 1,911 per class.
        </p>
        <p>In our experiment we calculated for each class the number of
contexts that overlapped with the other nine classes. This asymmetric
comparison gave us for any two classes CLi and CLj the metric of
CCLi ∩ CCLj and CCLi ∪ CCLj .</p>
        <p>Given two classes, CLi and CLj , if CLi is a subclass of CLj ,
then its context should be contained in the context of CLj . This is
because an instance of CLi is also an instance of CLj and therefore
has a broader context than an instance of the superclass. Therefore,
we compute the certainty of a hypothesis that CLi is a subclass of
CLj to be
μSub-Sup =</p>
        <sec id="sec-4-2-1">
          <title>CCLi ∩ CCLj</title>
        </sec>
        <sec id="sec-4-2-2">
          <title>CCLj</title>
          <p>Our experience involves an analysis of hierarchy linking. Figure 2
presents the RSS class relations hierarchy created for μSub-Sup ≥
0.8 and μSub-Sup ≥ 0.5. As the value of μSub-Sup decreases, the
hierarchy and the relations between the classes become more
elaborated. For example, in the RSS data for μSub-Sup ≥ 0.8 the
superclass Money Latest has four subclasses. If we examine the same
classes for a lower verification level of μSub-Sup ≥ 0.5 we receive
a three level hierarchy.</p>
          <p>Table 1 compares the certainty level of the Superclass-Subclasss
operator, for two class pairs in the RSS data set. When evaluating the
classes Money Latest and Money News International, there is a
high μSub-Sup level.</p>
          <p>Money Latest</p>
          <p>Money News
International</p>
          <p>Money Top</p>
          <p>Stories
5</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>RELATED WORK</title>
      <p>
        A formal mathematical framework that delineates the relationships
between contexts and ontologies is presented in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. To deal with the
uncertainty associated with automatic context extraction from
existing instances, such as documents, a ranking model was provided,
which ranks ontology concepts according to their suitability with a
given context.
      </p>
      <p>
        A semi-automated method for ontology evolution using
documents clustering was proposed in [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. From the results of the
clustering ontology enrichments and updates are extracted. In contrast to
the above work, which is based on a single word ontology concept
description, we use a set of contexts describing each ontology class.
      </p>
      <p>
        Noy and Klein [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] defined a set of ontology-change operations
and their effects on instance data used during the ontology evolution
process. They describe ontologies schemas and database schemas
from the point of view of evolution and highlight the main
differences between them. We presented a model that shows how these
ontology change operations can be verified based on context.
      </p>
      <p>
        Tools for merging and aligning ontologies, such as SENSUS [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
PROMPT [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], and Cyc [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], have been developed in the past. These
tools generally present a set of basic operations that are performed
during the mergence and alignment of ontologies and that determine
the effects that each of these operations has on the process.
      </p>
      <p>
        A work on multi-contextual ontology evolution [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] defines a set
of properties that by semantic autonomy must hold at the same time.
6
      </p>
    </sec>
    <sec id="sec-6">
      <title>CONCLUSION</title>
      <p>This work presents a model and a set of algorithms to
semiautomatically support ontology relationship evolution using contexts.
Given an ontology operator and operands, the model provides the
quantification of the extent to which the relationship is valid. The
model is supported by empirical analysis, using initial experiences
with real-world RSS traces. The experiences with these traces show
how relationships between the classes can be created and modified.
Preliminary empirical results show that our model can provide good
estimations of the need for ontology changes.</p>
      <p>To recap, the main contribution of this work is both conceptual
and algorithmic. We present an ontology verification model, a
quantified model for automatically assessing the validity of relationships
in an ontology, and we also provide a mapping of several ontology
operators for determining relationships among classes.</p>
      <p>The results of this work will be embedded as part of the
TerreGov solution. Future research will examine the model performance
on eGovernment data and other large data sets. In addition, we plan
on extending the model to include additional operators.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Banerjee</surname>
          </string-name>
          , H.-T. Chou,
          <string-name>
            <given-names>J.</given-names>
            <surname>Garza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Woelk</surname>
          </string-name>
          , and
          <string-name>
            <given-names>N.</given-names>
            <surname>Ballou</surname>
          </string-name>
          , '
          <article-title>Data model issues for object-oriented applications'</article-title>
          ,
          <source>ACM Transactions on Office Information Systems</source>
          ,
          <volume>5</volume>
          (
          <issue>1</issue>
          ),
          <fpage>3</fpage>
          -
          <lpage>26</lpage>
          , (
          <year>1987</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>T. R.</given-names>
            <surname>Gruber</surname>
          </string-name>
          , '
          <article-title>A translation approach to portable ontologies'</article-title>
          ,
          <source>Knowledge Acquisition</source>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ), (
          <year>1993</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>K.</given-names>
            <surname>Knight</surname>
          </string-name>
          and
          <string-name>
            <given-names>S. K.</given-names>
            <surname>Luk</surname>
          </string-name>
          , '
          <article-title>Building a large-scale knowledge base for machine translation'</article-title>
          ,
          <source>in Proceedings of the Twelfth National Conference on Artificial Intelligence (AAAI-94)</source>
          , (
          <year>1994</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>D. B.</given-names>
            <surname>Lenat</surname>
          </string-name>
          , '
          <article-title>Cyc: A large-scale investment in knowledge infrastructure'</article-title>
          ,
          <source>Communications of ACM</source>
          ,
          <volume>38</volume>
          (
          <issue>11</issue>
          ),
          <fpage>33</fpage>
          -
          <lpage>38</lpage>
          , (
          <year>1995</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>J. McCarthy</surname>
          </string-name>
          , 'Notes on formalizing context',
          <source>In Proceedings of the Thirteenth International Joint Conference on Artificial Intelligence</source>
          , (
          <year>1993</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Klein</surname>
          </string-name>
          , '
          <article-title>Ontology evolution: Not the same as schema evolution'</article-title>
          ,
          <source>Knowledge and Information Systems</source>
          ,
          <volume>6</volume>
          (
          <issue>4</issue>
          ),
          <fpage>428</fpage>
          -
          <lpage>440</lpage>
          , (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          and
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Musen</surname>
          </string-name>
          , '
          <article-title>The prompt suite: Interactive tools for ontology merging</article-title>
          and mapping',
          <source>International Journal of HumanComputer Studies</source>
          ,
          <volume>59</volume>
          (
          <issue>6</issue>
          ),
          <fpage>983</fpage>
          -
          <lpage>1024</lpage>
          , (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.</given-names>
            <surname>Segev</surname>
          </string-name>
          , '
          <article-title>Identifying the multiple contexts of a situation'</article-title>
          ,
          <source>in Proceedings of IJCAI-Workshop Modeling and Retrieval of Context (MRC2005)</source>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Segev</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Gal</surname>
          </string-name>
          , '
          <article-title>Putting things in context: A topological approach to mapping contexts and ontologies'</article-title>
          ,
          <source>in Proceedings of AAAI-Workshop Workshop on Contexts and Ontologies: Theory, Practice and Applications</source>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>E.</given-names>
            <surname>Toch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gal</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Dori</surname>
          </string-name>
          , '
          <article-title>Automatically grounding semanticallyenriched conceptual models to concrete web services'</article-title>
          , in ER, eds.,
          <string-name>
            <given-names>L.M.L.</given-names>
            <surname>Delcambre</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Kop</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.C.</given-names>
            <surname>Mayr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          , and
          <string-name>
            <given-names>O.</given-names>
            <surname>Pastor</surname>
          </string-name>
          , volume
          <volume>3716</volume>
          of Lecture Notes in Computer Science, pp.
          <fpage>304</fpage>
          -
          <lpage>319</lpage>
          . Springer, (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>G.</given-names>
            <surname>Tsatsaronis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pitkanen</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Vazirgiannis</surname>
          </string-name>
          , '
          <article-title>Clustering for ontology evolution'</article-title>
          ,
          <source>in Proceedings of the 29th Annual Conference of the German Classification Society (GfKl</source>
          <year>2005</year>
          ), (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Zurawski</surname>
          </string-name>
          , '
          <article-title>Reasoning about multi-contextual ontology evolution'</article-title>
          ,
          <source>in Proceedings of the First International Workshop on Context and Ontologies: Theories, Practice and Applications</source>
          ,
          <source>The Twentieth National Conference on Artificial Intelligence (AAAI-05)</source>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>