EXPRESS: a data EXtraction, Processing, and Restructuring System
ACM Transactions on Database Systems (TODS)
The description logic handbook: theory, implementation, and applications
The description logic handbook: theory, implementation, and applications
Data exchange: getting to the core
ACM Transactions on Database Systems (TODS) - Special Issue: SIGMOD/PODS 2003
Clio grows up: from research prototype to industrial tool
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Data exchange: semantics and query answering
Theoretical Computer Science - Database theory
Data exchange: computing cores in polynomial time
Proceedings of the twenty-fifth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
ACM SIGMOD Record
Tractable Reasoning and Efficient Query Answering in Description Logics: The DL-Lite Family
Journal of Automated Reasoning
Logical foundations of relational data exchange
ACM SIGMOD Record
IJCAI'05 Proceedings of the 19th international joint conference on Artificial intelligence
A tableaux decision procedure for SHOIQ
IJCAI'05 Proceedings of the 19th international joint conference on Artificial intelligence
The DL-lite family and relations
Journal of Artificial Intelligence Research
Data exchange and schema mappings in open and closed worlds
Journal of Computer and System Sciences
Data exchange beyond complete data
Proceedings of the thirtieth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Ontology alignment evaluation initiative: six years of experience
Journal on data semantics XV
| Hi-index | 0.00 |
Data exchange is a field of database theory that deals with transferring data between differently structured databases, with motivation coming from industry [21,17]. The starting point of intensive investigation of the problem of data exchange was given in [14] where it was defined as, given data structured under a source schema and a mapping specifying how it should be translated to a target schema, to transform the source data into data structured under the target schema such that it accurately reflects the source data w.r.t. the mapping. This problem has been studied for different combinations of languages used to specify the source and target schema, and the mappings [8]. Most of the results in the literature consider tuple generating dependencies (tgds) as the language to specify mappings. Tgds allow one to express containment of conjunctive queries, and have been widely employed in other areas of database theory. Furthermore, once a target instance is materialized, one mightwant to perform query answering over it.