You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by bu...@apache.org on 2016/01/06 23:46:46 UTC
svn commit: r977195 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/documentation/scufl2/bundle.html
Author: buildbot
Date: Wed Jan 6 22:46:45 2016
New Revision: 977195
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/scufl2/bundle.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 6 22:46:45 2016
@@ -1 +1 @@
-1723420
+1723430
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 6 22:46:45 2016
@@ -1 +1 @@
-1723420
+1723430
Modified: websites/staging/taverna/trunk/content/documentation/scufl2/bundle.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/scufl2/bundle.html (original)
+++ websites/staging/taverna/trunk/content/documentation/scufl2/bundle.html Wed Jan 6 22:46:45 2016
@@ -245,7 +245,7 @@ This specification requires that one of
<li><strong>Must</strong> set the bundle <strong>mimetype</strong> to <code>application/vnd.taverna.scufl2.workflow-bundle</code>.</li>
<li><strong>Must</strong> add a workflow bundle document in <code>application/rdf+xml</code> format.</li>
<li><strong>Should</strong> store the workflow bundle document in <code>/workflowBundle.rdf</code>.</li>
-<li><strong>Must not</strong> contain a resource <code>/workflowBundle.rdf</code> that is not the workflow bundle document.</li>
+<li><strong>Must not</strong> contain a resource called <code>/workflowBundle.rdf</code> that is not the workflow bundle document.</li>
<li><strong>May</strong> add additional representation of the workflow bundle document (and other documents).
Alternates of the workflow bundle document <strong>should</strong> be included in the <code>META-INF/container.xml</code>,
but only if they can be considered to fully specify the workflow bundle as in the RDF/XML format.
@@ -268,12 +268,12 @@ In this case, the bundle is not consider
<li><strong>Should</strong> store the workflow bundle document in <code>/workflowBundle.rdf</code>,
unless the workflow bundle is not to be considered to have a 'main' or 'prominent' role within the archive.
(For instance, if the archive is a collection of workflow bundles.)</li>
-<li><strong>Should</strong> have a <code>mimetype</code> and <code>META-INF/container.xml</code> resource which declares the archive's main entry point,
+<li><strong>Should</strong> have a <code>mimetype</code> and <code>META-INF/container.xml</code> resource that declares the archive's main entry point,
like the data bundle document.
The mime type <strong>must not</strong> be <code>application/vnd.taverna.scufl2.workflow-bundle</code>, and
the root files <strong>should not</strong> be the workflow bundle document.</li>
<li><strong>Should</strong> link to the workflow bundle document from a resource within the archive, which (ultimately)
- is linked to from one of the <code>rootfile</code> documents.
+ is linked-to from one of the <code>rootfile</code> documents.
Such documents <strong>should</strong> be in RDF/XML format.</li>
<li><strong>Should</strong> declare the media type of the RDF/XML workflow bundle document as <code>application/rdf+xml</code>
in its <code>META-INF/manifest.xml</code></li>
@@ -285,7 +285,7 @@ In this case, the bundle is not consider
<li><strong>Should</strong> assume that if the archive's <code>mimetype</code> is <code>application/vnd.taverna.scufl2.workflow-bundle</code>,
then the <code>rootfile</code> in <code>META-INF/container.xml</code> with the media type {{application/rdf+xml})
is the root workflow bundle document.</li>
-<li><strong>May</strong> assume that any alternate formats listed as a <code>rootfile</code> in a <code>application/vnd.taverna.scufl2.workflow-bundle</code>
+<li><strong>May</strong> assume that any alternate formats listed as a <code>rootfile</code> in an <code>application/vnd.taverna.scufl2.workflow-bundle</code>
archive would fully cover the specification of the RDF/XML representation, and read such formats instead.</li>
<li><strong>May</strong> assume that any <code>application/rdf+xml</code> document with a <code>xsi:type="WorkflowBundleDocument"</code>
can be parsed according to the Scufl2 XML schema.</li>
@@ -296,10 +296,8 @@ In this case, the bundle is not consider
the workflow bundle <strong>must</strong> be identified as the root of the archive.
If the Workflow Bundle document is in <code>workflowBundle.rdf</code> within the archive, the workflow identifier is <code>./</code>.
This <strong>should</strong> be achieved by setting <code>xml:base="./"</code> and <code>rdf:about=""</code>.</p>
-<p>One can mint a URI to refer to resources within the bundle archive, including the workflow bundle,
- workflows and representations.
- If <code>http://example.com/myWfBundle.scufl2</code> returns a <a href="/documentation/scufl2/taverna_bundle">Scufl2 workflow bundle</a>
- archive of the content type <code>application/vnd.taverna.scufl2.workflow-bundle</code>,<br />
+<p>One can mint a URI to refer to resources within the bundle archive, including the workflow bundle, workflows and representations.
+ If <code>http://example.com/myWfBundle.scufl2</code> returns a <a href="/documentation/scufl2/taverna_bundle">Scufl2 workflow bundle</a> archive of the content type <code>application/vnd.taverna.scufl2.workflow-bundle</code>,<br />
then (assuming default structure of the archive):</p>
<ul>
<li><code>http://example.com/myWfBundle.scufl2</code> identifies the Workflow Bundle representation (the <em>archive</em>).</li>
@@ -420,15 +418,14 @@ Two execution profiles are provided, and
Each workflow must have an <strong>rdfs:seeAlso</strong> link to the bundle resource that defines the workflow,
typically <code>workflow/workflowName.rdf</code> corresponding to the non-information resource <code>workflow/workflowName/</code>.</li>
<li><strong>mainWorkflow</strong> (optional) refers to the top-level <a href="/documentation/scufl2/workflow">workflow</a> of this bundle.
- It is valid to have a workflow bundle without a main workflow,
- for instance if the bundled workflows are unconnected "workflow fragments."
+ Workflow bundles without a main workflow can be valid if, for instance, the bundled workflows are unconnected "workflow fragments."
If there is a <strong>mainProfile</strong>, the workflow bundle must also have a <strong>mainWorkflow</strong>.
The main workflow must always be listed under <strong>workflow</strong>.</li>
<li><strong>profile</strong> (optional) describes the <a href="/wiki/display/developer/Scufl2-Profile">profiles</a> that specify
how to <strong>execute</strong> the bundled workflows. In particular, the profile provides a set of configured
activities bound to the processors for a particular run environment. If no profiles are specified, this is an
abstract workflow bundle.</li>
-<li><strong>mainProfile</strong> (optional) is the suggested <strong>main profile</strong>. Execution platforms unable to choose
+<li><strong>mainProfile</strong> (optional) specifies the suggested <strong>main profile</strong>. Execution platforms unable to choose
between the provided profiles can select this profile as a default. It is valid to have a workflow bundle
without a main profile (even if it has other profiles), but any main profile must also be listed under
<strong>profile</strong>.</li>