Rename Remote UDP extension #540

Author: m-mohr

CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - **New extensions:**
-    - [Remote UDP Extension](./extensions/remote-udp/README.md)
+  - [Remote Process Definition Extension](./extensions/remote-process-definition/README.md)
 
 ### Fixed
 
@@ -24,8 +24,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - **New extensions:**
-    - [Commercial Data Extension](./extensions/commercial-data/README.md)
-    - [Federation Extension](./extensions/federation/README.md)
+  - [Commercial Data Extension](./extensions/commercial-data/README.md)
+  - [Federation Extension](./extensions/federation/README.md)
 - `GET /`: New Relation types: [#404](https://github.com/Open-EO/openeo-api/issues/404)
   - `create-form` to link to the registration page
   - `recovery-form` to link to the credentials recovery page.

README.md

@@ -29,11 +29,11 @@ See also the [changelog](CHANGELOG.md) and the [milestones](https://github.com/O
 
 ## Extensions
 
-| Name                                           | Version | Stability    | Description |
-| ---------------------------------------------- | ------- | ------------ | ----------- |
-| [Commercial Data](extensions/commercial-data/) | 0.1.0   | experimental | Provides an interface for discovering, ordering and using commercial data. |
-| [Federation](extensions/federation/)           | 0.1.0   | experimental | Covers federation aspects, i.e. where multiple back-ends are exposed as a single API. |
-| [Remote UDP](extensions/remote-udp/)           | 0.1.0   | experimental | Load user-defined processes that are hosted externally through the process namespace into process graphs. |
+| Name                                                               | Version | Stability    | Description |
+| ------------------------------------------------------------------ | ------- | ------------ | ----------- |
+| [Commercial Data](extensions/commercial-data/)                     | 0.1.0   | experimental | Provides an interface for discovering, ordering and using commercial data. |
+| [Federation](extensions/federation/)                               | 0.1.0   | experimental | Covers federation aspects, i.e. where multiple back-ends are exposed as a single API. |
+| [Remote Process Definition](extensions/remote-process-definition/) | 0.1.0   | experimental | Load user-defined processes that are hosted externally through the process namespace into process graphs. |
 
 ## Repository
 
@@ -44,7 +44,7 @@ This repository contains a set of files formally describing the openEO API, each
 * The [assets](assets/) folder contains some useful additional files such as examples or schemas. All of these are non-binding additions. The source of truth are the top-level specification files.
 * The [extensions](extensions/) folder contains extensions to the openEO API.
 
-# Development
+## Development
 
 The `draft` branch is the latest version and is the one to create Pull Requests against.
 

extensions/remote-udp/README.md renamed to extensions/remote-process-definition/README.md

@@ -1,17 +1,18 @@
-# Remote UDP Extension
+# Remote Process Definition Extension
 
 The openEO API is a specification for interoperable cloud-based processing of large Earth observation datasets.
 
 This extension enables user to load user-defined processes that are hosted external to the openEO API (e.g., GitHub or cloud storage) through the process namespace into process graphs.
 
 - Version: **0.1.0**
 - Stability: **experimental**
-- Conformance class: `https://api.openeo.org/extensions/remote-udp/0.1.0`
+- Conformance class: `https://api.openeo.org/extensions/remote-process-definition/0.1.0`
 
 ## Justification
 
 The openEO API defines the `namespace` property in a process node of a process graph as follows:
->  The following options are predefined by the openEO API, but additional namespaces may be introduced by back-ends or in a future version of the API.
+
+> The following options are predefined by the openEO API, but additional namespaces may be introduced by back-ends or in a future version of the API.
 > * `null` [...]
 > * `backend` [...]
 > * `user` [...]