{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"thinker-tim-berners-lee","title":"Tim Berners-Lee — The Universal Link and the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Tim Berners-Lee — The Universal Link and the Semantic Web**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Tim Berners-Lee — The Universal Link and the Semantic Web\n\n## §SELF — thinker-tim-berners-lee\n\n**What this page is:** A profile of the computer scientist who invented the World Wide Web and later proposed a machine-readable layer on top of it.\n**What it explains:** The URL as the core invention, the Semantic Web vision, why it failed, and why large language models make it possible now.\n**Why read it:** You will understand why the URL matters, what the Semantic Web was trying to do, and why its failure was a reader problem, not a data problem.\n\n### What Tim Berners-Lee Did\n\nTim Berners-Lee is a British computer scientist who invented the World Wide Web in 1989 while working at CERN (the European Organization for Nuclear Research). He created three technologies:\n\n- **HTTP (HyperText Transfer Protocol):** The rules for how a client (usually a web browser) asks a server for a resource and how the server responds. A protocol is a set of agreed-upon rules for communication.\n- **HTML (HyperText Markup Language):** The format for writing documents that can contain links to other documents. Markup means annotations added to text to give it structure (headings, paragraphs, links).\n- **URL (Uniform Resource Locator):** The addressing scheme that gives every piece of information on the web a permanent, unique address.\n\n### The Key Idea: The URL\n\nThe URL is Berners-Lee's most important invention. Before the URL, there was no universal way to point at a piece of information. A URL like `https://example.com/page` does three things at once: it names a resource, it says where to find it, and it says how to retrieve it.\n\nThis seems obvious now. It was not obvious then. The URL is what makes the web a web — every document can point to every other document, across any server, any organization, any country. A link in a document in Tokyo can point to a document in Toronto. The user clicks it and the browser knows exactly what to do.\n\n### The Semantic Web (2006)\n\nIn 2006, Berners-Lee proposed the Semantic Web. The idea: extend the web so that machines, not just humans, can understand the information. The core mechanism was to give every entity — every person, article, tool, service, concept — a URI (Uniform Resource Identifier). A URI is like a URL but more general: it identifies a thing without necessarily saying where to retrieve it.\n\nThe vision was that machines would traverse a graph of linked data. A graph, in computer science, is a structure made of nodes (things) connected by edges (relationships). If every entity has a URI and relationships are expressed as links between URIs, then a machine can follow links from one entity to another, building an understanding of how things connect.\n\nMeaning would live in the connections, not in the documents. A document says \"Alice works at Company X.\" The Semantic Web would encode this as a triple: Alice (subject) → works-at (predicate) → Company X (object). Each part is a URI. A machine could then traverse this graph and answer questions like \"Who works at Company X?\" by following the links.\n\n### Linked Data Principles\n\nBerners-Lee defined four rules for publishing data on the Semantic Web:\n\n1. Use URIs as names for things.\n2. Use HTTP URIs so people can look them up.\n3. When someone looks up a URI, provide useful information, using the standards (RDF, SPARQL).\n4. Include links to other URIs so they can discover more things.\n\nRDF (Resource Description Framework) is a format for expressing those subject-predicate-object triples. SPARQL is a query language for asking questions of RDF data stores.\n\n### What the Semantic Web Got Right\n\nThe idea was correct. Structuring knowledge as a graph of linked entities is a powerful way to represent meaning. The four Linked Data principles are sound. If machines could actually read and traverse these graphs, the web would be a database that answers questions instead of just serving pages.\n\n### What the Semantic Web Got Wrong or Left Unfinished\n\nIt failed because it needed a reader that understood what it was traversing, and no such reader existed.\n\nThe Semantic Web assumed that if you encoded facts as RDF triples and linked them together, machines would be able to reason over them. But a machine reading a triple like `http://example.org/Alice → http://example.org/works-at → http://example.org/CompanyX` does not know what \"works-at\" means. It knows the URI. It can look it up. But the response it gets is more RDF, more URIs, more things to look up. Without a way to *understand* the meaning of the predicates, the machine is just chasing pointers.\n\nThis is the same problem HATEOAS faced: links are only useful if the reader understands what they mean. Programmers tried to solve this with ontologies — formal definitions of what each URI means. But ontologies are brittle, expensive to build, and never covered enough of the world to be useful. The Semantic Web stalled because the web of data was built, but there was no agent that could read it.\n\n### Why This Is Changing Now\n\nA large language model (LLM) is a program trained on text that can infer meaning from context. An LLM encountering the triple above does not need an ontology. It knows what \"works-at\" means because it has read that phrase billions of times in natural language. It can traverse a graph of linked data and understand the relationships, because the relationships are expressed in terms it already knows.\n\nThe LLM is the reader the Semantic Web was waiting for.\n\n### Solid Protocol\n\nBerners-Lee's latest project is Solid (Social Linked Data). Solid is a protocol that gives users personal data pods — storage spaces they control, where their data lives. Applications ask permission to access the pod, and the user grants or denies it. The data in the pod uses linked data interfaces. Combined with LLMs that can read and reason over this linked data, Solid could enable a web where users own their data and intelligent agents act on their behalf.\n\n### How It Connects to Other Ideas\n\n- **Roy Fielding's REST:** The Semantic Web's graph of linked URIs is an extension of REST's hypermedia principle. Both assume a client that discovers meaning by following links. Both failed for the same reason until LLMs appeared.\n- **Object Interface Protocol (OIP):** OIP endpoints describe what they offer. An LLM can read an OIP endpoint's description (which uses linked data patterns) and understand how to interact with it, the same way it can read a Semantic Web graph.\n\n### Sources\n\n- Berners-Lee, Tim. \"Information Management: A Proposal.\" CERN, 1989. The original web proposal.\n- Berners-Lee, Tim, James Hendler, and Ora Lassila. \"The Semantic Web.\" *Scientific American*, May 2001.\n- Berners-Lee, Tim. \"Linked Data — Design Issues.\" W3C, 2006.\n- Solid Project: https://solidproject.org\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-tim-berners-lee`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-tim-berners-lee`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Tim%20Berners-Lee%20%E2%80%94%20The%20Universal%20Link%20and%20the%20Semantic%20Web`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-tim-berners-lee"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-tim-berners-lee/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:48.803Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"095c6a15d7aec2358cea6bea667285a211e9ae697cef28e531006eab0ea318e6"},{"ts":"2026-07-17T02:43:02.123Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-tim-berners-lee","response":"41 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"095c6a15d7aec2358cea6bea667285a211e9ae697cef28e531006eab0ea318e6","hash":"fe11f9daed293ace113b3a48e77fe6fcd585fd74f67bea7cd76882d57556da31"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"fe11f9daed293ace113b3a48e77fe6fcd585fd74f67bea7cd76882d57556da31"},"posted_at":"2026-07-15T04:20:48.803Z","created_at":"2026-07-15T04:20:48.803Z","updated_at":"2026-07-17T02:43:02.123Z","machine":{"shape":"article.machine/v1","slug":"thinker-tim-berners-lee","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-tim-berners-lee","json":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee","bundle":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-tim-berners-lee","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-tim-berners-lee\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-tim-berners-lee\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-tim-berners-lee/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-tim-berners-lee\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-tim-berners-lee | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-tim-berners-lee","json":"/api/articles/thinker-tim-berners-lee","markdown":"/api/articles/thinker-tim-berners-lee/bundle?format=markdown","skill":"/api/articles/thinker-tim-berners-lee/skill","topology":"/api/articles/thinker-tim-berners-lee/topology","versions":"/api/articles/thinker-tim-berners-lee/revisions","invocations":"/api/articles/thinker-tim-berners-lee/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-tim-berners-lee","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"b67974500159e64fc41a5c0790c31daf715b16531fe966fdbd9839496fa8481b","object":{"object_type":"article-object","identity":{"id":"article:thinker-tim-berners-lee","slug":"thinker-tim-berners-lee","title":"Tim Berners-Lee — The Universal Link and the Semantic Web"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/thinker-tim-berners-lee","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-tim-berners-lee/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-tim-berners-lee\ndescription: Apply the Tim Berners-Lee — The Universal Link and the Semantic Web article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Tim Berners-Lee — The Universal Link and the Semantic Web\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-tim-berners-lee). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-tim-berners-lee.\n- Read claims and relationships at /api/articles/thinker-tim-berners-lee/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- hierarchy:nav -- Path: OIP https://miscsubjects.com/a/oip › Thinker Reference https://miscsubjects.com/a/oip-thinker-reference › Thinkers https://miscsubjects.com/a/oip-thinkers › Tim Berners-Lee — The Universal Link and the Semantic W\n\n## Representations\n\n- Human: /a/thinker-tim-berners-lee\n- JSON: /api/articles/thinker-tim-berners-lee\n- Relationships: /api/articles/thinker-tim-berners-lee/topology\n- History: /api/articles/thinker-tim-berners-lee/revisions\n"},"json":{"route":"/api/articles/thinker-tim-berners-lee","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-tim-berners-lee/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-tim-berners-lee","thinker","tim","berners","lee"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-tim-berners-lee/invocations?status=success","failure_events":"/api/articles/thinker-tim-berners-lee/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"thinker-tim-berners-lee","title":"Tim Berners-Lee — The Universal Link and the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Tim Berners-Lee — The Universal Link and the Semantic Web**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Tim Berners-Lee — The Universal Link and the Semantic Web\n\n## §SELF — thinker-tim-berners-lee\n\n**What this page is:** A profile of the computer scientist who invented the World Wide Web and later proposed a machine-readable layer on top of it.\n**What it explains:** The URL as the core invention, the Semantic Web vision, why it failed, and why large language models make it possible now.\n**Why read it:** You will understand why the URL matters, what the Semantic Web was trying to do, and why its failure was a reader problem, not a data problem.\n\n### What Tim Berners-Lee Did\n\nTim Berners-Lee is a British computer scientist who invented the World Wide Web in 1989 while working at CERN (the European Organization for Nuclear Research). He created three technologies:\n\n- **HTTP (HyperText Transfer Protocol):** The rules for how a client (usually a web browser) asks a server for a resource and how the server responds. A protocol is a set of agreed-upon rules for communication.\n- **HTML (HyperText Markup Language):** The format for writing documents that can contain links to other documents. Markup means annotations added to text to give it structure (headings, paragraphs, links).\n- **URL (Uniform Resource Locator):** The addressing scheme that gives every piece of information on the web a permanent, unique address.\n\n### The Key Idea: The URL\n\nThe URL is Berners-Lee's most important invention. Before the URL, there was no universal way to point at a piece of information. A URL like `https://example.com/page` does three things at once: it names a resource, it says where to find it, and it says how to retrieve it.\n\nThis seems obvious now. It was not obvious then. The URL is what makes the web a web — every document can point to every other document, across any server, any organization, any country. A link in a document in Tokyo can point to a document in Toronto. The user clicks it and the browser knows exactly what to do.\n\n### The Semantic Web (2006)\n\nIn 2006, Berners-Lee proposed the Semantic Web. The idea: extend the web so that machines, not just humans, can understand the information. The core mechanism was to give every entity — every person, article, tool, service, concept — a URI (Uniform Resource Identifier). A URI is like a URL but more general: it identifies a thing without necessarily saying where to retrieve it.\n\nThe vision was that machines would traverse a graph of linked data. A graph, in computer science, is a structure made of nodes (things) connected by edges (relationships). If every entity has a URI and relationships are expressed as links between URIs, then a machine can follow links from one entity to another, building an understanding of how things connect.\n\nMeaning would live in the connections, not in the documents. A document says \"Alice works at Company X.\" The Semantic Web would encode this as a triple: Alice (subject) → works-at (predicate) → Company X (object). Each part is a URI. A machine could then traverse this graph and answer questions like \"Who works at Company X?\" by following the links.\n\n### Linked Data Principles\n\nBerners-Lee defined four rules for publishing data on the Semantic Web:\n\n1. Use URIs as names for things.\n2. Use HTTP URIs so people can look them up.\n3. When someone looks up a URI, provide useful information, using the standards (RDF, SPARQL).\n4. Include links to other URIs so they can discover more things.\n\nRDF (Resource Description Framework) is a format for expressing those subject-predicate-object triples. SPARQL is a query language for asking questions of RDF data stores.\n\n### What the Semantic Web Got Right\n\nThe idea was correct. Structuring knowledge as a graph of linked entities is a powerful way to represent meaning. The four Linked Data principles are sound. If machines could actually read and traverse these graphs, the web would be a database that answers questions instead of just serving pages.\n\n### What the Semantic Web Got Wrong or Left Unfinished\n\nIt failed because it needed a reader that understood what it was traversing, and no such reader existed.\n\nThe Semantic Web assumed that if you encoded facts as RDF triples and linked them together, machines would be able to reason over them. But a machine reading a triple like `http://example.org/Alice → http://example.org/works-at → http://example.org/CompanyX` does not know what \"works-at\" means. It knows the URI. It can look it up. But the response it gets is more RDF, more URIs, more things to look up. Without a way to *understand* the meaning of the predicates, the machine is just chasing pointers.\n\nThis is the same problem HATEOAS faced: links are only useful if the reader understands what they mean. Programmers tried to solve this with ontologies — formal definitions of what each URI means. But ontologies are brittle, expensive to build, and never covered enough of the world to be useful. The Semantic Web stalled because the web of data was built, but there was no agent that could read it.\n\n### Why This Is Changing Now\n\nA large language model (LLM) is a program trained on text that can infer meaning from context. An LLM encountering the triple above does not need an ontology. It knows what \"works-at\" means because it has read that phrase billions of times in natural language. It can traverse a graph of linked data and understand the relationships, because the relationships are expressed in terms it already knows.\n\nThe LLM is the reader the Semantic Web was waiting for.\n\n### Solid Protocol\n\nBerners-Lee's latest project is Solid (Social Linked Data). Solid is a protocol that gives users personal data pods — storage spaces they control, where their data lives. Applications ask permission to access the pod, and the user grants or denies it. The data in the pod uses linked data interfaces. Combined with LLMs that can read and reason over this linked data, Solid could enable a web where users own their data and intelligent agents act on their behalf.\n\n### How It Connects to Other Ideas\n\n- **Roy Fielding's REST:** The Semantic Web's graph of linked URIs is an extension of REST's hypermedia principle. Both assume a client that discovers meaning by following links. Both failed for the same reason until LLMs appeared.\n- **Object Interface Protocol (OIP):** OIP endpoints describe what they offer. An LLM can read an OIP endpoint's description (which uses linked data patterns) and understand how to interact with it, the same way it can read a Semantic Web graph.\n\n### Sources\n\n- Berners-Lee, Tim. \"Information Management: A Proposal.\" CERN, 1989. The original web proposal.\n- Berners-Lee, Tim, James Hendler, and Ora Lassila. \"The Semantic Web.\" *Scientific American*, May 2001.\n- Berners-Lee, Tim. \"Linked Data — Design Issues.\" W3C, 2006.\n- Solid Project: https://solidproject.org\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-tim-berners-lee`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-tim-berners-lee`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Tim%20Berners-Lee%20%E2%80%94%20The%20Universal%20Link%20and%20the%20Semantic%20Web`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-tim-berners-lee"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-tim-berners-lee/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:48.803Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"095c6a15d7aec2358cea6bea667285a211e9ae697cef28e531006eab0ea318e6"},{"ts":"2026-07-17T02:43:02.123Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-tim-berners-lee","response":"41 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"095c6a15d7aec2358cea6bea667285a211e9ae697cef28e531006eab0ea318e6","hash":"fe11f9daed293ace113b3a48e77fe6fcd585fd74f67bea7cd76882d57556da31"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"fe11f9daed293ace113b3a48e77fe6fcd585fd74f67bea7cd76882d57556da31"},"posted_at":"2026-07-15T04:20:48.803Z","created_at":"2026-07-15T04:20:48.803Z","updated_at":"2026-07-17T02:43:02.123Z","machine":{"shape":"article.machine/v1","slug":"thinker-tim-berners-lee","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-tim-berners-lee","json":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee","bundle":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-tim-berners-lee/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-tim-berners-lee","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-tim-berners-lee\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-tim-berners-lee\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-tim-berners-lee/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-tim-berners-lee\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-tim-berners-lee | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-tim-berners-lee","json":"/api/articles/thinker-tim-berners-lee","markdown":"/api/articles/thinker-tim-berners-lee/bundle?format=markdown","skill":"/api/articles/thinker-tim-berners-lee/skill","topology":"/api/articles/thinker-tim-berners-lee/topology","versions":"/api/articles/thinker-tim-berners-lee/revisions","invocations":"/api/articles/thinker-tim-berners-lee/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-tim-berners-lee","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"b67974500159e64fc41a5c0790c31daf715b16531fe966fdbd9839496fa8481b"}}}