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
URL query strings #10
Comments
Hi Si, Yeah this is an awkward one. Query parameters are absolutely allowed and encouraged. It would be great if Hydra could help us, but this part of the Hydra standard remains non-existent after five years. The query parameters you do use though should be described, possibly by templated links. There are some other standards or approaches people have adopted to filtering, that are able to accommodate more sophisticated filters than just exact matches. I think we need to look at a few and settle on one. Other people have had the same issue. There's a good review here. Do you like the look of any of those approaches? L |
Templated links seem ok. Although I'm not entirely sure where I'd see this information. E.g. would it be included in the response from a request to I'd probably veer towards the |
I think that's right, you simply extend your Happy to go with your suggestion of I think the real fun begins when we start to consider spatial filtering on collections. Bounding box seems like an obvious MVP, but do we also need distance within a point for radial searches etc? How would that be expressed as an |
Closing this as discussion on these matters is continuing in #18. |
Are we allowed to use query strings? If so are they any regulations we should be abiding by?
For example, let's say I want to request a list of all the deployments that are open to the public. Therefore my URL may look like this:
https://urbanobservatory.bham.ac.uk/deployments?public=true
Is this ok?
I remember hydra being mentioned, but I can't obviously see anything on there about this.
The text was updated successfully, but these errors were encountered: