Skip to main content
search
All Posts By

Rob Dolin

Jun 18
Love0

One Last Call for Comments, so Finish Your Issue or PR

By Blog

With this blog post, we open a two-week last call for comments period for the OpenAPI Specification v3.

As mentioned last month, the OpenAPI Specification v3 is now entering a last call for comments period. You can find the latest release candidate of the OpenAPI Specification v3 at: https://github.com/OAI/OpenAPI-Specification/releases

At its meeting on Friday, 16 June, the Technical Developer Community (TDC) confirmed the below dates:

  • 4 weeks from 22 May through 16 June: to resolve remaining pull requests
  • 2 weeks from 19 June through 30 June: Comment period ← You are here
  • 2 weeks from 3 July through 14 July: to resolve remaining comments and issues
  • 1 week from 17 July through 21 July: release window (tentative)

Whether you haven’t looked at the spec since v2.0, or keep a well-worn copy of v3.0.0-rc1 next to your keyboard, this is the single best opportunity you will have to affect the spec draft before it is released.

Here are a few ways you can offer your feedback:

The OpenAPI Specification v3 is at a “release candidate” stage.  A few areas where comments would be particularly helpful are clarity of examples and descriptions of functionality.  Suggestions of new features or large changes to existing features are welcome, but in all likelihood will be considered only for a future release.

NOTE: Members of the TDC have expressed a preference for pull requests, since it makes the intention clearer, and since all changes must eventually pass through that stage. If you’re unable to submit a PR, an issue is the next best choice.

If you’re looking to generally learn more about the OpenAPI Spec v3, check-out:

Now playing: Closing Time by Semisonic

 

May 25
Love0

The Open API Initiative Is Sending You a Save the Date Card

By Blog

We’re getting close to OpenAPI Spec v3.0.0 final. If you’ve been waiting to start kicking the tires on the OpenAPI Specification (OAS) v3.0.0 (f.k.a. Swagger), now is the time to be prototyping or coding. Mark your calendar for a two-week last comment period from Monday, 19 June to Friday, 30 June, and watch for a final release in July.

On March 1st, the Open API Initiative (OAI) announced the publication of the first OpenAPI Specification v3.0.0 Implementer’s Draft. This release was tagged 3.0.0-rc0, and we had a subsequent release tagged 3.0.0-rc1 near the end of April.

At its meeting on Friday, 19 May, the Technical Developer Community (TDC) agreed to target the below timeline for release:

  • 4 weeks from 22 May through 16 June: Resolve remaining pull requests
  • 2 weeks from 19 June through 30 June: Comment period
  • 2 weeks from 3 July through 14 July: Resolve remaining comments and issues
  • 1 week from 17 July through 21 July: TENTATIVE release window

In case you’re not getting push notifications to your mobile device for every change into the OpenAPI Spec repo, here are some useful links:

As mentioned above, if you’re not already doing so, now is a great time to review the latest OpenAPI Spec v3.0.0, consider how your systems and tools can take advantage of the new functionality, and consider if anything could be improved before v3.0.0 final release.

Lastly, if you’re writing any kind of tool that uses the 3.0 draft spec in any way, please let us know by completing this very short survey, because only through implementing code against the draft spec can we gain confidence in its readiness!

Tony Tam
VP of Swagger Products at SmartBear Software
Jeremy Whitlock
Software Engineer at Google
Ron Ratovsky
Swagger Developer Evangelist at SmartBear Software
Darrel Miller
Software Developer at Microsoft
Marsh Gardiner
Product Manager at Google
Jason Harmon
Head of APIs at Typeform
Close Menu