The open API manifesto. To Scale the API economy.
Open APIs, as public web APIs are a wonderful way to share resources over the world wide web. We think that these open APIs can make the revolution the web needs to support the humans-to-humans, humans-to-machines and machines-to-machines communications, in automated, lightweight and efficient interactions. Because of the business behind it, lots of people call “web APIs” open APIs, where they can be open to only one, few, many or all, with restricted to non-restricted usage. These open APIs describe the interface to access to a resource, a data or a service which have often also restricted usage. After the case of Oracle vrsus Google, it seems that even API copyright trolls are pending.
For a better understanding for developers, companies and institutions we decided to work on an ”Open API definition” Lots of people in the industry tried to make it without success in the API space, so we decided to crowdsource it as possible. We’ve made a tour around API experts met in API conferences to build a first draft about it, described hereunder as the definition of open is quite different towards people.
Main principles : We think that these open APIs, to enable a sharing economy on the web need to be :
- Accessible as easy to discover and to use
- Public as accessible to everybody
- Transparent as sharing with the network new resources publicly
- Neutral as accessible, public and transparent , so non-discriminant, to 3rd-parties usage
The main goal is to find the requirements an open API need to fill in order to be recognized as an open API by the whole industry. The aim of the contribution is to be able to put in the first draft requirements the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document as described in RFC 2119.