<!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>Define Hybrid Class Resolving Disjointness Due to Subsumption</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Rim Djedidi</string-name>
          <email>rim.djedidi@supelec.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marie-Aude Aufaure</string-name>
          <email>marie-aude.aufaure@ecp.fr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department</institution>
          ,
          <addr-line>Supélec Campus de Gif Plateau du Moulon - 3, rue Joliot Curie - 91192 Gif sur Yvette Cedex</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>MAS Laboratory, SAP Business Object Chair -Centrale Paris Grande Voie des Vignes</institution>
          ,
          <addr-line>F-92295 Châtenay-Malabry Cedex</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <fpage>100</fpage>
      <lpage>103</lpage>
      <abstract>
        <p>The pattern “Define Hybrid Class Resolving Disjointness due to Subsumption” is proposed as a Logical Ontology Design Pattern (Logical OP) solving a problem of disjointness inconsistency caused by a subsumption relation. Further away from solving design problems where the primitives of the representation language do not directly support certain logical constructs, this pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common subclass. The solution presented by the pattern resolves the inconsistency while preserving existing knowledge, i.e. a resolution alternative avoiding axiom deletion.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <sec id="sec-1-1">
        <title>2.1 Problem</title>
        <p>In this section, we specify the problem that the pattern deals with and the
requirements covered by it; we detail the description of the solution given by this
pattern and the consequences of its application; and we illustrate the pattern by an
example problem and its corresponding solution.</p>
        <p>The pattern “Define Hybrid Class Resolving Disjointness due to Subsumption” is
proposed to solve a problem of disjointness inconsistency caused by a subsumption
relation. When we need to define – for some modeling issues related to domain of
interest – a class as a sub-class of two disjoint classes, a disjointness inconsistency is
caused.</p>
        <p>The problem can be illustrated by the following scenario: let’s consider a class
Sub_Class defined as a sub-class of a class Disjoint_Class 2; and a class
Disjoint_Class 1 disjoint with the Disjoint_Class 2 (Fig. 1). If we need to add a
subclass relation between the Sub_Class and the Disjoint_Class 1, this generates a
disjointness inconsistency:
− If the extension of the Sub_Class contains individuals instantiating this sub-class,
the logical inconsistency will be extended to the knowledge base;
− If the Sub_Class is not instantiated to individuals, it will be diagnosed as an
unsatisfiable class.
{Disjoint}</p>
        <p>Disjoint_Class 2</p>
        <p>Sub_Class</p>
        <p>
          To solve this inconsistency, one can think about deleting the disjointness axiom.
However, this can alter the semantics expressed in the ontology, and negatively affect
consistency checking and automatic evaluation of existing individuals as explained in
[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>This pattern tackles the questions of how to resolve the inconsistency caused by
such kind of subsumption while preserving existing knowledge.</p>
        <p>Intent The purpose of this pattern is to support the semantics of a subsumption
defined under two disjoint classes and resolve the resulting inconsistency.
Covered Requirements The pattern solves a problem of disjointness inconsistency
caused by a subsumption relation without deleting the disjointness axiom so that
existing knowledge can be preserved.</p>
      </sec>
      <sec id="sec-1-2">
        <title>2.2 Solution</title>
        <p>The pattern resolves a disjointness inconsistency –due to a subsumption–by defining a
Hybrid Class based on the definition of disjoint classes implicated in the
inconsistency; and redistributing correctly sub-class relations between the sub-class,
the hybrid class, and the most specific common super-class of the disjoint classes
implicated. The definition of the Hybrid Class is the union (OR) of the definitions of
the disjoint classes.</p>
        <p>The application of the solution can be described by the following process (Fig. 2):
1. The pattern defines a Hybrid Class as a union of the definitions of the disjoint
classes implicated in the inconsistency to be resolved;
2. The pattern defines a subsumption between the most specific common super-class
of the disjoint classes implicated in the inconsistency, and the Hybrid Class
created;
2
3. The pattern defines a subsumption between the Hybrid Class and the sub-class
involved in the inconsistency.</p>
        <p>Common_Super_Class</p>
        <p>Consequences The application of the pattern resolves the disjointness inconsistency
(even if the involved sub-class is instantiated by individuals) and preserves existing
knowledge. As a Logical OP, this pattern is independent from a specific domain of
interest. However, it depends on the expressivity of the logical formalism used for the
representation of the ontology. Therefore, the language of the targeted ontology
should allow expressing class union.</p>
      </sec>
      <sec id="sec-1-3">
        <title>2.3 Example</title>
      </sec>
      <sec id="sec-1-4">
        <title>Example Problem</title>
        <p>axioms:
To explain pattern application, we present in this section, an example problem and its
corresponding solution according to the pattern.</p>
        <p>Let’s consider the OWL ontology O defined by the following
{Animal Fauna-Flora, Plant</p>
        <p>Plant, Plant Animal}</p>
        <p>Fauna-Flora, Carnivorous-Plant</p>
        <p>If we apply a change to the ontology defining Carnivorous-Plant class as a
subclass of the class Animal, we cause a disjointness inconsistency. The proposed pattern
resolves this kind of inconsistency.</p>
        <p>Example Solution The application of the pattern to resolve the example above is
performed as follow:
1. The pattern defines a class Animal_Plant as a union of the definitions of the
disjoint classes Animal and Plant;
2. The pattern defines a subsumption between the most specific common super-class
of the disjoint classes Fauna-Flora and the hybrid class created Animal_Plant;</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>3 Pattern Usage</title>
      <p>
        The proposed – Logical OP – pattern “Define Hybrid Class Resolving Disjointness
due to Subsumption” is applied as an Alternative Resolution Pattern in an ontology
evolution approach ONTO-EVOAL, guided by Change Management Patterns (CMP)
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. CMP patterns drive and control the change management process at three key
phases: change specification, change analysis, and change resolution, by modeling
three categories of patterns: Change Patterns classifying types of changes,
Inconsistency Patterns classifying types of logical inconsistencies, and Alternative
Patterns classifying types of inconsistency resolution alternatives.
      </p>
    </sec>
    <sec id="sec-3">
      <title>4 Summary and Future Work</title>
      <p>The purpose of this pattern is to support the semantics of a subsumption defined under
two disjoint classes and resolve the resulting inconsistency without removing existing
knowledge. This pattern can be extended and adapted to resolve disjointness
inconsistency due to instantiation.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Völker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vrandecic</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sure</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hotho</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Learning Disjointness</article-title>
          . In F.,
          <string-name>
            <surname>Enrico</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Michael</surname>
          </string-name>
          , May. Wolfgang (Eds.).
          <source>Proceedings of the 4th European Semantic Web Conference</source>
          ,
          <string-name>
            <surname>ESWC</surname>
          </string-name>
          <year>2007</year>
          . LNCS: Vol.
          <volume>4519</volume>
          pp:
          <fpage>175</fpage>
          -
          <lpage>189</lpage>
          . (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Djedidi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aufaure</surname>
            ,
            <given-names>M-A.</given-names>
          </string-name>
          :
          <article-title>Ontology Change Management</article-title>
          . In: A.
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Weigand</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Behrendt</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Tochtermann</surname>
          </string-name>
          , T. Pellegrini (Eds.),
          <string-name>
            <surname>I-Semantics</surname>
            <given-names>2009</given-names>
          </string-name>
          ,
          <source>Proceedings of IKNOW '09 and I-SEMANTICS '09, ISBN 978-3-85125-060-2</source>
          , pp.
          <fpage>611</fpage>
          --
          <lpage>621</lpage>
          , Verlag der Technischen Universitt Graz. (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>