search

Open-EO / openeo-api

The openEO API specification
http://api.openeo.org
Apache License 2.0
91 stars 11 forks source link

License for UDP? #531

Closed m-mohr closed 3 months ago

m-mohr commented 6 months ago

A license field for user-defined processes might be a good idea.

soxofaan commented 6 months ago

How do you envision this information to be consumed? Just as a visualization thing or should clients/backends check licences against allow-lists in some way?

m-mohr commented 6 months ago

Just for consumption, i.e. if you wish to publish your algorithm somewhere... Came up in alignment discussions with OGC API - Processes, which have such a field.

soxofaan commented 6 months ago

Other related metadata fields that could be considered or might be relevant to the discussion: author and version (as discussed earlier in https://github.com/Open-EO/openeo-api/issues/480 )

This is not meant as scope-creep for this ticket, but it could help to to decide if you want to put all this kind of metadata at the object top level, or group things under a more generic "metadata" field (e.g. to isolate free-form metadata from more standardized properties)

m-mohr commented 4 months ago

Agreed, maybe we can take over these fields from STAC.

soxofaan commented 3 months ago

Another thing to consider here is a changelog (or link to one)

m-mohr commented 3 months ago

I just realized we already have a solution for license and changelog in the links:

{
  "rel": "version-history",
  "href": "http://openeo.example/changelog.txt",
  "type": "text/plain",
  "title": "Changelog"
}

and 

{
  "rel": "license",
  "href": "http://openeo.example/license.txt",
  "type": "text/plain",
  "title": "License: CC-BY-4.0"
}
m-mohr commented 3 months ago

See PR #536 for a clarification in the spec.