<!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>A Study on the Correspondence between FCA and E LI Ontologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Melisachew Wudage Chekol</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Amedeo Napoli</string-name>
          <email>amedeo.napolig@inria.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>LORIA (INRIA, CNRS, and Universite de Lorraine)</institution>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The description logic EL has been used to support ontology design in various domains, and especially in biology and medecine. EL is known for its e cient reasoning and query answering capabilities. By contrast, ontology design and query answering can be supported and guided within an FCA framework. Accordingly, in this paper, we propose a formal transformation of ELI (an extension of EL with inverse roles) ontologies into an FCA framework, i.e. KELI , and we provide a formal characterization of this transformation. Then we show that SPARQL query answering over ELI ontologies can be reduced to lattice query answering over KELI concept lattices. This simpli es the query answering task and shows that some basic semantic web tasks can be improved when considered from an FCA perspective.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        with SPARQL. However, including inferred data in query answering requires
either a reasoner to infer all implicit information or query rewriting using property
paths (that enable navigation in a hierarchy) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The latter obliges the user to
know the nuts and bolts of SPARQL. To overcome these di culties, we reduce
SPARQL query answering in E LI ontologies into query answering in concept
lattices along with the transformation of the queried ontology into a formal
context. Then, the resulting concept lattice provides support for query answering
(but this does not replace SPARQL) and also for visualization and navigation
of relations within SW data.
      </p>
      <p>Overall, we work towards (i) a formal characterization of the transformation
of ontologies into a formal context, (ii) translating the di culty of SPARQL
query answering over ontologies into query answering over concept lattices, and
nally (iii) providing organization of SPARQL query answers with concept
lattices.
2</p>
      <p>
        Transforming E LI Ontologies into Formal Contexts
A formal context represents data using objects and their attributes. Formally, it
is a triple K = (G; M; I) where G is a set of objects, M is a set of attributes,
and I G M is a binary relation. A derivation operator (0) is used to compute
formal concepts of a context. Given a set of objects A, a derivation operator 0
computes the maximal set of attributes shared by objects in A and is denoted
by A0 (this is done dually with set of attributes B). A formal concept is a pair
(A; B) where A0 = B and B0 = A. A set of formal concepts ordered with the set
inclusion relation form a concept lattice [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>One di culty of transforming DL ontologies into formal contexts is mainly
due to the fact that while DL languages are based on the open world assumption
(OWA), FCA relies on the closed world assumption (CWA). The former permits
to specify only known data whereas the later demands that all data should
be explicitly speci ed. To slightly close the gap between these two worlds, we
provide a transformation that maintains a DL semantics into an FCA setting.</p>
      <p>
        To transform an E LI ontology O = hT ; Ai into a formal context K =
(G; M; I), the schema axioms in the TBox become background implications [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
Then, individuals in the ABox correspond to objects in G, class names in the
ABox and TBox yield attributes in M , and ABox assertions create relations
between objects and attributes I G M . Here, we consider acyclic TBoxes to
avoid that class names become objects in a context. The following table gives a
summary of the correspondence.
      </p>
      <p>E LI O = hT ; Ai FCA formal context KO = (G; M; I) +</p>
      <p>background implications L
T = fC v Dg fC ! Dg 2 L</p>
      <p>A = fC(a); a 2 G, C 2 M , and (a; C) 2 I</p>
      <p>R(a; b)g a; b 2 G, 9R:&gt;; 9R :&gt; 2 M , (a; 9R:&gt;) 2 I,
and (b; 9R :&gt;) 2 I
Art
tC
Prd</p>
      <p>Act</p>
      <p>AFNY
Example 1. Consider the transformation of the following E LI ontology O =
hT ; Ai into a formal context KO and its background implications L.
T = fActorsFromNewYork (AFNY) v Actor (Act);</p>
      <p>FilmProducer (Prd) v Artist (Art); Actor v Artist; Artist v Person (Per)g
A = ftomCruise (tC) 2 ActorsFromNewYorkg</p>
      <p>L = f AFNY ! Act; Prd ! Art;
KO AFNY Prd Act Art Per
tC
x</p>
      <p>
        Act ! Art; Art ! Per g
Construction of a concept lattice: In [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], an algorithm to construct a concept
lattice from a formal context w.r.t. background implications is provided. This
technique is employed here and the concept lattice associated with the formal
context and background implications of Example 1 is depicted in Figure 1.
      </p>
      <p>This is a simple example but SNOMED-CT and NCIT are much larger than
that but not more complex. Let us how a concept lattice based on an E LI
ontology can be queried.
3</p>
      <p>
        SPARQL query answering over ontologies vs query
answering over concept lattices
SPARQL query answering over E LI ontologies can be considered from the point
of view of query answering over KELI concept lattices. Querying concept lattices
amounts to fetching the objects given a set of attributes as query constants and
to fetch the attributes given a set of objects as query constants or terms [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
Query terms can be connected using the logical operators: and, union, and set
di erence to form a complex term.
      </p>
      <p>SPARQL query answering over ontologies can be done in two main ways: (1)
Materialization amounts to computing all implicit data before evaluating the
query. This can be done by using a DL reasoner. (2) Query rewriting amounts to
converting a query into another one using property paths and schema axioms.</p>
      <p>Query answering over E LI ontologies with SPARQL appears to be harder
than query answering over KELI concept lattices. SPARQL requires expensive
tasks such as materialization and query rewriting but its expressive power is
better than lattice querying. By contrast, lattice querying is practically su cient
to retrieve instances for E LI ontologies as shown by the following example.
Example 2. Let us consider the evaluation of the SPARQL query Q on the
ontology O (in Figure 1) and its materialization O0. Q = select all objects, elements
who are artists = SELECT ?x WHERE f?x a Artist .g: Under simple
entailment evaluation of a SPARQL query, the answer of Q over O is empty. To
get non-empty answers for Q, one can evaluate Q over the materialization of
O that we call O0, where Q(O0) = ftomCruiseg. Another way is to rewrite Q
into Q0 = SELECT ?x WHERE f?x a/rdfs:subClassOf Artist .g. Q0
selects all instances of Artist and that of its subclasses by navigating through
the subclass relation. Then, the evaluation of Q0(O) returns ftomCruiseg.</p>
      <p>By contrast, Q is converted into a lattice query as q(x) = (x; Artist). The
evaluation of this query over a concept lattice KO obtained from O (Figure
1) is Q0(KO) = ftomCruiseg, as it is su cient to return all objects which are
instances of Artist or any of its subconcept.
4</p>
    </sec>
    <sec id="sec-2">
      <title>Discussion</title>
      <p>It can be convenient to use FCA as a guideline for designing and querying E LI
ontologies. In addition, FCA provides visualization and navigation capabilities.
The present work does not apply to all ontologies but seems to be well suited
to E LI ontologies. We plan to extend and experiment the proposed approach,
especially with real-world and large datasets.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Distel</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Exploring nite models in the description logic EL gfp</article-title>
          .
          <source>In: ICFCA</source>
          . pp.
          <volume>146</volume>
          {
          <fpage>161</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Carpineto</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romano</surname>
          </string-name>
          , G.:
          <article-title>Concept data analysis: Theory and applications</article-title>
          . Wiley (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>d'Aquin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Motta</surname>
          </string-name>
          , E.:
          <article-title>Extracting relevant questions to an RDF dataset using formal concept analysis</article-title>
          .
          <source>In: Proceedings of the sixth international conference on Knowledge capture</source>
          . pp.
          <volume>121</volume>
          {
          <fpage>128</fpage>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Attribute exploration with background knowledge</article-title>
          .
          <source>Theoretical Computer Science</source>
          <volume>217</volume>
          (
          <issue>2</issue>
          ),
          <volume>215</volume>
          {
          <fpage>233</fpage>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wille</surname>
          </string-name>
          , R.:
          <source>Formal Concept Analysis</source>
          . Springer, Berlin (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Glimm</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Using SPARQL with RDFS and OWL entailment</article-title>
          .
          <source>Reasoning Web. Semantic Technologies for the Web of Data</source>
          pp.
          <volume>137</volume>
          {
          <issue>201</issue>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kirchberg</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leonardi</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tan</surname>
            ,
            <given-names>Y.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Link</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ko</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>B.S.:</given-names>
          </string-name>
          <article-title>Formal concept discovery in semantic web data</article-title>
          .
          <source>In: ICFCA</source>
          . pp.
          <volume>164</volume>
          {
          <fpage>179</fpage>
          . Springer-Verlag (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Sertkaya</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A survey on how description logic ontologies bene t from FCA</article-title>
          .
          <source>In: CLA</source>
          . vol.
          <volume>672</volume>
          , pp.
          <volume>2</volume>
          {
          <issue>21</issue>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>