Author: buildbot
Date: Wed Jul 13 17:34:53 2016
New Revision: 992692
Log:
Staging update by buildbot for taverna
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
websites/staging/taverna/trunk/content/documentation/provenance/index.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 13 17:34:53 2016
@@ -1 +1 @@
-1752465
+1752466
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 13 17:34:53 2016
@@ -1 +1 @@
-1752465
+1752466
Modified:
websites/staging/taverna/trunk/content/documentation/provenance/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/provenance/index.html
(original)
+++ websites/staging/taverna/trunk/content/documentation/provenance/index.html
Wed Jul 13 17:34:53 2016
@@ -248,17 +248,23 @@ This provenance is kept in an internal d
provide “science-level provenance.” myGrid is planning a
capability for such data provenance
in different ways:</p>
<ol>
-<li>Merging and propagation of <a
href="http://www.w3.org/TR/prov-aq/";>PROV-AQ</a>-provided provenance
+<li>
+<p><strong>Merging and propagation</strong> of <a
href="http://www.w3.org/TR/prov-aq/";>PROV-AQ</a>-provided provenance
traces for <a
href="http://dev.mygrid.org.uk/wiki/display/taverna/REST";>REST services</a>
- (including matching data identity) -- âwhite-box serviceâ</li>
-<li>A provenance âbackchannelâ for <a
href="/documentation/components">Components</a>,
+ (including matching data identity) -- âwhite-box serviceâ</p>
+</li>
+<li>
+<p><strong>A provenance âbackchannelâ</strong> for <a
href="/documentation/components">Components</a>,
which can be populated either by the underlying service directly or by
shims within the
component.
This allows higher-level provenance that is meaningful for a set of
components instead of
- service-specific execution details.</li>
-<li>Annotation of workflow fragments by
+ service-specific execution details.</p>
+</li>
+<li>
+<p><strong>Annotation of workflow fragments</strong> by
<a
href="http://www.slideshare.net/dgarijo/common-motifs-in-scientific-workflows-an-empirical-analysis";>common
motifs</a>,
- which can provide higher-level provenance for data generated by the
workflow</li>
+ which can provide higher-level provenance for data generated by the
workflow</p>
+</li>
</ol>
<p>The paper <a
href="http://www.edbt.org/Proceedings/2013-Genova/papers/workshops/a45-alper.pdf";>Enhancing
and Abstracting Scientific Workflow Provenance for Data
Publishing</a>
@@ -287,20 +293,26 @@ The <a href="https://github.com/wf4ever/
a data model and software component for provenance capture and analysis for
Taverna.
Our research in this area is often pursued in collaboration with external
partners:</p>
<ul>
-<li><strong>Provenance capture.</strong> A model and architecture for
capturing provenance.
+<li>
+<p><strong>Provenance capture.</strong> A model and architecture for capturing
provenance.
We have designed a data model for <em>Janus</em> that is at the same time
specific to Taverna,
but can also be exported to other models,
notably the <a href="http://openprovenance.org/";>Open Provenance
Model</a> (OPM),
to enable interoperability with third party provenance-generating systems.
- Taverna has been retrofitted with provenance-generating capabilities.</li>
-<li><strong>Provenance processing</strong> An expressive provenance query
language and efficient query-processing model for large
- provenance graphs.</li>
-<li><strong>Provenance interoperability.</strong> Investigation into
provenance interoperability and exchange, using the OPM.
+ Taverna has been retrofitted with provenance-generating capabilities.</p>
+</li>
+<li>
+<p><strong>Provenance processing</strong> An expressive provenance query
language and efficient query-processing model for large
+ provenance graphs.</p>
+</li>
+<li>
+<p><strong>Provenance interoperability.</strong> Investigation into provenance
interoperability and exchange, using the OPM.
The Taverna provenance component now exports data as OPM graphs,
and can also import OPM graphs (with basic features) received from third
parties.
We have also been working with the Kepler group on a project to promote
provenance
interoperability, in collaboration with Prof. Ludaescher at UC Davis, CA,
and
- Ilkay Antintas at UCSD, CA.</li>
+ Ilkay Antintas at UCSD, CA.</p>
+</li>
<li><strong>Provenance modeling and management.</strong> Investigation into
the role of semantics and of Linked Open Data (LOD) in provenance
modelling and management, in collaboration with the Knoesis Centre at
Wright University,
Ohio (Prof. Amit Sheth, Dr. Satya Sahoo) and with Jun Zhao of Oxford
University.</li>
