OAS 3.0 introduces a new, more simplified structure.

Simplified structure, with increased reusability

In this article, we will share some of the major updates in the latest version of OAS, and breakdown what you need to know when transitioning to OAS 3.0. But we also wanted to provide a more detailed breakdown, with clips and key takeaways from the presentation. The full video of our discussion is available here. In the 60-minute presentation, the speakers shared their insight on how the specification has been restructured, what new features they’re most excited about, and how API teams can start to transition to OAS 3.0. OAS 3.0 was the first major release since the specification was donated to the OpenAPI Initiative, and renamed from the Swagger Specification to OpenAPI Specification in 2015.Īt the end of last year, we had the opportunity to be joined by two members of the OpenAPI Initiative, Ron Ratovsky, member of the OAI Technical Steering Committee (and Swagger Developer Evangelist here at SmartBear), and Ole Lensmar, Chair of the OAI board, for a discussion on the newest features and enhancements in OAS 3.0. The latest version of the OpenAPI Specification, OpenAPI 3.0 (OAS 3.0), was released last year and is already gaining adoption from API developers and organizations looking to standardize on OAS.

Swagger editor 3.0 openapi