Course contentsShow
← Web Development
Lesson 35 of 2,9821. The Web Platform FoundationFree lesson

Living Standards vs Versioned Specifications

The shift from numbered versions to continuously updated living standards and what this means for developers.

Living Standards vs Versioned Specifications

You'll learn: Why the web stopped releasing numbered versions like "HTML5" and moved to a model of continuous updates.

The Old Way: Versioned Specifications

For years, web standards worked like software releases. We had HTML 1.0, HTML 2.0, up through HTML5. Each version took years to develop, debate, and finalize. Once published, that version was "done" — frozen in time. If something needed to change, you'd wait for the next major version.

The problem? The web evolved faster than committees could meet. Browsers implemented features before specs were finished. Developers needed answers now, not in three years.

The New Way: Living Standards

WHATWG (which you learned about in the previous lesson) pioneered a different approach: living standards. Think of it like a Wikipedia page versus a printed encyclopedia. Wikipedia updates continuously as new information emerges. A printed encyclopedia is locked to its publication date.

A living standard is a specification that's constantly maintained and updated. There's no "HTML6" coming. Instead, the HTML Living Standard gets small improvements, clarifications, and new features added regularly. When browsers implement something new, the spec evolves to match reality.

What This Means for You as a Developer

You don't wait for "the next version" anymore. Features appear gradually. Browser compatibility becomes more important than version numbers. You check whether a feature is supported in your target browsers, not whether you're "using HTML5 vs HTML6."

The web platform stays flexible and responsive to real-world needs without the bureaucracy of version releases.

Key Takeaway: Living standards replaced numbered versions, letting the web evolve continuously instead of waiting years between frozen releases — making the platform more agile for developers.