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 22:58:14 UTC
svn commit: r977181 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/documentation/scufl2/bundle.html
Author: buildbot
Date: Wed Jan 6 21:58:14 2016
New Revision: 977181
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 21:58:14 2016
@@ -1 +1 @@
-1723383
+1723417
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 6 21:58:14 2016
@@ -1 +1 @@
-1723383
+1723417
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 21:58:14 2016
@@ -217,10 +217,10 @@ h2:hover > .headerlink, h3:hover > .head
<p>Defines the <em>workflows</em> and <em>profiles</em> of a
<a href="/documentation/scufl2/taverna_bundle">Taverna Workflow Bundle</a>.
The <em>main workflow</em> is also normally defined, which would be the top-level workflow to execute.
-The profiles defines how these workflows can be realised and <em>executed</em> on different environments,
+The profiles define how these workflows can be realised and <em>executed</em> on different environments,
one of which can be suggested as the <em>main profile</em>.</p>
<h2 id="bundle-path-and-root-files">Bundle path and root files<a class="headerlink" href="#bundle-path-and-root-files" title="Permanent link">¶</a></h2>
-<p>The <strong>workflow bundle document</strong> in RDF/XML format <strong>should</strong> be in in <code>/workflowBundle.rdf</code> within the bundle archive.</p>
+<p>The <strong>workflow bundle document</strong> in RDF/XML format <strong>should</strong> be in <code>/workflowBundle.rdf</code> within the bundle archive.</p>
<p>If the archive is a <a href="/documentation/scufl2/taverna_bundle">workflow bundle</a>,
i.e. <code>/mimetype</code> is <code>application/vnd.taverna.scufl2.workflow-bundle</code>,
then the <code>META-INF/container.xml</code> can define <strong>root files</strong> at alternative paths and media types.
@@ -239,44 +239,46 @@ This specification requires that one of
</pre></div>
-<p>This defines the RDF/XML root file to be <code>/workflowBundle.rdf</code> -
- with <code>workflowBundle.ttl</code> being an alternate representation the resource in Turtle format.</p>
+<p>The code above defines the RDF/XML root file to be <code>/workflowBundle.rdf</code>, with <code>workflowBundle.ttl</code> being an alternate representation of the resource in Turtle format.</p>
<p>SCUFL2-compliant workflow bundle writers:</p>
<ul>
-<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> which is not the workflow bundle document</li>
+<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> which 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.
+ (So for instance, a <code>text/html</code> or <code>image/png</code> representation would not normally be considered a
+ <strong>rootfile</strong> if it does not include all the structural information from the RDF/XML representation
+ as specified here.)</li>
+</ul>
+<p>SCUFL2-compliant workflow bundle writers have additional constraints.</p>
+<ul>
<li>If the <code>application/rdf+xml</code> representation is not in <code>/workflowBundle.rdf</code>,
the writer <strong>must</strong> include <code>META-INF/container.xml</code> with the required <code><rootfile></code> entries.</li>
<li><code>META-INF/container.xml</code>, if present, <strong>must</strong> contain one and only one <code>rootfile</code> with the media-type
- <code>application/rdf+xml</code>.
- rootfiles of other media-types <strong>may</strong> be included, but their formats and restrictions are not defined by this specification.</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.
- (So for instance a <code>text/html</code> or <code>image/png</code> representation would not normally be considered a
- <strong>rootfile</strong> if it does not include all the structural information from the RDF/XML representation as specified here)</li>
+ <code>application/rdf+xml</code>. Rootfiles of other media-types <strong>may</strong> be included, but their formats and restrictions are not defined by this specification.</li>
</ul>
<p>It is possible to include a workflow bundle document within a different kind of archive or bundle,
for instance in a data bundle.
-In this case the bundle is not considered an <code>application/vnd.taverna.scufl2.workflow-bundle</code> -
- but producers of such archives:</p>
+In this case, the bundle is not considered an <code>application/vnd.taverna.scufl2.workflow-bundle</code>.</p>
+<p>Producers of these different kinds of archives:</p>
<ul>
<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>
+ (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,
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>
-<li><strong>Should</strong> link to the workflow bundle document from a resource within the archive which (ultimately)
+ 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.
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>
</ul>
-<p>SCUFL2 compliant workflow bundle readers:</p>
+<p>SCUFL2-compliant workflow bundle readers:</p>
<ul>
<li><strong>Should</strong> assume that <code>/workflowBundle.rdf</code> - if present -
is the root workflow bundle in the <code>application/rdf+xml</code> format specified here.</li>
@@ -286,50 +288,50 @@ In this case the bundle is not considere
<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>
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>
+ can be parsed according to the Scufl2 XML schema.</li>
</ul>
<h2 id="identifiers">Identifiers<a class="headerlink" href="#identifiers" title="Permanent link">¶</a></h2>
<p>Workflow bundles and their resources <strong>must</strong> be declared with relative identifiers within the archive.
-In a <code>application/vnd.taverna.scufl2.workflow-bundle</code> archive,
- 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>.<br />
-This <strong>should</strong> be achieved by setting <code>xml:base="./"</code> and <code>rdf:about=""</code>.</p>
-<p>This means that one can mint a URI to refer to resources within the bundle archive, including the workflow bundle,
+ In an <code>application/vnd.taverna.scufl2.workflow-bundle</code> archive,
+ 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>
+ 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 for the Workflow Bundle representation (the archive)</li>
-<li><code>http://example.com/myWfBundle.scufl2/</code> identifies the Workflow Bundle (as described here)</li>
-<li><code>http://example.com/myWfBundle.scufl2/workflowBundle.rdf</code> identifies the Workflow Bundle representation in RDF/XML</li>
+<li><code>http://example.com/myWfBundle.scufl2</code> identifies the Workflow Bundle representation (the <em>archive</em>).</li>
+<li><code>http://example.com/myWfBundle.scufl2/</code> identifies the <em>Workflow Bundle</em> (as described here).</li>
+<li><code>http://example.com/myWfBundle.scufl2/workflowBundle.rdf</code> identifies the Workflow Bundle representation in RDF/XML.</li>
<li><code>http://example.com/myWfBundle.scufl2/workflow/HelloWorld/</code> identifies the "HelloWorld"
- <a href="/documentation/scufl2/workflow">workflow</a> within the bundle</li>
-<li><code>http://example.com/myWfBundle.scufl2/workflow/HelloWorld.rdf</code> identifies the "HelloWorld" workflow representation in RDF/XML</li>
+ <a href="/documentation/scufl2/workflow">workflow</a> within the bundle.</li>
+<li><code>http://example.com/myWfBundle.scufl2/workflow/HelloWorld.rdf</code> identifies the "HelloWorld" workflow representation in RDF/XML.</li>
<li><code>http://example.com/myWfBundle.scufl2/workflow/HelloWorld/processor/Hello/</code> identifies the "Hello"
processor within the "HelloWorld" workflow.</li>
</ul>
<h3 id="embedded-workflow-bundles">Embedded workflow bundles<a class="headerlink" href="#embedded-workflow-bundles" title="Permanent link">¶</a></h3>
-<p>If the archive is another type of bundle which includes the workflow bundle
+<p>If the archive is another type of bundle, which includes the workflow bundle
(but is not primarily playing the role as the format for this workflow bundle),
the local workflow identifier <strong>should</strong> be unique within the archive.
-This is easiest achieved by using the same folder technique as for the workflow representations:</p>
+This is most easily achieved by using the same folder technique as for the workflow representations:</p>
<ul>
-<li><code>workflowBundle1.rdf</code> can define <code>workflowBundle1/</code></li>
-<li><code>exampleWorkflowBundles/hello.rdf</code> defines <code>exampleWorkflowBundles/hello/</code></li>
+<li><code>workflowBundle1.rdf</code> can define <code>workflowBundle1/</code>.</li>
+<li><code>exampleWorkflowBundles/hello.rdf</code> defines <code>exampleWorkflowBundles/hello/</code>.</li>
</ul>
<p>Such embedded workflow bundles <strong>should</strong> include their constituent representations
- (such as <code>workflow/HelloWorld.rdf</code>) within that folder,
- for instance <code>exampleWorkflowBundles/hello/workflow/HelloWorld.rdf</code> to define
- <code>exampleWorkflowBundles/hello/workflow/HelloWorld/</code> - but could also be shared among bundles,
- for instance both <code>workflowBundle1.rdf</code> and <code>workflowBundle2.rdf</code> might refer to <code>workflow/Shared.rdf</code>.</p>
+ (such as <code>workflow/HelloWorld.rdf</code>) within that folder.
+For instance, <code>exampleWorkflowBundles/hello/workflow/HelloWorld.rdf</code> defines
+ <code>exampleWorkflowBundles/hello/workflow/HelloWorld/</code>. But this could also be shared among bundles;
+ for instance, both <code>workflowBundle1.rdf</code> and <code>workflowBundle2.rdf</code> might refer to <code>workflow/Shared.rdf</code>.</p>
<h3 id="global-workflow-bundle-identifiers">Global workflow bundle identifiers<a class="headerlink" href="#global-workflow-bundle-identifiers" title="Permanent link">¶</a></h3>
<p>Workflow bundles <strong>should</strong> declare a <strong>sameBaseAs</strong> reference to a globally unique non-informational URI.</p>
-<p>Anyone can generate such a URI using the form <code>http://ns.taverna.org.uk/2010/workflowBundle/UUID/</code> -
- for instance <code>http://ns.taverna.org.uk/2010/workflowBundle/28f7c554-4f35-401f-b34b-516e9a0ef731/</code> -
+<p>Anyone can generate such a URI using the form <code>http://ns.taverna.org.uk/2010/workflowBundle/UUID/</code>.
+ One example would be: <code>http://ns.taverna.org.uk/2010/workflowBundle/28f7c554-4f35-401f-b34b-516e9a0ef731/</code> -
including the trailing slash.</p>
<p>The semantics of <strong>sameBaseAs</strong> is a kind of recursive version of <strong>owl:sameAs</strong> -
- so also resources which URI start with the same will be included.</p>
+ so resources with URI having the same beginning will be included.</p>
<p>So if:</p>
<div class="codehilite"><pre><span class="p">@</span><span class="n">prefix</span> <span class="p">:</span> <span class="o"><</span><span class="p">;</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">ns</span><span class="p">.</span><span class="n">taverna</span><span class="p">.</span><span class="n">org</span><span class="p">.</span><span class="n">uk</span><span class="o">/</span>2010<span class="o">/</span><span class="n">scufl2</span><span class="o">></span> <span class="p">.</span>
<span class="p">@</span><span class="n">prefix</span> <span class="n">rdfs</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">w3</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>2000<span class="o">/</span>01<span class="o">/</span><span class="n">rdf</span><span class="o">-</span><span class="n">schema</span><span class="o">></span> <span class="p">.</span>
@@ -360,7 +362,7 @@ This is easiest achieved by using the sa
<blockquote>
<p><img alt="" src="/img/warning.png" /><strong>Not implemented by API</strong> Scufl2 API do not yet</p>
<p>automatically update the workflow bundle identifier.
-<a href="http://www.mygrid.org.uk/dev/issues/browse/SCUFL2-41">SCUFL2-41</a></p>
+Refer to <a href="http://www.mygrid.org.uk/dev/issues/browse/SCUFL2-41">SCUFL2-41</a></p>
<p>To update the URI, use <code>workflowBundle.setSameBaseAs(WorkflowBundle.generateIdentifier())</code>.</p>
</blockquote>
<h2 id="example-representation-in-rdfxml">Example representation in RDF/XML<a class="headerlink" href="#example-representation-in-rdfxml" title="Permanent link">¶</a></h2>
@@ -405,32 +407,40 @@ This is easiest achieved by using the sa
</pre></div>
-<p>This example defines the workflow bundle "HelloWorld".
-It contains one workflow <code>workflow/HelloWorld</code>, which is also the <strong>main workflow</strong>.
-Any additional workflows are typically nested (and nested-nested, etc) workflows bound as activities in processors).
+<p>The above example defines the workflow bundle "HelloWorld".
+It contains one workflow (<code>workflow/HelloWorld</code>), which is also the <strong>main workflow</strong>.
+(Any additional workflows are typically nested (and nested-nested, etc) workflows bound as activities in processors).
Two execution profiles are provided, and <code>profile/tavernaWorkbench</code> is dedicated as the <strong>main profile</strong>.</p>
<h2 id="properties">Properties<a class="headerlink" href="#properties" title="Permanent link">¶</a></h2>
<ul>
<li><strong>name</strong> (required) gives the human readable title for this workflow archive.
This is a subproperty of <code>dc:title</code>.</li>
<li><strong>sameBaseAs</strong> (optional) gives a unique URI which is <strong>owl:sameAs</strong> with this workflow bundle and its children.</li>
-<li><strong>workflow</strong> (required) All <a href="/documentation/scufl2/workflow">workflows</a> included in this bundle.
+<li><strong>workflow</strong> (required) must be included for all <a href="/documentation/scufl2/workflow">workflows</a> included in this bundle.
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) The reference to the top-level <a href="/documentation/scufl2/workflow">workflow</a> of this bundle.
+<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".
- If there is a <strong>mainProfile</strong> the workflow bundle must also have a <strong>mainWorkflow</strong>.
+ for instance if 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) <a href="/wiki/display/developer/Scufl2-Profile">profiles</a> specifying 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>
-<li><strong>mainProfile</strong> (optional) 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 be listed under <strong>profile</strong>.</li></li>
-<li><strong>rdfs:seeAlso</strong> (optional) link to annotations about the workflow bundle and its content. Traditionally found in <code>annotation/workflowBundle.rdf</code>, which should contain further links to annotations from different sources, for instance <code>annotation/myExperiment.rdf</code> for annotations included from myExperiment.</li></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
+ 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>
+<li><strong>rdfs:seeAlso</strong> (optional) describes a link to annotations about the workflow bundle and its content. Traditionally found
+ in <code>annotation/workflowBundle.rdf</code>, which should contain further links to annotations from different
+ sources. For instance, <code>annotation/myExperiment.rdf</code> lists annotations included from myExperiment.</li>
</ul>
<h2 id="bundle-links">Bundle links<a class="headerlink" href="#bundle-links" title="Permanent link">¶</a></h2>
<p>The workflow bundle document is the starting point for finding all workflow bundle resources within the archive.
-Each of the workflows and profiles must therefore have a <strong>rdfs:seeAlso</strong> link to the bundle resource that defines it.</p>
-<p>If alternate formats other than the required RDF/XML format is included in the bundle,
- these formats can therefore link to resources in other formats, for instance in an additional <code>workflowBundle.ttl</code>
+Therefore, each of the workflows and profiles must have a <strong>rdfs:seeAlso</strong> link to the bundle resource that defines it.</p>
+<p>If alternate formats other than the required RDF/XML format are included in the bundle,
+ these formats can link to resources in other formats, for instance to a <code>workflowBundle.ttl</code>
(<a href="http://www.w3.org/TeamSubmission/turtle/">Turtle format</a>):</p>
<div class="codehilite"><pre><span class="p">@</span><span class="n">prefix</span> <span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">ns</span><span class="p">.</span><span class="n">taverna</span><span class="p">.</span><span class="n">org</span><span class="p">.</span><span class="n">uk</span><span class="o">/</span>2010<span class="o">/</span><span class="n">scufl2</span>#<span class="o">></span> <span class="p">.</span>
<span class="p">@</span><span class="n">prefix</span> <span class="n">rdfs</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">w3</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>2000<span class="o">/</span>01<span class="o">/</span><span class="n">rdf</span><span class="o">-</span><span class="n">schema</span>#<span class="o">></span> <span class="p">.</span>
@@ -461,20 +471,21 @@ Each of the workflows and profiles must
<ul>
<li><strong>Should</strong> write the workflow bundle RDF/XML document according to the SCUFL2 XML schema,
use the default namespace <code>xmlns="http://ns.taverna.org.uk/2010/scufl2#"</code> and declare the
- <code>xsi:type="WorkflowBundleDocument"</code></li>
+ <code>xsi:type="WorkflowBundleDocument"</code>.</li>
<li><strong>Must</strong> ensure the workflow bundle RDF/XML document is valid <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a>
and includes the properties deemed required by this specification.
Conforming to the XML schema should ensure this.</li>
-<li><strong>Should</strong> set the <code>xml:base</code> property to <code>"./"</code></li>
-<li><strong>Should</strong> set <strong>rdf:about</strong> to <code>""</code> (or <code>"./"</code> if <code>xml:base</code> is not set)</li>
-<li><strong>Should</strong> declare a <strong>mainWorkflow</strong> and <strong>mainProfile</strong></li>
+<li><strong>Should</strong> set the <code>xml:base</code> property to <code>"./"</code>.</li>
+<li><strong>Should</strong> set <strong>rdf:about</strong> to <code>""</code> (or <code>"./"</code> if <code>xml:base</code> is not set).</li>
+<li><strong>Should</strong> declare a <strong>mainWorkflow</strong> and <strong>mainProfile</strong>.</li>
<li><strong>Must</strong> ensure that any <strong>workflow</strong>/<strong>profile</strong> has a relative <strong>rdfs:seeAlso</strong> link to a bundle resource in
<code>application/rdf+xml</code> which defines
that <a href="/documentation/scufl2/workflow">workflow</a> / <a href="/documentation/scufl2/profile">profile</a>.</li>
</ul>
<p>SCUFL2 compliant readers, when parsing a workflow bundle document:</p>
<p><strong>May</strong> assume that a declared workflow/profile is defined in the referenced representation.
- For instance, if:</p>
+ For instance, in the code example below, <code>workflow/SomeNestedWorkflow.rdf</code> <strong>must</strong> contain a
+ <a href="/documentation/scufl2/workflow">workflow definition</a> for <code>workflow/SomeNestedWorkflow/</code>. </p>
<div class="codehilite"><pre><span class="nt"><workflow></span>
<span class="nt"><Workflow</span> <span class="na">rdf:about=</span><span class="s">"workflow/SomeNestedWorkflow/"</span><span class="nt">></span>
<span class="nt"><rdfs:seeAlso</span> <span class="na">rdf:resource=</span><span class="s">"workflow/SomeNestedWorkflow.rdf"</span> <span class="nt">/></span>
@@ -483,9 +494,7 @@ Each of the workflows and profiles must
</pre></div>
-<p>then <code>workflow/SomeNestedWorkflow.rdf</code> <strong>must</strong> contain a <a href="/documentation/scufl2/workflow">workflow definition</a>
- for <code>workflow/SomeNestedWorkflow/</code>. <br />
-<strong>May</strong> parse the <code>/workflowBundle.rdf</code> as RDF/XML <br />
+<p><strong>May</strong> parse the <code>/workflowBundle.rdf</code> as RDF/XML <br />
<strong>May</strong> parse the {/workflowBundle.rdf}} according to the XML schema if the <code>xsi:type="WorkflowBundleDocument"</code>
is set on the <code>rdf:RDF</code> element.</p></div>
</div>