Feature Request: Support OpenAPI spec 3.1.0

[Yuutakasan]

2021/02/17 OpenAPI spec 3.1.0 release please support.

https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0

[Yuutakasan]

@EricWittmann It seems to be quite difficult to add the OpenAPIO Spec3.1 WebHook settings, especially if the path parameter settings that I would like to add change to optional, which would affect the parser, validation, and other settings.

Do you have any plans to support this one?

[EricWittmann]

We certainly do want to add support for OAI 3, but are having a hard time finding the bandwidth to do it. That said, we're currently working on a new managed service here at Red Hat that will use the OpenAPI and AsyncAPI editors we've built as part of Studio. So my hope is that we'll have some time to spend on the editors to fix some bugs and upgrade them to support newer versions of those specs.

[Yuutakasan]

@EricWittmann I see. Certainly, with Async API support, we could Webhook and Callback support is not necessary. Eric, do you think that using Async API to link APIs will become the industry standard in the future, rather than using OpenAPI spec + OpenAPI generator to support webhooks?

[EricWittmann]

I think it really depends on the use-case. For actual asynchronous APIs (APIs based on messaging technologies like Kafka or JMS) I would expect that AsyncAPI will become the standard. But for REST APIs with the occasional webhook, I think those elements will remain relevant on OpenAPI. I'm hoping that no one will use OpenAPI to describe real event-based architectures!