Wrong CQL Text/JSON conformance classes

[m-mohr]

I think the CQL Text/JSON conformance classes are not correct. I haven't checked the implementation myself, just base my knowledge on the MS PC API deployment and the docs: https://stac-utils.github.io/stac-fastapi/api/stac_fastapi/extensions/core/filter/filter/#filterextension

• MSPC and docs: https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:cql-text and json equivalent
• The Filter extension indicates: http://www.opengis.net/spec/cql2/1.0/conf/cql2-text and json equivalent

Originally posted by @m-mohr in #371 (comment)

[gadomski]

@philvarner I believe @m-mohr is correct, stac-fastapi is doing it wrong, but if you don't mind can you double-check? E.g. I get this against the pgstac backend on current main (6db83a9):

$ curl -s http://localhost:8080/conformance | jq | grep cql-text
    "https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:cql-text",

[gadomski]

Once complicating factor, @m-mohr, is that http://www.opengis.net/spec/cql2/1.0/conf/cql2-text is a 404. So the spec itself seems to be wrong (or at least has broken dependencies). @philvarner can you advise?

[m-mohr]

OGC URIs often don't resolve, that's normal, I think. @gadomski
Same applies for example for http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30 and http://www.opengis.net/spec/ogcapi-features-3/1.0/conf/filter, which are used already.

[gadomski]

That's very weird, but OK, thanks.