svn commit: r992763 - in /websites/staging/taverna/trunk: cgi-bin/ content/ content/documentation/components/index.html

[buildbot]

Author: buildbot
Date: Thu Jul 14 00:23:26 2016
New Revision: 992763

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/components/index.html

Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 14 00:23:26 2016
@@ -1 +1 @@
-1752569
+1752572

Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 14 00:23:26 2016
@@ -1 +1 @@
-1752569
+1752572

Modified: 
websites/staging/taverna/trunk/content/documentation/components/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/components/index.html 
(original)
+++ websites/staging/taverna/trunk/content/documentation/components/index.html 
Thu Jul 14 00:23:26 2016
@@ -194,20 +194,40 @@ Instead it shows <a class="alert-link" h
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="toc">
+<ul>
+<li><a href="#overview">Overview</a></li>
+<li><a href="#requirements">Requirements</a></li>
+<li><a href="#workflows">Workflows</a><ul>
+<li><a href="#example-workflow-with-components">Example workflow with 
components</a></li>
+</ul>
+</li>
+<li><a href="#including-a-component-in-a-workflow">Including a component in a 
workflow</a></li>
+<li><a href="#executing-a-component-in-a-workflow-run">Executing a component 
in a workflow run</a></li>
+<li><a href="#components">Components</a><ul>
+<li><a href="#component-creation">Component creation</a></li>
+</ul>
+</li>
+<li><a href="#component-profile">Component profile</a></li>
+<li><a href="#component-creation-against-a-profile">Component creation against 
a profile</a></li>
+<li><a href="#checking-a-component-against-a-profile">Checking a component 
against a profile</a></li>
+<li><a href="#publishing-a-component">Publishing a component</a></li>
+<li><a href="#discovering-a-component">Discovering a component</a></li>
+</ul>
+</div>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" 
title="Permanent link">&para;</a></h2>
 <p>Taverna Workflow Components are a system for creating shareable, reusable, 
-   encapsulated sub-workflows that perform clearly defined tasks while 
abstracting away from 
+   encapsulated sub-workflows that perform clearly defined tasks while 
abstracting
    the details of how those tasks are performed. 
-They are an integrated feature of Taverna Since Workbench 2.5.0 and Server 
2.5.4.</p>
-<p>As part of the BioVeL and SCAPE projects, 
-  we have developed a system of service components for Taverna. 
-This consists of tools for the creation, management and use of workflow 
components, 
-   and a repository for the storage and sharing of those components. 
+They are an integrated feature of Taverna since Workbench 2.5.0 and Server 
2.5.4.</p>
+<p>Taverna's system of service components was developed as part of the BioVeL 
and SCAPE projects. They consist of tools for the creation, management and use 
of workflow components, 
+   along with a repository for the storage and sharing of those components. 
 Workflow components within a given component family will work together 
cleanly, 
-   for example by adhering to a tidy type system and being well described.</p>
-<p>A set of minimal functional requirements for service component management 
has been developed 
-   based upon previous component-related work carried out as part of the 
e-Lico project and 
-   also an examination of the needs of BioVeL and SCAPE.</p>
-<p>These requirements include:</p>
+   for example, by adhering to a tidy type system and being well described.</p>
+<h2 id="requirements">Requirements<a class="headerlink" href="#requirements" 
title="Permanent link">&para;</a></h2>
+<p>A set of minimal functional requirements for service component management 
has been developed. These requirements are 
+   based upon previous component-related work carried out as part of the 
e-Lico project as well as an examination of the needs of BioVeL and SCAPE.</p>
+<p>The requirements include:</p>
 <ul>
 <li>The ability to create components</li>
 <li>The specification of the characteristics that are necessary for a set of 
components to 
@@ -221,31 +241,35 @@ Workflow components within a given compo
 </ul>
 <p><img class="aligncenter" title="The Model of Components" 
src="/img/registry.png" alt="" 
      width="433" height="251" /></p>
-<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent 
link">&para;</a></h2>
+<h2 id="workflows">Workflows<a class="headerlink" href="#workflows" 
title="Permanent link">&para;</a></h2>
+<h3 id="example-workflow-with-components">Example workflow with components<a 
class="headerlink" href="#example-workflow-with-components" title="Permanent 
link">&para;</a></h3>
 <p>This is an example workflow that includes components, with internal ports 
hidden for simplicity:</p>
 <p><img class="alignnone" title="Componentized Workflow" 
src="/img/component_b_1.png" alt="" 
      width="679" height="294" /></p>
 <p>Without components, using the same view, it would instead look like 
this:</p>
 <p><a 
href="http://www.taverna.org.uk/pages/wp-content/uploads/2013/05/component_c.png";><img
 class="aligncenter" title="Un-componentized Workflow" 
src="/img/component_c.png" alt="" width="245" height="526" /></a></p>
 <h2 id="including-a-component-in-a-workflow">Including a component in a 
workflow<a class="headerlink" href="#including-a-component-in-a-workflow" 
title="Permanent link">&para;</a></h2>
-<p>A component can be added into a Taverna workflow in the same way as an 
ordinary service, 
+<p>A component can be added into a Taverna workflow in the same way as an 
ordinary service: 
    by dragging it from the service panel of the workbench into the workflow 
design view. 
-   Note that although it may be realized internally as a workflow, 
-   a user sees it as a ‘black box’ and cannot (normally) edit the 
component’s workflow.</p>
+   <em>Although it may be realized internally as a workflow, 
+   a user sees it as a ‘black box’ and cannot (normally) edit the 
component’s workflow.</em></p>
 <p><img class="aligncenter" src="/img/arch3.png" alt="" width="500" 
height="401" /></p>
-<p>It is intended that there will be consistency checks to ensure that 
components are only plugged 
-   together in a sensible manner, and for the discovery of and connection to 
suitable components 
+<p>It is intended that there will be consistency checks to ensure components 
are only plugged 
+   together in a sensible manner, and for the discovery of (and connection to) 
suitable components 
    based upon existing workflow structure.</p>
 <h2 id="executing-a-component-in-a-workflow-run">Executing a component in a 
workflow run<a class="headerlink" 
href="#executing-a-component-in-a-workflow-run" title="Permanent 
link">&para;</a></h2>
 <p>When a component is invoked during a workflow run, the underlying workflow 
is called with the 
    corresponding data. 
 The results of the workflow are used as the output data for the component 
invocation. 
-Note that the user sees the component invocation as a ‘black box’ and 
cannot see details of 
-   what happens inside.</p>
-<p>Note that if you publish a workflow containing a component, you 
<em>need</em> to make sure that the 
+<em>The user sees the component invocation as a ‘black box’ and cannot see 
details of 
+   what happens inside.</em></p>
+<blockquote>
+<p>If you publish a workflow containing a component, you <em>must</em> make 
sure the 
    component is publicly readable in a globally-accessible component registry; 
    myExperiment is such a suitable registry.</p>
-<h2 id="component-creation">Component creation<a class="headerlink" 
href="#component-creation" title="Permanent link">&para;</a></h2>
+</blockquote>
+<h2 id="components">Components<a class="headerlink" href="#components" 
title="Permanent link">&para;</a></h2>
+<h3 id="component-creation">Component creation<a class="headerlink" 
href="#component-creation" title="Permanent link">&para;</a></h3>
 <p>It was decided that the majority of the information necessary for a 
component will be specified 
    as a Taverna workflow. 
 This allows complex internal component functionality and removes the need for 
extensive new