opengeospatial · pvretano · Mar 31, 2025 · Apr 27, 2025
diff --git a/.github/workflows/generate.yml b/.github/workflows/generate.yml
@@ -18,12 +18,12 @@ jobs:
       matrix:
         os: [ ubuntu-latest ]
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           token: ${{ github.token }}
           submodules: true
 
-      - uses: actions/cache@v2
+      - uses: actions/cache@v4
         with:
           path: ~/.fontist
           key: fontist-${{ runner.os }}

diff --git a/README.md b/README.md
@@ -29,7 +29,7 @@ GET /processes
 Lists the processes this API offers.
 
 ```
-GET /processes/{process-id}
+GET /processes/{processID}
 ```
 
 Returns a detailed description of a process.
@@ -41,26 +41,26 @@ GET /jobs
 Returns the running and finished jobs for a process (optional).
 
 ```
-POST /processes/{process-id}/execution
+POST /processes/{processID}/execution
 ```
 
 Executes a process, i.e. creates a new job. Inputs, outputs and the process id will have to be specified in
 a JSON document that needs to be send in the POST body.
 
 ```
-GET /jobs/{job-id}
+GET /jobs/{jobID}
 ```
 
 Returns the status of a job of a process.
 
 ```
-DELETE /jobs/{job-id}
+DELETE /jobs/{jobID}
 ```
 
 Cancel a job execution.
 
 ```
-GET /jobs/{job-id}/results
+GET /jobs/{jobID}/results
 ```
 
 Returns the result of a job of a process.

diff --git a/core/abstract_tests/ATS_class_core.adoc b/core/abstract_tests/ATS_class_core.adoc
@@ -4,7 +4,7 @@
 ====
 [%metadata]
 identifier:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/conf/core
-subject:: <<rc_core,http://www.opengis.net/spec/ogcapi-processes-1/1.0/conf/core>>
+subject:: <<rc_core,http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core>>
 classification:: Target Type:Web API
 conformance-test:: /conf/core
 conformance-test:: /conf/core/api-definition-op

diff --git a/core/abstract_tests/dismiss/ATS_job-dismiss-op.adoc b/core/abstract_tests/dismiss/ATS_job-dismiss-op.adoc
@@ -9,9 +9,9 @@ test-purpose:: Validate that a running job can be dismissed.
 test-method::
 +
 --
-1. Create an asynchronous job as per test <<ats_core_process-execute-op,/conf/core/process-execute-op>>; not the job identifier, {jobID}, assigned to the job.
+1. Create an asynchronous job as per test <<ats_core_process-execute-op,/conf/core/process-execute-op>>; not the job identifier, `{jobID}`, assigned to the job.
 
-2. Issue an HTTP DELETE operation to the URL '/jobs/{jobID}'.
+2. Issue an HTTP DELETE operation to the URL `/jobs/{jobID}`.
 
 3. Validate the contents of the returned document using test <<ats_dismiss_job-dismiss-success,/conf/dismiss/job-dismiss-success>>.
 --

diff --git a/core/examples/openapi/ogcapi-processes-1-example.yaml b/core/examples/openapi/ogcapi-processes-1-example.yaml
@@ -226,7 +226,7 @@ paths:
             application/json:
               schema:
                 $ref: "https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/core/openapi/responses/ServerError.yaml"
-  '/jobs/{jobID}/results/{outputId}':
+  '/jobs/{jobID}/results/{outputID}':
     get:
       summary: retrieve the result of a job identified by it output ID
       description: |-

diff --git a/core/recommendations/job-list/REC_access-control-job-list.adoc b/core/recommendations/job-list/REC_access-control-job-list.adoc
@@ -4,5 +4,5 @@
 identifier:: /rec/job-list/access-control-job-list
 label:: /rec/job-list/access-control-job-list
 
-Servers implementing the conformance class 'Job List' SHOULD have an access control in place for the /jobs endpoint to prevent misuse of job-ids.
+Servers implementing the conformance class 'Job List' SHOULD have an access control in place for the /jobs endpoint to prevent misuse of job identifiers.
 ====
diff --git a/core/requirements/core/REQ_job-result-op.adoc b/core/requirements/core/REQ_job-result-op.adoc
@@ -5,5 +5,5 @@
 identifier:: /req/core/job-result
 label:: /req/core/job-result
 
-For each <<output_description_schema,defined process output>> with identifier `outputId`, the server SHALL support the HTTP GET operation at the path `/jobs/{jobID}/results/{outputID}`.
+For each <<output_description_schema,defined process output>> with identifier `outputID`, the server SHALL support the HTTP GET operation at the path `/jobs/{jobID}/results/{outputID}`.
 ====
diff --git a/core/requirements/kvp-execute/REQ_array-input-value.adoc b/core/requirements/kvp-execute/REQ_array-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/array-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as type `array` in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as type `array` in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -22,7 +22,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,yaml]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -31,7 +31,7 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 
 ====
diff --git a/core/requirements/kvp-execute/REQ_binary-input-value-qualified.adoc b/core/requirements/kvp-execute/REQ_binary-input-value-qualified.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/binary-input-value-qualified
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as <<req_ogc-process-description_input-binary,binary>> type in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as <<req_ogc-process-description_input-binary,binary>> type in the <<sc_process_description,process description>>.
 . The input value needs to <<qualified-value-schema,qualified>> with a <<format-schema,format>> specification.
 --
 
@@ -18,7 +18,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -42,6 +42,6 @@ style: deepObject
 explode: true
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 ====
diff --git a/core/requirements/kvp-execute/REQ_binary-input-value.adoc b/core/requirements/kvp-execute/REQ_binary-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/binary-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as <<req_ogc-process-description_input-binary,binary>> type in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as <<req_ogc-process-description_input-binary,binary>> type in the <<sc_process_description,process description>>.
 . The input value does not need to be <<qualified-value-schema,qualified>> with a <<format-schema,format>> specification.
 --
 
@@ -18,7 +18,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -28,6 +28,6 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 ====
diff --git a/core/requirements/kvp-execute/REQ_boolean-input-value.adoc b/core/requirements/kvp-execute/REQ_boolean-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/boolean-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}` is defined as type `boolean` in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}` is defined as type `boolean` in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -17,7 +17,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -26,6 +26,6 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represented the identifier of the input.
+where the token `{inputID}` represented the identifier of the input.
 --
 ====
diff --git a/core/requirements/kvp-execute/REQ_complex-input-value.adoc b/core/requirements/kvp-execute/REQ_complex-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/complex-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as type `object` in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as type `object` in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -22,7 +22,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,yaml]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -31,7 +31,7 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 
 ====
diff --git a/core/requirements/kvp-execute/REQ_input-by-reference.adoc b/core/requirements/kvp-execute/REQ_input-by-reference.adoc
@@ -16,7 +16,7 @@ If the input cardinality is 1 then the input parameter SHALL have the following
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -41,7 +41,7 @@ style: deepObject
 explode: true
 ----
 
-where the token `{input-name}` represented the identifier of the input.
+where the token `{inputID}` represented the identifier of the input.
 --
 
 [.component,class=part]

diff --git a/core/requirements/kvp-execute/REQ_input-cardinality.adoc b/core/requirements/kvp-execute/REQ_input-cardinality.adoc
@@ -8,8 +8,8 @@ label:: /req/kvp-execute/input-cardinality
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as having a cardinality greater than one (i.e. `minOccurs` > 1) in the <<sc_process_description,process description>>.
-. The number of input values specified for the `{input-name}` process input is greater than one.
+. A process input, with identifier `{inputID}`, is defined as having a cardinality greater than one (i.e. `minOccurs` > 1) in the <<sc_process_description,process description>>.
+. The number of input values specified for the `{inputID}` process input is greater than one.
 --
 
 [.component,class=part]
@@ -23,7 +23,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,yaml]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -39,7 +39,7 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 
 [.component,class=part]

diff --git a/core/requirements/kvp-execute/REQ_numeric-input-value.adoc b/core/requirements/kvp-execute/REQ_numeric-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/numeric-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as a numeric type input in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as a numeric type input in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -17,7 +17,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -26,6 +26,6 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represented the identifier of the input and the token {numeric-type} is the value `number` or `integer`.
+where the token `{inputID}` represented the identifier of the input and the token {numeric-type} is the value `number` or `integer`.
 --
 ====
diff --git a/core/requirements/kvp-execute/REQ_output.adoc b/core/requirements/kvp-execute/REQ_output.adoc
@@ -7,7 +7,7 @@ label:: /req/kvp-execute/output
 
 [.component,class=conditions]
 --
-. A process output, with identifier `{output-name}`, is defined in the <<sc_process_description,process description>>.
+. A process output, with identifier `{outputID}`, is defined in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -16,7 +16,7 @@ The output parameter SHALL have the following characteristics:
 
 [source,yaml]
 ----
-name: {output-name}
+name: {outputID}
 in: query
 required: false
 schema:
@@ -39,6 +39,6 @@ style: deepObject
 explode: true
 ----
 
-where the token `{output-name}` represents the identifier of the output.
+where the token `{outputID}` represents the identifier of the output.
 --
 ====
diff --git a/core/requirements/kvp-execute/REQ_string-input-value.adoc b/core/requirements/kvp-execute/REQ_string-input-value.adoc
@@ -8,7 +8,7 @@ label:: /req/kvp-execute/string-input-value
 [.component,class=conditions]
 --
 . The process input value is specified in-line in an execute request.
-. A process input, with identifier `{input-name}`, is defined as type `string` in the <<sc_process_description,process description>>.
+. A process input, with identifier `{inputID}`, is defined as type `string` in the <<sc_process_description,process description>>.
 --
 
 [.component,class=part]
@@ -17,7 +17,7 @@ The input parameter SHALL have the following characteristics:
 
 [source,YAML]
 ----
-name: {input-name}
+name: {inputID}
 in: query
 required: false
 schema:
@@ -26,6 +26,6 @@ style: form
 explode: false
 ----
 
-where the token `{input-name}` represents the identifier of the input.
+where the token `{inputID}` represents the identifier of the input.
 --
 ====
diff --git a/core/sections/clause_8_ogc-process-description.adoc b/core/sections/clause_8_ogc-process-description.adoc
@@ -346,7 +346,7 @@ NOTE: This schema can also be obtained from https://raw.githubusercontent.com/op
 
 === Example
 
-The following URL is an example of retrieving a <<sc_process_description,process description>> from the `/processes/{processId}` endpoint.
+The following URL is an example of retrieving a <<sc_process_description,process description>> from the `/processes/{processID}` endpoint.
 [source]
 ----
 https://processing.example.org/processes/EchoProcess

diff --git a/...sions/deploy_replace_undeploy/standard/abstract_tests/cwl/replace/ATS_body.adoc b/...sions/deploy_replace_undeploy/standard/abstract_tests/cwl/replace/ATS_body.adoc
@@ -11,7 +11,7 @@ test-method::
 --
 1. Construct a path for each "rel=http://www.opengis.net/def/rel/ogc/1.0/processes" link on the landing page as well as for the {root}/processes path.
 
-2. Append `/{processId}` to each path, where `{processId}` is a mutable process id.
+2. Append `/{processID}` to each path, where `{processID}` is a mutable process id.
 
 3. Send a PUT request for one path using the media type "application/cwl" and the application package content
 

diff --git a/...ns/deploy_replace_undeploy/standard/abstract_tests/docker/replace/ATS_body.adoc b/...ns/deploy_replace_undeploy/standard/abstract_tests/docker/replace/ATS_body.adoc
@@ -11,7 +11,7 @@ test-method::
 --
 1. Construct a path for each "rel=http://www.opengis.net/def/rel/ogc/1.0/processes" link on the landing page as well as for the {root}/processes path.
 
-2. Append `/{processId}` to each path, where `{processId}` is the process id retrieved from <<ats_ogcapppkg_deploy_response-success,/conf/ogcapppkg/deploy/response-success>>.
+2. Append `/{processID}` to each path, where `{processID}` is the process id retrieved from <<ats_ogcapppkg_deploy_response-success,/conf/ogcapppkg/deploy/response-success>>.
 
 3. Send a PUT request for one path using the media type "application/ogcapppkg+json" with as body a default OGC Application Package
 

diff --git a/...ploy_replace_undeploy/standard/abstract_tests/dru/replace/ATS_content-type.adoc b/...ploy_replace_undeploy/standard/abstract_tests/dru/replace/ATS_content-type.adoc
@@ -11,7 +11,7 @@ test-method::
 --
 1. Construct a path for each "rel=http://www.opengis.net/def/rel/ogc/1.0/processes" link on the landing page as well as for the {root}/processes path.
 
-2. Append `/{processId}` to each path, where `{processId}` is a mutable process id.
+2. Append `/{processID}` to each path, where `{processID}` is a mutable process id.
 
 3. Issue an HTTP PUT request with an unsupported media type, i.e. `text/plain`, on each path.