{"_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":"what-is-semantic-web","title":"What Is the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is the Semantic Web**\n>\n> **Shelf:** Protocol Concepts · **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# What Is the Semantic Web\n\n## §SELF — what-is-semantic-web\n\n**What this page is:** A description of the Semantic Web vision, its technologies, and why it did not achieve wide adoption.\n**What it explains:** RDF, RDFS, OWL, SPARQL, JSON-LD, and Linked Data principles.\n**Why read it:** To understand how machine-readable data on the web works, why the original vision stalled, and how large language models change the equation.\n\n### What the Semantic Web Is\n\nThe Semantic Web is Tim Berners-Lee's vision (first articulated in a 2001 Scientific American article, then formalized through W3C standards from 2001 to 2010 and beyond) of a web where data is machine-readable, not just human-readable. The core proposition: web pages should contain structured, labeled data that software can parse, reason about, and connect automatically.\n\n### Why It Matters\n\nThe web as originally built contains pages (documents) linked by hyperlinks. Humans read the pages and understand the links. Machines can fetch pages and follow links, but they cannot understand what the content means. The Semantic Web attempted to solve this by adding semantic annotations — labels that say \"this string is a person's name\" or \"this number is a price.\" Search engines partially adopted this (Google Rich Snippets, Facebook Open Graph). The broader vision — a global graph of interconnected, machine-understandable data — never reached critical mass because there was no general-purpose consumer that could traverse and use the graph.\n\n### The Key Idea\n\nThe Resource Description Framework (RDF) is the data model. Every piece of information is a triple: subject-predicate-object. Example: `<Alice> <knows> <Bob>` or `<Alice> <age> \"30\"`. Each element in a triple is identified by a URI (Uniform Resource Identifier), a global identifier analogous to a URL but for things rather than pages. A collection of triples forms a directed graph: subjects and objects are nodes, predicates are labeled edges. Programs can traverse this graph by following edges from node to node.\n\nRDF Schema (RDFS) adds a vocabulary for defining types (`rdfs:Class`) and properties (`rdfs:Property`), and relationships like `rdfs:subClassOf` (one type is a subset of another).\n\nOWL (Web Ontology Language) extends RDFS with logical constructs: you can state that a property is transitive (if A is-connected-to B and B is-connected-to C, then A is-connected-to C), or that two classes are disjoint (nothing is both a Mammal and a Reptile). OWL reasoners can infer new triples from existing ones.\n\nSPARQL is a query language for RDF graphs. It resembles SQL but operates on triple patterns. You ask for all bindings of variables that match a set of triple patterns in the graph.\n\nJSON-LD (JavaScript Object Notation for Linked Data) is a way to embed RDF triples inside ordinary JSON objects using `@context` to map keys to URIs. It allows web APIs to serve semantic data without requiring consumers to understand RDF explicitly.\n\n### What They Got Right\n\n**Linked Data principles (Berners-Lee, 2006).** Four rules: (1) Use URIs as names for things. (2) Use HTTP URIs so those names can be looked up. (3) When someone looks up a URI, provide useful information (using RDF, SPARQL, etc.). (4) Include links to other URIs so more things can be discovered. These principles are sound and underpin modern API design, even where RDF is not used.\n\n**The graph model.** Representing knowledge as a graph (nodes connected by labeled edges) is the correct abstraction for many types of data. Graph databases (Neo4j, Amazon Neptune) and knowledge graphs (Google Knowledge Graph, Wikidata) use this model successfully.\n\n**JSON-LD as a bridge.** JSON-LD achieves interoperability: existing JSON parsers can read it, and RDF tools can extract semantic triples from it. It is the most widely adopted Semantic Web technology in practice.\n\n**Wikidata.** A collaborative knowledge base of over 100 million items, each with a URI, described in RDF. It is the largest working implementation of the Semantic Web vision.\n\n### What They Got Wrong or Left Unfinished\n\n**No consumer application.** The Semantic Web built a data infrastructure but never created the application that would make that infrastructure valuable to end users. Without a reason to publish structured data, publishers did not. This is a chicken-and-egg problem: no data means no applications, no applications means no incentive to publish data.\n\n**OWL was too complex.** The full OWL language (OWL 2 DL) is undecidable in some profiles — meaning a reasoner might run forever on certain inputs. Simpler subsets were defined but the complexity discouraged adoption.\n\n**The ontology construction bottleneck.** Building accurate, shared ontologies (agreed-upon vocabularies for a domain) requires domain experts, logicians, and ongoing maintenance. Most organizations could not afford this effort.\n\n**Assumed publishers would annotate.** The vision required content creators to add semantic markup manually. In practice, most publishers do not. Automated extraction (parsing natural language, scraping tables) turned out to be more scalable.\n\n### How It Connects to Other Ideas\n\n**Knowledge graphs.** Google's Knowledge Graph, Wikidata, and enterprise knowledge graphs are direct descendants of the Semantic Web. They use the RDF graph model but typically simplify or bypass OWL reasoning in favor of direct query and embedding-based methods.\n\n**Schema.org.** A collaborative vocabulary (founded by Google, Microsoft, Yahoo, and Yandex) for annotating web pages. It uses the Semantic Web stack (RDF, JSON-LD) but restricts the vocabulary to a manageable set of types and properties. It is the most successful practical application of Semantic Web technology.\n\n**Large language models.** An LLM can parse text, extract entities and relationships, and traverse linked data. It is the first general-purpose consumer that can take a URI, fetch the data at that URI, interpret it in context, and follow links to other URIs. This addresses the original missing-consumer problem.\n\n**Linked Open Data.** A project to publish existing open datasets (government data, scientific data, cultural heritage) as RDF on the web. DBpedia (structured data extracted from Wikipedia) is the largest Linked Open Data source.\n\n### Sources\n\nBerners-Lee, T., Hendler, J., & Lassila, O. (2001). \"The Semantic Web.\" *Scientific American*, 284(5), 34-43.\n\nBerners-Lee, T. (2006). \"Linked Data — Design Issues.\" W3C. https://www.w3.org/DesignIssues/LinkedData.html\n\nW3C. (2014). \"JSON-LD 1.0.\" W3C Recommendation. https://www.w3.org/TR/json-ld/\n\nW3C. (2012). \"OWL 2 Web Ontology Language Document Overview.\" W3C Recommendation. https://www.w3.org/TR/owl2-overview/\n\nHogan, A. et al. (2021). *Knowledge Graphs*. Morgan & Claypool.\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- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — 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- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-semantic-web`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-semantic-web`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20the%20Semantic%20Web`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: machine-readable operations without requiring a global ontology committee — local object contracts + registry.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-semantic-web","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-semantic-web/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: Protocol Concepts (oip-protocol-concepts). 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":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: machine-readable operations without requiring a global ontology committee — local object contracts + registry."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:04.697Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"415a613b2e92970b8c277f409300460120d293d5e25b4323db014e615881efdd"},{"ts":"2026-07-15T06:25:01.084Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"415a613b2e92970b8c277f409300460120d293d5e25b4323db014e615881efdd","hash":"1cb3899bb0c98e716fdf8d8f7217b517a77d0282d46f5cc40f852038faa7a0ef"},{"ts":"2026-07-17T02:43:40.036Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-semantic-web","response":"46 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"1cb3899bb0c98e716fdf8d8f7217b517a77d0282d46f5cc40f852038faa7a0ef","hash":"4513066124f3bac818a4dc0376cd4ddbf63452f6a05b9ff57bc9feac7d806e40"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"4513066124f3bac818a4dc0376cd4ddbf63452f6a05b9ff57bc9feac7d806e40"},"posted_at":"2026-07-15T04:21:04.697Z","created_at":"2026-07-15T04:21:04.697Z","updated_at":"2026-07-17T02:43:40.036Z","machine":{"shape":"article.machine/v1","slug":"what-is-semantic-web","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-semantic-web","json":"https://miscsubjects.com/api/articles/what-is-semantic-web","bundle":"https://miscsubjects.com/api/articles/what-is-semantic-web/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-semantic-web/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-semantic-web","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\":\"what-is-semantic-web\",\"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\":\"what-is-semantic-web\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-semantic-web/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\":\"what-is-semantic-web\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-semantic-web | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-semantic-web","json":"/api/articles/what-is-semantic-web","markdown":"/api/articles/what-is-semantic-web/bundle?format=markdown","skill":"/api/articles/what-is-semantic-web/skill","topology":"/api/articles/what-is-semantic-web/topology","versions":"/api/articles/what-is-semantic-web/revisions","invocations":"/api/articles/what-is-semantic-web/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-semantic-web","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"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":"43f5c5e29e36c4a94fd1b1003630884bbabc3af352b98c0f0f422d0dd7e77152","object":{"object_type":"article-object","identity":{"id":"article:what-is-semantic-web","slug":"what-is-semantic-web","title":"What Is 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/what-is-semantic-web","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-semantic-web/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-semantic-web\ndescription: Apply the What Is the Semantic Web article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is the Semantic Web\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-semantic-web). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-semantic-web.\n- Read claims and relationships at /api/articles/what-is-semantic-web/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 › Protocol Concepts https://miscsubjects.com/a/oip-protocol-concepts › What Is the Semantic Web Shelf: Proto\n\n## Representations\n\n- Human: /a/what-is-semantic-web\n- JSON: /api/articles/what-is-semantic-web\n- Relationships: /api/articles/what-is-semantic-web/topology\n- History: /api/articles/what-is-semantic-web/revisions\n"},"json":{"route":"/api/articles/what-is-semantic-web","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-semantic-web/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","concepts","what-is-semantic-web","objection-7","oip-edge","what","is","semantic","web"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-semantic-web/invocations?status=success","failure_events":"/api/articles/what-is-semantic-web/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":"what-is-semantic-web","title":"What Is the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is the Semantic Web**\n>\n> **Shelf:** Protocol Concepts · **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# What Is the Semantic Web\n\n## §SELF — what-is-semantic-web\n\n**What this page is:** A description of the Semantic Web vision, its technologies, and why it did not achieve wide adoption.\n**What it explains:** RDF, RDFS, OWL, SPARQL, JSON-LD, and Linked Data principles.\n**Why read it:** To understand how machine-readable data on the web works, why the original vision stalled, and how large language models change the equation.\n\n### What the Semantic Web Is\n\nThe Semantic Web is Tim Berners-Lee's vision (first articulated in a 2001 Scientific American article, then formalized through W3C standards from 2001 to 2010 and beyond) of a web where data is machine-readable, not just human-readable. The core proposition: web pages should contain structured, labeled data that software can parse, reason about, and connect automatically.\n\n### Why It Matters\n\nThe web as originally built contains pages (documents) linked by hyperlinks. Humans read the pages and understand the links. Machines can fetch pages and follow links, but they cannot understand what the content means. The Semantic Web attempted to solve this by adding semantic annotations — labels that say \"this string is a person's name\" or \"this number is a price.\" Search engines partially adopted this (Google Rich Snippets, Facebook Open Graph). The broader vision — a global graph of interconnected, machine-understandable data — never reached critical mass because there was no general-purpose consumer that could traverse and use the graph.\n\n### The Key Idea\n\nThe Resource Description Framework (RDF) is the data model. Every piece of information is a triple: subject-predicate-object. Example: `<Alice> <knows> <Bob>` or `<Alice> <age> \"30\"`. Each element in a triple is identified by a URI (Uniform Resource Identifier), a global identifier analogous to a URL but for things rather than pages. A collection of triples forms a directed graph: subjects and objects are nodes, predicates are labeled edges. Programs can traverse this graph by following edges from node to node.\n\nRDF Schema (RDFS) adds a vocabulary for defining types (`rdfs:Class`) and properties (`rdfs:Property`), and relationships like `rdfs:subClassOf` (one type is a subset of another).\n\nOWL (Web Ontology Language) extends RDFS with logical constructs: you can state that a property is transitive (if A is-connected-to B and B is-connected-to C, then A is-connected-to C), or that two classes are disjoint (nothing is both a Mammal and a Reptile). OWL reasoners can infer new triples from existing ones.\n\nSPARQL is a query language for RDF graphs. It resembles SQL but operates on triple patterns. You ask for all bindings of variables that match a set of triple patterns in the graph.\n\nJSON-LD (JavaScript Object Notation for Linked Data) is a way to embed RDF triples inside ordinary JSON objects using `@context` to map keys to URIs. It allows web APIs to serve semantic data without requiring consumers to understand RDF explicitly.\n\n### What They Got Right\n\n**Linked Data principles (Berners-Lee, 2006).** Four rules: (1) Use URIs as names for things. (2) Use HTTP URIs so those names can be looked up. (3) When someone looks up a URI, provide useful information (using RDF, SPARQL, etc.). (4) Include links to other URIs so more things can be discovered. These principles are sound and underpin modern API design, even where RDF is not used.\n\n**The graph model.** Representing knowledge as a graph (nodes connected by labeled edges) is the correct abstraction for many types of data. Graph databases (Neo4j, Amazon Neptune) and knowledge graphs (Google Knowledge Graph, Wikidata) use this model successfully.\n\n**JSON-LD as a bridge.** JSON-LD achieves interoperability: existing JSON parsers can read it, and RDF tools can extract semantic triples from it. It is the most widely adopted Semantic Web technology in practice.\n\n**Wikidata.** A collaborative knowledge base of over 100 million items, each with a URI, described in RDF. It is the largest working implementation of the Semantic Web vision.\n\n### What They Got Wrong or Left Unfinished\n\n**No consumer application.** The Semantic Web built a data infrastructure but never created the application that would make that infrastructure valuable to end users. Without a reason to publish structured data, publishers did not. This is a chicken-and-egg problem: no data means no applications, no applications means no incentive to publish data.\n\n**OWL was too complex.** The full OWL language (OWL 2 DL) is undecidable in some profiles — meaning a reasoner might run forever on certain inputs. Simpler subsets were defined but the complexity discouraged adoption.\n\n**The ontology construction bottleneck.** Building accurate, shared ontologies (agreed-upon vocabularies for a domain) requires domain experts, logicians, and ongoing maintenance. Most organizations could not afford this effort.\n\n**Assumed publishers would annotate.** The vision required content creators to add semantic markup manually. In practice, most publishers do not. Automated extraction (parsing natural language, scraping tables) turned out to be more scalable.\n\n### How It Connects to Other Ideas\n\n**Knowledge graphs.** Google's Knowledge Graph, Wikidata, and enterprise knowledge graphs are direct descendants of the Semantic Web. They use the RDF graph model but typically simplify or bypass OWL reasoning in favor of direct query and embedding-based methods.\n\n**Schema.org.** A collaborative vocabulary (founded by Google, Microsoft, Yahoo, and Yandex) for annotating web pages. It uses the Semantic Web stack (RDF, JSON-LD) but restricts the vocabulary to a manageable set of types and properties. It is the most successful practical application of Semantic Web technology.\n\n**Large language models.** An LLM can parse text, extract entities and relationships, and traverse linked data. It is the first general-purpose consumer that can take a URI, fetch the data at that URI, interpret it in context, and follow links to other URIs. This addresses the original missing-consumer problem.\n\n**Linked Open Data.** A project to publish existing open datasets (government data, scientific data, cultural heritage) as RDF on the web. DBpedia (structured data extracted from Wikipedia) is the largest Linked Open Data source.\n\n### Sources\n\nBerners-Lee, T., Hendler, J., & Lassila, O. (2001). \"The Semantic Web.\" *Scientific American*, 284(5), 34-43.\n\nBerners-Lee, T. (2006). \"Linked Data — Design Issues.\" W3C. https://www.w3.org/DesignIssues/LinkedData.html\n\nW3C. (2014). \"JSON-LD 1.0.\" W3C Recommendation. https://www.w3.org/TR/json-ld/\n\nW3C. (2012). \"OWL 2 Web Ontology Language Document Overview.\" W3C Recommendation. https://www.w3.org/TR/owl2-overview/\n\nHogan, A. et al. (2021). *Knowledge Graphs*. Morgan & Claypool.\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- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — 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- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-semantic-web`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-semantic-web`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20the%20Semantic%20Web`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: machine-readable operations without requiring a global ontology committee — local object contracts + registry.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-semantic-web","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-semantic-web/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: Protocol Concepts (oip-protocol-concepts). 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":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: machine-readable operations without requiring a global ontology committee — local object contracts + registry."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:04.697Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"415a613b2e92970b8c277f409300460120d293d5e25b4323db014e615881efdd"},{"ts":"2026-07-15T06:25:01.084Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"415a613b2e92970b8c277f409300460120d293d5e25b4323db014e615881efdd","hash":"1cb3899bb0c98e716fdf8d8f7217b517a77d0282d46f5cc40f852038faa7a0ef"},{"ts":"2026-07-17T02:43:40.036Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-semantic-web","response":"46 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"1cb3899bb0c98e716fdf8d8f7217b517a77d0282d46f5cc40f852038faa7a0ef","hash":"4513066124f3bac818a4dc0376cd4ddbf63452f6a05b9ff57bc9feac7d806e40"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"4513066124f3bac818a4dc0376cd4ddbf63452f6a05b9ff57bc9feac7d806e40"},"posted_at":"2026-07-15T04:21:04.697Z","created_at":"2026-07-15T04:21:04.697Z","updated_at":"2026-07-17T02:43:40.036Z","machine":{"shape":"article.machine/v1","slug":"what-is-semantic-web","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-semantic-web","json":"https://miscsubjects.com/api/articles/what-is-semantic-web","bundle":"https://miscsubjects.com/api/articles/what-is-semantic-web/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-semantic-web/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-semantic-web","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\":\"what-is-semantic-web\",\"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\":\"what-is-semantic-web\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-semantic-web/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\":\"what-is-semantic-web\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-semantic-web | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-semantic-web","json":"/api/articles/what-is-semantic-web","markdown":"/api/articles/what-is-semantic-web/bundle?format=markdown","skill":"/api/articles/what-is-semantic-web/skill","topology":"/api/articles/what-is-semantic-web/topology","versions":"/api/articles/what-is-semantic-web/revisions","invocations":"/api/articles/what-is-semantic-web/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-semantic-web","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"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":"43f5c5e29e36c4a94fd1b1003630884bbabc3af352b98c0f0f422d0dd7e77152"}}}