API Terms of Service : A creative commons pattern
summary
Project proposes a reusable, partly machine-readable API Terms of Service pattern inspired by a creative commons pattern, backed by qualitative interviews with API users, providers and regulators, a live survey and prototypes (license wizard, tiered certification, simple clause framework). Findings flag painful vendor changes (Google Maps, LinkedIn, Twitter), researchers blocked by access, and developers who don’t read ToS; cites the EU JRC analysis of 4000 ToS / 40% mention API. Focus is on standard clauses (SLA, payments, data reuse, storage, copyright) and pragmatic adoption paths.
AI-written summary · about
chapters (8)
- 0:00API Terms of Service research
- 1:49Project goals and CC model
- 4:39Initial interview findings
- 14:15Research insights and standardization
- 17:26Design and legal approaches
- 22:07Survey and feedback collection
- 26:04Community adoption and usability
- 28:12Q&A on self-service contracts
related talks
40mThe API mindset: tech, product, business and legal
01h 29mAPI Design Anti-patterns: How to identify & avoid them
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
49mAdvanced API design: how an awesome API can attract friends...
49mBuilding Software Better: API Lifecycle Management for Developers
30mConsumer APIs Must be Product-Driven
27mBuilding Great Web APIs
26mDesigning Accessible APIs