The Open API Initiative (OAI) announces the OpenAPI Specification v3.0.0

As you may have read in my most recent blog post on the IBM Code site, containers continue to be a hot topic, and progress is being made on the open container technology front – thanks to the community supporting the Open Container Initiative. Enterprises use containers to build agile software delivery pipelines faster, more securely and consistently.

But that is only one of three key elements that I think of when the topic of “Cloud-native” application development comes up. The other two are APIs and Micro-services. Many developers today know that Micro-services oriented applications are ones in which the key elements are broken down into smaller services, which are loosely coupled with dependencies explicitly described. This approach significantly increases the overall agility and maintainability of applications – as opposed to a more traditional, monolithic application development approach.

Lastly, APIs are the glue that hold together an applications collection of micro-services and containers. They provide pathways through which micro-services communicate with each other. APIs provide access to data sources, whether local or remote. APIs are most valuable for creating new business models and streamlining selling strategies across all channels. They removing barriers to growing revenue by integrating platforms and applications so businesses can quickly launch new revenue models and scale fast.

Creating an open description format for API services that is vendor neutral, portable and open is critical to ensure that your organization can leverage API tooling from a number of like-minded companies without falling under the control of any single vendor’s approach. That is why back in November of 2015 IBM in conjunction with eScale, Apigee, Capital One, Google, Intuit, Microsoft, PayPal and Restlet announced the formation of the Open API Initiative. It was based on the open source project called Swagger, started by Tony Tam back in 2010.

I first met Tony at the Apigee offices in downtown San Jose in January of 2015, and am proud that IBM provided early guidance as Tony and the Swagger community considered their options prior to electing to donate the donated the Swagger specification to the Linux Foundation. It is widely recognized as the most popular open source framework for defining and creating RESTful APIs, and today tens of thousands of developers are building thousands of open source repos of tools leveraging the OpenAPI Specification.

Is this most of this new news for you? If so, you might want to check out this short video as Angel Diaz, IBM VP Developer Technology and Advocacy introduces Tony Tam’s “History of Swagger and the Open API Initiative” lightning talk at the IBM Open Tech Summit at Interconnect 2016.

The Open API Initiative Delivers v3.0.0 Specification

On July 26, the Open API Initiative (OAI) announced the 3.0.0 release of the OpenAPI Specification. The OAI provides a foundation for developing interoperability of APIs and other technologies. The full OAI press release is here, but I like the IBM quote:

“The OAI has progressed this specification relatively quickly, and the IBM Cognitive Cloud and API Economy teams are set to embrace this new, open specification”, said Todd Moore, VP of Open Technology, Digital Business Group at IBM. “By helping to establish the OAI, IBM joined with other companies who understand that robust, scalable, and secure APIs for enterprise systems form the basis of modern digital ecosystems. In addition, today’s software developers want open tooling to help them quickly and consistently create APIs to accelerate business transformation. Our clients trust IBM to help them manage their entire API management life-cycle.”

Looking for the v3.0.0 specification details? Check out the OAI GitHub repo here. In addition to the successful completion of the specification, another indicator of a successful project is the continued growth and diversity in project membership. The Open API Initiative has swelled to 27 members in the last 18 months and continues to accelerate beyond API vendors to include leaders in banking, healthcare, and governments worldwide.

Want to connect? Follow me @jeffborek and DM me if you have something positive to share, or thoughts on how to make things better.

See you next time!

Join The Discussion

Your email address will not be published. Required fields are marked *