From e7ba6866d4b3691342433ca4bf6c0189c2fb4266 Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Mon, 2 Sep 2024 13:48:00 +0200 Subject: [PATCH] ADES => OGC DRU --- dev/.words | 1 + meta/implementation.md | 18 +++++++++--------- proposals/run_ogcapi.json | 2 +- 3 files changed, 11 insertions(+), 10 deletions(-) diff --git a/dev/.words b/dev/.words index 846e729a..a8f3d8a9 100644 --- a/dev/.words +++ b/dev/.words @@ -48,3 +48,4 @@ Hyndman date1 date2 favor +Undeploy diff --git a/meta/implementation.md b/meta/implementation.md index 7eb6785e..67c4f0e6 100644 --- a/meta/implementation.md +++ b/meta/implementation.md @@ -239,15 +239,15 @@ OGC API - Processes and OGC EO Application Packages (AP) can generally be utiliz As a pre-defined process that exposes itself as a normal openEO process. It is not exposed to the user that in the background an AP is invoked. -2. **Pre-deployment through ADES** - - In addition to the openEO API, a provider can offer access to an [Application Deployment and Execution Service (ADES)](https://github.com/eoepca/proc-ades). - The ADES is likely external to the openEO API tree due to the conflicting `GET /processes` endpoint. - As such the ADES exposes itself in the `GET /` endpoint of the openEO API instance through a link. - The link must have the relation type `http://www.opengis.net/def/rel/ogc/1.0/processes`, which points to the ADES `/processes` endpoint. - Users can deploy APs through the ADES and use them through the process `run_ogcapi`. +2. **Pre-deployment through *OGC API - Processes - Part 2: Deploy, Replace, Undeploy*** + + In addition to the openEO API, a provider can offer access to an instance of *OGC API - Processes - Part 2: Deploy, Replace, Undeploy* (OGC DRU). + The OGC DRU instance is likely external to the openEO API tree due to the conflicting `GET /processes` endpoint. + As such the OGC DRU instance exposes itself in the `GET /` endpoint of the openEO API instance through a link. + The link must have the relation type `http://www.opengis.net/def/rel/ogc/1.0/processes`, which points to the `/processes` of the OGC API - Processes endpoint. + Users can deploy APs through the OGC DRU instance and use them through the process `run_ogcapi`. - If the provider doesn't offer an ADES itself, users could also deploy their AP with another provider. + If the provider doesn't offer an OGC DRU instance itself, users could also deploy their AP with another provider. In this case use the process `run_ogcapi_externally` instead. Example process node: @@ -257,7 +257,7 @@ OGC API - Processes and OGC EO Application Packages (AP) can generally be utiliz "process_id": "run_ogcapi", "arguments": { "data": ..., // Data, e.g. subtypes datacube or stac - "id": "my-ap", // Identifier of the application package in the ADES + "id": "my-ap", // Identifier of the application package in OGC API - Processes "context": { // Parameters as defined in the CWL file "cwl_param1": true, "param2": 99 diff --git a/proposals/run_ogcapi.json b/proposals/run_ogcapi.json index 72c37e63..9b54eb65 100644 --- a/proposals/run_ogcapi.json +++ b/proposals/run_ogcapi.json @@ -1,7 +1,7 @@ { "id": "run_ogcapi", "summary": "Run a OGC API process", - "description": "Runs an OGC API - Processes process that the service provider offers through an Application Deployment and Execution Service (ADES).", + "description": "Runs an OGC API - Processes process that the service provider offers through an instance of OGC API - Processes - Part 2 (Deploy, Replace, Undeploy).", "categories": [ "cubes", "import",