See common-workflow-language/cwl-website@d302cb2 from refs/heads/main

Author: cwl-bot

draft-3/CommandLineTool.html

@@ -583,13 +583,10 @@ <h2 id="Input_binding" class="section">4.1 Input binding <a href="#Input_binding
 </li>
 <li><p>Collect <code>CommandLineBinding</code> objects from the <code>inputs</code> schema and
 associate them with values from the input object.  Where the input type
-is a record, array, or map, recursively walk the schema and input object,</p>
+is a record, array, or map, recursively walk the schema and input object,
+collecting nested <code>CommandLineBinding</code> objects and associating them with
+values from the input object.</p>
 </li>
-</ol>
-  collecting nested `CommandLineBinding` objects and associating them with
-  values from the input object.
-
-<ol start="3">
 <li><p>Create a sorting key by taking the value of the <code>position</code> field at
 each level leading to each leaf binding object.  If <code>position</code> is not
 specified, it is not added to the sorting key.  For bindings on arrays

draft-3/SchemaSalad.html

@@ -359,12 +359,10 @@ <h2 id="Field_name_resolution" class="section">3.1 Field name resolution <a href
 which are not part of the vocabulary are resolved using the following
 rules:</p>
 <ul>
-<li>If an field name URI begins with a namespace prefix declared in the
-document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and</li>
-</ul>
-colon must be replaced by the namespace declared in `@context`.
-
-<ul>
+<li><p>If an field name URI begins with a namespace prefix declared in the
+document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and
+colon must be replaced by the namespace declared in <code>@context</code>.</p>
+</li>
 <li><p>If there is a vocabulary term which maps to the URI of a resolved
 field, the field name must be replace with the vocabulary term.</p>
 </li>

v1.0/CommandLineTool.html

@@ -649,13 +649,10 @@ <h2 id="Input_binding" class="section">4.1 Input binding <a href="#Input_binding
 </li>
 <li><p>Collect <code>CommandLineBinding</code> objects from the <code>inputs</code> schema and
 associate them with values from the input object.  Where the input type
-is a record, array, or map, recursively walk the schema and input object,</p>
+is a record, array, or map, recursively walk the schema and input object,
+collecting nested <code>CommandLineBinding</code> objects and associating them with
+values from the input object.</p>
 </li>
-</ol>
-  collecting nested `CommandLineBinding` objects and associating them with
-  values from the input object.
-
-<ol start="3">
 <li><p>Create a sorting key by taking the value of the <code>position</code> field at
 each level leading to each leaf binding object.  If <code>position</code> is not
 specified, it is not added to the sorting key.  For bindings on arrays

v1.0/SchemaSalad.html

@@ -372,12 +372,10 @@ <h2 id="Field_name_resolution" class="section">3.1 Field name resolution <a href
 which are not part of the vocabulary are resolved using the following
 rules:</p>
 <ul>
-<li>If an field name URI begins with a namespace prefix declared in the
-document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and</li>
-</ul>
-colon must be replaced by the namespace declared in `@context`.
-
-<ul>
+<li><p>If an field name URI begins with a namespace prefix declared in the
+document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and
+colon must be replaced by the namespace declared in <code>@context</code>.</p>
+</li>
 <li><p>If there is a vocabulary term which maps to the URI of a resolved
 field, the field name must be replace with the vocabulary term.</p>
 </li>

v1.0/Workflow.html

@@ -1575,13 +1575,13 @@ <h3>Fields</h3>
 this input parameter.</p>
 <p>If <code>valueFrom</code> is a parameter reference or expression, it must be
 evaluated to yield the actual value to be assiged to the input field.</p>
-<p>The <code>self</code> value in the parameter reference or expression must be
-parameter <strong>is</strong> specified in this workflow step's <code>scatter</code> field.</p>
+<p>The <code>self</code> value in the parameter reference or expression must be</p>
 <ol>
 <li><code>null</code> if there is no <code>source</code> field</li>
 <li>the value of the parameter(s) specified in the <code>source</code> field when this
 workflow input parameter <strong>is not</strong> specified in this workflow step's <code>scatter</code> field.</li>
-<li>an element of the parameter specified in the <code>source</code> field when this workflow input</li>
+<li>an element of the parameter specified in the <code>source</code> field when this workflow input
+parameter <strong>is</strong> specified in this workflow step's <code>scatter</code> field.</li>
 </ol>
 <p>The value of <code>inputs</code> in the parameter reference or expression must be
 the input object to the workflow step after assigning the <code>source</code>

v1.1/CommandLineTool.html

@@ -851,13 +851,10 @@ <h2 id="Input_binding" class="section">4.1 Input binding <a href="#Input_binding
 </li>
 <li><p>Collect <code>CommandLineBinding</code> objects from the <code>inputs</code> schema and
 associate them with values from the input object.  Where the input type
-is a record, array, or map, recursively walk the schema and input object,</p>
+is a record, array, or map, recursively walk the schema and input object,
+collecting nested <code>CommandLineBinding</code> objects and associating them with
+values from the input object.</p>
 </li>
-</ol>
-  collecting nested `CommandLineBinding` objects and associating them with
-  values from the input object.
-
-<ol start="3">
 <li><p>Create a sorting key by taking the value of the <code>position</code> field at
 each level leading to each leaf binding object.  If <code>position</code> is not
 specified, it is not added to the sorting key.  For bindings on arrays

v1.1/SchemaSalad.html

@@ -413,12 +413,10 @@ <h2 id="Field_name_resolution" class="section">3.1 Field name resolution <a href
 which are not part of the vocabulary are resolved using the following
 rules:</p>
 <ul>
-<li>If an field name URI begins with a namespace prefix declared in the
-document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and</li>
-</ul>
-colon must be replaced by the namespace declared in `@context`.
-
-<ul>
+<li><p>If an field name URI begins with a namespace prefix declared in the
+document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and
+colon must be replaced by the namespace declared in <code>@context</code>.</p>
+</li>
 <li><p>If there is a vocabulary term which maps to the URI of a resolved
 field, the field name must be replace with the vocabulary term.</p>
 </li>

v1.1/Workflow.html

@@ -2340,13 +2340,13 @@ <h3>Fields</h3>
 this input parameter.</p>
 <p>If <code>valueFrom</code> is a parameter reference or expression, it must be
 evaluated to yield the actual value to be assiged to the input field.</p>
-<p>The <code>self</code> value in the parameter reference or expression must be
-parameter <strong>is</strong> specified in this workflow step's <code>scatter</code> field.</p>
+<p>The <code>self</code> value in the parameter reference or expression must be</p>
 <ol>
 <li><code>null</code> if there is no <code>source</code> field</li>
 <li>the value of the parameter(s) specified in the <code>source</code> field when this
 workflow input parameter <strong>is not</strong> specified in this workflow step's <code>scatter</code> field.</li>
-<li>an element of the parameter specified in the <code>source</code> field when this workflow input</li>
+<li>an element of the parameter specified in the <code>source</code> field when this workflow input
+parameter <strong>is</strong> specified in this workflow step's <code>scatter</code> field.</li>
 </ol>
 <p>The value of <code>inputs</code> in the parameter reference or expression must be
 the input object to the workflow step after assigning the <code>source</code>

v1.2/CommandLineTool.html

@@ -1162,13 +1162,10 @@ <h2 id="Input_binding" class="section">4.1 Input binding <a href="#Input_binding
 </li>
 <li><p>Collect <code>CommandLineBinding</code> objects from the <code>inputs</code> schema and
 associate them with values from the input object.  Where the input type
-is a record, array, or map, recursively walk the schema and input object,</p>
+is a record, array, or map, recursively walk the schema and input object,
+collecting nested <code>CommandLineBinding</code> objects and associating them with
+values from the input object.</p>
 </li>
-</ol>
-  collecting nested `CommandLineBinding` objects and associating them with
-  values from the input object.
-
-<ol start="3">
 <li><p>Create a sorting key by taking the value of the <code>position</code> field at
 each level leading to each leaf binding object.  If <code>position</code> is not
 specified, it is not added to the sorting key.  For bindings on arrays

v1.2/SchemaSalad.html

@@ -448,12 +448,10 @@ <h2 id="Field_name_resolution" class="section">3.1 Field name resolution <a href
 which are not part of the vocabulary are resolved using the following
 rules:</p>
 <ul>
-<li>If a field name URI begins with a namespace prefix declared in the
-document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and</li>
-</ul>
-colon must be replaced by the namespace declared in `@context`.
-
-<ul>
+<li><p>If a field name URI begins with a namespace prefix declared in the
+document context (<code>@context</code>) followed by a colon <code>:</code>, the prefix and
+colon must be replaced by the namespace declared in <code>@context</code>.</p>
+</li>
 <li><p>If there is a vocabulary term which maps to the URI of a resolved
 field, the field name must be replace with the vocabulary term.</p>
 </li>