Each entry is a conformance result: the signed record of one run of a WAI conformance
corpus against an implementation (conform-result/1).
An entry is listed when wai verify --conformant, built from the commit below,
admits its record against that commit's corpus: the record is the one that was signed, its
run passed every required case of its suite, and the corpus it names is that suite's at the
commit. Every record is served at its entry, so anyone can check it again.
A record states what one run observed: the implementation as the run's command named it,
the corpus and each case's answer. It is not a certificate. A record signed with a key made
for its run shows it is the record that run wrote; one signed with a key the runner holds
also says who ran it (conformance-results §6).
The suites wai conform runs at the commit, by area, each with its corpus
under wai/ and the records listed for it. wai conform --list
prints them from a checkout.
trust
verifierclaimclaim-conformance/
typed claim receipts (jwp-receipts §3.1): accept with the link hash, or reject at a step with a reason
objects, head proofs, ranges and headers as an origin serves them (http-delivery §5.3, §6.2)
No record listed.
cachecachecache-conformance/
an HTTP cache in front of the reference origin, started by the command ({port}, {origin}), held to http-delivery §9; informative tests report what it stored
a browser sink's answer to each call of the corpus, byte for byte: routes, choices, constraints, bindings, frame tiers and states, side tables (browser-sink §12)
a MOQT relay at a moqt:// or https:// URL, held to the interop cases by the interop client at one draft: setup, namespaces, subscriptions, errors and a WAI track carried with its receipts
In a checkout of open-standards at the commit, wai verify --conformant --root wai <record>
gives the admission this list uses, and wai conform makes a record of your
own run: Conformance runs.