Better example (openeo) domains #489 and minor clean-up

Open-EO · Apr 18, 2023 · 2370307 · 2370307
1 parent 380a756
commit 2370307
Show file tree

Hide file tree

Showing 3 changed files with 86 additions and 89 deletions.
diff --git a/extensions/commercial-data/README.md b/extensions/commercial-data/README.md
@@ -90,7 +90,7 @@ Example response from `GET /collections/PLEIADES/queryables`:
 ```json
 {
    "$schema":"http://json-schema.org/draft-07/schema#",
-   "$id":"http://example.com/commercial_data/PLEIADES/queryables",
+   "$id":"http://openeo.example/collections/PLEIADES/queryables",
    "type":"object",
    "title":"Queryables of Airbus Pleiades collection.",
    "description":"Available properties for CQL filtering of products.",

diff --git a/extensions/commercial-data/openapi.yaml b/extensions/commercial-data/openapi.yaml
@@ -18,15 +18,15 @@ tags:
   - name: Orders
     description: Management of commercial data orders
 servers:
-  - url: 'https://localhost/api/{version}'
+  - url: 'https://openeo.example/api/{version}'
     description: >-
       The URL of the API MAY freely be chosen by the back-end providers. The
       path, including API versioning, is a *recommendation* only. Nevertheless,
       all servers MUST support HTTPS as the authentication methods are not
       secure with HTTP only!
     variables:
       version:
-        default: v1.0
+        default: v1
         description: >-
           API versioning is RECOMMENDED. As the openEO API is following
           [SemVer](https://semver.org/) only the MAJOR part of the stable
@@ -130,7 +130,7 @@ paths:
                   unique identifier (ID) of the created order.
                 format: uri
                 type: string
-                example: 'https://example.openeo.org/api/orders/40264b5-c3ae-46f4-a907-0f612d763d97'
+                example: 'https://openeo.example/api/v1/orders/40264b5-c3ae-46f4-a907-0f612d763d97'
             OpenEO-Identifier:
               required: true
               schema: