[ Call for Papers
[ Submission
| Publication
| Important Dates
| Organization Committee
| Program Committee
| CFP
| Pre-proceedings
]
| 08:50 am--09:00 am | Welcome |
| 09:00 am--10:00 am | Keynote talk by Maurizio Lenzerini |
| 10:00 am--10:30 am | Coffee break |
| 10:30 am--12:00 am | Regular paper session (papers A, B, and C) |
| 12:00 am--01:30 pm | Lunch |
| 01:30 pm--02:30 pm | Regular paper session (papers D and E) |
| 02:30 pm--03:00 pm | Position paper session (papers 1 and 2) |
| 03:00 pm--03:30 pm | Coffee break |
| 03:30 pm--04:45 pm | Position paper session (papers 3 to 7) |
| 04:45 pm--05:00 pm | General discussion |
Database textbooks generally explain that integrity constraints should be satisfied at all times because they capture the set of all legal databases. Nevertheless, data inconsistency is a phenomenon that often occurs in practice. The most common reason for inconsistency is the need to integrate distributed, independent data sources: different databases that are consistent by themselves can contain conflicting tuples. The conflicts are revealed only when the tuples are brought together in an integrated database. In such situations, it is of practical importance to know how to deal with violations of integrity constraints. In general, there is no single best way to restore consistency, leaving us with a multitude of possible repairs. Even when we do not know the right repair, we can still try to prevent query answers from containing incorrect tuples. This idea is known as consistent query answering (CQA).
A similar concept arises in the context of incomplete databases: when an incompletely specified database can be completed in more than one way, we may want to restrict query answers to contain only the tuples that are in the query answer in each possible completion. Incomplete databases can arise, for example, when the data exchange rules between a source and a target database only partially determine the target. Also, an incomplete database may play a role similar to a set of repairs, representing different ways of solving existing data conflicts.
Another related area is that of uncertainty handling, where numeric probability factors are associated with data. Such data represent observations and arise in sensor networks or distributed databases. For example, the position of a moving object can only be ascertained with some degree of probability.
Recently, there has been a surge of interest in the areas of inconsistent, incomplete, and probabilistic databases, partly driven by the demands of data integration and sensor database applications. The goal of this EDBT Workshop is to bring together database researchers working on inconsistency, incompleteness, and uncertainty to review recent progress and outline future research directions. The focus of the workshop will be primarily on semantic and computational issues arising in the representation and querying of inconsistent, incomplete, and uncertain databases.
Topics of interest include, but are not limited to:
Paper submissions must be in electronic form using Portable Document Format (.pdf). Papers should be formatted according to the Springer-Verlag LaTeX2e style llncs for Lecture Notes in Computer Science, which is available at http://www.springer.de/comp/lncs/authors.html. The length should not exceed 15 pages.
The submissions will be judged for scientific quality and relevance. At least one author of each accepted paper must attend the workshop to present the work.
Authors shall submit their papers electronically through the submission page for IIDB 2006.
All accepted papers will be included in the informal proceedings to be distributed at the workshop. Papers may be accepted for full presentation at the workshop and publication in the proceedings, or for a short/poster presentation and publication of a 3-page abstract.
As with the previous edition of EDBT, post-proceedings of EDBT workshops will be published by Springer-Verlag in the series Lecture Notes in Computer Science. Regular papers (full presentation) will be considered for inclusion in the formal proceedings.
| Paper Submission Deadline: | December 22, 2005 |
| Notification of Acceptance: | January 25, 2006 |
| Camera Ready Copy Due: | February 22, 2006 |
| Workshop: | March 26, 2006 |