SSTorytime vs vault-ld
Mark Burgess's Semantic Spacetime knowledge graph on Postgres: write notes in the N4L language, compile them into a story graph, then search, browse and path-solve it via Go API or web UI. — versus — An open spec for Markdown vaults as linked data: YAML-LD frontmatter plus a shared @context makes notes an RDF graph, with reference scripts that round-trip vault to Turtle and back.
Both turn hand-written notes into a knowledge graph: vault-ld keeps Markdown and adds YAML-LD so notes become RDF; SSTorytime uses its own N4L note syntax and a non-RDF spacetime model on Postgres.
| SSTorytime | vault-ld | |
|---|---|---|
| Stars | 259 | 235 |
| Forks | 41 | 23 |
| Language | Go | Python |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | 2 months ago |
| Topics | knowledge-graphs | knowledge-graphs |
| Curated connections | 2 | 7 |
SSTorytime — the curator's take
For people who want to think with a knowledge graph, not just store one: you write semi-formal notes in N4L, the compiler loads them into a Semantic Spacetime graph on plain Postgres, and tools search it, solve paths and surface storylines. It deliberately rejects RDF and topic maps for four relation types — near, leads-to, contains, expresses — from the CFEngine/Promise Theory author: opinionated theory, carefully built, with a no-unvalidated-AI-code policy. It is alpha and learning-oriented: several CLI tools are labelled preliminary, and LLM access lives in a separate MCP-SST connector. Skip it for automatic LLM extraction from documents or standards-bound enterprise KGs — an RDF/OWL stack or an extraction pipeline fits there.
vault-ld — the curator's take
Read it if you keep an Obsidian-style vault and also own RDF ontologies: it makes a note and an OWL class the same kind of object, so business semantics land inside the wiki your team already edits while the ontology gains a human-readable surface. The roundtrip is the real claim — Turtle in, Markdown editing, Turtle out, with anything unmappable flagged rather than silently dropped. Set expectations: this is a specification plus two reference Python scripts (`vault_to_rdf.py`, `rdf_to_vault.py`) and an example vault — no UI, no server, no query engine — and blank nodes and language tags sit outside what the format can express.