International audiencePROV has been adopted by a number of workflow systems for encoding the traces of workflow executions. Exploiting these prove-nance traces is hampered by two main impediments. Firstly, workflow systems extend PROV differently to cater for system-specific constructs. The difference between the adopted PROV extensions yields heterogene-ity in the generated provenance traces. This heterogeneity diminishes the value of such traces, e.g. when combining and querying provenance traces of different workflow systems. Secondly, the provenance recorded by workflow systems tends to be large, and as such difficult to browse and understand by a human user. In this paper 4 , we propose SHARP, a Linked Data approach for harmonizing cro...
Provenance generated by different workflow systems is generally expressed using different formats. T...
Background The automation of data analysis in the form of scientific workflows has become a widely ...
Workflow provenance typically assumes that each module is a “black-box”, so that each output depends...
International audiencePROV has been adopted by a number of workflow systems for encoding the traces ...
International audienceSHARP is a Linked Data approach for harmonizing cross-workflow provenance. In ...
International audienceSHARP is a Linked Data approach for harmonizing cross-workflow provenance. In ...
Scientific workflow management systems are increaingly providing the ability to manage and query the...
Scientific workflow management systems are increaingly providing the ability to manage and query the...
Provenance traces captured by scientific workflows can be useful for designing, debugging and mainte...
Journal ArticleThe automated tracking and storage of provenance information promises to be a major a...
Several workflow management systems and scripting languages have adopted provenance tracking, yet ma...
Workflow provenance typically assumes that each module is a “black-box”, so that each output depends...
Abstract—Scientific collaboration increasingly involves data sharing between separate groups. We con...
Workflow-level provenance declarations can improve the precision of coarse provenance traces by redu...
Scientific workflows are commonly used to model and execute large-scale scientific experiments. They...
Provenance generated by different workflow systems is generally expressed using different formats. T...
Background The automation of data analysis in the form of scientific workflows has become a widely ...
Workflow provenance typically assumes that each module is a “black-box”, so that each output depends...
International audiencePROV has been adopted by a number of workflow systems for encoding the traces ...
International audienceSHARP is a Linked Data approach for harmonizing cross-workflow provenance. In ...
International audienceSHARP is a Linked Data approach for harmonizing cross-workflow provenance. In ...
Scientific workflow management systems are increaingly providing the ability to manage and query the...
Scientific workflow management systems are increaingly providing the ability to manage and query the...
Provenance traces captured by scientific workflows can be useful for designing, debugging and mainte...
Journal ArticleThe automated tracking and storage of provenance information promises to be a major a...
Several workflow management systems and scripting languages have adopted provenance tracking, yet ma...
Workflow provenance typically assumes that each module is a “black-box”, so that each output depends...
Abstract—Scientific collaboration increasingly involves data sharing between separate groups. We con...
Workflow-level provenance declarations can improve the precision of coarse provenance traces by redu...
Scientific workflows are commonly used to model and execute large-scale scientific experiments. They...
Provenance generated by different workflow systems is generally expressed using different formats. T...
Background The automation of data analysis in the form of scientific workflows has become a widely ...
Workflow provenance typically assumes that each module is a “black-box”, so that each output depends...