A fuzzy model for calculating workflow trust using provenance data
Proceedings of the 15th ACM Mardi Gras conference: From lightweight mash-ups to lambda grids: Understanding the spectrum of distributed computing requirements, applications, tools, infrastructures, interoperability, and the incremental adoption of key capabilities
ATM: an automatic trust monitoring algorithm for service software
Proceedings of the 2009 ACM symposium on Applied Computing
The Foundations for Provenance on the Web
Foundations and Trends in Web Science
Towards design support for provenance awareness: a classification of provenance questions
Proceedings of the Joint EDBT/ICDT 2013 Workshops
An agent based network resource planner for workflow applications
Multiagent and Grid Systems - Agent Based Computing: From Model to Implementation
Hi-index | 0.00 |
Workflow forms a key part of many existing Service Oriented applications, involving the integration of services that may be made available at distributed sites. It is possible to distinguish between an "abstract" workflow description outlining which services must be involved in a workflow execution and a "physical" workflow description outlining the particular instances of services that were used in a particular enactment. Provenance information provides a useful way to capture the physical workflow description automatically especially if this information is captured in a standard format. Subsequent analysis on this provenance information may be used to evaluate whether the abstract workflow description has been adhered to, and to enable a user executing a workflow-based application to establish "trust" in the outcome.