Align with OGC API Commons?

[m-mohr]

Should we try to align with OGC API Commons? I think we are already partially there:

• / is (mostly?) compatible
• /collections and /collections/{collectionId} are compatible with WFS3. Will probably evolve a little more and we need to add the basic query parameters. But nothing fancy.
• We may need to add /conformance and /api, but that's not a big deal.

Then we then we could basically apply to be an OGC API ;-) , though we are not following WPS yet and may never do. I guess we'll find out once the Hackathon is done and they have a more stable version of OGC API Commons.

[m-mohr]

Interesting points to think about:
opengeospatial/ogcapi-features#236
opengeospatial/ogcapi-features#248 (comment)

[m-mohr]

We'll add this to a Tiles (WFS/STAC Items) extension.

[m-mohr]

API is already mostly(?) OGC API - Features compliant, I added /conformance recently and also the other links and updated /. If OGC API Commons diverges from OGC API - Features, we need to see how that evolves overall.

[m-mohr]

OGC API Commons will not be ready until the project ends. Thus we are sticking with OGC API Features 1.0 for now and may revisit this in the future.

[m-mohr]

For 1.2.0 and OGC submission we should consider adding some openEO related conformance classes to /conformance:

• Each extension gets one
• openEO API itself gets one
• ...