SHACL conformance

Shifty passes all 120 approved cases in the pinned W3C SHACL 1.0 Core/SPARQL suite. One proposed case also passes and is counted separately.

Recorded results

This report was produced on 2026-11-11 using 0.6.0-alpha.4 at commit aaaea85.

Suite section	Passed	Failed	Errors
SHACL Core (approved)	98	0	0
SHACL-SPARQL (approved)	22	0	0
SHACL-SPARQL (proposed)	1	0	0

Both the W3C reports and Shifty’s structured validation results passed. The CLI and Python file-input reports also matched across all 121 cases, including seven tests that expect a validation failure diagnostic.

• EARL implementation report

• Per-test results and run metadata (JSON)

• CLI/Python parity results (JSON)

• Report checksums

The CI run produced these files from a clean checkout. Earlier report snapshots are also retained.

What this checks

The runner uses W3C suite revision 40231dfb97c5b606d22ae733947c0d14b4f45c07. It loads each case’s declared shapes and data, disables inference, and treats unsupported features as errors. Actual and expected reports are compared using the suite’s report comparison rules; process-local blank-node labels are compared by graph isomorphism.

Passing covers the cases in this suite, rather than every possible use of SHACL. The suite does not test SHACL-AF, SHACL-JS, or SHACL 1.2. See Feature support for support and limitations beyond these tests. These are implementation results, not a W3C endorsement.

To reproduce the report, follow Run the W3C SHACL suite. The conformance workflow runs on changes to main and on pull requests.