Why API Standards Matter and How to Use Them
In this episode of "What Would the Web do?" we dive into the world of standards. Our premise is that everybody in the Web and API space uses standards anyway, so it's important to understand the space and to make sure that you use standards as effectively as possible. As an introduction, we look at standards from three different angles:
What is the difference between monolithic standards that completely define APIs for some application scenario and modular ones? We come away with the conclusion that for most API designs, modular designs are the way to go, and HTTP building blocks are a good foundation to build on.
What does a maturity model for standards look like? We distinguish five levels: patterns, personal, corporate, vertical, and global. In many cases, building blocks come into existence through a maturity process that advances through these stages.
How to standards organizations work? We look at the examples of IETF, W3C, ISO, and OASIS, and briefly discuss how they differ in terms of participation, process, and openness.
Our take-away message is that it is important to follow standards and the API space, because they help with API design both for providers and consumers. If you are in the API space, follow the standardization space at least loosely. Large organizations should have designate experts who participate in standards work, or at least track the work of relevant standards bodies.
00:00 Introduction
00:59 Why do People use Standards?
02:48 Fundamental Standards in the API Space
04:39 Monolithic vs. Modular Standards
09:24 Maturity Model for Standards
18:05 Standards Organizations (IETF/W3C/ISO/OASIS)
29:14 Wrap-Up