Support OpenApi Specification 3.1

[westse]

Is your feature request related to a problem? Please describe.
OAS 3.1 is the future, and swagger has added support. What is needed for specmatic to support 3.1? Can the effort be broken up into smaller steps? How can the community help?

Describe the solution you'd like
All existing specmatic features should work against OAS 3.1 api specifications.

Describe alternatives you've considered
OAS 3.0.x works for now but projects using specmatic that want to move to OAS 3.1 are either blocked or are forced to abandoned specmatic.

[harikrishnan83]

hello @westse, The suggestion to break the effort of OpenAPI 3.1 support into smaller tasks is a good idea. As a first step we plan to isolate OpenAPI 3.0.x related code such that we can add OpenAPI 3.1 related parsing capability. We will keep you posted on this. Thanks. cc @joelrosario @jaydeepk

[hernaneg350]

I don't mean to put pressure, just wanted to know if I can help contribute in any way. This is preventing us from being able to adopt Specmatic, and we are really looking forward to implement it in our org.

[ipichris]

Im confused. This issue is linked on the roadmap (https://specmatic.in/roadmap/) as "completed" in Q4/2023.
Is there OpenAPI 3.1 support? If no when will it be implemented?