Expand description
Text-driven SHACL validation — the entry point the docs playground / any “paste shapes + data, get a report” caller uses.
- Data is N3/N-Triples text (parsed by the engine’s own
N3Parser). Numeric object literals are inline-encoded (so range constraints work); IRIs/strings areq_hashed and retained in a resolver (so string constraints — pattern/length/language — work). - Shapes are a compact JSON list (
ShapeSpec) mapping 1:1 onto theShaclConstraintvocabulary.
validate_json runs the comprehensive ShaclEngine and returns the
ValidationReport as JSON.
Structs§
- Constraint
Spec - One constraint in a
ShapeSpec. Exactly the field for thekindis read. - Shape
Spec - One shape in the playground/JSON input.
Functions§
- build_
graph - Parse N3/N-Triples text into a quin graph plus a hash→lexical resolver.
- shape_
from_ spec - Build a
CompiledShapefrom aShapeSpec. - validate_
json - JSON-in / JSON-out convenience for the playground & WASM boundary.
- validate_
text - Validate N3/N-Triples
dataagainstspecsand return the report.