<!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>Inconsistency-Tolerant Ontology-Based Data Access Revisited: Taking Mappings into Account</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>LaBRI - CNRS</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>University of Bordeaux</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>France meghyn.bienvenu@labri.fr</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>We give a brief overview of our recent work on inconsistencytolerant OBDA with mappings, published at IJCAI'18 [4].</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Ontology-based data access (OBDA) aims to improve access to data (typically
stored in relational databases) by using an ontology to provide a conceptual
view of the data that describes the semantic relationships holding between
different terms [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. The focus of the work reported in this abstract is handling
data inconsistencies in OBDA. It is widely acknowledged that real-world data
su ers from numerous data quality issues, and errors in data are frequent. In
the context of OBDA, such errors can lead to logical contradictions, in which
case standard OBDA semantics (based upon classical rst-order logic)
trivializes. Fixing the errors by making changes to the underlying data is typically
impossible, as we often do not have permission to modify the data (and even
if we do, it may not be clear which modi cations should be made). A solution
is to adopt inconsistency-tolerant semantics, which allow meaningful answers to
be obtained from inconsistent data.
      </p>
      <p>
        The problem of querying inconsistent data using alternative semantics has
been extensively studied by the database community, under the name of
consistent query answering [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. In the database setting, inconsistencies arise from
violations of integrity constraints, and a repair is a database that satis es the
constraints and di ers minimally from the original database. Various notions of
repairs have been considered, among them, subset repairs ( -repairs), which are
inclusion-maximal consistent subsets of the database, and symmetric di erence
repairs ( -repairs), which may both add and delete facts and minimize the set
of such changes. Consistent query answering then amounts to computing those
query answering that hold in every repair.
      </p>
      <p>
        Recent years have seen a urry of activity on the topic of
inconsistencytolerant query answering of DL knowledge bases, with proposals of di erent
inconsistency-tolerant semantics [
        <xref ref-type="bibr" rid="ref7 ref8">8, 7</xref>
        ], complexity analyses of query answering
under said semantics [
        <xref ref-type="bibr" rid="ref11 ref3">11, 3</xref>
        ], and some rst implemented systems [
        <xref ref-type="bibr" rid="ref12 ref6 ref9">6, 9, 12</xref>
        ]. We
refer readers to the survey [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] for further references. Many of the considered
semantics are based upon the notion of an ABox repair, de ned as a -maximal
subset of the ABox that is consistent w.r.t. the TBox. These include the AR
semantics (which requires a query to hold w.r.t. every repair, as in consistent
query answering), brave semantics (the dual of AR, which requires a query to
      </p>
      <p>GAV
GAV:;6=</p>
      <p>DL-Lite
PTime DLs
DL-Lite
PTime DLs</p>
      <p>AR</p>
      <p>IAR</p>
      <p>brave
coNP-c in AC0 in AC0
coNP-c coNP-c NP-c
2p-c
2p-c
2p-c
2p-c
2p-c
2p-c
hold in some repair), and IAR semantics (a strengthening of AR semantics,
which queries the intersection of all repairs).</p>
      <p>Existing works have focused on a simpli ed version of ontology-based data
access (OBDA), in which the data is given as a set of ABox facts over the TBox
signature, leaving open the question of how best to adapt repair-based semantics
to handle mappings. There are (at least) two natural options: either consider
the repairs of the ABox that results from applying the mappings to the data
(`map-then-repair' approach), or compute repairs at the database level using
the mapping and TBox to determine consistent database instances
(`repair-atsource' approach). The latter approach has not been considered before in the
OBDA literature, and we argue that it presents two important advantages w.r.t.
the map-then-repair approach. First, it avoids the arguably undesirable situation
where a repair contains ABox facts that originate from database tuples that are
jointly inconsistent w.r.t. the mapping and TBox, and second, it is much more
easily adapted to handle database integrity constraints.</p>
      <p>In this work, we formalize the repair-at-source approach and investigate its
computational properties. We begin by proposing a notion of OBDA repair,
which is de ned at the level of the database, with the mapping and ontology
serving to de ne consistent instances. As the repairs involve modi cations of the
underlying (closed-world) database, we in fact consider two notions: -repairs
and -repairs. New variants of the AR, brave, and IAR semantics are then
de ned based upon these two kinds of OBDA repairs.</p>
      <p>We perform a detailed study of the data complexity of OBDA under these
semantics, considering both DL-Lite and the general class of `data-tractable' DLs,
which includes DLs of the E L family and more expressive Horn DLs like
HornSHIQ. We consider two forms of global-as-view (GAV) mappings, one which
only allows positive atoms in mapping bodies and a more expressive variant
where mapping bodies may contain negated atoms and inequalities (GAV:;6=).
Mappings with complex bodies (in particular, negated atoms) are supported by
existing OBDA systems and have proven useful in OBDA applications.</p>
      <p>Our results (displayed in Figure 1) show that for plain GAV mappings, the
complexity is the same as in the simple OBDA setting without mappings; in
particular, the tractability results for DL-Lite under IAR and brave semantics
are preserved. By contrast, adding negated atoms leads to a jump in complexity,
with all problems moving to the second level of the polynomial hierarchy.</p>
      <p>Inconsistency-Tolerant OBDA Revisited: Taking Mappings into Account</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Arenas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bertossi</surname>
            ,
            <given-names>L.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chomicki</surname>
          </string-name>
          , J.:
          <article-title>Consistent query answers in inconsistent databases</article-title>
          .
          <source>In: Proceedings of PODS</source>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bertossi</surname>
            ,
            <given-names>L.E.</given-names>
          </string-name>
          :
          <article-title>Database Repairing and Consistent Query Answering</article-title>
          .
          <source>Synthesis Lectures on Data Management</source>
          , Morgan &amp; Claypool Publishers (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bienvenu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>On the complexity of consistent query answering in the presence of simple ontologies</article-title>
          .
          <source>In: Proceedings of AAAI</source>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bienvenu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Inconsistency-tolerant ontology-based data access revisited: Taking mappings into account</article-title>
          .
          <source>In: Proc. of IJCAI</source>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bienvenu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bourgaux</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Inconsistency-tolerant querying of description logic knowledge bases</article-title>
          .
          <source>In: Reasoning Web, Tutorial Lectures. Lecture Notes in Computer Science</source>
          , vol.
          <volume>9885</volume>
          , pp.
          <volume>156</volume>
          {
          <fpage>202</fpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bienvenu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bourgaux</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goasdoue</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Querying inconsistent description logic knowledge bases under preferred repair semantics</article-title>
          .
          <source>In: Proceedings of AAAI</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Bienvenu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosati</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Tractable approximations of consistent query answering for robust ontology-based data access</article-title>
          .
          <source>In: Proceedings of IJCAI</source>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lembo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosati</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruzzi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savo</surname>
            ,
            <given-names>D.F.</given-names>
          </string-name>
          :
          <article-title>Inconsistency-tolerant semantics for description logics</article-title>
          .
          <source>In: Proceedings of RR</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lembo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosati</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruzzi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savo</surname>
            ,
            <given-names>D.F.</given-names>
          </string-name>
          :
          <article-title>Inconsistency-tolerant query answering in ontology-based data access</article-title>
          .
          <source>Journal Web Sem</source>
          .
          <volume>33</volume>
          ,
          <issue>3</issue>
          {
          <fpage>29</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Poggi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lembo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvanese</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giacomo</surname>
            ,
            <given-names>G.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosati</surname>
          </string-name>
          , R.:
          <article-title>Linking data to ontologies</article-title>
          .
          <source>Journal of Data Semantics</source>
          <volume>10</volume>
          ,
          <issue>133</issue>
          {
          <fpage>173</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Rosati</surname>
          </string-name>
          , R.:
          <article-title>On the complexity of dealing with inconsistency in description logic ontologies</article-title>
          .
          <source>In: Proceedings of IJCAI</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Tsalapati</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoilos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stamou</surname>
            ,
            <given-names>G.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koletsos</surname>
          </string-name>
          , G.:
          <article-title>E cient query answering over expressive inconsistent description logics</article-title>
          .
          <source>In: Proceedings of IJCAI</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>