Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend well-known discovery #202

Closed
m-mohr opened this issue Aug 20, 2019 · 2 comments
Closed

Extend well-known discovery #202

m-mohr opened this issue Aug 20, 2019 · 2 comments

Comments

@m-mohr
Copy link
Member

m-mohr commented Aug 20, 2019

Originates from Open-EO/openeo-hub#29

For the well-known discovery document, it may be helpful to add some more top-level fields, e.g. title and description.

@m-mohr m-mohr added this to the v1.0 milestone Aug 20, 2019
@m-mohr m-mohr changed the title Expand well-known discovery Extend well-known discovery Aug 20, 2019
@m-mohr
Copy link
Member Author

m-mohr commented Sep 13, 2019

I'm undecided about this. It is another place that you need to maintain a description in whereas the user may just look at the description of the newest version. I see that a title could still be useful though... @christophfriedrich

@m-mohr
Copy link
Member Author

m-mohr commented Oct 23, 2019

I think we can easily stick with the approach we use currently, it doesn't "bloat" the API so much with additional fields.
Well-known discovery just includes information that is important for selecting the appropriate version/instance of openEO. If clients want more information (e.g. title/description), they can connect to the most recent production-ready instance. I'll add some language regarding this to the API.

m-mohr added a commit that referenced this issue Oct 23, 2019
@m-mohr m-mohr closed this as completed Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant