Link to Web Editor instances

[m-mohr]

Some tools point to the Web Editor. We could think about exposing a link in the capabilities to a (custom) Web Editor instance, so that other clients (e.g. QGIS) can link to the custom instances (e.g. CDSE) instead of the generic instance.

Example:

{
  "href": "https://openeo.dataspace.copernicus.eu/",
  "rel": "web-editor",
  "type": "text/html",
  "title": "CDSE openEO Web Editor",
  "version": "0.14.0"
}

[m-mohr]

Any thoughts @soxofaan ?

[soxofaan]

yes, makes sense.

would that be a core feature, an extension, or just an adhoc convention?

[soxofaan]

what does the "version" in the snippet refer to?
If it's the version of the web editor: I don't think it should be the openEO backend's responsibility to track that.
E.g. in CDSE, the openEO backend(s) and web editor deployments are completely decoupled

[m-mohr]

would that be a core feature, an extension, or just an adhoc convention?

I'd just add it to the core as one of the additional, optional link relation types. There's already a long list of proposed relation types in the current API.

would that be a core feature, an extension, or just an adhoc convention?

The version of the Web Editor. It's meant for feature tracking to some extent. If we change something in a breaking version in the Web Editor (e.g. in 1.0), this would help the client identify the version and handle it accordingly. I don't think we need to tackle the patch level changes for example so version "1" or "0.14" would be enough and could probably be hardcoded.

[soxofaan]

I'd just add it to the core as one of the additional, optional link relation types. There's already a long list of proposed relation types in the current API.

👍

The version of the Web Editor. It's meant for feature tracking to some extent. If we change something in a breaking version in the Web Editor (e.g. in 1.0), this would help the client identify the version and handle it accordingly.

I understand the why, but I'm not sure about the how.
Isn't it better to leave this to a capability/version discovery mechanism between the client and web editor, instead of letting the backend be in charge of this (while it should be client-agnostic).

[m-mohr]

There's no reliable way to get the version from the Web Editor yet. Maybe there should be?

[soxofaan]

That's probably going to be useful once you are going to make breaking changes in some sense, but not urgent to have at the moment, I guess.
Nor blocking for this link-rel issue