Issue Open-EO#508 Clarify updating expiration of signed URL

Author: soxofaan

CHANGELOG.md

@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `GET /file_formats`: Base paramater on top of normal JSON Schema, not Process JSON Schema
 - `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`)
+- `GET /jobs/{job_id}/results`: Clarify that signed URLs (used as "canonical" link) should be regenerated each time.
 
 ## [1.2.0] - 2021-05-25
 

openapi.yaml

@@ -4031,9 +4031,11 @@ components:
             default.
 
             It is **strongly recommended** to add a link with relation type
-            `canonical`, which points to this STAC document using a signed URL.
-            This way the STAC metadata can be used by non-openEO clients
+            `canonical` pointing to this STAC document using a signed URL.
+            This signed URL allows consumption of the STAC metadata
+            by (possibly non-openEO) clients and tools
             without additional authentication steps.
+            It is recommended to regenerate the signed URL (and its expiry) with each request.
 
             For relation types see the lists of
             [common relation types in openEO](#section/API-Principles/Web-Linking).