The Collections extension

[pvretano]

This issue discusses and extension for making the /collections endpoint of any OGC Web API searchable using the OGC API Records core queryables and core query parameters.

If a server wants to make its /collections end-point queryable it has to do the following:

1. Add the appropriate conformance URIs to its /conformance document. There may be more than one depending on the level of query capability offered (e.g. http://www.opengis.net/spec/ocgapi-records-1/1.0/queryable-collections or http://www.opengis.net/spec/ocgapi-records-1/1.0/cql-queryable-collections).
2. Add the mandatory core queryables as keys in the collection object if those keys are not already there (see Issue Conformance classes #42).
3. Add zero or more optional core queryables to the collection object (see Issue Conformance classes #42).
4. Implement the core query parameters of the /collection end-point (see Issue Conformance classes #42)
5. The response is exactly what it would be if you fetched the /collections resource but the only collections listed would be the ones that satisfy the query predicates.

[pvretano]

16-NOV-2020: The feeling of the SWG is that this should remain as an extension. The core should only include those few things that everyone has to implement. However, since this has come up many times, we will start the re-chartering process at the next member meeting to add this work item to the charter so that we can work on it. Unofficially, some work has been done already and it will be removed from the core and archived until the charter gets updated.

[pvretano]

Closing: The collection extension has been absorbed into Part 1 and is called the "Local Resources Catalogue" conformance class.