Markdown Document

A Markdown Document is a file-kind type assigned to plain Markdown (.md) files that are registered in a local corpus via the Sparqdown local server. Unlike a Sparqdown Document, the content of a Markdown Document is not parsed as Sparqdown — the registry records only its metadata (source address, filename, label) and does not build a semantic model from the body.

Why a distinct file-kind

The local server config maps file extensions to document types. Assigning .md files their own type (sdg:MarkdownDocument) allows:

  • Renderer dispatch — the viewer can present a Markdown Document with a Markdown renderer rather than the Sparqdown body renderer.
  • SHACL shape — future phases can attach a dedicated shape to sdg:MarkdownDocument that validates or enriches Markdown-specific metadata.
  • Search and filtering — authors can filter the corpus by file kind, separating Markdown notes from Sparqdown documents and binary files.

What the registry stores

For a Markdown Document the Version graph carries the standard document metadata — title (derived from filename), type assertion (sdg:MarkdownDocument), label, and source address. Content is not retained in the graph; it lives at the path recorded via sdg:sourceAddress.

Relationship to other types

  • A Markdown Document is a sd:Document and by configuration also a sdg:SparqdownDocument at the type-declaration level, but it is not authored in Sparqdown — the type assertion is metadata, not a parse claim.
  • Compare Pure File — the generic binary file-kind — and File — the default fallback file-kind for unrecognised extensions.