<!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>Recognizing Determinism in Prioritized Repairing of Inconsistent Databases</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Benny Kimelfeld</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ester Livshits</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Liat Peterfreund</string-name>
          <email>liatpfg@cs.technion.ac.il</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Technion</institution>
          ,
          <addr-line>Haifa 32000</addr-line>
          ,
          <country country="IL">Israel</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A repair of an inconsistent database is traditionally defined as a consistent database that differs from the inconsistent one in a “minimal way.” As there are often reasons to prefer one repair over another, researchers have introduced and investigated the framework of preferred repairs, where a priority relation between facts is lifted towards a priority relation between consistent databases, and repairs are restricted to ones that are optimal in the lifted sense. In this paper we describe our recent results on the complexity of deciding whether the priority relation suffices to clean the database unambiguously, or in other words, whether there is exactly one optimal repair. In particular, we show that different conventional semantics of priority lifting entail highly different complexities.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Database inconsistency arises for various reasons and in different applications. In
common applications of Big Data, information is obtained from imprecise sources (e.g.,
social encyclopedias or social networks) via imprecise procedures (e.g., natural-language
processing). It may also arise when integrating conflicting data from different sources
(each of which may be consistent). Arenas, Bertossi and Chomicki [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] introduced a
principled approach to managing inconsistency, via the notions of repairs and
consistent query answering. Informally, a repair of an inconsistent database I is a consistent
database J that differs from I in a “minimal” way.
      </p>
      <p>
        There are situations where it is natural to prefer one repair over another [
        <xref ref-type="bibr" rid="ref11 ref16 ref17 ref5">5, 11, 16,
17</xref>
        ]. For example, this is the case if one source is regarded more reliable than another
(e.g., enterprise data vs. Internet harvesting, and precise vs. imprecise sensing
equipment) or if available timestamp information implies that a more recent fact is more up
to date than an earlier one.
      </p>
      <p>
        Motivated by the above considerations, Staworko, Chomicki and Marcinkowski [
        <xref ref-type="bibr" rid="ref16 ref17">16,
17</xref>
        ] introduced the framework of preferred repairs. The main characteristic of this
framework is that it uses a priority relation between conflicting facts of an inconsistent
database, in order to define a notion of preferred repairs. Fagin et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] have built on
that concept (in conjunction with the framework of document spanners [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]) to devise
a language for declaring inconsistency cleaning in text information-extraction systems.
They have shown there that preferred repairs capture ad-hoc cleaning operations and
strategies of some prominent systems for text analytics [
        <xref ref-type="bibr" rid="ref2 ref6">2, 6</xref>
        ].
      </p>
      <p>
        While the classic complexity problems studied in the theory of repairs include
repair checking [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and consistent query answering [
        <xref ref-type="bibr" rid="ref15 ref3">3, 15</xref>
        ], the presence of preferences
gives rise to the determinism problem, which Staworko et al. [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] refer to as
categoricity: decide whether the provided priority relation suffices to clean the database
unambiguously. In this paper we describe our recent results on analyzing the complexity of
categoricity in the framework of preferred repairs.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Formal Setup</title>
      <p>
        We adopt the framework of preferred repairs devised by Staworko et al. [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], which has
also been used by Fagin et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        Prioritizing Inconsistent Databases. An inconsistent database over a schema S is a
database D that violates the constraints of S. We consider here two types of constraints.
One is the well known (and restricted) Functional Dependencies (FDs). An FD has the
form R : X ! Y , and it states that every two facts of the relation R either agree
on the attribute set Y or disagree on the attribute set X. The more general type of
constraints considered here is the one given by means of a conflict hypergraph [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. A
conflict hypergraph for a database instance I is a hypergraph H that has the facts of I
as its node set. A subinstance J of I is consistent with respect to (w.r.t.) H if J is an
independent set of H (that is, J contains no hyperedge of H).
      </p>
      <p>
        Recall that conflict hypergraphs can represent inconsistencies for various types of
integrity constraints, including FDs, the more general conditional FDs [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and the more
general denial constraints [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. In fact, every constraint that is anti-monotonic (i.e.,
where subsets of consistent sets are always consistent) can be represented as a conflict
hypergraph. In the case of denial constraints, the translation from the logical constraints
to the conflict hypergraph can be done in polynomial time under data complexity (i.e.,
when the schema signature and constraints are assumed to be fixed).
      </p>
      <p>A priority relation over a database instance I is an acyclic binary relation over the
facts of I. The semantics of f g is that “f is preferred to g” (e.g., because f comes
from a more trusted source, or because f is more recent). A prioritizing inconsistent
database is a triple (I; H; ) where I is a database instance, H is a conflict hypergraph
for I, and is a priority relation over I with the property that compares only between
facts that are neighbors in H.1 We say that is total if for every two facts f and g in I,
if f and g are neighbors then either f g or g f . A priority c over I is a completion
of (w.r.t. H) if is a subset of c and c is total.</p>
      <p>
        Preferred Repairs. Let D be an inconsistent prioritizing database. Staworko et al. [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]
define three different notions of preferred repairs: Pareto optimal, globally optimal,
and completion optimal. Informally speaking, the first two are based on the question
of whether a repair can be improved by replacing a set of facts with a preferable set of
facts. They differ in the way they define when one set of facts is considered preferable
to another. The third is based on the notion of completion.
1 This requirement has been made with the introduction of the framework [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Obviously, the
lower bounds we present hold even without this requirement. Moreover, our main upper bound,
Theorem 3, holds as well without this requirement.
      </p>
      <p>For the formal definitions, let (I ; H; ) be an inconsistent prioritizing database, and
J and J 0 two distinct consistent subinstances of I . We say that J is a Pareto
improvement of J 0 if there exists a fact f 2 J n J 0 such that f f 0 for all facts f 0 2 J 0 n J .
We say that J is a global improvement of J 0 if for every fact f 0 2 J 0 n J there exists a
fact f 2 J n J 0 such that f f 0. In words, J is a Pareto improvement of J 0 if in order
to obtain J from J 0 we insert and delete facts, and one of the inserted facts is preferred
to all deleted facts. And J is a global improvement of J 0 if in order to obtain J from
J 0 we insert and delete facts, and every deleted fact is compensated by some preferable
inserted fact.</p>
      <p>We then get the following variants of preferred repairs for an inconsistent
prioritizing database D = (I ; H; ). A consistent subinstance J of I is a: (a) Pareto-optimal
repair of D if there is no Pareto improvement of J , (b) globally-optimal repair of D if
there is no global improvement of J , and (c) completion-optimal repair of D if there
exists a completion c of such that J is a globally-optimal repair of (I ; H; c).</p>
      <p>
        We remark that in the definition of a completion-optimal repair, we could replace
“globally-optimal” with “Pareto-optimal” and obtain an equivalent definition [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. It
can be shown quite easily that under each of the three notions, an optimal repair is also
a repair in the sense of Arenas et al. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Categoricity. For each of the three semantics, there is always at least one optimal
repair [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. The problem of categoricity is that of deciding whether there is precisely
one optimal repair, and therefore the priority relation contains enough information to
clean the inconsistent database unambiguously. Formally, Pareto categoricity, global
categoricity and completion categoricity are the problems of deciding, given an
inconsistent prioritizing database D, whether D has a single Pareto-optimal repair, a single
globally-optimal repair, and a single completion-optimal repair, respectively. The
problem of repair uniqueness (in different repair semantics) is also referred to as
determinism [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] and fix certainty [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Complexity Results</title>
      <p>We now describe our complexity results for categoricity under the three semantics of
optimal repairs. We begin with the Pareto case. The following theorem gives a
dichotomy in data complexity, covering all possible schemas with functional
dependencies. As is often the case in dichotomy results, the main challenge in the proof is that of
covering all the hard cases.</p>
      <p>Theorem 1. Let S be a relational schema with a set of FDs. Pareto categoricity
over S can be solved in polynomial time if the restriction of to every relation of S is
equivalent to a single FD. In every other case, the problem is coNP-complete.</p>
      <p>Theorem 1 shows that in the case of FDs, the class of schemas that have a tractable
Pareto categoricity is very limited. Next, we discuss global categoricity, and again focus
on FDs. Here we do not have a dichotomy, and establishing one is left as an open
problem for future research.</p>
      <p>Theorem 2. Let S be a relational schema with a set
of FDs. The following hold.
1. If the restriction of to every relation of S is equivalent to a single FD, then global
categoricity over S can be solved in polynomial time.
2. Suppose that consists of two nontrivial FDs X ! Y and W ! Z on the same
relation. Suppose also that each of W and Z contains an attribute that is in none
of the other three attribute sets. Then global categoricity over S is 2p-complete.</p>
      <p>Theorem 2 states that the tractable case of Pareto categoricity remains tractable in
the global case. On other schemas, the complexity can rise to an even higher complexity
class. Next, we consider the completion case, where the picture is far more positive.
Theorem 3. Completion categoricity is decidable in polynomial time, even in the
general case where conflicts are given by a conflict hypergraph.</p>
      <p>Our polynomial time algorithm for solving completion categoricity is extremely
simple, but its proof of correctness is quite intricate.</p>
      <p>Lastly, we observe that in our proof of 2p-hardness for global categoricity, our
reduction constructs a nontransitive priority relation, and we ask whether transitivity
makes a difference. Let (I ; H; ) be an inconsistent prioritizing database. We say that
is transitive if for every two facts f and g in I , if f and g are neighbors in H and
contains a path from f to g, then f g. Transitivity is a natural assumption when
is interpreted as a partial order such as “is of better quality than” or “is more current
than.” We can show that the three semantics remain different in the presence of
transitivity. Yet, quite remarkably, the completion and global semantics coincide as far as
categoricity is concerned.</p>
      <p>Theorem 4. Consider an inconsistent prioritizing database, where conflicts are given
by a conflict hypergraph and the priority relation is transitive. Then, there is a single
completion-optimal repair if and only if there is a single globally optimal repair.</p>
      <p>Combining Theorems 3 and 4, we get the following corollary that shows the major
impact of transitivity on global categoricity, when contrasted with Theorem 2.
Corollary 1. For transitive priority relations, global categoricity is decidable in
polynomial time, even in the general case where conflicts are given by a conflict hypergraph.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusions</title>
      <p>
        We introduced our recent results on the complexity of the categoricity problem in the
framework of preferred repairs [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], where the goal is to determine whether the
provided priority relation suffices to repair the database unambiguously. We did not address
any qualitative discrimination among the three notions of repairs. Rather, we continue
the line of work [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ] that explores the impact of the choice on the entailed
computational complexity. It has been established that, as far as repair checking is concerned,
the Pareto and the completion semantics behave way better than the global one [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In
this work we have shown that from the viewpoint of categoricity, the Pareto semantics
departs from the completion one by being likewise intractable (while the global
semantics hits an even higher complexity class); hence, the completion semantics outstands
so far as the most efficient option to adopt.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>F. N.</given-names>
            <surname>Afrati</surname>
          </string-name>
          and
          <string-name>
            <given-names>P. G.</given-names>
            <surname>Kolaitis</surname>
          </string-name>
          .
          <article-title>Repair checking in inconsistent databases: algorithms and complexity</article-title>
          .
          <source>In ICDT</source>
          , pages
          <fpage>31</fpage>
          -
          <lpage>41</lpage>
          . ACM,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>D. E.</given-names>
            <surname>Appelt</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Onyshkevych</surname>
          </string-name>
          .
          <article-title>The common pattern specification language</article-title>
          .
          <source>In TIPSTER Text Program: Phase III</source>
          , pages
          <fpage>23</fpage>
          -
          <lpage>30</lpage>
          . Association for Computational Linguistics,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>M.</given-names>
            <surname>Arenas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. E.</given-names>
            <surname>Bertossi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Chomicki</surname>
          </string-name>
          .
          <article-title>Consistent query answers in inconsistent databases</article-title>
          .
          <source>In PODS</source>
          , pages
          <fpage>68</fpage>
          -
          <lpage>79</lpage>
          . ACM,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>P.</given-names>
            <surname>Bohannon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Geerts</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Kementsietsidis</surname>
          </string-name>
          .
          <article-title>Conditional functional dependencies for data cleaning</article-title>
          .
          <source>In ICDE</source>
          , pages
          <fpage>746</fpage>
          -
          <lpage>755</lpage>
          . IEEE,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Y.</given-names>
            <surname>Cao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Fan</surname>
          </string-name>
          , and
          <string-name>
            <given-names>W.</given-names>
            <surname>Yu</surname>
          </string-name>
          .
          <article-title>Determining the relative accuracy of attributes</article-title>
          .
          <source>In SIGMOD</source>
          , pages
          <fpage>565</fpage>
          -
          <lpage>576</lpage>
          . ACM,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>L.</given-names>
            <surname>Chiticariu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Krishnamurthy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Raghavan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Reiss</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Vaithyanathan. SystemT</surname>
          </string-name>
          :
          <article-title>An algebraic approach to declarative information extraction</article-title>
          .
          <source>In ACL</source>
          , pages
          <fpage>128</fpage>
          -
          <lpage>137</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>J.</given-names>
            <surname>Chomicki</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Marcinkowski</surname>
          </string-name>
          .
          <article-title>Minimal-change integrity maintenance using tuple deletions</article-title>
          .
          <source>Inf. Comput.</source>
          ,
          <volume>197</volume>
          (
          <issue>1-2</issue>
          ):
          <fpage>90</fpage>
          -
          <lpage>121</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>R.</given-names>
            <surname>Fagin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kimelfeld</surname>
          </string-name>
          , and
          <string-name>
            <surname>P. G. Kolaitis.</surname>
          </string-name>
          <article-title>Dichotomies in the complexity of preferred repairs</article-title>
          .
          <source>In PODS</source>
          , pages
          <fpage>3</fpage>
          -
          <lpage>15</lpage>
          . ACM,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>R.</given-names>
            <surname>Fagin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kimelfeld</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Reiss</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Vansummeren</surname>
          </string-name>
          .
          <article-title>Cleaning inconsistencies in information extraction via prioritized repairs</article-title>
          .
          <source>In PODS</source>
          , pages
          <fpage>164</fpage>
          -
          <lpage>175</lpage>
          . ACM,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>R.</given-names>
            <surname>Fagin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kimelfeld</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Reiss</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Vansummeren</surname>
          </string-name>
          .
          <article-title>Document spanners: A formal approach to information extraction</article-title>
          .
          <source>J. ACM</source>
          ,
          <volume>62</volume>
          (
          <issue>2</issue>
          ):
          <fpage>12</fpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>W.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Geerts</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Wijsen</surname>
          </string-name>
          .
          <article-title>Determining the currency of data</article-title>
          .
          <source>ACM Trans. Database Syst</source>
          .,
          <volume>37</volume>
          (
          <issue>4</issue>
          ):
          <fpage>25</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>W.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>W.</given-names>
            <surname>Yu</surname>
          </string-name>
          .
          <article-title>Towards certain fixes with editing rules and master data</article-title>
          .
          <source>VLDB J</source>
          .,
          <volume>21</volume>
          (
          <issue>2</issue>
          ):
          <fpage>213</fpage>
          -
          <lpage>238</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. W. Fan, S. Ma,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>W.</given-names>
            <surname>Yu</surname>
          </string-name>
          .
          <article-title>Interaction between record matching and data repairing</article-title>
          .
          <source>J. Data and Information Quality</source>
          ,
          <volume>4</volume>
          (
          <issue>4</issue>
          ):
          <volume>16</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>16</lpage>
          :
          <fpage>38</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. T. Gaasterland,
          <string-name>
            <given-names>P.</given-names>
            <surname>Godfrey</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Minker</surname>
          </string-name>
          .
          <article-title>An overview of cooperative answering</article-title>
          .
          <source>J. Intell. Inf. Syst.</source>
          ,
          <volume>1</volume>
          (
          <issue>2</issue>
          ):
          <fpage>123</fpage>
          -
          <lpage>157</lpage>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>P.</given-names>
            <surname>Koutris</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Wijsen</surname>
          </string-name>
          .
          <article-title>The data complexity of consistent query answering for self-join-free conjunctive queries under primary key constraints</article-title>
          .
          <source>In PODS</source>
          , pages
          <fpage>17</fpage>
          -
          <lpage>29</lpage>
          . ACM,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>S.</given-names>
            <surname>Staworko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chomicki</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Marcinkowski</surname>
          </string-name>
          .
          <article-title>Preference-driven querying of inconsistent relational databases</article-title>
          .
          <source>In EDBT Workshops</source>
          , volume
          <volume>4254</volume>
          <source>of LNCS</source>
          , pages
          <fpage>318</fpage>
          -
          <lpage>335</lpage>
          . Springer,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>S.</given-names>
            <surname>Staworko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chomicki</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Marcinkowski</surname>
          </string-name>
          .
          <article-title>Prioritized repairing and consistent query answering in relational databases</article-title>
          . Ann. Math. Artif. Intell.,
          <volume>64</volume>
          (
          <issue>2-3</issue>
          ):
          <fpage>209</fpage>
          -
          <lpage>246</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>