The World Wide Web is an open distributed hypermedia system built above the Internet. Its foundational architecture combines globally usable identifiers, a request-response interaction protocol, typed representations and links embedded in representations. The Web is therefore not the Internet, not one browser, not HTML alone and not a collection of websites.
The World Wide Web is an open distributed hypermedia system built above the Internet. Its foundational architecture combines globally usable identifiers, a request-response interaction protocol, typed representations and links embedded in representations. The Web is therefore not the Internet, not one browser, not HTML alone and not a collection of websites.
Open Hypermedia Publishing Through Global Identification, Representation and Interaction is defined here as the architecture and operational system that lets agents identify resources with URIs, interact with them through protocols such as HTTP, receive typed representations and traverse links between resources. It reduces the need for every publisher and reader to share one machine, database, software package or institutional catalogue.
Before the Web, remote information services commonly required service-specific commands, host knowledge, file paths or proprietary clients. The Web supplied a minimal common architecture for identifying a resource, requesting it, receiving a typed representation and traversing relationships to other resources.
Its foundational architecture combines globally usable identifiers, a request-response interaction protocol, typed representations and links embedded in representations. The Web is therefore not the Internet, not one browser, not HTML alone and not a collection of websites. It is a shared information space in which independently operated clients and servers can identify and exchange representations of resources.
It built on Libraries and catalogues, Writing systems, Internet and TCP/IP, Bulletin-board systems, Usenet and Internet chat and Database management systems.
It helped make possible Blogs and Content-Management Systems, Smartphones, Social Networking and Microblogging Platforms, Online video and streaming platforms and Podcasts and on-demand audio.
Identifiers remain the Web's connective tissue.
A stable Web reference can outlive a particular file path or representation when authorities manage identifiers well. The distinction is architectural even though poor URI management often destroys it. A publisher can point to a resource controlled by another institution without copying it or negotiating a shared database schema.
The World Wide Web is an open distributed hypermedia system built above the Internet. Its foundational architecture combines globally usable identifiers, a request-response interaction protocol, typed representations and links embedded in representations. The Web is therefore not the Internet, not one browser, not HTML alone and not a collection of websites. It is a shared information space in which independently operated clients and servers can identify and exchange representations of resources [1]-[9].
Tim Berners-Lee's 1989 proposal addressed information loss and organisational fragmentation at CERN. The 1990 proposal with Robert Cailliau described a practical hypertext project joining existing information systems. Berners-Lee then implemented the WorldWideWeb browser-editor, the first HTTP server and the first website. The line-mode browser widened access beyond the NeXT workstation, while CERN's 1993 decision to release core Web software without royalty barriers reduced a decisive adoption constraint [1]-[5].
The Web's components must remain analytically separate. A URI identifies a resource; HTTP defines interactions and messages; a representation communicates a resource's state; HTML is one representation format; a browser is a user agent; a server responds to requests; a hyperlink is a relationship expressed in a representation. A URL is a kind of URI used through a retrieval scheme, not a synonym for the entire Web [6]-[9].
The Web radically lowered publication and navigation costs, but did not abolish gatekeepers. Hosting providers, browser vendors, standards bodies, domain registries, certificate authorities, search engines, platforms and states control different points of access and visibility. Open architecture permits decentralised publication while commercial activity can still concentrate discovery, identity, infrastructure and attention.
The Web is a shared information space created by global identification, standard interactions, transferable representations and links. HTML pages are common occupants of that space, not the architecture itself.
Makes independently hosted information globally addressable, linkable, retrievable and publishable through interoperable clients and servers
Start with the key connections, then reveal the wider network when you need more context.
Provides linked resources, browsers, servers and HTTP publication.
Supplies linked information and browser-based services.
Provides earlier organised discovery practices.
Provides symbolic structure and document encoding.
Provides heterogeneous internetwork transport.
Supplies a universal browser interface for forums and community sites.
Coordinates identity, feeds and interaction above Web infrastructure.
Provides pages, links, browsers and public identifiers.
Supplies URLs, servers and public publishing.
Provides addressable resources and hyperlink graph.
Distributes assets and external manifests.
Hosts large Web applications and data services.
This marks the broad emergence and development of World Wide Web. Why it mattered: Makes independently hosted information globally addressable, linkable, retrievable and publishable through interoperable clients and servers.
Shows that the Web began as an organisational memory and linking problem, not as a plan for online shopping.
Core concepts are specified and first client, editor, server and site are implemented.
Defines a practical client-server hypertext system integrating existing services.
HTTP, HTML, URI and browser behaviour stabilise enough for large-scale publishing and commerce.
Databases, scripts, sessions and user-generated content make the Web interactive.
Line-mode access, external servers and community adoption expand the system.
Unrestricted software release and graphical browsers accelerate public use.
Global platforms and infrastructure providers dominate major flows while independent sites persist.
Robert Cailliau is one of the people connected to this topic. Open the profile for the wider historical context.
Tim Berners-Lee is one of the people connected to this topic. Open the profile for the wider historical context.
CERN is one of the organisations connected to this topic. Open the profile for the wider historical context.
IETF is one of the organisations connected to this topic. Open the profile for the wider historical context.
W3C is one of the organisations connected to this topic. Open the profile for the wider historical context.
These expandable sections preserve the detailed research behind the public explanation.
The World Wide Web is an open distributed hypermedia system built above the Internet. Its foundational architecture combines globally usable identifiers, a request-response interaction protocol, typed representations and links embedded in representations. The Web is therefore not the Internet, not one browser, not HTML alone and not a collection of websites. It is a shared information space in which independently operated clients and servers can identify and exchange representations of resources [1]-[9].
Tim Berners-Lee's 1989 proposal addressed information loss and organisational fragmentation at CERN. The 1990 proposal with Robert Cailliau described a practical hypertext project joining existing information systems. Berners-Lee then implemented the WorldWideWeb browser-editor, the first HTTP server and the first website. The line-mode browser widened access beyond the NeXT workstation, while CERN's 1993 decision to release core Web software without royalty barriers reduced a decisive adoption constraint [1]-[5].
The Web's components must remain analytically separate. A URI identifies a resource; HTTP defines interactions and messages; a representation communicates a resource's state; HTML is one representation format; a browser is a user agent; a server responds to requests; a hyperlink is a relationship expressed in a representation. A URL is a kind of URI used through a retrieval scheme, not a synonym for the entire Web [6]-[9].
The Web radically lowered publication and navigation costs, but did not abolish gatekeepers. Hosting providers, browser vendors, standards bodies, domain registries, certificate authorities, search engines, platforms and states control different points of access and visibility. Open architecture permits decentralised publication while commercial activity can still concentrate discovery, identity, infrastructure and attention.
The Web is a shared information space created by global identification, standard interactions, transferable representations and links. HTML pages are common occupants of that space, not the architecture itself.
| Field | Value | |---|---| | Public title | World Wide Web | | Analytical title | Open Hypermedia Publishing Through Global Identification, Representation and Interaction | | Recommended type | Open distributed hypermedia architecture, protocol family and publishing system | | Primary category | Distribution & amplification | | Secondary categories | Discovery; identification; representation; interaction; storage; governance; transmission | | Emergence | Proposal in 1989; first browser, editor and server in 1990; public Internet release in 1991; unrestricted CERN release in 1993 |
Open Hypermedia Publishing Through Global Identification, Representation and Interaction is defined here as the architecture and operational system that lets agents identify resources with URIs, interact with them through protocols such as HTTP, receive typed representations and traverse links between resources. It reduces the need for every publisher and reader to share one machine, database, software package or institutional catalogue.
The topic includes Web identifiers, user agents, servers, HTTP interaction, representation formats, hyperlinking, standards organisations and publication/access conditions. It excludes the Internet transport layer, individual search engines, domain-name resolution as an independent naming system, and particular publishing platforms where those are analysed separately.
A stable Web reference can outlive a particular file path or representation when authorities manage identifiers well. The distinction is architectural even though poor URI management often destroys it.
A publisher can point to a resource controlled by another institution without copying it or negotiating a shared database schema.
Clients can traverse resources delivered by unrelated servers because identification and interaction follow common rules.
A small publisher can operate a server and become reachable without joining a broadcast network or printing supply chain.
The same resource can be represented as HTML, an image, structured data or another media type, depending on protocol and server behaviour.
Forms, scripts, APIs, transactions and streaming later expand the Web beyond document retrieval while retaining core identification and interaction principles.
The Internet connects networks and transports packets. The Web identifies resources and exchanges representations above Internet protocols.
A browser is one client implementation. The Web exists across many clients, servers, standards and resources.
HTML is one representation language. Images, JSON, video, PDF and other media can also be Web representations.
The identifier is not the thing identified. Inspecting a URI does not reveal every property of its resource.
A resource is an identified conceptual target; a representation is transferable data communicating a state of that resource.
HTTP defines application semantics. TCP is one transport commonly used beneath it, but Web architecture is not conceptually identical to TCP.
A link creates reference and navigability without guaranteeing persistence, endorsement, permission or preservation.
A website can be independently operated. A platform coordinates many publishers under one provider's rules, identity system and discovery mechanisms.
Putting a resource on the Web does not make it easy to find. Search and social distribution are separate systems.
Interoperable publication does not guarantee traffic, ranking, accessibility, affordability or freedom from blocking.
Publishers expose resources through servers. User agents resolve identifiers, send protocol requests, receive representations, render or process them and follow embedded links. Intermediaries such as caches, proxies, gateways, content-delivery networks and search crawlers may participate without changing the conceptual distinction between identification, interaction and representation.
| Dimension | Pattern | |---|---| | Participation | Many publishers and many readers; direct, mediated or automated | | Timing | Usually asynchronous retrieval, with later extensions supporting near-real-time interaction | | Persistence | Depends on server retention, identifier management, archives, caches and formats | | Topology | Distributed client-server system with optional intermediaries | | Feedback | Links, forms, requests, responses, logs, comments and application actions | | Access | Connectivity, device, user agent, naming, hosting, literacy and policy |
| Stage | Function | |---|---| | Author or application | Creates or updates a resource and one or more representations | | URI authority | Assigns and manages identifiers within a namespace | | Origin server | Maps requests to resource handling and returns responses | | HTTP interaction | Carries method, target, headers, status and representation metadata | | Representation | Communicates resource state in HTML or another media type | | User agent | Retrieves, renders, interprets or transforms the representation | | Hyperlinks | Expose relationships and further identifiers | | Intermediaries | Cache, proxy, filter, accelerate or observe requests and responses | | Governance | Standards bodies, registries, browser vendors, hosts and states shape behaviour | | Recipient | Reads, listens, watches, submits data or invokes an application action |
Berners-Lee observed that CERN projects, people and documents changed faster than central documentation systems could track them. His 1989 proposal framed linked information as a response to organisational memory loss [1].
The 1990 Berners-Lee-Cailliau proposal described a simple scheme to integrate existing machine-stored information through browsers and hypertext servers rather than replacing every source system [2].
The WorldWideWeb program on NeXT functioned as both browser and editor, while the first server, httpd, hosted project information [3][4].
The line-mode browser allowed access from a wider range of terminals and systems, reducing dependence on the original graphical environment [4].
In August 1991 the project was presented to the wider Internet hypertext community, inviting use and collaboration [10].
CERN released core software without royalty restrictions in 1993, allowing independent implementation, modification and redistribution [5].
URI syntax, HTTP and HTML moved from experimental practice into published specifications and standards [6]-[8].
Mosaic and later commercial browsers made images, navigation and installation more accessible to non-specialists.
Forms, scripting, cookies, databases, server-side applications and APIs turned a document system into a general application environment.
Large intermediaries, app-like sites, content-delivery networks and mobile browsers concentrated traffic while retaining Web protocols underneath.
Hypertext systems and Internet services demonstrate linking and remote access but remain fragmented by software and protocol.
Core concepts are specified and first client, editor, server and site are implemented.
Line-mode access, external servers and community adoption expand the system.
Unrestricted software release and graphical browsers accelerate public use.
HTTP, HTML, URI and browser behaviour stabilise enough for large-scale publishing and commerce.
Databases, scripts, sessions and user-generated content make the Web interactive.
Global platforms and infrastructure providers dominate major flows while independent sites persist.
APIs, structured data, automated agents and AI systems increasingly consume Web resources alongside human readers.
Before the Web, remote information services commonly required service-specific commands, host knowledge, file paths or proprietary clients. The Web supplied a minimal common architecture for identifying a resource, requesting it, receiving a typed representation and traversing relationships to other resources.
| Before | After | |---|---| | Networked information existed in separate services, file stores and host-specific systems whose locations, interfaces and formats had to be known in advance | Makes independently hosted information globally addressable, linkable, retrievable and publishable through interoperable clients and servers |
| Dimension | Batch 11 evaluation question | |---|---| | Reach | What population, geography or corpus can be reached, indexed or carried? | | Latency | How long do publication, retrieval, response, propagation and refresh take? | | Persistence | Where do documents, indices, caches, fibres and records survive? | | Addressability | How are resources, pages, signals, routes or documents identified? | | Discoverability | Can relevant information be found without already knowing its location? | | Capacity | What limits scale: links, crawl budget, index size, spectrum, attenuation or equipment? | | Interoperability | Can independently built clients, servers, engines or optical systems work together? | | Governance | Who controls standards, ranking, access, infrastructure, visibility and removal? | | Access cost | What equipment, connectivity, literacy, capital or institutional support is required? | | Abuse surface | How can the system be spammed, manipulated, surveilled, censored, overloaded or monopolised? |
| Topic field | Value | |---|---| | Main problem addressed | Makes independently hosted information globally addressable, linkable, retrievable and publishable through interoperable clients and servers | | Key predecessors | Internet and TCP/IP; hypertext systems; document markup; client-server computing; domain naming | | Key successors | Web publishing; search engines; web applications; blogs and content-management systems; platforms; online commerce | | Primary category | Distribution & amplification | | Secondary categories | Discovery; identification; representation; interaction; storage; governance; transmission |
Publishers can operate servers and control their own resources without entering one central database.
Links connect resources across organisational and national boundaries.
A common interaction model can transfer many media types.
Clients and servers can evolve independently while honouring shared protocol semantics.
New resources and servers can join without redesigning a global catalogue.
Browsers, crawlers, scripts and assistive technologies can all act as Web agents.
Shared semantics allow performance optimisation and distribution through caches and proxies.
Methods, headers, media types and scripting support uses far beyond static pages.
Individuals, laboratories, firms and governments gained a direct route to global audiences.
References could cross institutional collections and create a navigable document graph.
Forms and secure interactions enabled transactions, administration and remote service delivery.
Independent browser, server and tooling implementations created a durable interoperability culture.
Hypertext, multimedia, interactive graphics and continuously updated pages changed publication.
APIs, structured data and crawlers turned published resources into inputs for other systems.
The linkable corpus made large-scale indexing, ranking and online intermediaries possible.
Provided the organisational problem, computing environment and decisive 1993 release conditions.
Develop and publish Web architecture, URI, HTTP and related standards.
Interpret standards, ship defaults and can create de facto behaviour through market share.
Control naming delegations and parts of the trust infrastructure used by Web access.
Determine affordability, availability, geographic reach and acceptable-use enforcement.
Mediate discovery and can make technically public resources practically invisible or dominant.
Accelerate, filter, observe and sometimes block traffic.
Apply censorship, surveillance, liability, accessibility, privacy and data-retention rules.
Create links, preserve resources, choose formats and collectively shape the information graph.
Resources move, vanish or change while old identifiers remain embedded elsewhere.
Open publication can still depend on a few search and social intermediaries for attention.
Requests, cookies, scripts and embedded services expose detailed activity traces.
Executable content, forms and third-party dependencies create phishing, malware and data-exfiltration risks.
A resource can be technically published but unusable to people with disabilities, slow links or unsupported devices.
Services can use Web technologies while restricting export, interoperability and independent identity.
Near-zero publication cost produces abundance faster than readers can evaluate it.
A reachable page is not necessarily authoritative, current or honest.
Hosting, DNS, certificates, browsers and networks create multiple points of failure or control.
Large-scale data centres, content delivery and device ecosystems externalise energy, mineral and maintenance costs.
| Relationship | Topic | Reason | |---|---|---| | Predecessor | Internet and TCP/IP Internet and TCP/IP | Provides heterogeneous internetwork transport. | | Predecessor | Writing systems Writing systems and markup traditions | Provides symbolic structure and document encoding. | | Predecessor | Libraries and catalogues Catalogues and classification | Provides earlier organised discovery practices. | | Successor | Search Engines Search engines | Crawls, indexes and ranks the Web corpus. | | Successor | Blogs and Content-Management Systems Blogs and content-management systems | Automates Web publication and serial updating. | | Successor | Social Networking and Microblogging Platforms Social networking platforms | Coordinates identity, feeds and interaction above Web infrastructure. | | Successor | Cloud computing and cloud storage Cloud computing | Hosts large Web applications and data services. | | Related | Email Email | Another Internet application with distinct addressing and delivery architecture. |
The relationship table separates enabling layers from applications. A predecessor may remain in use after this topic appears, and a successor may depend on the topic without replacing it.
Identifiers remain the Web's connective tissue.
Clients continue to send requests and receive status, metadata and representations.
Embedded references remain central to navigation, citation and crawling.
Many implementations can interoperate without sharing source code.
Typed representations let agents choose rendering and processing behaviour.
The inspectable document tradition remains influential even as applications grow more complex.
Independent sites remain technically possible despite platform concentration.
The Web also preserves its original fragility: references can outlive content.
Shows that the Web began as an organisational memory and linking problem, not as a plan for online shopping [1].
Defines a practical client-server hypertext system integrating existing services [2].
Demonstrates that reading and authoring were originally joined in one tool [3].
Publishes the project through the system it describes [4].
Shows how portability widened adoption beyond one workstation class.
Demonstrates how licensing conditions can determine infrastructure diffusion [5].
Separates universal identification from one document format [6].
Capture common practice as the Web shifts from prototype to interoperable infrastructure [7][8].
The research notes distinguishes proposal, prototype, public release, standardisation, operational deployment and mass adoption. These milestones frequently occur years apart and should not be folded into a single invention date.
|---|---|---|---| | World Wide Web-C01 | The Web is an application-level information system above the Internet rather than a synonym for it. | High | S01-S09 | | World Wide Web-C02 | Identification, interaction and representation are distinct foundations of Web architecture. | High | S06-S09 | | World Wide Web-C03 | HTML is one Web representation format, not the whole Web. | High | S07-S09 | | World Wide Web-C04 | The first WorldWideWeb client was also an editor. | High | S03 | | World Wide Web-C05 | CERN's unrestricted release materially reduced adoption barriers. | High | S05 | | World Wide Web-C06 | Publication and discovery are separate functions. | High | Architectural analysis | | World Wide Web-C07 | Open standards can coexist with concentrated browser, hosting and discovery power. | High | Institutional analysis | | World Wide Web-C08 | A URI identifies a resource, while a representation conveys a state of that resource. | High | S09 |
| Comparison | Main difference | Analytical value | |---|---|---| | Internet | Packet and network federation | Separates transport infrastructure from the Web information system. | | Gopher and FTP | Service-specific retrieval systems | Shows the Web's combination of universal identification, typed representations and embedded links. | | HTML | Representation language | Prevents a document format from swallowing the architecture. | | Browser | User agent implementation | Separates one product from the interoperable system. | | Search engine | Discovery intermediary | Shows that publication does not automatically solve retrieval. | | Platform | Coordinated service under one authority | Contrasts open publication with provider-controlled identity and distribution. |
The most important comparison is architectural rather than chronological. Similar user experiences can be produced by different identification, storage, transport, ranking and governance arrangements.
The World Wide Web converted a collection of networked machines and services into a potentially universal information space. Its decisive invention was not colourful pages. It was the combination of global identifiers, protocol interactions, transferable representations and links that independent publishers and software could implement.
That architecture reduced the need to know where every document lived or to use a bespoke interface for every collection. It also created new dependencies: identifier stewardship, server availability, compatible user agents, search, certificates, hosting and preservation. The Web decentralised the ability to publish more effectively than it decentralised attention.
Its history therefore contains both liberation and enclosure. Anyone can, in principle, publish a resource and link to another. In practice, a small set of browsers, search engines, platforms and infrastructure providers can decide which parts of that shared space are usable, trusted or visible.
The Web is a shared information space created by global identification, standard interactions, transferable representations and links. HTML pages are common occupants of that space, not the architecture itself.