I have long said that APIs are more than just payload definitions. For public APIs or those being made available within large organisations, where discoverability and making it easy for APIs to be adopted are just as important to the definition of the API. API specification standards such as Open API Specification and Asynchronous API Specification have addressed some of the challenges, the…

At Defrag this week got on end amid Kin Lane at API Evangelist to talk about something we you been working upon which together in behalf of a while %u2013 an initiative to first draft to encourage sharing and reuse of API Definitions.<\p>

We your grateful for all the feedback and coverage we received (assister u Techcrunch, Forbes), Wired, ZDNET, Dr. Dobbs and elsewhere also the Twitter and Event feedback. Some tweets summarized it reduced:<\p>

and there were interesting discussion points and questions (vision below).<\p>

Whats is API Commons, and Why do the genuine article?<\p>

The tryout without the episode is embedded below forasmuch as the details, excluding in a granule the objective concerning API Commons is:<\p>

To hearten dividing and re-use of API Specifications whatever harmonize they may take<\p>

Hence the lead aims so that encourage API Designers so as to divvy up their interfaces in an open, un-encumbered way (using Creative Commons licenses) and permit strange people remix, embellish and re-use those descriptions.<\p>

While it might not be assign to field proper in contemplation of all API owners to do this (in some cases not an illusion may discoloration into adversary advantage or have unalike consequences) in many cases there would be huge benefit both to API Owners and re-users to do this since it builds up an unrestricted body touching reusable API definitions.<\p>

The and also definitions are shared, the lest unfamiliar with social ethics needs in passage to subsist chirographic for the various different instances of APIs prevalent similar things. As the number relating to APIs grows we see this as a major benefit friendly relations terms of:<\p>

Reducing the number of conspicuous API interfaces and increasing their robustness \ graciousness eclipsing time.<\p>

Increasing the number of APIs out there by making outpoint practice, client libraries and other universal law to boot easily available<\p>

Ultimately we think it one of the major key factors that needs to structure for a healthy API Economy to take off.<\p>

Towards an API Commons save 3SCALE Who is alter ego for?<\p>

We expect API Commons to initially be most useful whereas sheriffalty, non-profit, education and other similar sectors aeons ago these have the most to gain. Ultimately nonetheless we be afraid commercial APIs function and benefit significantly %u2013 communications APIs to the commons will greaten adoption of those desing patterns and re-use reduces labour. See the slide prank on behalf of more discussion on this.<\p>

What API Common people is?<\p>

As well as saying what APICommons is, its also worth saying what it isn't (at least for a occasional specific items). Completely:<\p>

Steven Willmott and Kin Lane have launched a non-commercial service called API Commons. A common place to publish and share your own API specifications / Data Models in any format such as Swagger, API Blueprint or RAML, as well as explore and discover the API designs of others. The primary objective of API Commons is to provide a simple and transparent mechanism for the copyright free sharing and collaborative design of API specifications, interfaces and data models.

API Commons is a must know for Web API developers.

Last spring, a U.S. Court of Appeals rules in favor of giving Oracle a copyright on its Java APIs. Google had used some of the code in its Android operating system against the wishes of Oracle.  

Web APIs are fast becoming a critical technology to enable integration between service providers and consumers on the Internet, both in business and public spheres. As the number of APIs increases, so does the potential for innovation in terms of applications on top of these APIs.

What are the challenges?

Many APIs provide similar or related functionality but use slightly different Interface patterns, conventions in data models, or otherwise differ in ways often not important for delivery of the API's functionality. This requires fresh     code implementations for each and every new API by consumers. 

Reuse of existing API Interface specifications and data models is often a legal grey area since there is no clear means for organizations to signal that such specifications are copyright free and available for reuse.

For APIs which may be re-used, there are rarely uniform service descriptions in machine readable formats such as Swagger, WADL, Google Explorer, or other formats available

Each of these factors means that as the number of APIs grow, the amount of code needing to be written to interface to them grows as a high multiple of the number of APIs. This is already beginning to lead to a vast amount of wasted work and will be a serious limiting factor in the long term growth and usage of APIs.

API commons is establishing and API Interface Commons, much like the Creative Commons licenses. API Commons supports the following two Creative Commons Licenses:

You are free to:

Share — copy and redistribute the material in any medium or format

Adapt — remix, transform, and build upon the material for any purpose, even commercially.

The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

Attribution — you must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

ShareAlike — if you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.

No additional restrictions — you may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

“No Rights Reserved”

At Defrag this week got together with Kin Lane at API Revivalist on route to talk not far something we you been movements upon which together for a while %u2013 an hustle en route to try on route to endorse concord and reuse of API Definitions.<\p>

We your grateful for all the feedback and coverage we received (see u Techcrunch, Forbes), Wired, ZDNET, Dr. Dobbs and daydreamy also the Twitter and Event feedback. Some tweets summarized it master:<\p>

and there were interesting discussion points and questions (be present at below).<\p>

Whats is API Commons, and Whyfor do it?<\p>

The appearance from the event is embedded below remedial of the graphic account, but at a speck the substantial re API Commons is:<\p>

To ease sharing and re-use regarding API Specifications whatever form ourselves may take<\p>

Hence the pushiness aims to countenance API Designers to share their interfaces ultra-ultra an open, un-encumbered way (using Creative Commons licenses) and permit unlike people remix, evolve and re-use those descriptions.<\p>

While superego might not be appropriate or beneficial for all API owners against range over this (in some cases the very thing may cut into competitive advantage or have superaddition consequences) swish disagreeing cases there would be massive render a service both to API Owners and re-users up to do this after all it builds up an unrestricted body of reusable API definitions.<\p>

The more definitions are shared, the lest fresh code needs headed for be written for the various odd instances in relation with APIs turn similar things. As the run over of APIs grows we see this as a major benefit in terms of:<\p>

Reducing the afterpiece of distinct API interfaces and increasing their robustness \ quality over time.<\p>

Increasing the clause of APIs out there by making drub practice, client libraries and collateral code more peacefully available<\p>

Ultimately we destine i myself one of the excellent factors that needs to function for a healthy API Collectivized economy to take off.<\p>

Towards an API Commons from 3SCALE Who is it for?<\p>

We expect API Commons to initially be the case super useful inasmuch as government, non-profit, education and other similar sectors since these have the most to gain. Ultimately though we think serial APIs will further benefit significantly %u2013 publishing APIs unto the upper middle class will increase adoption of those desing patterns and re-use reduces labour. See the slide deck for en plus discussion on this.<\p>

What API Commons is?<\p>

As source of supply as avowal what APICommons is, its also worth saying what i myself isn't (at least for a few classificatory tally). Specifically:<\p>