Provenance Integration Requires Reconciliation
MetadataShow full item record
CitationAngelino, Elaine, Uri Braun, David A. Holland, Peter Macko, Daniel Margo, and Margo Seltzer. Forthcoming. Provenance integration requires reconciliation. In Proceedings of the Third Workshop on the Theory and Practice of Provenance (TaPP 2011), Heraklion Greece, June 2011.
AbstractWhile there has been a great deal of research on provenance systems, there has been little discussion about challenges that arise when making different provenance systems interoperate. In fact, most of the literature focuses on provenance systems in isolation and does not discuss interoperability – what it means, its requirements, and how to achieve it. We designed the Provenance-Aware Storage System to be a general- purpose substrate on top of which it would be “easy” to add other provenance-aware systems in a way that would provide “seamless integration” for the provenance captured at each level. While the system did exactly what we wanted on toy problems, when we began integrating StarFlow, a Python-based workflow/provenance system, we discovered that integration is far trickier and more subtle than anyone has suggested in the literature. This work describes our experience undertaking the integration of StarFlow and PASS, identifying several important additions to existing provenance models necessary for interoperability among provenance systems.
Citable link to this pagehttp://nrs.harvard.edu/urn-3:HUL.InstRepos:5168853
- FAS Scholarly Articles