Skip to main content

​
At a glance

​
The convergence of Linked Markdown and Vault-LD

Both Linked Markdown (by Wazoo) and Vault-LD (by The Knowledge Graph Guys) arrived at the same realization: standard CommonMark files with valid W3C JSON-LD / YAML-LD frontmatter are the open primitive for semantic Markdown and agent knowledge graphs. Because both specifications converged on zero nonstandard syntax and native JSON-LD semantics, an LMD document and a Vault-LD document accept the exact same document structure. A single .md file functions simultaneously as human-readable prose and a valid RDF graph node in both ecosystems.
The distinction is toolchain maturity and real-world deployment, not document format:
  • Linked Markdown (LMD) is backed by production-grade tooling: official multi-language Extract APIs (linked-markdown-py on PyPI, @wazoo/linked-markdown on JSR), a formal W3C Community Group Editor’s Draft, a published research paper (Zenodo DOI: 10.5281/zenodo.21216085), and a complete CLI toolchain (wiki, Wazoopedia, memsdk, and Wazoo Worlds).
  • Vault-LD is an open specification (SPEC.md) for lossless round-trip parsing in personal knowledge bases.

​
Why choose Linked Markdown

  • Ready-to-install packages for Python (pip install linked-markdown) and TypeScript (jsr:@wazoo/linked-markdown) with deterministic extract() APIs that convert markdown directly to RDF quads and JSON-LD nodes.
  • A formal W3C JSON-LD Community Group specification and a published DOI paper on semantic Markdown infrastructure.
  • Native integration with the wiki CLI (linting, SHACL shape validation, SPARQL querying, and static site rendering) and Wazoo Worlds context engines.

​
Interoperability

Because Linked Markdown and Vault-LD converged on the exact same underlying RDF 1.1 data model and JSON-LD semantics, they are 100% interoperable. Any Vault-LD document can be extracted, validated, and queried with linked-markdown SDKs or the wiki CLI toolchain.