Formats and roadmap
Which formats probat checks first, and which follow once the XPath 2.0, XSD and container engines exist.
The order follows the engines. Formats whose engines already exist as Rust crates come first; each new engine then unlocks several formats at once.
First
| Format | Checks |
|---|---|
| Any text file | Encoding, byte order mark, line endings, control, invisible and bidi characters |
| HTML | Conformance comparable to the W3C Nu Html Checker, including ARIA, SVG and MathML |
| XML | Well-formedness, RELAX NG, your own Schematron rules (XPath 1.0) |
| SVG, Atom | Against their schemas |
| robots.txt, Content Security Policy | Syntax and rules |
Next
| Format | Needs |
|---|---|
| E-invoices in UBL and CII: XRechnung, EN 16931, Peppol BIS Billing | XPath 2.0, XSD |
| ZUGFeRD / Factur-X | The invoice XML embedded in the PDF and its metadata |
| JSON, YAML, TOML, CSV, Markdown | Parsers, JSON Schema |
| CSS | Property and value grammar |
| EPUB, SEPA / ISO 20022, sitemaps | ZIP container, XSD |
| Corrupt or truncated files (PNG, JPEG, ZIP, PDF) | Structure and checksum checks |
Later
- Many more e-invoice formats and versions, addressed by versioned rule-set IDs.
- Office documents (ODF, OOXML).
- PDF/A and PDF/UA.
Signature validation and XBRL are not planned.