• Enable (and Encourage) people to openly declare API
Interface deﬁnitions to be under Reusable
• Enable discovery, sharing and forking
• Apply to API Deﬁnitions and Data Models (not
• Facilities API
• Own the
• Explicitly make it
•Others can Reuse
•Others can Extend
•Client code can be
So can the server
Others can Reuse,
Improve and Remix
Beneﬁts to API Designer
• Get broader adoption
• Get more shared tooling
• Feedback & Input
• Community Driven Standardisation
Just Like Open
Beneﬁts of using APIS from the
• Save work
• Clear copyright footing
• Increase the likelyhood of clients being available
• Help improve something existing
• Many Eyeballs
...: Just Like
Will people do this?
• Is it valuable enough?
• What about commercial conﬂicts?
• How will it be bootstrapped?
Value for APIs as a Whole
• Huge: In fact - APIs are probably not viable as a technology
• Reduce the amount of client code by orders of magnitude
• We will end up with fewer better API interfaces and more APIs
Why does this matter?
Assume 5 clients per API, Assume factor of 10 shared API defs over time
• Seems to be the logical place to start
• There is no incentive to have different models for the same
• No commercial barriers
• Some API Designs are Competitive Advantage
• In some cases shared standards would be better
• Parallels to the evolution of Open Source
Why Not OS?
• There have been copyright lawsuits so descriptions are at
least subject to copyright
• Descriptions are generally not executable by themselves
• Maybe Open Source licenses are needed in the future too
Why not just Creative Commons?
• Creative Commons is great
• But we need more structure and guidance
• We also need to be able to discover APIs in the commons
• We need to evaluate if creative commons is the right