Overview
Digital knowledge work increasingly demands documents that are simultaneously multilingual, multi‑audience, and multi‑channel. Traditional single‑file Markdown struggles when the same canonical content must coexist with translations, commentary, references, code exemplars, and revision notes – each with distinct lifecycles and audiences. This paper introduces MDKV, a simple but rigorous multitrack Markdown container that packages a document’s canonical content and auxiliary tracks into a single, portable `.mdkv` file. An `.mdkv` is a ZIP archive with a YAML `manifest.yaml` and a `tracks/` directory of UTF‑8 Markdown files. MDKV provides a principled data model, validation, search, and export services, a CLI, and a small GUI for selective preview and live editing. We formalize the MDKV model, present its software architecture, explain round‑trip export semantics, and evaluate design trade‑offs against adjacent technologies. The MDKV initial specification is open source under the Apache‑2.0 license and maintained at the project repository https://github.com/docxology/mdkv . We also situate MDKV with respect to Matroska (MKV) as background on containerization: although the two are orthogonal in domain (text vs. multimedia), they share conceptual lineage in extensible container design. We conclude with use cases, implications for governance and reproducibility, and future work such as richer validation rules and alternative exporters. This paper is itself a Markdown file that renders into a valid MDKV. The built artifact is available at paper/paper.mdkv ; combined exports are under paper/_bundle .
Overview source: Curated paper metadata.
Methods and contributions
Read the source for the full argument, qualifications, and evidence.
Findings and contributions
- The paper lists four contributions: a precise model and container format, a modular architecture exposed via CLI and GUI, detailed use cases, and guidance on cryptographic provenance and conformance.
- Export is designed to be deterministic: order follows the manifest, and identical inputs produce identical outputs.
- The author lists format limitations, including no built-in encryption or signing and code tracks that are listings rather than runnable notebooks.
- The paper notes that the reference validator currently checks for a track with id 'primary' rather than the type-level requirement.
- The paper is itself authored as a Markdown file that renders into a valid MDKV.
Methods
- ZIP container with YAML manifest and tracks/ directory of Markdown files — MDKV defines an .mdkv file as a ZIP archive holding a manifest.yaml index plus one UTF-8 Markdown file per track.
- Seven-type track taxonomy (primary, translation, commentary, code, etc.) — Document layers are separated into typed tracks that are composed into views only at export time.
- Python reference implementation split into core, storage, services, and CLI — The software follows a thin-orchestrator design with separate modules for data model and validation, persistence, search/export, and command-line entry points.
- Round-trip export via HTML-comment track headers — Combined Markdown exports prefix each track with a comment encoding its id, type, and language so attribution can be reconstructed.
- Normative MUST/SHOULD conformance requirements and minimal validator — The paper specifies conformance rules and a base validator checking title, authors, a primary track, track paths, types, and unique ids.
Summary sources: Paper metadata and evidence · Extracted source text.
Document downloads
PDFs are hosted here; supporting sources may use pinned archives.
- 2025_MDKV.pdf PDF · 0.14 MiB · extracted-text source
Citation
Citation metadata follows the unified bibliography.
Catalog details and resources
Related works
Ranked by recorded methods, topics, contributors and associated software, with contributor roles and domain-only matches labelled. Metadata overlap is not a citation or a scientific equivalence.