Skip to content
New issue

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

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

Already on GitHub? # to your account

Implementations for new task "Queries"/"Search" #528

Open
cportele opened this issue Mar 21, 2021 · 2 comments
Open

Implementations for new task "Queries"/"Search" #528

cportele opened this issue Mar 21, 2021 · 2 comments

Comments

@cportele
Copy link
Member

A new part "Queries" (or "Search") will specify the Query resource (path element ”search”) supporting GET and POST. The Query resource at path “/search” will support multi-collection queries, the Query resource at path “/collections/{collectionId}/search” will support queries on a single collection. Support for stored/persistent queries will be considered.

Before we assign a new part number to a new task and start to work on a new document, we need commitments for three independent implementations for each proposed conformance class.

If you have an interest in this extension, please consider to commit to implementing this extension and let us know in a comment to this issue.

Relevant links:

@pvretano
Copy link
Contributor

CubeWerx commits to an implementation.

@cportele
Copy link
Member Author

cportele commented Mar 22, 2021

interactive instruments commits to implementing the extension in ldproxy except joins and standing queries. We also do not plan to implement GML requirements classes, if those will be part of the spec.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
Development

No branches or pull requests

2 participants