You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by br...@apache.org on 2015/03/02 17:25:35 UTC

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

Author: brenninc
Date: Mon Mar  2 16:25:35 2015
New Revision: 1663345

URL: http://svn.apache.org/r1663345
Log:
fixed link

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=1663345&r1=1663344&r2=1663345&view=diff
==============================================================================
--- incubator/taverna/site/trunk/content/documentation/provenance/index.md (original)
+++ incubator/taverna/site/trunk/content/documentation/provenance/index.md Mon Mar  2 16:25:35 2015
@@ -81,7 +81,7 @@ The typical world of Taverna workflows i
 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](developers/work-in-progress/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