Web Standards

Web Standards are the shared specifications that let the web work the same way no matter whose browser, server, or client is running. They come primarily from the W3C, the WHATWG, and the IETF, and they cover the whole stack an API leans on — HTML, CSS, URLs, HTTP, and the JavaScript APIs exposed to the browser. The point is not any single document but the agreement: build to the standard and your work interoperates with everyone else’s.

• Multiple standards bodies - The W3C, WHATWG, and IETF each own pieces of the web platform, and they coordinate so the pieces fit together.
• Interoperability first - A standard exists so two implementations written by different people behave the same way against the same input.
• Living documents - Much of the modern web platform is maintained as continuously-updated “living standards” rather than frozen versions.
• The foundation APIs sit on - HTTP, URLs, and media types are web standards long before they are API design choices.

In API operations, web standards are the substrate everything else assumes. When I score a provider, I am really checking how faithfully they honor the underlying web standards — correct HTTP semantics, honest content negotiation, sane URL design — before I ever get to the API-specific specs like OpenAPI or AsyncAPI. As more traffic comes from agents rather than browsers, that faithfulness matters more, not less: an agent has no human to paper over a provider’s deviations from the standard, so the closer an API stays to the web platform it inherited, the more predictably machines can consume it.