Deprecate boilerplate feature requirements and update changelog

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <[email protected]>

Author: tetron

CommandLineTool.yml

@@ -52,6 +52,20 @@ $graph:
       ## Changelog for v1.3.0-dev1
 
       See also the [CWL Workflow Description, v1.3.0-dev1 changelog](Workflow.html#Changelog).
+
+      * New field `networkAccess` on
+        [CommandLineTool](#CommandLineTool).  This supercedes the
+        [NetworkAccess](#NetworkAccess) requirement, which is now
+        deprecated.
+      * New field `envDef` on [CommandLineTool](#CommandLineTool).
+        This supercedes the [EnvVarRequirement](#EnvVarRequirement)
+        requirement, which is now deprecated.
+      * New field `initialWorkDir` on
+        [CommandLineTool](#CommandLineTool).  This supercedes the
+        [InitialWorkDirRequirement](#InitialWorkDirRequirement)
+        requirement, which is now deprecated.
+
+
       For other changes since CWL v1.0, see the
       [CWL Command Line Tool Description, v1.1 changelog](https://www.commonwl.org/v1.1/CommandLineTool.html#Changelog)
       and

Workflow.yml

@@ -41,6 +41,17 @@ $graph:
 
       ## Changelog
       See also the [CWL Command Line Tool Description, v1.3.0-dev1 changelog](CommandLineTool.html#Changelog).
+
+      * Workflow steps may now specify iterative execution.  See
+        [LoopWorkflowStep](#LoopWorkflowStep)
+      * Including
+        [StepInputExpressionRequirement](#StepInputExpressionRequirement),
+        [MultipleInputFeatureRequirement](#MultipleInputFeatureRequirement),
+        [ScatterFeatureRequirement](#ScatterFeatureRequirement) and
+        [SubworkflowFeatureRequirement](#SubworkflowFeatureRequirement)
+        in `requirements` is no longer necessary to use the associated
+        feature.  These core features are now always available.
+
       For other changes since CWL v1.0, see the
       [CWL Workflow Description, v1.1 changelog](https://www.commonwl.org/v1.1/Workflow.html#Changelog)
       and
@@ -296,10 +307,6 @@ $graph:
 
     # Merging multiple inbound data links
 
-    To merge multiple inbound data links,
-    [MultipleInputFeatureRequirement](#MultipleInputFeatureRequirement) must be specified
-    in the workflow or workflow step requirements.
-
     If the sink parameter is an array, or named in a [workflow
     scatter](#ScatterWorkflowStep) operation, there may be multiple inbound
     data links listed in the `source` field.  The values from the
@@ -404,9 +411,6 @@ $graph:
         - Expression
       jsonldPredicate: "cwl:valueFrom"
       doc: |
-        To use valueFrom, [StepInputExpressionRequirement](#StepInputExpressionRequirement) must
-        be specified in the workflow or workflow step requirements.
-
         If `valueFrom` is a constant string value, use this as the value for
         this input parameter.
 
@@ -464,9 +468,6 @@ $graph:
         - Expression
       jsonldPredicate: "cwl:valueFrom"
       doc: |
-        To use valueFrom, [StepInputExpressionRequirement](#StepInputExpressionRequirement) must
-        be specified in the workflow or workflow step requirements.
-
         If `valueFrom` is a constant string value, use this as the value for
         this input parameter.
 
@@ -532,10 +533,6 @@ $graph:
 
     # Subworkflows
 
-    To specify a nested workflow as part of a workflow step,
-    [SubworkflowFeatureRequirement](#SubworkflowFeatureRequirement) must be
-    specified in the workflow or workflow step requirements.
-
     It is a fatal error if a workflow directly or indirectly invokes itself as
     a subworkflow (recursive workflows are not allowed).
 
@@ -617,10 +614,6 @@ $graph:
   extends: AbstractWorkflowStep
   docParent: "#Workflow"
   doc: |
-    To use scatter/gather,
-    [ScatterFeatureRequirement](#ScatterFeatureRequirement) must be specified
-    in the workflow or workflow step requirements.
-
     A "scatter" operation specifies that the associated workflow step or
     subworkflow should execute separately over a list of input elements.  Each
     job making up a scatter operation is independent and may be executed
@@ -806,12 +799,11 @@ $graph:
     * If all workflow steps are executed and complete with `success`, then the
     workflow status is `success`.
 
-    # Extensions
+    # Complex steps
 
-    [ScatterFeatureRequirement](#ScatterFeatureRequirement) and
-    [SubworkflowFeatureRequirement](#SubworkflowFeatureRequirement) are
-    available as standard [extensions](#Extensions_and_Metadata) to core
-    workflow semantics.
+    Individual workflow steps may specify complex behavior.  Currently
+    this consists scatter/gather, conditional execution, iterative
+    execution (loops), or executing other workflows.
 
   fields:
     - name: "class"
@@ -840,6 +832,10 @@ $graph:
   name: SubworkflowFeatureRequirement
   extends: ProcessRequirement
   doc: |
+    **Deprecated as of v1.3** This feature is available by default,
+      workflows that use it do not need to declare it.  Including this
+      requirement is a no-op.
+
     Indicates that the workflow platform must support nested workflows in
     the `run` field of [AbstractWorkflowStep](#AbstractWorkflowStep).
   fields:
@@ -858,6 +854,10 @@ $graph:
   type: record
   extends: ProcessRequirement
   doc: |
+    **Deprecated as of v1.3** This feature is available by default,
+      workflows that use it do not need to declare it.  Including this
+      requirement is a no-op.
+
     Indicates that the workflow platform must support the `scatter` and
     `scatterMethod` fields of [ScatterWorkflowStep](#ScatterWorkflowStep).
   fields:
@@ -876,6 +876,10 @@ $graph:
   type: record
   extends: ProcessRequirement
   doc: |
+    **Deprecated as of v1.3** This feature is available by default,
+      workflows that use it do not need to declare it.  Including this
+      requirement is a no-op.
+
     Indicates that the workflow platform must support multiple inbound data links
     listed in the `source` field of [WorkflowStepInput](#WorkflowStepInput).
   fields:
@@ -894,6 +898,10 @@ $graph:
   name: StepInputExpressionRequirement
   extends: ProcessRequirement
   doc: |
+    **Deprecated as of v1.3** This feature is available by default,
+      workflows that use it do not need to declare it.  Including this
+      requirement is a no-op.
+
     Indicate that the workflow platform must support the `valueFrom` field
     of [WorkflowStepInput](#WorkflowStepInput).
   fields: