A survey of approaches to automatic schema matching
The VLDB Journal — The International Journal on Very Large Data Bases
Representing and reasoning about mappings between domain models
Eighteenth national conference on Artificial intelligence
Checking query containment with the CQC method
Data & Knowledge Engineering
Debugging schema mappings with routes
VLDB '06 Proceedings of the 32nd international conference on Very large data bases
SPIDER: a schema mapPIng DEbuggeR
VLDB '06 Proceedings of the 32nd international conference on Very large data bases
VLDB '02 Proceedings of the 28th international conference on Very Large Data Bases
SVT: schema validation tool for microsoft SQL-server
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
Computing explanations for unlively queries in databases
Proceedings of the sixteenth ACM conference on Conference on information and knowledge management
Muse: a system for understanding and designing mappings
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
The Spicy system: towards a notion of mapping quality
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
Information integration in the enterprise
Communications of the ACM - Enterprise information integration: and other tools for merging data
Validation of mappings between schemas
Data & Knowledge Engineering
| Hi-index | 0.00 |
Schema mappings define relationships between schemas in a declarative way. We demonstrate MVT, a mapping validation tool that allows the designer to ask whether the mapping has certain desirable properties. The answers to these questions will provide information on whether the mapping adequately matches the intended needs and requirements. MVT is able to deal with a highly expressive class of mappings and database schemas, which allows the use of negations, order comparisons and null values. The tool does not only provide a Boolean answer as test result, but also a feedback for that result. Depending on the tested property and on the test result, the provided feedback can be in the form of example schema instances, or in the form of an explanation, that is, highlighting the mapping assertions and schema constraints responsible for getting such a result.