The Past: Origins and Early Growth
Initial Motivation: The Web was created out of a personal need to organize random information and a professional need at CERN to create a shared space for institutional knowledge, enabling a “self-managing team.”
Core Concepts:
- Universal Space: The goal was a single “universe of network accessible information.”
- The Power of the URL: The most important concept was the URL, an identifier that could point to anything, breaking the constraints of previous closed hypertext systems.
- Unconstrained Hypertext: The flexibility to map any existing information structure (trees, databases, etc.) onto the Web without changing the source.
Early Challenges & Development:
- Initial resistance due to the perceived complexity of HTML (“all those angle brackets”) and a “not invented here” culture.
- The first browser was also an editor, built on a NeXT computer, but its reach was limited.
- The simple, text-only Line Mode Browser was created to ensure universal access for everyone, regardless of their platform.
- The “snowball effect” began by putting the CERN phonebook online, giving people a reason to use the system.
The Turning Point:
- While early browsers like Pei Wei’s ViolaWWW (which had Java-like applets) were ahead of their time, the creation of Mosaic at NCSA was the key moment.
- Mosaic, inspired by Viola, added inline images and was easy to install, leading to a massive surge in popularity. This established the Web as primarily a browsing (consumption) medium, not the editing (creation) medium originally envisioned.
- Growth Pattern: Growth was exponential and constant (a straight line on a logarithmic chart), described as a “slow bang” rather than a single explosion.
The Present (as of 1996): Success and Threats
- Dominant Use: The Web had primarily become a “corporate broadcast medium,” a one-to-many communication tool, rather than the collaborative, many-to-many space Berners-Lee had imagined.
- Emerging Technologies: Excitement was building around VRML (3D), Style Sheets, and especially Java, which was seen as a way to finally bring a modern, object-oriented programming language to the mainstream.
- The Threat of Fragmentation:
- The biggest danger was the Web splintering into incompatible versions due to browser-specific features.
- The rise of “This page is best viewed with…” messages signaled a return to the pre-Web era of data incompatibility.
- The Solution: The W3C:
- The World Wide Web Consortium (W3C) was formed as a neutral, international body to bring technology providers and users together.
- Its goal is to rapidly produce common “specifications” and “recommendations” (not slow, formal “standards”) to prevent fragmentation and ensure the Web remains a single, unified space.
The Future: Long-Term Goals and Responsibilities
- Industrial Strength Web: A key goal is to fix underlying infrastructure issues (e.g., redundancy, broken links) to make the Web robust and reliable. This includes solving the problem of distributing copies of heavily used documents across the globe to reduce load and increase speed (the problem that Content Distribution Networks - CDNs solve today)
- From Interactivity to “Intercreativity”:
- Berners-Lee distinguishes between “interactivity” (clicking buttons on a form) and true “intercreativity”—a collaborative space where people build things together.
- This requires integrating real-time communication, shared manipulable 3D objects, and notification systems directly into the Web’s fabric.
- The Semantic Web: A vision for a Web where information is machine-readable, not just human-readable. This would allow software agents to understand context and perform complex tasks (e.g., verifying property ownership by analyzing semantic data, not just text). Berners-Lee explicitly mentions that this verification would be possible by ‘tracing through the digital signatures’ on the documents.
- Challenges and Final Warning:
- Maintain Flexibility: It is crucial to avoid designing protocols that constrain future evolution (e.g., embedding one language like Javascript inside another like HTML without clear separation).
- Designers’ Responsibility: Protocol designers are not just “techies”; they are designing the social space of the future. Their decisions define the rules for privacy, identity, and communication in cyberspace for decades to come.