{"slug":"oip-from-semantic-web","title":"What OIP Should Take from the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [OIP Lineages](https://miscsubjects.com/a/oip-from-lineages) › **What OIP Should Take from the Semantic Web**\n>\n> **Shelf:** OIP Lineages · **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 OIP Should Take from the Semantic Web\n\n## §SELF — oip-from-semantic-web\n\n**What this page is:** A list of Semantic Web technologies and principles that OIP adopts, plus the parts OIP explicitly rejects.\n**What it explains:** How machine-readable web data standards apply to OIP objects and why OIP uses only a subset.\n**Why read it:** To understand why OIP objects are described the way they are — and why some Semantic Web technologies are left out.\n\n### What the Semantic Web Is\n\nThe Semantic Web is Tim Berners-Lee's vision (articulated 2001–2010 and beyond) of a web where data is structured so machines can read and process it directly. Instead of HTML pages meant for human eyes, the Semantic Web publishes data in formats (RDF, JSON-LD) that software can parse, link, and reason over. The core idea: give every piece of data a persistent URI, describe it in a standard vocabulary, and link it to other data so machines can traverse the graph.\n\n### Why It Matters\n\nThe web succeeded for humans because pages link to each other. The Semantic Web attempted the same for machines. It partially succeeded: JSON-LD is widely used, schema.org markup is common, and Linked Data principles power knowledge graphs at major organizations. It partially failed: the full stack (OWL reasoning, RDF/XML, SPARQL endpoints at scale) proved too complex and slow for general use. OIP takes the parts that worked and discards the parts that did not.\n\n### The Key Idea\n\nOIP objects should be describable in standard, machine-readable formats so any tool — not just OIP-native models — can discover what an object does, what parameters it accepts, and how to invoke it. The description format should be parseable by existing Linked Data tools. The description should not require a heavy reasoning engine or a complex ontology stack to interpret.\n\n### What OIP Takes from the Semantic Web\n\n**JSON-LD for object descriptions.** JSON-LD (JavaScript Object Notation for Linked Data) is a JSON format that embeds semantic context. An OIP object contract written in JSON-LD is parseable as ordinary JSON by simple tools and as Linked Data by Semantic Web tools. This gives interoperability for free: a model can read it as JSON; a knowledge graph can ingest it as RDF. No format conversion needed.\n\n**URI as identity.** In the Semantic Web, a URI (Uniform Resource Identifier) is not just an address you look up. It is the permanent identifier of the thing itself. OIP applies this: every object, every receipt, every capability has a URI. The URI is the name of the entity. If you have the URI, you can refer to the entity unambiguously forever.\n\n**Graph traversal.** The Semantic Web organizes data as a graph of triples — subject, predicate, object. OIP's voxel graph (the structure of objects, receipts, and their relationships) should be exportable as RDF triples. An external tool should be able to query the graph with SPARQL-like queries: find all receipts for this object, find all objects created by this model, find all capabilities derived from this parent token. The graph is queryable.\n\n**Linked Data principles.** Tim Berners-Lee defined four Linked Data principles: (1) use HTTP URIs as identifiers; (2) return useful information when those URIs are looked up; (3) include links to other URIs; (4) use standard formats (RDF, JSON-LD). OIP follows all four. An OIP object URI returns the object's contract and current state when dereferenced. The contract includes URIs linking to related objects, receipts, and capabilities.\n\n**Hydra vocabulary.** Hydra is a lightweight vocabulary for describing web APIs in RDF. OIP uses Hydra's `Operation`, `supportedProperty`, and `statusCodes` to describe object contracts. `Operation` declares what actions an object supports. `supportedProperty` declares what parameters each action requires. `statusCodes` declares what responses the object can return. A model reading the contract knows, without trial and error, how to interact with the object.\n\n### What OIP Does Not Take from the Semantic Web\n\n**OWL reasoning.** OWL (Web Ontology Language) is a formal language for defining complex ontologies and performing logical inference. It is powerful but slow. OWL reasoning engines can take seconds or minutes to classify a moderately complex ontology. This is acceptable for offline knowledge-base construction. It is unacceptable for runtime model interaction. OIP does not use OWL reasoning.\n\n**RDF/XML.** RDF/XML is the original W3C standard format for RDF data. It is verbose, difficult to read, and unpopular. JSON-LD supersedes it for all practical purposes. OIP uses JSON-LD exclusively. No RDF/XML.\n\n**The full Semantic Web stack.** The complete Semantic Web vision includes multiple layers: URIs, Unicode, XML, RDF, RDF Schema, OWL, rules, proof, trust. Each layer adds complexity. OIP takes the bottom layers (URIs, JSON-LD/RDF, basic vocabularies) and stops. It does not implement the upper layers because they add machinery without adding value for model-to-model interaction.\n\n### The Boundary\n\nOIP takes the parts of the Semantic Web that make objects discoverable and interoperable. OIP leaves the parts that add complexity without practical value for runtime execution. The test is simple: if a technology helps a model find an object, understand its contract, and invoke it — OIP uses it. If the technology is designed for offline reasoning, ontology engineering, or philosophical completeness — OIP does not.\n\n### Sources\n\n- Berners-Lee, Tim, James Hendler, and Ora Lassila. \"The Semantic Web.\" *Scientific American,* 2001. (Original vision statement.)\n- Berners-Lee, Tim. \"Linked Data — Design Issues.\" W3C, 2006. (The four Linked Data principles.)\n- Lanthaler, Markus, and Christian Gütl. \"On Using JSON-LD to Create Evolvable RESTful Services.\" *WWW Companion,* 2012. (JSON-LD for API descriptions.)\n- Lanthaler, Markus. \"Creating 3rd Generation Web APIs with Hydra.\" *WWW Companion,* 2013. (Hydra vocabulary.)\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- [OIP Lineages shelf](https://miscsubjects.com/a/oip-from-lineages) — 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 OIP Should Take from Capability Security](https://miscsubjects.com/a/oip-from-capability-security)\n- [What OIP Should Take from REST](https://miscsubjects.com/a/oip-from-rest)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/oip-from-semantic-web`\n- JSON article: `https://miscsubjects.com/api/articles/oip-from-semantic-web`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20OIP%20Should%20Take%20from%20the%20Semantic%20Web`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","lineages","oip-from-semantic-web"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/oip-from-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: OIP Lineages (oip-from-lineages). 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":3,"label":"OIP Lineages on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:24.973Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"904cd9b942aaf87dd83dbf29434060a0f5b8ef4ec6158acd0c58f230c39af675"},{"ts":"2026-07-17T02:36:13.081Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-from-semantic-web","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"904cd9b942aaf87dd83dbf29434060a0f5b8ef4ec6158acd0c58f230c39af675","hash":"9a91e28e0a58159066a9650f1f1b9a22f0c6cf75d98c72de141d43f01ec3bacd"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"9a91e28e0a58159066a9650f1f1b9a22f0c6cf75d98c72de141d43f01ec3bacd"},"posted_at":"2026-07-15T04:20:24.973Z","created_at":"2026-07-15T04:20:24.973Z","updated_at":"2026-07-17T02:36:13.081Z","machine":{"shape":"article.machine/v1","slug":"oip-from-semantic-web","kind":"article","read":{"human":"https://miscsubjects.com/a/oip-from-semantic-web","json":"https://miscsubjects.com/api/articles/oip-from-semantic-web","bundle":"https://miscsubjects.com/api/articles/oip-from-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":0,"objections_url":"https://miscsubjects.com/api/articles/oip-from-semantic-web/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-from-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\":\"oip-from-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\":\"oip-from-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/oip-from-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\":\"oip-from-semantic-web\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-from-semantic-web | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-from-semantic-web","json":"/api/articles/oip-from-semantic-web","markdown":"/api/articles/oip-from-semantic-web/bundle?format=markdown","skill":"/api/articles/oip-from-semantic-web/skill","topology":"/api/articles/oip-from-semantic-web/topology","versions":"/api/articles/oip-from-semantic-web/revisions","invocations":"/api/articles/oip-from-semantic-web/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-from-semantic-web","slug":"oip-from-semantic-web","title":"What OIP Should Take from 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/oip-from-semantic-web","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-from-semantic-web/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-from-semantic-web\ndescription: Apply the What OIP Should Take from 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 OIP Should Take from the Semantic Web\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-from-semantic-web). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-from-semantic-web.\n- Read claims and relationships at /api/articles/oip-from-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 › OIP Lineages https://miscsubjects.com/a/oip-from-lineages › What OIP Should Take from the Semantic Web She\n\n## Representations\n\n- Human: /a/oip-from-semantic-web\n- JSON: /api/articles/oip-from-semantic-web\n- Relationships: /api/articles/oip-from-semantic-web/topology\n- History: /api/articles/oip-from-semantic-web/revisions\n"},"json":{"route":"/api/articles/oip-from-semantic-web","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-from-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: Cyrus 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: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.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/massoumicyrus/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: Cyrus 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: Cyrus 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/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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","lineages","oip-from-semantic-web","oip","from","semantic","web"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-from-semantic-web/invocations?status=success","failure_events":"/api/articles/oip-from-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":"oip-from-semantic-web","title":"What OIP Should Take from the Semantic Web","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [OIP Lineages](https://miscsubjects.com/a/oip-from-lineages) › **What OIP Should Take from the Semantic Web**\n>\n> **Shelf:** OIP Lineages · **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 OIP Should Take from the Semantic Web\n\n## §SELF — oip-from-semantic-web\n\n**What this page is:** A list of Semantic Web technologies and principles that OIP adopts, plus the parts OIP explicitly rejects.\n**What it explains:** How machine-readable web data standards apply to OIP objects and why OIP uses only a subset.\n**Why read it:** To understand why OIP objects are described the way they are — and why some Semantic Web technologies are left out.\n\n### What the Semantic Web Is\n\nThe Semantic Web is Tim Berners-Lee's vision (articulated 2001–2010 and beyond) of a web where data is structured so machines can read and process it directly. Instead of HTML pages meant for human eyes, the Semantic Web publishes data in formats (RDF, JSON-LD) that software can parse, link, and reason over. The core idea: give every piece of data a persistent URI, describe it in a standard vocabulary, and link it to other data so machines can traverse the graph.\n\n### Why It Matters\n\nThe web succeeded for humans because pages link to each other. The Semantic Web attempted the same for machines. It partially succeeded: JSON-LD is widely used, schema.org markup is common, and Linked Data principles power knowledge graphs at major organizations. It partially failed: the full stack (OWL reasoning, RDF/XML, SPARQL endpoints at scale) proved too complex and slow for general use. OIP takes the parts that worked and discards the parts that did not.\n\n### The Key Idea\n\nOIP objects should be describable in standard, machine-readable formats so any tool — not just OIP-native models — can discover what an object does, what parameters it accepts, and how to invoke it. The description format should be parseable by existing Linked Data tools. The description should not require a heavy reasoning engine or a complex ontology stack to interpret.\n\n### What OIP Takes from the Semantic Web\n\n**JSON-LD for object descriptions.** JSON-LD (JavaScript Object Notation for Linked Data) is a JSON format that embeds semantic context. An OIP object contract written in JSON-LD is parseable as ordinary JSON by simple tools and as Linked Data by Semantic Web tools. This gives interoperability for free: a model can read it as JSON; a knowledge graph can ingest it as RDF. No format conversion needed.\n\n**URI as identity.** In the Semantic Web, a URI (Uniform Resource Identifier) is not just an address you look up. It is the permanent identifier of the thing itself. OIP applies this: every object, every receipt, every capability has a URI. The URI is the name of the entity. If you have the URI, you can refer to the entity unambiguously forever.\n\n**Graph traversal.** The Semantic Web organizes data as a graph of triples — subject, predicate, object. OIP's voxel graph (the structure of objects, receipts, and their relationships) should be exportable as RDF triples. An external tool should be able to query the graph with SPARQL-like queries: find all receipts for this object, find all objects created by this model, find all capabilities derived from this parent token. The graph is queryable.\n\n**Linked Data principles.** Tim Berners-Lee defined four Linked Data principles: (1) use HTTP URIs as identifiers; (2) return useful information when those URIs are looked up; (3) include links to other URIs; (4) use standard formats (RDF, JSON-LD). OIP follows all four. An OIP object URI returns the object's contract and current state when dereferenced. The contract includes URIs linking to related objects, receipts, and capabilities.\n\n**Hydra vocabulary.** Hydra is a lightweight vocabulary for describing web APIs in RDF. OIP uses Hydra's `Operation`, `supportedProperty`, and `statusCodes` to describe object contracts. `Operation` declares what actions an object supports. `supportedProperty` declares what parameters each action requires. `statusCodes` declares what responses the object can return. A model reading the contract knows, without trial and error, how to interact with the object.\n\n### What OIP Does Not Take from the Semantic Web\n\n**OWL reasoning.** OWL (Web Ontology Language) is a formal language for defining complex ontologies and performing logical inference. It is powerful but slow. OWL reasoning engines can take seconds or minutes to classify a moderately complex ontology. This is acceptable for offline knowledge-base construction. It is unacceptable for runtime model interaction. OIP does not use OWL reasoning.\n\n**RDF/XML.** RDF/XML is the original W3C standard format for RDF data. It is verbose, difficult to read, and unpopular. JSON-LD supersedes it for all practical purposes. OIP uses JSON-LD exclusively. No RDF/XML.\n\n**The full Semantic Web stack.** The complete Semantic Web vision includes multiple layers: URIs, Unicode, XML, RDF, RDF Schema, OWL, rules, proof, trust. Each layer adds complexity. OIP takes the bottom layers (URIs, JSON-LD/RDF, basic vocabularies) and stops. It does not implement the upper layers because they add machinery without adding value for model-to-model interaction.\n\n### The Boundary\n\nOIP takes the parts of the Semantic Web that make objects discoverable and interoperable. OIP leaves the parts that add complexity without practical value for runtime execution. The test is simple: if a technology helps a model find an object, understand its contract, and invoke it — OIP uses it. If the technology is designed for offline reasoning, ontology engineering, or philosophical completeness — OIP does not.\n\n### Sources\n\n- Berners-Lee, Tim, James Hendler, and Ora Lassila. \"The Semantic Web.\" *Scientific American,* 2001. (Original vision statement.)\n- Berners-Lee, Tim. \"Linked Data — Design Issues.\" W3C, 2006. (The four Linked Data principles.)\n- Lanthaler, Markus, and Christian Gütl. \"On Using JSON-LD to Create Evolvable RESTful Services.\" *WWW Companion,* 2012. (JSON-LD for API descriptions.)\n- Lanthaler, Markus. \"Creating 3rd Generation Web APIs with Hydra.\" *WWW Companion,* 2013. (Hydra vocabulary.)\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- [OIP Lineages shelf](https://miscsubjects.com/a/oip-from-lineages) — 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 OIP Should Take from Capability Security](https://miscsubjects.com/a/oip-from-capability-security)\n- [What OIP Should Take from REST](https://miscsubjects.com/a/oip-from-rest)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/oip-from-semantic-web`\n- JSON article: `https://miscsubjects.com/api/articles/oip-from-semantic-web`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20OIP%20Should%20Take%20from%20the%20Semantic%20Web`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","lineages","oip-from-semantic-web"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/oip-from-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: OIP Lineages (oip-from-lineages). 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":3,"label":"OIP Lineages on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:24.973Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"904cd9b942aaf87dd83dbf29434060a0f5b8ef4ec6158acd0c58f230c39af675"},{"ts":"2026-07-17T02:36:13.081Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-from-semantic-web","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"904cd9b942aaf87dd83dbf29434060a0f5b8ef4ec6158acd0c58f230c39af675","hash":"9a91e28e0a58159066a9650f1f1b9a22f0c6cf75d98c72de141d43f01ec3bacd"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"9a91e28e0a58159066a9650f1f1b9a22f0c6cf75d98c72de141d43f01ec3bacd"},"posted_at":"2026-07-15T04:20:24.973Z","created_at":"2026-07-15T04:20:24.973Z","updated_at":"2026-07-17T02:36:13.081Z","machine":{"shape":"article.machine/v1","slug":"oip-from-semantic-web","kind":"article","read":{"human":"https://miscsubjects.com/a/oip-from-semantic-web","json":"https://miscsubjects.com/api/articles/oip-from-semantic-web","bundle":"https://miscsubjects.com/api/articles/oip-from-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":0,"objections_url":"https://miscsubjects.com/api/articles/oip-from-semantic-web/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-from-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\":\"oip-from-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\":\"oip-from-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/oip-from-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\":\"oip-from-semantic-web\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-from-semantic-web | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-from-semantic-web","json":"/api/articles/oip-from-semantic-web","markdown":"/api/articles/oip-from-semantic-web/bundle?format=markdown","skill":"/api/articles/oip-from-semantic-web/skill","topology":"/api/articles/oip-from-semantic-web/topology","versions":"/api/articles/oip-from-semantic-web/revisions","invocations":"/api/articles/oip-from-semantic-web/invocations"}}}}