Document additional relation types for process metadata #531

Author: m-mohr

CHANGELOG.md

@@ -12,6 +12,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `PATCH /services/{service_id}` and `PATCH /jobs/{job_id}`: Explicitly allow updating back-end specific properties (as in `POST`)
 - `GET /services/{service_id}` and `GET /jobs/{job_id}`: Explicitly allow listing back-end specific properties (as provided in `POST`)
 - Clarified for log levels which default values apply
+- Clarified how the relation types `license`, `version-history` and `author` can be used to enrich the process metadata. [#531](https://github.com/Open-EO/openeo-api/issues/531)
 
 ## [1.2.0] - 2021-05-25
 

openapi.yaml

@@ -5262,11 +5262,19 @@ components:
             (link to older version) and `successor-version` (link to newer version) can also be used
             to show the relation between versions.
 
+            2. `version-history`: A link to a changelog and/or a list of versions of the process
+            (see also the relation types `latest-version` etc.).
+
             2. `example`: Links to examples of other processes that use this process.
 
             3. `cite-as`: For all DOIs associated with the process, the respective DOI
             links SHOULD be added.
 
+            4. `license`: Links to applicable license(s). The link titles should reflect the license names.
+
+            5. `author`: Links to authors of the process. The `href` can use the `mailto:` protocol to
+            link to an email address. The link titles should reflect the author names and affiliations.
+
             For additional relation types see also the lists of
             [common relation types in openEO](#section/API-Principles/Web-Linking).
           items: