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

What to do with "api" term? #2

Open
letmaik opened this issue Jan 31, 2016 · 0 comments
Open

What to do with "api" term? #2

letmaik opened this issue Jan 31, 2016 · 0 comments

Comments

@letmaik
Copy link
Contributor

letmaik commented Jan 31, 2016

Currently, http://coverageapi.org/ns#api is used as a generic term for interfacing with a server API with the help of URL templates, as used by Hydra. Hydra itself currently defines only the "search" term and possibly in the near future "filter" (subproperty of "search"), however this doesn't fit to all coverage API use cases, since we also have operations like "embedding" and "subsetting". Looking at WCS as a reference, there are many more parameters that a server could offer like reprojection and interpolation.

It would be better to have a more concrete term than just "api". Maybe "query"? The term must be able to capture most concepts offered by common coverage data APIs, which are filtering, subsetting, transformation, ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant