Distribution¶

The conformance suite is published as a versioned, downloadable artifact so a porter can pin their runner to a specific suite version instead of tracking the repository directly.

Latest release¶

kpointer-conformance-0.2.0.zip (sha256)

This link is updated by hand each time the suite version changes; see Release process notes for the checklist that keeps it current.

All versions¶

Every released version's ZIP and sidecar stay published — none are pruned from the site as new versions ship.

What's in the ZIP¶

Each archive is self-contained: it bundles the fixtures, their JSON Schemas, manifest.json, and conformance/README.md, all at the same relative paths they occupy in the repository's conformance/ directory. A runner that validates against the ZIP's own bundled schemas works fully offline.

Schema URLs: online is latest, the ZIP is pinned¶

Every schema declares a canonical $id under https://kpointer.commonsware.com/conformance/, e.g.:

"$id": "https://kpointer.commonsware.com/conformance/syntax/parsing.schema.json"

Those URLs — and the same-path fixture JSON alongside them — always resolve to the current suite version on the site. There is no per-version schema URL scheme (no /conformance/0.1.0/...). If you need a specific version pinned in place, use that version's ZIP: its bundled schemas and fixtures never change underneath you.

Browsing fixtures online¶

The fixtures themselves are also served at their on-disk paths, e.g. conformance/syntax/parsing.json and conformance/manifest.json.

Changelog¶

See the Conformance Suite Changelog for what changed in each suite version.

Consuming this in your runner¶

See Writing a Workalike and the porting guide overview for how to build a runner against the fixtures, and Capabilities / Error Codes for the optional-feature and error-taxonomy details referenced above.