ENQUIRE
software project written in 1980 by Tim Berners-Lee at CERN
ENQUIRE was a software project written in 1980 by Tim Berners-Lee at CERN, which was the predecessor to the World Wide Web. It was a simple hypertext program that had some of the same ideas as the Web and the Semantic Web but was different in several important ways.
According to Berners-Lee, the name was inspired by the title of an old how-to book, Enquire Within upon Everything.
The conditions
Around 1980, approximately 10,000 people were working at CERN with different hardware, software and individual requirements. Much work was done by email and file exchange, which the scientists used to keep track of different parts of intersecting projects. Berners-Lee started to work for 6 months on 23 June 1980 at CERN, where he developed ENQUIRE as a personal organizational tool. The requirements for setting up a new system were compatibility with different networks, disk formats, data formats, and character encoding schemes, which made any attempt to transfer information between dissimilar systems a daunting and generally impractical task. When Berners-Lee built ENQUIRE, he was not aware of the prior ideas about Memex, NLS and Project Xanadu developed by Vannevar Bush, Douglas Engelbart and Ted Nelson. Only after his work on ENQUIRE, as Berners-Lee began to refine his ideas, did the work of these predecessors help to confirm the legitimacy of his concept.
Differences to the World Wide Web
ENQUIRE had pages called cards and hyperlinks within the cards.
Begin with the source’s own compact description: “ENQUIRE” is software project written in 1980 by Tim Berners-Lee at CERN. The dossier treats that line as a proposition to test through ENQUIRE, software and project, not as a finished interpretation.
Why this record matters
The phrase “software project written in 1980 by Tim Berners-Lee at CERN” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Sep 1, 2026. The linked authority identifier is Q2385520. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1980.
A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “ENQUIRE”, its source revision and the description used here.
- Expand the search: follow ENQUIRE primary sources, ENQUIRE archive and ENQUIRE research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “ENQUIRE”?
- Which observation, specimen, dataset or publication supports the account?
- Is the terminology current, historical or disputed?
Search terms from this dossier
This entry incorporates text from “ENQUIRE” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.