Data-driven understanding and refinement of schema mappings
SIGMOD '01 Proceedings of the 2001 ACM SIGMOD international conference on Management of data
Clio grows up: from research prototype to industrial tool
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Nested mappings: schema mapping reloaded
VLDB '06 Proceedings of the 32nd international conference on Very large data bases
Debugging schema mappings with routes
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
Muse: Mapping Understanding and deSign by Example
ICDE '08 Proceedings of the 2008 IEEE 24th International Conference on Data Engineering
MVT: a schema mapping validation tool
Proceedings of the 12th International Conference on Extending Database Technology: Advances in Database Technology
A tool for mapping discovery over revealing schemas
Proceedings of the 12th International Conference on Extending Database Technology: Advances in Database Technology
DEMo: data exchange modeling tool
Proceedings of the VLDB Endowment
Generating SPARQL executable mappings to integrate ontologies
ER'11 Proceedings of the 30th international conference on Conceptual modeling
Efficient management of uncertainty in XML schema matching
The VLDB Journal — The International Journal on Very Large Data Bases
MostoDE: A tool to exchange data amongst semantic-web ontologies
Journal of Systems and Software
Hi-index | 0.00 |
Schema mappings are logical assertions that specify the relationships between a source and a target schema in a declarative way. The specification of such mappings is a fundamental problem in information integration. Mappings can be generated by existing mapping systems (semi-)automatically from a visual specification between two schemas. In general, the well-known 80-20 rule applies for mapping generation tools. They can automate 80% of the work, covering common cases and creating a mapping that is close to correct. However, ensuring complete correctness can still require intricate manual work to perfect portions of the mapping. Previous research on mapping understanding and refinement and anecdotal evidence from mapping designers suggest that the mapping design process can be perfected by using data examples to explain the mapping and alternative mappings. We demonstrate Muse, a data example driven mapping design tool currently implemented on top of the Clio schema mapping system. Muse leverages data examples that are familiar to a designer to illustrate nuances of how a small change to a mapping specification changes its semantics. We demonstrate how Muse can differentiate between alternative mapping specifications and infer the desired mapping semantics based on the designer's actions on a short sequence of simple data examples.