Conformance
Conformant is a digest
you can check.
Every document is validated against the official GS1 EPCIS 2.0.1 JSON schema, pinned by sha256, so “conformant” is a digest you can recompute rather than a word we chose. The pins are published below; the validator answers here with no key.
curl -sS https://epcis.dev/validate \
-H 'content-type: application/json' \
--data-binary @receiving-2.0.json
200 application/json
{
"type": "OK",
"valid": true,
"schema": {
"artefact": "epcis-json-schema.json",
"version": "2.0.1",
"sha256": "0f46ff694efffd8d8…0ae210af"
},
"errors": []
}
The pins.
GS1's normative artifacts, vendored and pinned by digest. Retrieve the same artifacts from ref.gs1.org and hash them yourself.
| artifact | role | sha256 | retrieved |
|---|---|---|---|
| openapi.json | REST binding shapes (Capture + Query interfaces) | 3d33792c520d7a7a1d080382d956730bb07021c7dd1cc17229fce27b784d66fc | 2026-07-19 |
| epcis-json-schema.json | document/event validation — the projection-invariant schema | 0f46ff694efffd8d8ce840a33dfde84228add11b516b8b258f3200740ae210af | 2026-07-19 |
| epcis-context.jsonld | JSON-LD expansion checks | 5056c65f991425b1d3a35e35edf4f7d0c7ff56cf688c2912b930f93494713737 | 2026-07-19 |
| query-schema.json | SimpleEventQuery validation | 4b5583c9a0a715324594617f3cf6744f4f930568484f7df8fb7aa81819355341 | 2026-07-19 |
| epcis-shacl.ttl | semantic-graph validation (secondary) | 7db2547a7a55e7d6e6f19c0ad472d1f0987ef19f3d04a43b195bca55c0cc7f42 | 2026-07-19 |
The suite.
The automated suite runs the GS1 test-case requirements against an EPCIS implementation and produces a run record with a rejudgeable evidence bundle, so an auditor can re-run the judgment. Runs are advisory.
- suite0.4.0verdict logic 0.3.2
- checks18over the published GS1 test-case requirements
- pinned to2b888befbc07the GS1 EPCIS repository, by commit
Get a capture key.
Translate, validate and hash run here with no key. Capture, query and MCP open with a capture key.