OGC API conformance classes for Filter

[m-mohr]

To improve compatibility, I'd propose to also list the OGC API conformance classes for the filter extensions whenever one of our conformance classes fully includes one of theirs or if a set of our conformance classes map one of their conformance classes. This would help to make out ecosystem align more. I don't see a good reason (yet?) why we stick solely with custom conformance classes instead of mapping them whenever possible. In general, it would be great to have a list of how our conformance classes relate to the OGC API conformance classes.

[philvarner]

Good idea.

[philvarner]

OGC API conformance classes draft updated opengeospatial/ogcapi-features@29ab01f

[philvarner]

I ended up not adding a table, since we're not aligned except for one minor difference

[m-mohr]

I don't understand. My point was to add OGC API conformance URIs and I don't see them in the PR. Also, why are we completely misaligned with them?

[philvarner]

I typed that too quickly -- I meant to say were are aligned except for one minor difference (upper/lower function in Advanced Comparison Operators). All of the conformance classes are named the same, and all of the URIs have the same ending.

[m-mohr]

Ah, okay. But wouldn't it be more clear to just list them so that people can copy&paste them easily instead of have them search for them? From the docs it doesn't become directly clear how to "convert" the URLs (to get OGC API compliant), too, right?