Just a heads up that we're now looking at adding our first OAS 3.0.x definitions to the directory. To distinguish them, the filenames will be openapi.yaml/openapi.json but everything else should be the same. At the moment there is no plan to downconvert these definitions to OAS 2.0 - please let me know if either of these considerations are likely to be a problem for you.
@MikeRalphson I've had some trouble with the downconverting when I experimented with it. AFAICT the MIME-types on a method are lost, i.e. don't translate to produces/consumes
Good to know. Maybe we can start a to do list issue on api-spec-converter? At the moment the downconverter moves things around OK, but doesn't do all the necessary conversions to eg parameters and schemas.
Sounds good. is it this project? https://github.com/LucyBot-Inc/api-spec-converter
Yep, that's the one.
I've filed an issue about this specific case
Great, thanks.
FYI, yesterday I gave a talk to dive into this topic as part of an interview process. I'm quite intrigued by this problem space and can see some interesting tasks to work on: https://steveej.github.io/slides/zhaw-techtalk-0/#36 feel free to take a look from the beginning and start discussing with me, pointing me to things, or both
That's a really good overview of where OpenAPI sits now and where its going. My only nitpick is that OAS 3.0.0 was released in 2017. You may be interested in the 3.1 roadmap issue on the OAS repository OAI/OpenAPI-Specification#1466
@MikeRalphson fixed, thanks :-)