Provenance and scientific workflows: challenges and opportunities
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
A model of process documentation to determine provenance in mash-ups
ACM Transactions on Internet Technology (TOIT)
Tracking Files in the Kepler Provenance Framework
SSDBM 2009 Proceedings of the 21st International Conference on Scientific and Statistical Database Management
Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications
Document provenance in the cloud: constraints and challenges
EUNICE'10 Proceedings of the 16th EUNICE/IFIP WG 6.6 conference on Networked services and applications: engineering, control and management
The Foundations for Provenance on the Web
Foundations and Trends in Web Science
A provenance-based compliance framework
FIS'10 Proceedings of the Third future internet conference on Future internet
Future Generation Computer Systems
PrIMe: A methodology for developing provenance-aware applications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Supporting secure provenance update by keeping "provenance" of the provenance
ICT-EurAsia'13 Proceedings of the 2013 international conference on Information and Communication Technology
Hi-index | 0.00 |
The open provenance architecture approach to the challenge was distinct in several regards. In particular, it allows different components of the challenge workflow to independently record documentation, and for the workflow to be executed in different environments, made possible by an open, well-defined data model and architecture. Another noticeable feature is that we distinguish between the data recorded about what has occurred, process documentation, and the provenance of a data item, which is all that caused the data item to be as it is. In this view, provenance is obtained as the result of a query over process documentation. This distinction allows us to tailor the system to best address the separate requirements of recording and querying documentation. Other notable features include the explicit recording of causal relationships between both events and data items, an interaction-based world model, intensional definition of data items in queries rather than relying on explicit naming mechanisms, and styling of documentation to support non-functional application requirements such as reducing storage costs or ensuring privacy of data. In this paper, we describe how each of these features aid us in answering the challenge's provenance queries. Copyright © 2007 John Wiley & Sons, Ltd.