svn commit: r1752466 - /incubator/taverna/site/trunk/content/documentation/provenance/index.md

[gn...@apache.org]

Author: gnaylor
Date: Wed Jul 13 17:34:46 2016
New Revision: 1752466

URL: http://svn.apache.org/viewvc?rev=1752466&view=rev
Log:
Edit, minor

Modified:
    incubator/taverna/site/trunk/content/documentation/provenance/index.md

Modified: incubator/taverna/site/trunk/content/documentation/provenance/index.md
URL: http://svn.apache.org/viewvc/incubator/taverna/site/trunk/content/documentation/provenance/index.md?rev=1752466&r1=1752465&r2=1752466&view=diff
==============================================================================
--- incubator/taverna/site/trunk/content/documentation/provenance/index.md (original)
+++ incubator/taverna/site/trunk/content/documentation/provenance/index.md Wed Jul 13 17:34:46 2016
@@ -80,15 +80,17 @@ Taverna workflows typically use local to
 provide “science-level provenance.” myGrid is planning a capability for such data provenance 
 in different ways:
 
-1. Merging and propagation of [PROV-AQ](http://www.w3.org/TR/prov-aq/)-provided provenance
+1. **Merging and propagation** of [PROV-AQ](http://www.w3.org/TR/prov-aq/)-provided provenance
      traces for [REST services](http://dev.mygrid.org.uk/wiki/display/taverna/REST)
      (including matching data identity) -- “white-box service”
-2. A provenance “backchannel” for [Components](/documentation/components),
+
+2. **A provenance “backchannel”** for [Components](/documentation/components),
      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.
-3. Annotation of workflow fragments by
+
+3. **Annotation of workflow fragments** by
      [common motifs](http://www.slideshare.net/dgarijo/common-motifs-in-scientific-workflows-an-empirical-analysis),
      which can provide higher-level provenance for data generated by the workflow
 
@@ -131,8 +133,10 @@ Our research in this area is often pursu
      notably the [Open Provenance Model](http://openprovenance.org/) (OPM),
      to enable interoperability with third party provenance-generating systems.
    Taverna has been retrofitted with provenance-generating capabilities.
+
  - **Provenance processing** An expressive provenance query language and efficient query-processing model for large
      provenance graphs.
+
  - **Provenance interoperability.** 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.