Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
m-mohr authored Sep 2, 2024
1 parent 7f883c1 commit b5cd5af
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions meta/implementation.md
Original file line number Diff line number Diff line change
Expand Up @@ -233,15 +233,15 @@ We have found some libraries that can be used for an implementation:

## OGC API - Processes

OGC API - Processes and OGC EO Application Packages (AP) can generally be unilized in openEO in three different ways:
OGC API - Processes and OGC EO Application Packages (AP) can generally be utilized in openEO in three different ways:

1. **openEO process**

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).
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.
Expand Down

0 comments on commit b5cd5af

Please sign in to comment.