TY - JOUR
T1 - Extracting causal graphs from an open provenance data model
AU - Miles, Simon
AU - Groth, Paul
AU - Munroe, Steve
AU - Jiang, Sheng
AU - Assandri, Thibaut
AU - Moreau, Luc
PY - 2008/4/10
Y1 - 2008/4/10
N2 - 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.
AB - 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.
KW - Causation
KW - Provenance
KW - Service-oriented architectures
KW - e-science
UR - http://www.scopus.com/inward/record.url?scp=41149175552&partnerID=8YFLogxK
U2 - 10.1002/cpe.1236
DO - 10.1002/cpe.1236
M3 - Artículo
AN - SCOPUS:41149175552
SN - 1532-0626
VL - 20
SP - 577
EP - 586
JO - Concurrency and Computation: Practice and Experience
JF - Concurrency and Computation: Practice and Experience
IS - 5
ER -