Docs

Implementation registry

Evidence of implementation, not permission to implement.

This registry lists deployments for which ESFI can verify generated MPF output. It is deliberately narrower than a list of projects that may intend to support the format. MPF is an open format: anyone can publish and read it without being listed here.

All emitters listed below declare Machine Page Format (MPF) 0.7 and publish inspectable discovery output. Each entry says how to check it yourself.

ESFI website

Emitter: esfi.eu Format: Machine Page Format (MPF) Declared version: 0.7 Reference implementation: mpf-build — git.esfi.eu/esfi/mpf

The ESFI website generates MPF companions for its published HTML pages and a site-level MPF index. The current generated index includes pages in English, French, Dutch and German.

Verify it

  1. Fetch https://esfi.eu/index.mpf. Confirm that the frontmatter declares mpf: '0.7', domain: esfi.eu, an mpf-url, a source-hash, a content-id and an mpf-id. Specification 0.7
  2. Fetch https://esfi.eu/llms.mpf and inspect the generated site index. Specification 0.7
  3. Fetch https://esfi.eu/llms.txt and confirm that it advertises MPF: 0.7 and MPF-index: /llms.mpf; when MPF-spec is present, it must identify the canonical 0.7 specification. Specification 0.7
  4. Compute the SHA-256 of the served https://esfi.eu/ HTML and compare it with source-hash in index.mpf. A match shows that the pair is in step.
  5. For a translated page, fetch the corresponding /fr/, /nl/ or /de/ MPF path and compare its content-id and language-variants with the default-language page. Specification 0.7
  6. Fetch https://esfi.eu/.well-known/mpf and query _mpf.esfi.eu as a DNS TXT record, where published. Confirm that the scope they declare matches companion-scope in the page files. ESFI practice

ESFI documentation

Emitter: docs.esfi.eu Format: Machine Page Format (MPF) Declared version: 0.7 Reference implementation: mpf-build — git.esfi.eu/esfi/mpf

This site generates MPF companions for its pages and a site-level MPF index. Position pages and standards pages declare different processing scope; each page’s frontmatter states its own.

Verify it

  1. Fetch https://docs.esfi.eu/llms.txt. Confirm that it advertises MPF: 0.7, an MPF-index path and an MPF-spec pointing to the canonical 0.7 specification. Specification 0.7
  2. Follow the advertised index and inspect an indexed MPF document; its frontmatter must declare mpf: '0.7'. Specification 0.7
  3. Compare the source-hash of any page companion with the SHA-256 of its served HTML.
  4. Open the MPF file of a topic page and of a standards page, and compare their companion-scope. The difference is deliberate and declared.
  5. Fetch https://docs.esfi.eu/.well-known/mpf and query _mpf.docs.esfi.eu as a DNS TXT record, where published. ESFI practice

Registry rule

An implementation belongs here only when generated output can be inspected and matched to a published ESFI format version. Planned support, an unused library, or a configuration that has not produced inspectable output is not sufficient.

A listing records that output was verified against a published version. It does not certify the accuracy of the content, the truth of the publisher’s declarations, or the quality of the site.

To propose an implementation for the registry, publish inspectable output first. The steps above are the same ones ESFI uses to verify an entry.

The current format contract is documented in the Specification 0.7. The previous Specification 0.6 remains available for historical documents. Version lifecycle rules are documented in Versioning.