Try the test viewer.
schemas.shex), ShExJ (.json) and sometimes SHACL (.shacl).The ShExC and ShExJ files with the same stem name are equivalent. A ShExC syntax test consists of these steps:
start, inclusion, predicate, and datatype properties.shapes object).values properties.ValueAnd or ValueOr expression contains ValueAnd or ValueOr expressions in the list of valueExprs.negativeSyntaxThese tests violate the ShEx2 grammar.
negativeStrucutreThese tests should raise errors when parsed, noting the rule about nested ValueAnd and ValueOr expressions.
validationmanifest.ttl, ShExJ (obselete primer) - manifest.json)..ttl).ValidationTest or ValidationFailure.A ShEx validator is logic-conformant when it returns success for the tests of type ValidationTest and failure for the tests of type ValidationFailure.
A ShEx validator is result-conformant (experimental) when it executes as ValidationTest and produces the same result structure as produced by this procedure:
node, shape, subject, predicate, and object properties.error-conformant (even more experimental) when it executes a ValidationFailure and produces the same result structure as produced by the procedure above.coverageOne frequently wants to ask “does the test suite include X”.
One way to test that is to guess by the relatively formulaic filenames and test names in validation/manifest.
Another is to “grep” through the JSON representations of the queries for something with the appropriate structure, e.g. using jq to EachOfs that include a pattern with a min cardinality of 0:
(for f in schemas/*.json; do
jq -e '.[]|..|objects|select(.type=="EachOf").expressions[]|select(.min==0)' $f > /dev/null &&
echo $f;
done
)
which yields the files which include this pattern:
schemas/1val1IRIREFExtra1Or.json
schemas/3circularRef1.json
schemas/kitchenSink.json
validation-contrib and schemas-contribsht:Repair) and feasibility localization / structured error reporting (sht:Feasibility).validation (manifest.ttl, manifest.jsonld) and the same .ttl data convention; the schemas live in schemas-contrib/ as ShExC only (no ShExJ/ShExR trio, no representation tests).ValidationTest/ValidationFailure plus traits. There are no reference results, so a validator can be checked for logic-conformance here but not result-conformance, and a conformant implementation is not required to run them at all.docGrammars for the three renderings of a ShEx schema, and the pieces that relate them:
ShExJ.jsg — ShExJ, as a JSON Schema Grammar.ShExR.shex — ShExR: the ShEx schema that RDF renderings of
ShEx schemas are validated against. Hand-maintained, and the source for
ShExR.ttl and ShExR.ntriples, which bin/mkShExR.js
derives and npm test keeps in sync.ShExJ-context.jsonld — the JSON-LD context that
turns ShExJ into ShExR. Generated from vocab/vocab.csv, which is
also the source of https://www.w3.org/ns/shex.syntax-deltas.html — where ShExC, ShExJ and ShExR
disagree about what a schema may say, with the evidence for each. Notably,
ShExR admits a ShapeDecl as start where neither of the others can express
one.