Handling of terms-of-service and privacy-policy

[soxofaan]

from https://github.com/Open-EO/openeo-api/blob/master/CHANGELOG.md

Links with relation types terms-of-service and privacy-policy explicitly documented. Clients must handle them properly if present. #212

[m-mohr]

Related issue with a Web Editor example: Open-EO/openeo-api#212

[jonathom]

Do you already have the terms of service and privacy documents someplace?
you can assign me @jdries

[jdries]

Good point, we probably need to have them in the metadata.
However, we were just discussing this internally, and basically we're not sure if there's a good place to do this in a Python API. We rather think that users have to consent with our terms of service and privacy policy when they register for the account.

The problem is that it is hard to get explicit consent in the API itself. Also, a user that would use http requests directly, would have to agree with terms of service...

[jonathom]

That's also a good solution 👍

[m-mohr]

Here's a related issue that has an idea for it, which is inspired by the R client a bit: #216