I am nobody, but I have been around the block or two when it comes to API specifications. You are unlikely to agree with most of my views on API specifications, and there are folks out there who strongly believe you have to contribute code to the conversations, otherwise you don’t exist or matter. However, if you are truly interested in creating a new specification for APIs or a specification that will make APIs obsolete, you are welcome to come by and talk about the merits of your new specification anytime-—who knows, you might learn something from me, or maybe you might teach me something I have missed. If you are unfamiliar with my work, here are a handful of conversations I’ve helped stir the pot on over the years that might bring value to your efforts.
- Swagger - Helped amplify the amazing work of Tony, Erin, and Ron during the first wave.
- API Blueprint - Championing API-design first energy coming out of Apiary before Oracle crushed.
- RAML - Was the original sock puppet for the specification and was used to help launch the spec.
- JSON-LD - Worked to give Markus and early JSON-LD a platform in tech as well as government.
- OpenAPI - Helped share stories and even was helping herd the OAI cats for a period of time.
- Collections - Helped push the collection specification from testing to a multi-protocol solution.
- AsyncAPI - Fought to carve out a safe and warms space for the spec to properly incubate and mature.
- JSON Schema - Fought to carve out a space to help the spec regroup and find its footing as a spec.
- APIs.json - Created and evolving my own opinionated approach to defining the business of APIs.
APIs.json is the only spec I have ever submitted a pull request (PR) on. The rest I have just invested in as I invest in everything else—telling, sharing, and amplifying stories. It is what I do. I know all of these specs, have used all of these specs, and I have believed in all of them and have ridden or drove the hype train around them at one time or another. If you are serious about contributing a new specification into the space, declaring there is a need for another API spec wars, and believe that markets should work things out, then please come by for an API Evangelist podcast conversations on the subject. I’d love to hear your perspective, and learn from the exhaustive research and due diligence you’ve done on the space, what the current state is, and why you feel a new specification is what everyone needs.
