Today we are really happy to announce the integration of API Commons into the APISpark platform. The integration specs are explained further below, but for those who aren’t familiar with the project, here’s a little more details!
Kin Lane explains what led him to launch this initiative in a recent InfoQ article:
We both felt like there should be a place where API providers could publish the API designs, defined using emerging API definition formats like API Blueprint, RAML and Swagger, and take a stance on the copyright of their API design, using the Creative Commons license of their choice.
We feel strongly that API designs should remain openly licensed, allowing for re-use of the best API patterns available today. People tend to emulate what they see, and without common patterns, providers tend to reinvent the wheel each time. In 2014, you should have common patterns for calendars, directories, images, videos and other resources we depend on every day for personal and business apps.
With this integration, APISpark lets you define copyright and licensing metadata and automatically generates your API Commons manifest including your API definition based on Swagger specification.Click on the image below to enlarge it.
This saves you time and allows you to quickly share your API design in the commons.
In the coming weeks, we plan to introduce the following enhancements:
- Easier selection of predefined API licenses (Creative Commons and popular Open Source ones)
- Automated publication of your API manifest into API Commons (using their web API)
See other APISpark 2.1 enhancements.
Follow-up: importance of API Commons underlined after the new ruling in Oracle vs Google case