From 684715990e7912eb098ce7fc4725305550b2cd6e Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Mon, 9 Sep 2024 16:02:18 +0200 Subject: [PATCH] Add planned steps --- crosswalks/ogcapi-processes.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/crosswalks/ogcapi-processes.md b/crosswalks/ogcapi-processes.md index 695e32ae..6f979078 100644 --- a/crosswalks/ogcapi-processes.md +++ b/crosswalks/ogcapi-processes.md @@ -233,22 +233,22 @@ Each job complies to the structure discussed in [Job status](#job-status). - OAP1: `GET /jobs/{jobID}` Similar properties in OAP1 and openEO: -- `jobID` (required) / `id` (required) -- `processID` (string) / `process` (required, object containing chained processes) -- `status` (required, below: OAP1 | openEO) +- `jobID` (required) / `id` (required) -> OAP1 changes to `id` +- `processID` (string) / `process` (required, object containing chained processes) -> openEO doesn't require it +- `status` (required, below: OAP1 | openEO) -> OAP1 switches to openEO status codes - *n/a* | created - accepted | queued - running | running - successful | finished - failed | error - dismissed | canceled -- `created` (required in openEO only) +- `created` (required in openEO only) -> OAP1 to require `created` - `updated` - `progress` - `links` ([to be added to openEO](https://github.com/Open-EO/openeo-api/issues/495)) Additional properties in OAP1: -- `type` (required) (always: `process`) +- `type` (required) (always: `process`) -> openEO to add `type: "openeo"` (potentially not required with default value `openeo`) - `messsage` (-> use logs in openEO) - `started` (-> use logs in openEO) - `finished` (-> use logs in openEO)