When RepreZen joined the OpenAPI Initiative last year, I waxed poetic in a guest post about OpenAPI as a REST API description language:
A lot of API providers have been waiting to upgrade from OpenAPI 2.0 to 3.0 as their go-to API description language. Most have been looking for two things: (1) signs of broader adoption; and (2) more robust tool support.
RepreZen API Studio is now based on a newer version of Eclipse. What does it mean for API developers? Better look-and-feel and improved usability mean more time to work on the fun stuff, so you can create better APIs faster.
I'm excited to be speaking at several upcoming events, each with an impressive lineup of workshops, talks, and outstanding opportunities to learn and network with API thought leaders.
OpenAPI is an extensible language. And over the past few days, I've been exploring new ways to make those language extensions more discoverable and easier to use.
KaiZen OpenAPI Editor is an Eclipse-based editor for the OpenAPI Specification (OAS). OpenAPI v2, formerly known as the Swagger specification, is the most widely used and supported API description language, and OpenAPI v3 is a new major version, released in July 2017 with significant new features and improvements.
Are you excited about OpenAPI 3.0?
Here's why it matters: The Swagger 2.0 specification was released 2½ years ago, emerging as the de facto industry standard for API definition and documentation. SmartBear made it official a year later, in November 2015 with the formation of the OpenAPI Initiative under the Linux Foundation, with Google, IBM, Microsoft and others as founding members.
The next generation of API modeling is now here. With the OpenAPI Spec v3 Draft release, developers can describe a broader range of modern REST APIs in greater detail, including hyperlinks, webhooks, better JSON Schema support, rich examples, and more.
At RepreZen, we're excited and working hard to bring the full range of OpenAPI 3.0's expanded capabilities into the RepreZen API Studio design experience. KaiZen OpenAPI Parser, now available on GitHub, is the first cornerstone of our open source stack for OpenAPI 3, based on the draft spec. It's built for speed, and highly configurable. If you're building OpenAPI 3 tooling or solutions in Java, this is a great place to start.
APIs are the neural connections of the digital economy, allowing systems to connect, collaborate, and converse with meaningful data. But these connections don't start with fully working APIs; they start with API design.
When I started out in this business back in 1999, my first job was with a small and thriving consultancy in Rotterdam, Holland called 'Holland Object Technology' or 'HOT Objects' for short (may it RIP). One of the first conversations I recall having at this wonderful, creative little company was with my boss - a 6'6" former Dutch army sargeant with an incredible intellect and vast experience. "What's great about this business," he said, "is that you can have an idea for a steam engine in the morning - and watch it running on the lawn in the afternoon!"
He had captured the essence of what I really enjoyed about software engineering: the rapidity with which one could be creative, the almost magical speed (when compared with classical professions like 'real' engineering) with which one could conjure things of mere thought-stuff that actually did something useful (unlike the many dead essays I had written as English undergraduate).
Guest Post by Paul Bruce from SmartBear Software
Paul Bruce, Product Marketing Manager for the Ready! API family of products at SmartBear, shares his thoughts on the new RAPID-ML Plugin for Ready! API.
We’re excited to announce a new partnership with the good folks at RepreZen! Both SmartBear and RepreZen share a deep passion for great API design. We’ve combined the power of our platforms to simplify the process of designing and testing high-quality APIs from inception to production deployment.