v1.3.0 release + extensions

Author: m-mohr

CHANGELOG.md

@@ -4,13 +4,24 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Unreleased / Draft
+## [Unreleased] / Draft
+
+### Added
+
+### Deprecated
+
+### Changed
+
+### Fixed
+
+## [1.3.0] - 2026-02-02
 
 ### Added
 
 - **New extensions:**
   - [Remote Process Definition Extension](./extensions/remote-process-definition/README.md)
   - [Processing Parameters Extension](./extensions/processing-parameters/README.md)
+  - [Workspaces Extension](./extensions/workspaces/README.md)
 - `GET /`: New relation type `web-editor` [#577](https://github.com/Open-EO/openeo-api/issues/577)
 - `GET /credentials/oidc`: Added `authorization_parameters` property to enforce specific parameters for the authorization endpoint [#534](https://github.com/Open-EO/openeo-api/issues/534)
 - `POST /result`: Added response header "OpenEO-Identifier" to expose an identifier associated with a synchronous processing request.
@@ -24,17 +35,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Deprecated
 
 - Deprecated the openEO-specific Bearer token format (authentication mechanism/provider id/access token) [#558](https://github.com/Open-EO/openeo-api/issues/558)
-
-### Changed
-
-- Migrate from openEO-specific tokens to JWT, i.e. deprecating the openEO-specific format in favor of JWT [#558](https://github.com/Open-EO/openeo-api/issues/558)
-
-### Deprecated
-
 - STAC 0.9.x
 
 ### Changed
 
+- Updated Federation Extension to v0.2.0
+- Migrate from openEO-specific tokens to JWT, i.e. deprecating the openEO-specific format in favor of JWT [#558](https://github.com/Open-EO/openeo-api/issues/558)
 - `GET /`: Requires the fields `type` and `conformsTo`
 - `GET /udf_runtimes`: Requires at least one UDF runtime to be provided. [#511](https://github.com/Open-EO/openeo-api/issues/511)
 
@@ -479,6 +485,7 @@ Initial version.
 
 
 [Unreleased]: <https://github.com/Open-EO/openeo-api/compare/master...dev>
+[1.3.0]: <https://github.com/Open-EO/openeo-api/compare/1.2.0...1.3.0>
 [1.2.0]: <https://github.com/Open-EO/openeo-api/compare/1.1.0...1.2.0>
 [1.1.0]: <https://github.com/Open-EO/openeo-api/compare/1.0.1...1.1.0>
 [1.0.1]: <https://github.com/Open-EO/openeo-api/compare/1.0.0...1.0.1>

README.md

@@ -6,12 +6,13 @@ openEO develops an open API to connect R, Python and JavaScript clients to big E
 
 ## Versions / Branches
 
-The [master branch](https://github.com/Open-EO/openeo-api/tree/master) is the 'stable' version of the openEO API specification. It is currently version **1.2.0** of the specification. The [draft branch](https://github.com/Open-EO/openeo-api/tree/draft) is where active development takes place.
+The [master branch](https://github.com/Open-EO/openeo-api/tree/master) is the 'stable' version of the openEO API specification. It is currently version **1.3.0** of the specification. The [draft branch](https://github.com/Open-EO/openeo-api/tree/draft) is where active development takes place.
 
 | Version / Branch                                          | Status      | Description |
 | --------------------------------------------------------- | ----------- | ----------- |
 | [draft](https://api.openeo.org/draft)                     | planned     | *Unstable* - Next version. |
-| [**1.2.0**](https://api.openeo.org)                       | **current** | Clarifications, new extensions, vector data cubes, STAC (API) updates, more link relation types, improved batch job results and logs. [Changelog](CHANGELOG.md#120---2023-05-31). |
+| [**1.3.0**](https://api.openeo.org)                       | **current** | Clarifications, Remote Process Definition and Processing Parameters extensions, new token format, batch job improvements, etc. [Changelog](CHANGELOG.md#130---2026-02-02). |
+| [1.2.0](https://api.openeo.org/1.2.0)                     | legacy      | Clarifications, Commercial Data and Federation extensions, vector data cubes, STAC (API) updates, more link relation types, improved batch job results and logs. [Changelog](CHANGELOG.md#120---2023-05-31). |
 | [1.1.0](https://api.openeo.org/1.1.0)                     | legacy      | Clarifications, STAC updates, return value for child processes, more details for logs and jobs, default clients for OIDC. [Changelog](CHANGELOG.md#110---2021-06-15). |
 | [1.0.1](https://api.openeo.org/1.0.1)                     | legacy      | Clarifications, bugfixes and CORS improvements. [Changelog](CHANGELOG.md#101---2020-12-07). |
 | [1.0.0](https://api.openeo.org/1.0.0)                     | legacy      | First stable version of openEO. [Changelog](CHANGELOG.md#100---2020-07-17). |
@@ -32,9 +33,10 @@ See also the [changelog](CHANGELOG.md) and the [milestones](https://github.com/O
 | 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. |
+| [Federation](extensions/federation/)                               | 0.2.0   | experimental | Covers federation aspects, i.e. where multiple back-ends are exposed as a single API. |
 | [Processing Parameters](extensions/processing-parameters/)         | 0.1.0   | experimental | Explore and handle additional processing parameters that a back-end can offer for the processing modes (sync. processing, batch jobs, web services). |
 | [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. |
+| [Workspaces](extensions/workspaces/)                               | 0.1.0   | experimental | Connect external file storage systems (e.g. cloud buckets) to openEO back-end implementations. |
 
 ## Repository
 

extensions/federation/README.md

@@ -4,9 +4,9 @@ The openEO API is a specification for interoperable cloud-based processing of la
 
 This is an extension for federation aspects, i.e. where multiple back-ends are exposed as a single API.
 
-- Version: **0.1.0**
+- Version: **0.2.0**
 - Stability: **experimental**
-- Conformance class: `https://api.openeo.org/extensions/federation/0.1.0`
+- Conformance class: `https://api.openeo.org/extensions/federation/0.2.0`
 
 **Note:** This document only documents the additions to the specification.
 Extensions can not change or break existing behavior of the openEO API.
@@ -84,7 +84,7 @@ schema:
 
 ```json
 {
-  "api_version": "1.2.0",
+  "api_version": "1.3.0",
   "federation": {
     "vito": {
       "title": "VITO",

extensions/workspaces/README.md

@@ -10,4 +10,4 @@ The Workspace Extension to the openEO API provides an interface for connecting e
 **Note:** This document only documents the additions to the specification.
 Extensions can not change or break existing behavior of the openEO API.
 
-The Workspace API is inspired by the [EOEPCA Workspace API](https://github.com/EOEPCA/rm-workspace-api) with regards to workspace management.
+The Workspace API is inspired by the [EOEPCA Workspace API](https://github.com/EOEPCA/rm-workspace-api) with regards to workspace management.

openapi.yaml

@@ -1,11 +1,11 @@
 openapi: 3.0.2
 info:
   title: openEO API
-  version: 1.2.0
+  version: 1.3.0
   description: |-
     The openEO API specification for interoperable cloud-based processing of large Earth observation datasets.
 
-    **Conformance class:** `https://api.openeo.org/1.2.0`
+    **Conformance class:** `https://api.openeo.org/1.3.0`
 
     # API Principles
 
@@ -629,7 +629,7 @@ paths:
                       Version number of the openEO API specification the back-end
                       implements.
                     enum:
-                      - 1.2.0
+                      - 1.3.0
                   backend_version:
                     type: string
                     description: >-
@@ -1029,9 +1029,9 @@ paths:
               example:
                 versions:
                   - url: 'https://openeo.example/api/v0'
-                    api_version: 0.5.1
+                    api_version: 0.4.2
                   - url: 'https://openeo.example/api/v1'
-                    api_version: 1.2.0
+                    api_version: 1.3.0
                   - url: 'https://dev.openeo.example/api/v2'
                     production: false
                     api_version: 2.0.0-beta
@@ -1212,7 +1212,7 @@ paths:
         Otherwise, the implemented functionality can usually be retrieved from
         the [capabilities](#tag/Capabilities/operation/capabilities) in openEO.
 
-        The general openEO conformance class is `https://api.openeo.org/1.2.0`.
+        The general openEO conformance class is `https://api.openeo.org/1.3.0`.
         See the individual openEO API extensions for their conformance classes.
 
         The conformance classes listed at this endpoint and listed in the 
@@ -1694,7 +1694,7 @@ paths:
                       Clients must be able to handle multiple process specification versions at the same time.
                       
                       This is **not** the openEO API specification version.
-                    example: 1.2.0
+                    example: 2.0.0
                   processes:
                     type: array
                     items:
@@ -3776,16 +3776,16 @@ components:
         implementation conforms to. Conformance classes are commonly used in
         all OGC API standards and the STAC API specification.
 
-        The general openEO conformance class is `https://api.openeo.org/1.2.0`.
+        The general openEO conformance class is `https://api.openeo.org/1.3.0`.
         See the individual openEO API extensions for their conformance classes.
       type: array
       items:
         type: string
         format: uri
       example:
-        - https://api.openeo.org/1.2.0
+        - https://api.openeo.org/1.3.0
         - https://api.openeo.org/extensions/commercial-data/0.1.0
-        - https://api.openeo.org/extensions/federation/0.1.0
+        - https://api.openeo.org/extensions/federation/0.2.0
         - https://api.stacspec.org/v1.0.0/core
         - https://api.stacspec.org/v1.0.0/collections
     udf_runtime:
@@ -6807,7 +6807,7 @@ components:
 
         1. **JSON Web Token (JWT) - RECOMMENDED**
 
-           - Conformance class: `https://api.openeo.org/1.2.0/authentication/jwt`
+           - Conformance class: `https://api.openeo.org/1.3.0/authentication/jwt`
            
            The Bearer token is an access token in [JWT](https://datatracker.ietf.org/doc/html/rfc7519) format
            as defined in RFC 7519. For openEO, it MUST include the issuer in the

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openeo/api",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "author": "openEO Consortium",
   "license": "Apache-2.0",
   "description": "The openEO API specification.",