Skip to content
One document, two readers The chevron-M mark above a Markdown panel and a JSON-LD panel meeting at a round-trip arrow, with a mif-validate conformance badge below. ONE DOCUMENT, TWO READERS human-readable # A decision, in prose Markdown · a person reads machine-parseable { "@type": "Decision", "entity": { … } } JSON-LD · a parser resolves mif-validate · lossless round-trip · L1→L3

Introduction

One document, read losslessly two ways — human Markdown, machine JSON-LD. No translation, no drift.

This site is the normative specification for MIF (Modeled Information Format). It defines the data model, the two on-disk formats, the type system, and the conformance rules, and it serves the canonical JSON Schemas.

Start with the Specification Overview, then work through the core model, the Markdown and JSON-LD formats, the data types, and the reference sections (conformance, conversion, security, appendices) from the sidebar.

The canonical JSON Schemas are served under /schema/:

  • https://mif-spec.dev/schema/mif.schema.json
  • https://mif-spec.dev/schema/citation.schema.json
  • https://mif-spec.dev/schema/ontology/ontology.schema.json
  • https://mif-spec.dev/schema/definitions/entity-reference.schema.json

$id values are stable and unversioned; immutable per-release mirrors are available at /schema/<version>/…. See the schema catalog and versioning notes.

Task-oriented guides, tutorials, API references, and the Architecture Decision Records live in the ecosystem documentation at modeled-information-format.github.io.