Tim Berners-Lee wrote Information Management: A Proposal at CERN, outlining a distributed hypertext system to help researchers share and track information. This document is widely treated as the starting point for what became the World Wide Web. A revised version followed in 1990, helping move the idea toward implementation.
The first website, hosted at `info.cern.ch`, went online to explain what the World Wide Web was and how to use it. Making a live, reachable site was a key step from an internal CERN project to something others could try. It also created pressure for shared technical rules so different computers and programs could interoperate.
CERN signed a declaration placing key World Wide Web software into the public domain, including core libraries and server code. This reduced legal barriers and encouraged broad adoption and experimentation outside CERN. The decision helped the web grow as an open system rather than a proprietary product.
The World Wide Web Consortium (W3C) was founded to develop open standards that keep the web interoperable across different browsers and servers. Having a central standards body made it easier to agree on common formats such as HTML. This helped reduce fragmentation as more companies began building web software.
RFC 1866 defined HTML 2.0, turning earlier, informal web practices into a clearer specification. It described core document structure and features such as links and forms, supporting more consistent implementation across browsers. This was an early example of web technology being documented through open internet standards.
RFC 2068 provided an early, detailed specification for HTTP/1.1, the protocol used by web clients and servers to request and deliver resources. Compared with earlier practice, HTTP/1.1 improved how connections and caching could work at scale. This version was later revised and consolidated, but it marked a major step toward a modern web transport standard.
W3C published HTML 3.2 as a Recommendation, reflecting features that were already widely deployed in browsers. Standardizing those features improved compatibility, especially for common page elements like tables and applets. It also set the stage for larger, more structured updates in HTML 4.
HTML 4.0 was published as a W3C Recommendation, aiming to improve interoperability and long-term maintainability of web pages. It expanded support for scripting, style sheets (CSS), and accessibility and internationalization features. The release helped shift web authoring toward cleaner structure and better separation between content and presentation.
RFC 2396 defined the generic syntax for Uniform Resource Identifiers (URIs), including the structure used by many web addresses. Clear URI rules mattered because both HTML (links) and HTTP (requests) depend on consistent identifiers. Standardizing URI parsing reduced ambiguity across software implementations.
RFC 2616 replaced earlier HTTP/1.1 documents and became the best-known reference for HTTP/1.1 for many years. It described request/response behavior, headers, caching, and other core rules needed for reliable web communication. This consolidation helped align browser and server behavior during a period of rapid web growth.
HTML 4.01 updated HTML 4.0 with corrections and clarifications, helping developers and browser makers converge on consistent behavior. It stabilized a widely used version of HTML that remained important for many years. This “tightening up” was especially valuable as web development became a mainstream industry.
XHTML 1.0 became a W3C Recommendation, rewriting HTML 4.01 rules to fit XML 1.0’s stricter syntax. The goal was to make web documents easier for machines to process and to align the web with broader XML-based tools. In practice, it also highlighted tensions between strict parsing and the web’s need to handle real-world, imperfect markup.
RFC 3986 updated and clarified the generic syntax for URIs, refining how identifiers should be parsed and compared. These rules matter across the web because links, redirects, and resource naming all rely on stable identifier behavior. The update helped reduce inconsistencies that could break interoperability at global scale.
W3C released the first public working draft of HTML5, signaling a shift toward a new major revision focused on real-world web applications. The effort aimed to standardize features already emerging in browsers, while improving error handling so pages would work more consistently. This milestone marked the beginning of a long standardization process leading to a stable recommendation.
In 2014, the IETF replaced RFC 2616 with a set of documents (including RFC 7230 and RFC 7231) that restructured and clarified HTTP/1.1. Breaking the spec into focused parts made it easier to update, test, and implement correctly. This revision also reflected lessons learned from years of large-scale web deployment, such as proxies and caches.
HTML5 was published as a W3C Recommendation, completing a major revision of HTML aimed at modern web applications. It standardized features like built-in multimedia support (audio and video) and APIs for richer interaction, reducing reliance on browser plugins. This recommendation served as a clear closing point for the 1990–2014 era of major HTML/HTTP standard consolidation and revision.
HTTP/HTML Standards Development and Major Revisions (1990–2014)