Should we allow OpenAPI 3.0 or 3.1 spec version from /api?

[philvarner]

OGC API Part 5 will define using OpenAPI 3.1 spec for the service-desc
opengeospatial/ogcapi-features#404

After discussion at STAC API mtg today, I think we wait on this to see where Part 5 gets to.

[m-mohr]

Maybe not arbitrary, but maybe allow 3.0 and 3.1 (or 3.x) - OAFeat allows 3.0 in the core and is coming up with an extension for 3.1 so that seems to be a good choice, I think.

[m-mohr]

To recap the call a bit: OAFeat allows everything basically. Is there a good reason that we diverge from that? being future-proof makes sense (e.g. allow 3.1) so that we don't need to go STAC API 2.0 just because of this change.

Why has this been moved from beta.5 to 6?

[philvarner]

I re-wrote this to specify OpenAPI 3.0 or 3.1. However, I don't think we have a good reason for requiring that only those two can be used, so I'm in favor using the exact same language as OAFeat, and just recommending users use either OpenAPI 3.0 or 3.1

[m-mohr]

I fully agree with you.