influences.sgit.ai / register / Tim Berners-Lee & the Semantic Web / trace

Tim Berners-Lee & the Semantic Web — the trace table

The falsifiable part of the entry, on its own and with its sources attached. Each row is a claim that a pattern from the anchor work appears at a named place in the estate — checkable against the repositories, which is the only thing that separates this from a reading list.

Pattern from the anchorWhere the estate implements itVersionStatusSource of the row
Machine-readable meaning as the target — a graph a machine can act on rather than a document it can only parseThe estate's graph substrate and the concept document that sets out its thinkingv0.4.0implementedv0_4_0__thinking-in-graphs.md, cited in 02__ §T3
Meaning attached to nodes (RDF's typed-resource model)Deliberately inverted. The estate derives meaning from edges instead, and the concept document states the inversion as a correction rather than a variationv0.4.0absentv0_4_0__thinking-in-graphs.md, the Insight (and Mistake) section
Meaning derived from connection between thingsThe edge-first graph model the estate's ontology work is built onv0.4.0implementedv0_4_0__thinking-in-graphs.md
Personal data under the person's own control (Solid pods)Encrypted vaults, keyed by their holder — compared to pods explicitly, as complementary architectures with different threat modelsv0.6.17partialv0.6.17__architecture__solid-protocol-integration-complementary-architectures.md
Interoperation with Solid itself — a vault that can read or write a podNowhere. The brief is an architectural comparison, not an integrationv0.6.17absentthe same brief, which scopes itself as a comparison

Every row names where it came from. A trace row is only worth having if you can find out how it was arrived at, so the last column carries the document in the commissioning pack that supports it. No row on this site was written from memory or inference — where the evidence runs out, the row is marked absent or the table says so.

The same rows, as data

The influence map is computed from these files rather than drawn, so the graph cannot disagree with the tables it is made of.