structcorpus

Public, reproducible test material for structured-document readers and their language bindings. YAML comes first; JSON and XML namespaces are reserved until a consumer needs them.

structcorpus holds the inputs, the expected properties, the provenance records, and the generators. It does not contain a parser. Each consumer writes a small driver that runs its own API against a pinned corpus release.

Principles

• Public only. Every case is synthetic, or comes from a public source with documented redistribution rights. Nothing is derived from private data, and redacted or blinded material is never admitted. See SecDR-0001 and docs/admission.md.
• Format truth is kept apart from adapter policy. Format-level event streams can be checked against any engine. Value trees, budgets, and resource accounting appear only under a named, versioned profile. See DDR-0002.
• Byte-exact fixtures. Git never rewrites line endings under fixtures/ or expected/. See DDR-0001.
• Nothing to install beyond python3. The tools use only the Python 3.9+ standard library; there is no package manager and no virtual environment. See ADR-0002.
• Bounded execution. Hostile cases run only under enforced limits. See SecDR-0002.

Usage

python3 tools/corpus.py validate          # repository, metadata, and case rules
python3 tools/corpus.py hydrate --tier conformance --output /tmp/structcorpus-out
python3 tools/corpus.py verify --root /tmp/structcorpus-out
python3 tools/corpus.py canon FILE.json   # canonical (JCS) form of a metadata file
python3 tools/corpus.py list --tier stress --show-budgets   # what each tier contains

Maintainers run make check for everything non-mutating: formatting, lint, JSON Schema validation, tests, and a double hydration. Format, lint, and schema checks use goneat (PDR-0002). Consumers need only python3.

Before pushing, maintainers run make prepush. It adds a containment self-test that needs a container runtime (docs/running.md).

Large tables are generated, not committed: each recipe under recipes/ pins its generator, parameters, case count, and a digest of the exact output (DDR-0004). Hydration writes only to a new directory outside the checkout.

Cases live in manifests/cases.jsonl and reference inputs under fixtures/yaml/. Profiles are in manifests/profiles/ and span conventions in manifests/span-conventions/; the record formats are defined in DDR-0003 and schemas/.

list will arrive with the recipe ladders. See PDR-0001 for the release stages.

Status

Pre-release foundation. No cases have shipped yet. Decision records are Proposed. Coverage is tracked in docs/coverage.md.

Consuming

Pin a commit or release, together with its content hashes and the profile revision. Never track main.

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option. Material imported from public upstreams keeps its own license and notices, recorded per case.