Optional Extensions

An optional extension is an addition that sits beside the Standard without changing it. This page lists the extensions published so far.

An extension is not part of the Standard. Its requirements bind only an implementation that says it uses that extension, at that version. It does not change what a core field means or when one is required, and where an extension and the Standard's text disagree, the text governs. Extensions are not part of the Standard's releases: they are not in its downloads, bundles or checksum lists. Using one makes no one certified, compliant or approved.

Portable verification 0.1.0

How to export sealed decision records so that someone else can check them, and how that check reports what it found. It adds two objects beside the records, an export and a verification report, and adds no field to a decision record.

• Status: Proposal. It may still change before it gets its own tag.
• Written against: version 1.2 of the text (reading edition rev. 10, tag v1.2-rev10) with reference files 5.1.2 (tag ref-5.1.2).
• Where it is: extensions/portable-verification/ in the standard repository, as it stood at tag v1.3-rev11: its text, its two JSON schemas and its test cases.
• Proposed by: Laurent Lemonnier, iSoluce.

The rules every extension follows

The standard repository sets these rules for every extension: it is optional, it sits beside the Standard, it has its own version number, it names the release it was written against, and it says nothing about what any law requires. The records remain input, not evidence.

← Back to the Decision Provenance Standard