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

Overview: view #348

Closed
jerstlouis opened this issue Nov 21, 2024 · 1 comment
Closed

Overview: view #348

jerstlouis opened this issue Nov 21, 2024 · 1 comment
Labels
Part 2 Issues to be resolved prior to TC vote

Comments

@jerstlouis
Copy link
Member

jerstlouis commented Nov 21, 2024

Review the text around Views, viewId in particular should be avoided, because not only access mechanisms / view resources are immediately after /collections/, but also things like /schema and /metadata.

Review text saying:

The view identifiers are maintained as a controlled vocabulary by the OGC.

Perhaps clarify that this could be a Naming Authority check list item to register / avoid clashes with these collection resources when publishing OGC API standards ?

@joanma747
Copy link
Contributor

View suggests a "read only" path. That is not the case for /items or /coverage. This could be an argument about using this term and go back to "representations" or "access pattern". The #140 discusses how to call this in depth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Part 2 Issues to be resolved prior to TC vote
Projects
Development

No branches or pull requests

2 participants