Add support for the /jobs/{jobId}/results/{outputID}/{N} path.

core/abstract_tests/core/ATS_job-result-op.adoc

@@ -5,12 +5,12 @@
 [%metadata]
 identifier:: /conf/core/job-result-op
 target:: /req/core/job-result-op
-test-purpose:: Validate that each process output with identifier `{outputID}` can be retrived from the `/jobs/{jobID}/results/{outputID}` endpoint.
+test-purpose:: Validate that each process output with identifier `{outputID}` can be retrieved from the `/jobs/{jobID}/results/{outputID}` endpoint.
 test-method::
 +
 --
 1. Negotiate asynchronous process execution as per test <<ats_core_process-execute-auto-execution-mode,/conf/core/process-execute-auto-execution-mode>> or <<ats_core_process-execute-default-execution-mode,/conf/core/process-execute-default-execution-mode>>.
 
-2. Validate that each process output can be retrived as per requirement <<req_core_job-result-op,/req/core/job-result-op>>.
+2. Validate that each process output can be retrieved as per requirement <<req_core_job-result-op,/req/core/job-result-op>>.
 --
 ====

core/abstract_tests/ogc-process-description/ATS_data-access-apis.adoc

@@ -10,7 +10,7 @@ test-method::
 --
 1. Retrieve the description of each process the server offers according to test <<ats_core_process-description-op,/conf/core/process-description-op>>.
 
-2. Inspect each input of each process and determine if the `dataAccessApi` parmater is present.
+2. Inspect each input of each process and determine if the `dataAccessApi` parameter is present.
 
 3. If it is present then verify that the value of the parameter is either empty or contains a list of data access APIs (e.g. ogc-api-features, ogc-api-coverages, etc.).
 

core/abstract_tests/ogc-process-description/ATS_data-classes.adoc

@@ -11,7 +11,7 @@ test-method::
 --
 1. Retrieve the description of each process the server offers according to test <<ats_core_process-description-op,/conf/core/process-description-op>>.
 
-2. Inspect each input of each process and determine if the `dataClasses` parmater is present.
+2. Inspect each input of each process and determine if the `dataClasses` parameter is present.
 
 3. If it is present then verify that the value of the parameter is an array of strings.
 

core/abstract_tests/ogc-process-description/ATS_execution-unit-requirements.adoc

@@ -11,7 +11,7 @@ test-method::
 --
 1. Retrieve the description of each process the server offers according to test <<ats_core_process-description-op,/conf/core/process-description-op>>.
 
-2. Inspect each input of each process and determine if the `executionUnitRequirements` parmater is present.
+2. Inspect each input of each process and determine if the `executionUnitRequirements` parameter is present.
 
 3. If the `remote-access` member is specified, verify that its value is either `true` or `false`.
 

core/recommendations/core/PER_job-results-success-async-one-multi-valued-other-formats.adoc

@@ -0,0 +1,24 @@
+[[per_core_job-results-async-one-multi-valued-other-formats]]
+[permission]
+====
+[%metadata]
+identifier:: /per/core/job-results-async-one-multi-valued-other-formats
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+--
+
+[.component,class=part]
+--
+Servers MAY support other response formats or encodings (e.g. ZIP or `multipart/*`) that do not conform to https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/openapi/schemas/processes-core/values.yaml[values.yaml].
+--
+
+[.component,class=part]
+--
+This Standard does not provide any guidance on these other formats or encodings.
+--
+
+====

core/recommendations/core/PER_process-execute-multiple-values-pkg.adoc

@@ -0,0 +1,8 @@
+[[per_core_process-execute-multiple-values-pkg]]
+[permission]
+====
+[%metadata]
+identifier:: /per/core/process-execute-multiple-values-pkg
+
+A server MAY, through content negotiation, respond with something other than that specified by requirement <<req_core_process-execute-sync-one-multi-valued-json,/req/core/process-execute-sync-one-multi-valued-json>>.  A server MAY, for example, respond with a https://www.iso.org/standard/60101.html[ZIP] file or a https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html[multi-part MIME] document containing all the requested output values.
+====

core/recommendations/core/PER_process-execute-success-sync-one-multi-valued-other-formats.adoc

@@ -0,0 +1,24 @@
+[[per_core_process-execute-sync-one-multi-valued-other-formats]]
+[permission]
+====
+[%metadata]
+identifier:: /per/core/process-execute-sync-one-multi-valued-other-formats
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is synchronous.
+. The number of requested (whether <<implicit-explicit-outputs,implicitly or explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the requested output is defined as having `maxOccurs>1`.
+--
+
+[.component,class=part]
+--
+Servers MAY support other response formats or encodings (e.g. ZIP or `multipart/*`) that do not conform to https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/openapi/schemas/processes-core/values.yaml[values.yaml].
+--
+
+[.component,class=part]
+--
+This Standard does not provide any guidance on these other formats or encodings.
+--
+
+====

core/recommendations/core/REC_job-results-success-async-one-multi-valued-json-prefer-minimal.adoc

@@ -0,0 +1,24 @@
+[[rec_core_job-results-async-one-multi-valued-json-prefer-minimal]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/job-results-async-one-multi-valued-json-prefer-minimal
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. The negotiated https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[return preference] is `minimal`.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _small_, that value SHOULD be included in-line in the response.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _large_, that value SHOULD be included by reference via hyperlink in the response.
+--
+====

core/recommendations/core/REC_job-results-success-async-one-multi-valued-json-prefer-none.adoc

@@ -0,0 +1,24 @@
+[[rec_core_job-results-async-one-multi-valued-json-prefer-none]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/job-results-async-one-multi-valued-json-prefer-none
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. A return preference is _**not**_ specified via the HTTP https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[`prefer`] header.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _small_, that value SHOULD be included in-line in the response.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _large_, that value SHOULD be included by reference via hyperlink in the response.
+--
+====

core/recommendations/core/REC_job-results-success-async-one-multi-valued-json-prefer-representation.adoc

@@ -0,0 +1,19 @@
+[[rec_core_job-results-async-one-multi-valued-json-prefer-representation]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/job-results-async-one-multi-valued-json-prefer-representation
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. The negotiated https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[return preference] is `representation`.
+--
+
+[.component,class=part]
+--
+Each requested output value SHOULD be included in-line in the response.
+--
+====

core/recommendations/core/REC_process-execute-success-sync-one-multi-valued-json-prefer-minimal.adoc

@@ -0,0 +1,24 @@
+[[rec_core_process-execute-sync-one-multi-valued-json-prefer-minimal]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/process-execute-sync-one-multi-valued-json-prefer-minimal
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is synchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. The negotiated https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[return preference] is `minimal`.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _small_, that value SHOULD be included in-line in the response.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output value is _large_, that value SHOULD be included by reference via hyperlink in the response.
+--
+====

core/recommendations/core/REC_process-execute-success-sync-one-multi-valued-json-prefer-none.adoc

@@ -0,0 +1,24 @@
+[[rec_core_process-execute-sync-one-multi-valued-json-prefer-none]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/process-execute-sync-one-multi-valued-json-prefer-none
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is synchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. No https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[return preference] accompanies the request.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of the output values is _small_, that value SHOULD be included in-line in the response.
+--
+
+[.component,class=part]
+--
+If the server deems that the size of an output values is _large_, that value SHOULD be included by reference via hyperlink in the response.
+--
+====

core/recommendations/core/REC_process-execute-success-sync-one-multi-valued-json-prefer-representation.adoc

@@ -0,0 +1,19 @@
+[[rec_core_process-execute-sync-one-multi-valued-json-prefer-representation]]
+[recommendation]
+====
+[%metadata]
+identifier:: /rec/core/process-execute-sync-one-multi-valued-json-prefer-representation
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is synchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. In the <<sc_process_description,process description>> the output is defined as having `maxOccurs>1`.
+. The negotiated https://datatracker.ietf.org/doc/html/rfc7240#section-4.2[return preference] is `representation`.
+--
+
+[.component,class=part]
+--
+Each requested output value SHOULD be included in-line in the response.
+--
+====

core/recommendations/ogc-process-description/PER_extend-data-access-apis-values.adoc

@@ -4,5 +4,5 @@
 [%metadata]
 identifier:: /per/ogc-process-description/extend-data-access-apis-values
 
-The list of values for the `dataAccessApi` paramater MAY be extended as necessary to accomondate other, perhaps even non_OGC, data access APIs.
+The list of values for the `dataAccessApi` paramater MAY be extended as necessary to accommodate other, perhaps even non_OGC, data access APIs.
 ====

core/requirements/core/REQ_job-result-op-0th.adoc

@@ -0,0 +1,8 @@
+[[req_core_job-result-op-0th]]
+[requirement]
+====
+[%metadata]
+identifier:: /req/core/job-result-op-0th
+
+For each output, with output identifier `outputID`, defined in the <<sc_process_description,description of a process>> and requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) in an <<execute-request-body,execute request>>, the server SHALL support the HTTP GET operation at the path `/jobs/{jobID}/results/{outputID}/0`.
+====

core/requirements/core/REQ_job-result-op-Nth.adoc

@@ -0,0 +1,24 @@
+[[req_core_job-result-op-Nth]]
+[requirement]
+====
+[%metadata]
+identifier:: /req/core/job-result-op-Nth
+
+
+[.component,class=conditions]
+--
+. The output with output identifier `outputID` is defined in the <<sc_process_description,process description>> as having `maxOccurs>1`.
+. The output with output identifier `outputID` is  <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>> requested in an <<execute-request-body,execute request>>.
+--
+
+[.component,class=part]
+--
+The server SHALL support the HTTP GET operation at the path `/jobs/{jobID}/results/{outputID}/{N}`.
+--
+
+[.component,class=part]
+--
+The path element _N_ is a 0-based index into the array of values generated by the process for this output.
+--
+
+====

core/requirements/core/REQ_job-results-param-outputs-response.adoc

@@ -4,5 +4,5 @@
 [%metadata]
 identifier:: /req/core/job-results-param-outputs-response
 
-Only the outputs with identifers specified using the optional <<req_core_job-results-param-outputs,`outputs` parameter>> SHALL be included in the response.
+Only the outputs with identifiers specified using the optional <<req_core_job-results-param-outputs,`outputs` parameter>> SHALL be included in the response.
 ====

core/requirements/core/REQ_job-results-success-async-one-Nth.adoc

@@ -0,0 +1,35 @@
+[[req_core_job-results-async-one-Nth]]
+[requirement]
+====
+[%metadata]
+identifier:: /req/core/job-results-async-one-Nth
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous,
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+. The requested output with identifier `outputID` is defined in the <<sc_process_description,process description>> as having `maxOccurs>1`.
+. The path `/jobs/{jobID}/results/{outputID}/{N}` is accessed to retrieve the 0-based _N^th^_ value from the array of values produced for this output.
+--
+
+[.component,class=part]
+--
+The server SHALL respond with an HTTP status code of 200.
+--
+
+[.component,class=part]
+--
+In the response headers, the server SHALL include an HTTP header named `OGC-Output-Values-Count` indicating how many processing values are retrievable for this output.
+--
+
+[.component,class=part]
+--
+The media type of the response SHALL be as negotiated as per the https://datatracker.ietf.org/doc/html/rfc2616#section-12[HTTP content negotiation rules].
+--
+
+[.component,class=part]
+--
+The content of the response body SHALL be the 0-based _N^th^_ value in the negotiated output format.
+--
+
+====

core/requirements/core/REQ_job-results-success-async-one-multi-valued.adoc

@@ -0,0 +1,40 @@
+[[req_core_job-results-async-one-multi-valued]]
+[requirement]
+====
+[%metadata]
+identifier:: /req/core/job-results-async-one-multi-valued
+
+[.component,class=conditions]
+--
+. The <<sc_execution_mode,negotiated execution mode>> is asynchronous.
+. The number of requested (whether <<implicit-process-output,implicitly>> or <<explicit-process-output,explicitly>>) outputs in the <<execute-request-body,execute request>> is 1.
+- In its <<sc_process_description,process description>> the requested output is defined as having `maxOccurs>1`.
+. The results are retrieved from the `/jobs/{jobID}/results/{outputID}` endpoint.
+--
+
+[.component,class=part]
+--
+The server SHALL respond with an HTTP status code of 200.
+--
+
+[.component,class=part]
+--
+In the response headers, the server SHALL include an HTTP header named `OGC-Output-Values-Count` indicating how many processing values are retrievable for this output.
+--
+
+[.component,class=part]
+--
+The media type of the response SHALL be `application/json`.
+--
+
+[.component,class=part]
+--
+The response HTTP headers SHALL include a `Link: href="https://www.opengis.net/def/profile/OGC/0/ogc-values", rel="profile"`.
+--
+
+[.component,class=part]
+--
+The content of response SHALL conform to the <<schema_values,values.yaml>> schema.
+--
+
+====

core/requirements/core/REQ_job-results-success-async-one.adoc

@@ -16,6 +16,11 @@ identifier:: /req/core/job-results-async-one
 The server SHALL respond with an HTTP status code of 200.
 --
 
+[.component,class=part]
+--
+In the response headers, the server SHALL include an HTTP header named `OGC-Output-Values-Count` indicating how many processing values are retrievable for this output.
+--
+
 [.component,class=part]
 --
 The media type of the response SHALL be as negotiated as per the https://datatracker.ietf.org/doc/html/rfc2616#section-12[HTTP content negotiation rules].
@@ -27,3 +32,8 @@ The content of response body SHALL be the requested process output value in the
 --
 
 ====
+
+NOTE: Unless the definition of an output sets `maxOccurs>1`, the value of the `OGC-Output-Values-Count` HTTP header will usually be 1.
+
+NOTE: If the requested output is multi-valued (i.e. `maxOccurs>1` in the <<sc_process_description,process description>>), then the negotiated response will need to be some type of container for the array of values generated by the process for this output.  For example, this could be a JSON response where the array of values is encoded as a JSON array or a multi-part response where each part contains one value from the array or some archive (e.g. ZIP or tar) where each array value is stored in an individual file.
+