2004
DOI: 10.1613/jair.1322
|View full text |Cite
|
Sign up to set email alerts
|

Coherent Integration of Databases by Abductive Logic Programming

Abstract: We introduce an abductive method for a coherent integration of independent data-sources. The idea is to compute a list of data-facts that should be inserted to the amalgamated database or retracted from it in order to restore its consistency. This method is implemented by an abductive solver, called Asystem, that applies SLDNFA-resolution on a meta-theory that relates different, possibly contradicting, input databases. We also give a pure model-theoretic analysis of the possible ways to `recover' consistent da… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
48
0

Year Published

2005
2005
2022
2022

Publication Types

Select...
5

Relationship

0
5

Authors

Journals

citations
Cited by 28 publications
(48 citation statements)
references
References 73 publications
0
48
0
Order By: Relevance
“…By this, only erroneous fragments of tuples are modified. 3 The condition that in every tuple at least one component belongs to HU(DB) is meant to exclude degenerated cases, in which a tuple consists of null values only. A potential repair R of DB is an update of D that preserves IC with respect to S (R |= S IC).…”
Section: Database Repair As a Distance Minimization Problemmentioning
confidence: 99%
See 1 more Smart Citation
“…By this, only erroneous fragments of tuples are modified. 3 The condition that in every tuple at least one component belongs to HU(DB) is meant to exclude degenerated cases, in which a tuple consists of null values only. A potential repair R of DB is an update of D that preserves IC with respect to S (R |= S IC).…”
Section: Database Repair As a Distance Minimization Problemmentioning
confidence: 99%
“…In the context of database systems, this notion was introduced by [1], and then considered by many others, including [2-4, 6, 7, 13, 22, 21, 29, 34]. Some implementations of these methods are reported in [3,18,19,28]. Despite their syntactic and semantic differences, as well as the different notions of repair used by different consistency maintenance formalisms, the rationality behind all these methods is of keeping the 'recovered' data 'as close as possible' to the original (inconsistent) data.…”
Section: Introductionmentioning
confidence: 99%
“…-Systems for data integration, in which the major concern is to resolve contradictions that may occur when the distributed data is amalgamated (see, e.g., [1][2][3][4][5]8]). …”
Section: Introductionmentioning
confidence: 99%
“…relate the different terminologies of the local databases and that of the global integrity constraints, 2. identify inconsistencies (i.e., violations of integrity constraints) and resolve them by making some (minimal amount of) changes in the unified database, 3. search for solutions that may lie outside the active domain of the databases (in order, e.g., to satisfy the second constraint above).…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation