Part5 Provenance

.gitignore

@@ -42,6 +42,9 @@ extensions/job_management/**/24-051.doc
 extensions/job_management/**/24-051.err
 extensions/job_management/**/24-051.xml
 extensions/job_management/**/24-051.presentation.xml
+extensions/provenance/**/26-038.html
+extensions/provenance/**/26-038.presentation.xml
+extensions/provenance/**/26-038.xml
 node_modules
 package.json
 package-lock.json

asciidoctor.json

@@ -1,7 +1,7 @@
 {
         "0":  {
                 "OGC_doc_number": "18-062r3",
-                "urn":"http://www.opengis.net/doc/IS/ogcapi-processes-1/2.0",
+                "urn":"https://www.opengis.net/doc/IS/ogcapi-processes-1/2.0",
                 "title":"OGC API - Processes - Part 1: Core",
                 "version":"2.0.0",
                 "path":"18-062.adoc",
@@ -17,7 +17,7 @@
         },
         "1":  {
                 "OGC_doc_number": "20-044",
-                "urn":"http://www.opengis.net/doc/IS/ogcapi-processes-2/1.0",
+                "urn":"https://www.opengis.net/doc/IS/ogcapi-processes-2/1.0",
                 "title":"OGC API - Processes - Part 2: Deploy, Replace, Undeploy",
                 "version":"1.0.0",
                 "path":"extensions/deploy_replace_undeploy/standard/20-044.adoc",
@@ -33,7 +33,7 @@
         },
         "2":  {
                 "OGC_doc_number": "21-099",
-                "urn":"http://www.opengis.net/doc/IS/ogcapi-processes-3/1.0",
+                "urn":"https://www.opengis.net/doc/IS/ogcapi-processes-3/1.0",
                 "title":"OGC API - Processes - Part 3: Workflows and Chaining",
                 "version":"1.0.0",
                 "path":"extensions/workflows/21-099.adoc",
@@ -49,10 +49,26 @@
         },
         "3":  {
                 "OGC_doc_number": "24-051",
-                "urn":"http://www.opengis.net/doc/IS/ogcapi-processes-4/1.0",
+                "urn":"https://www.opengis.net/doc/IS/ogcapi-processes-4/1.0",
                 "title":"OGC API - Processes - Part 4: Job Management",
                 "version":"1.0.0",
-                "path":"extensions/job_management/standard/21-099.adoc",
+                "path":"extensions/job_management/standard/24-051.adoc",
+                "options": ["--trace"],
+                "a":[
+                        "data-uri",
+                        "stylesdir=./resources/stylesheets",
+                        "dot=/usr/bin/dot"
+                ],
+                "r":[
+                        "asciidoctor-diagram"
+                ]
+        },
+        "4":  {
+                "OGC_doc_number": "26-038",
+                "urn":"https://www.opengis.net/doc/IS/ogcapi-processes-5/1.0",
+                "title":"OGC API - Processes - Part 5: Provenance",
+                "version":"1.0.0",
+                "path":"extensions/provenance/standard/26-038.adoc",
                 "options": ["--trace"],
                 "a":[
                         "data-uri",

core/requirements/core/REQ_job-exception-no-such-job.adoc

@@ -16,7 +16,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-job".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-job"]`.
 --
 
 ====

core/requirements/core/REQ_job-results-exception-invalid-query-parameter-value.adoc

@@ -16,7 +16,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/invalid-query-parameter-value".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/invalid-query-parameter-value"]`.
 --
 
 ====

core/requirements/core/REQ_job-results-exception-no-such-job.adoc

@@ -16,7 +16,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-job".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-job"]`.
 --
 
 ====

core/requirements/core/REQ_job-results-exception-results-not-available.adoc

@@ -22,7 +22,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/result-not-available".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/result-not-available"]`.
 --
 
 ====

core/requirements/core/REQ_job-results-exception-results-not-ready.adoc

@@ -21,7 +21,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/result-not-ready".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/result-not-ready"]`.
 --
 
 ====

core/requirements/core/REQ_process-exception-no-such-process.adoc

@@ -16,7 +16,7 @@ The content of that response SHALL be based upon the OpenAPI 3.0 schema https://
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-process".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-process"]`.
 --
 
 ====

core/sections/clause_2_conformance.adoc

@@ -41,13 +41,13 @@ The _Core_ does not mandate the use of any specific process description language
 This class defines an information model, encoded in JSON, which may be used to
 specify the interface of a process including the inputs that the process expects and the outputs that the process will generate.
 
-Besides the standard input types one might expect for a process (e.g. integer, string, double, etc.) this Standard defines the following conformance class: 
+Besides the standard input types one might expect for a process (e.g. integer, string, double, etc.) this Standard defines the following conformance class:
 
-* <<rc_collection-input,Collection Input>> 
+* <<rc_collection-input,Collection Input>>
 
 that allows OGC API collections to be specified as process inputs.  The <<rc_collection-input,Collection Input>> class only supports collections that are local to the current deployment to be specified as process inputs.  The following conformance class:
 
-* <<rc_remote-collections,Remote Collections>> 
+* <<rc_remote-collections,Remote Collections>>
 
 extends the collection input requirements to support specifying remote collections as process inputs.
 
@@ -61,7 +61,7 @@ In addition to supporting collections as process inputs, the following conforman
 
 * <<rc_collection-output,Collection Output>>
 
-defines requirements that allow process execution to be triggered by requesting output data using an standard <<def-data-access-mechanism,OGC API data access mechanisms>>.  In this way, process execution becomes opaque, hidden behind a standard OGC data access API (e.g. features, coverages, etc.).  
+defines requirements that allow process execution to be triggered by requesting output data using an standard <<def-data-access-mechanism,OGC API data access mechanisms>>.  In this way, process execution becomes opaque, hidden behind a standard OGC data access API (e.g. features, coverages, etc.).
 
 In the <<rc_core,Core>> executing a process requires sending a JSON-encoded execution request to the server using the HTTP POST method.  To support embedding process execution requests into other documents this Standard defines the:
 
@@ -71,13 +71,13 @@ conformance class which allows process inputs to be encoded as query parameters
 
 The standard request and response encoding used in this Standard is JSON.  The standard media type for JSON is `application/json` which does not allow for the discrimination of one JSON schema from another.  In order to resolve this issue the Standard supports content negotiation by profile and defines the `profile` query parameter in the:
 
-* <<rc_query-param-profile>.
+* <<rc_query-param-profile>>.
 
 conformance class.  Using the `profile` query parameter JSON-encoded responses can be requested that conform to a specific JSON schemas.
 
 Three additional conformance classes are specified that extend the basic functionality defined in the _Core_ requirements class:
 
-* <<rc_job-list,Job list>> for requesting a list of jobs with optional filtering capabilities, 
+* <<rc_job-list,Job list>> for requesting a list of jobs with optional filtering capabilities,
 
 * <<rc_dismiss,Dismiss>> for cancelling active jobs or deleting completed jobs, and
 

extensions/deploy_replace_undeploy/standard/requirements/cwl/REQ_exception-workflow-not-found.adoc

@@ -21,7 +21,7 @@ include::../../../../../openapi/schemas/common-core/exception.yaml[]
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be "https://www.opengis.net/def/exceptions/ogcapi-processes-2/1.0/workflow-not-found".
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-2/1.0/workflow-not-found"]`.
 --
 
 ====

extensions/deploy_replace_undeploy/standard/requirements/deploy-replace-undeploy/deploy/REQ_unsupported-media-type.adoc

@@ -22,7 +22,7 @@ include::../../../../../../openapi/schemas/common-core/exception.yaml[]
 
 [.component,class=part]
 --
-The `type` of the exception SHALL be `"https://www.opengis.net/def/exceptions/ogcapi-processes-2/1.0/unsupported-media-type"`.
+The `type` of the exception SHALL be `pass:["https://www.opengis.net/def/exceptions/ogcapi-processes-2/1.0/unsupported-media-type"]`.
 --
 
 ====

extensions/deploy_replace_undeploy/standard/sections/clause_10_oas.adoc

@@ -1,4 +1,4 @@
 [[clause_oas]]
 == OpenAPI 3.0
 
-See <<OAProc-1>>, Clause 9.
+See <<OAProc-1>>, Clause 12.

extensions/deploy_replace_undeploy/standard/sections/clause_9_cwl.adoc

@@ -84,7 +84,7 @@ include::../requirements/cwl/REQ_body.adoc[]
 
 ==== Multipart CWL request body
 
-include::../recommendations/cwl/REC_body-cwl-multipart.adoc[]
+include::../recommendations/cwl/PER_body-cwl-multipart.adoc[]
 
 The following multipart example illustrates one request payload with a root workflow selected by the `start` parameter, with supporting documents referenced by `filename`, `cid:` URI and remote URL combinations. The full contents of the individual <<rc_cwl,CWL>> documents are not included for simplification. Note that the <<rc_cwl,CWL>> YAML representation are employed to provide a concise example, but other <<rc_cwl,CWL>> media-types are permitted in any desired combination.
 

extensions/job_management/standard/24-051.adoc

@@ -3,15 +3,15 @@
 :docsubtype: implementation
 :docnumber: 24-051
 :status: draft
-:copyright-year: 2019
+:copyright-year: 2026
 :edition: 1.0
 :language: en
 :published-date: yyyy-mm-dd
 :received-date: yyyy-mm-dd
 :issued-date: yyyy-mm-dd
 :external-id: http://www.opengis.net/doc/IS/ogcapi-processes-4/1.0
-:keywords: process, instance, spatial, data, openapi, job, create, update, delete, add, remove, REST, PATCH, POST, DELETE, W3C PROV, Provenance
-:submitting-organizations: Geolabs; Terradue Srl.; Technologies Luqia, Centre de Recherche Informatique de Montréal (CRIM)
+:keywords: process, instance, spatial, data, openapi, job, create, update, delete, add, remove, REST, PATCH, POST, DELETE
+:submitting-organizations: Geolabs; Terradue Srl.; Technologies Luqia, Centre de Recherche Informatique de Montréal (CRIM); CubeWerx Inc.
 :editor: Gérald Fenoy, Francis Charette-Migneault
 :mn-document-class: ogc
 :mn-output-extensions: xml,html,doc,pdf
@@ -37,13 +37,11 @@ include::sections/clause_7_ogcapi-processes.adoc[]
 
 include::sections/clause_8_openeo.adoc[]
 
-include::sections/clause_9_provenance.adoc[]
+include::sections/clause_9_oas.adoc[]
 
-include::sections/clause_10_oas.adoc[]
+include::sections/clause_10_media_types.adoc[]
 
-include::sections/clause_11_media_types.adoc[]
-
-include::sections/clause_12_security_considerations.adoc[]
+include::sections/clause_11_security_considerations.adoc[]
 
 include::sections/annex_ats.adoc[]
 

extensions/job_management/standard/requirements/requirements_class_job-management.adoc

@@ -3,7 +3,7 @@
 .Requirements Class 'Job Management'
 ====
 [%metadata]
-identifier:: http://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management
+identifier:: https://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management
 obligation:: requirement
 subject:: Web API
 inherit:: <<OAProc-1,OGC API - Processes - Part 1: Core, Conformance Class 'Core'>>

extensions/job_management/standard/requirements/requirements_class_ogcapi-processes.adoc

@@ -3,12 +3,12 @@
 .Requirements Class 'OGC API - Processes'
 ====
 [%metadata]
-identifier:: http://www.opengis.net/spec/ogcapi-processes-4/1.0/req/ogcapi-processes
+identifier:: https://www.opengis.net/spec/ogcapi-processes-4/1.0/req/ogcapi-processes
 obligation:: requirement
 subject:: Web API
 inherit:: <<OAProc-1,OGC API - Processes - Part 1: Core>>
 inherit:: <<OAProc-3,OGC API - Processes - Part 3: Workflows and Chaining, Conformance Class 'nested-processing'>>
-inherit:: <<rc_job-management,http://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management>>
+inherit:: <<rc_job-management,https://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management>>
 requirement:: /req/ogcapi-processes/create-body
 requirement:: /req/ogcapi-processes/definition-response-body
 requirement:: /req/ogcapi-processes/schema

extensions/job_management/standard/requirements/requirements_class_openeo.adoc

@@ -3,10 +3,10 @@
 .Requirements Class 'openEO'
 ====
 [%metadata]
-identifier:: http://www.opengis.net/spec/ogcapi-processes-4/1.0/req/openeo
+identifier:: https://www.opengis.net/spec/ogcapi-processes-4/1.0/req/openeo
 obligation:: requirement
 subject:: Web API
-inherit:: <<rc_job-management,http://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management>>
+inherit:: <<rc_job-management,https://www.opengis.net/spec/ogcapi-processes-4/1.0/req/job-management>>
 requirement:: /req/openeo/create-body
 requirement:: /req/openeo/definition-response-body
 requirement:: /req/openeo/schema

extensions/job_management/standard/sections/annex_history.adoc

@@ -14,4 +14,5 @@
 |2026-06-23 |None |Francis Charette-Migneault |all |Align the `/jobs/{jobId}/definition` with processingEntityType from Core.
 |2026-06-23 |None |Francis Charette-Migneault |all |Add the definitions for `created` status and pending job req/rec/per.
 |2026-06-23 |None |Francis Charette-Migneault |all |Clarify multiple ambiguities and permissions related to managing jobs updates.
+|2026-07-06 |None |Francis Charette-Migneault |all |Moved Provenance definitions from Part 4 (this document) to a dedicated Part 5.
 |===

extensions/job_management/standard/sections/clause_0_front_material.adoc

@@ -10,7 +10,9 @@ The OGC API - Processes - Part 2: Deploy, Replace, Undeploy draft specification
 
 The OGC API - Processes - Part 3: Workflows draft specification extends the core capabilities specified in OGC API - Processes - Part 1: Core [<<OAProc-1>>] with the ability to ...
 
-The OGC API - Processes - Part 4: Job Management draft specification extends the core capabilities specified in OGC API - Processes - Part 1: Core [<<OAProc-1>>] with the ability to create, manage and monitor jobs that are associated with processes execution. This part of the standard also defines how to ensure provenance information is preserved and findable.
+The OGC API - Processes - Part 4: Job Management draft specification extends the core capabilities specified in OGC API - Processes - Part 1: Core [<<OAProc-1>>] with the ability to create, manage and monitor jobs that are associated with processes execution.
+
+The OGC API - Processes - Part 5: Provenance draft specification extends the core capabilities specified in OGC API - Processes - Part 1: Core [<<OAProc-1>>] with provenance information associated with processes execution through associated jobs.
 
 CAUTION: This is a DRAFT version of the 4th part of the OGC API - Processes standards. This draft is not complete and there are open issues that are still under discussion.