search

opengeospatial / ogcapi-records

An open standard for the discovery of geospatial resources on the Web.
https://ogcapi.ogc.org/records
Other
56 stars 26 forks source link

cql-filter requirements class without conformance class #284

Closed ycespb closed 1 year ago

ycespb commented 1 year ago

The specification uses a requirements class URI for cql-filter ( http://www.opengis.net/spec/ogcapi-records-1/1.0/req/cql-filter) while other capabilities are identified by their conformance class (e.g. in https://docs.ogc.org/DRAFTS/20-004.html#_core). Should there not be a corresponding "conformance class" URI and should the conformance class URI /conf/ be listed in the /conformance response or should the /req/ URI be included in the /conformance response or none of the two ? The same /req/ URI is borrowed by STAC where it is used as "conformance class". See also https://github.com/stac-api-extensions/collection-search/issues/9 .

m-mohr commented 1 year ago

Related to #283, I guess.

pvretano commented 1 year ago

Actually, all the conformance URIs referenced in the permission should be references to requirements. I should also update the URI to be /req/searchable-catalogue/requirements rather than /req/searchable-catalogue/conformance. These requirement URIs are not meant to be listed in the /conformance declaration; those are actually listed here.