RDF/XML serialization is deferred.
{
"@context": {
"schema": "https://schema.org/",
"wiki": "https://wazootech.github.io/wiki/",
"foaf": "http://xmlns.com/foaf/0.1/",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"xsd": "http://www.w3.org/2001/XMLSchema#",
"owl": "http://www.w3.org/2002/07/owl#",
"dc": "http://purl.org/dc/elements/1.1/",
"dcterms": "http://purl.org/dc/terms/",
"sh": "http://www.w3.org/ns/shacl#",
"wazoo": "https://schema.wazoo.dev/"
},
"@id": "wiki:SHACL",
"@type": "schema:TechArticle",
"schema:articleBody": "# SHACL\n\nThe **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.\n\nIn this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.\n\n## Defining custom SHACL shapes (validation)\n\nSHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:\n\n```yaml\nwiki:\n input:\n - wiki\n - shapes\n```\n\nMarkdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).\n\nThe validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference=\"rdfs\"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.\n\nTo constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):\n\n```yaml\n---\ntype: sh:NodeShape\nrdfs:label: Project Shape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:string\n sh:message: Project must have exactly one name string.\n - sh:path: schema:startDate\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:date\n sh:message: Project must have a startDate in YYYY-MM-DD format.\n---\n```\n\nWhen you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.\n\n### Lists and property paths\n\nA YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:status\n sh:in:\n - schema:ActiveActionStatus\n - schema:CompletedActionStatus\n - sh:path: [schema:author, schema:name]\n sh:minCount: 1\n - sh:path:\n sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]\n sh:minCount: 1\n---\n```\n\nHere the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.\n\n### Shape page checks\n\n`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:\n\n- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.\n- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).\n- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.\n- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).\n\nWhile any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.\n\nSeparately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.\n\nShapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.\n\n### JSON Schema (optional)\n\nOn the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nwazoo:jsonSchema: schemas/project.json\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n---\n```\n\n`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.\n\nSee [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.\n\nPure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.\n\n## Related\n\n- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation\n- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)\n- [Style Guide](Style_Guide.md) — shape authoring and filenames\n- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`\n- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout\n\n## References\n\n- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)",
"schema:dateCreated": {
"@type": "xsd:dateTime",
"@value": "2026-10-31T23:19:03Z"
},
"schema:dateModified": {
"@type": "xsd:dateTime",
"@value": "2026-10-31T23:19:03Z"
},
"schema:description": "Shapes Constraint Language for validating RDF graphs.",
"schema:headline": "SHACL"
}
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:SHACL a schema:TechArticle;
schema:description "Shapes Constraint Language for validating RDF graphs.";
schema:articleBody "# SHACL\n\nThe **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.\n\nIn this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.\n\n## Defining custom SHACL shapes (validation)\n\nSHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:\n\n```yaml\nwiki:\n input:\n - wiki\n - shapes\n```\n\nMarkdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).\n\nThe validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference=\"rdfs\"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.\n\nTo constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):\n\n```yaml\n---\ntype: sh:NodeShape\nrdfs:label: Project Shape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:string\n sh:message: Project must have exactly one name string.\n - sh:path: schema:startDate\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:date\n sh:message: Project must have a startDate in YYYY-MM-DD format.\n---\n```\n\nWhen you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.\n\n### Lists and property paths\n\nA YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:status\n sh:in:\n - schema:ActiveActionStatus\n - schema:CompletedActionStatus\n - sh:path: [schema:author, schema:name]\n sh:minCount: 1\n - sh:path:\n sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]\n sh:minCount: 1\n---\n```\n\nHere the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.\n\n### Shape page checks\n\n`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:\n\n- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.\n- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).\n- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.\n- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).\n\nWhile any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.\n\nSeparately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.\n\nShapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.\n\n### JSON Schema (optional)\n\nOn the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nwazoo:jsonSchema: schemas/project.json\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n---\n```\n\n`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.\n\nSee [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.\n\nPure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.\n\n## Related\n\n- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation\n- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)\n- [Style Guide](Style_Guide.md) — shape authoring and filenames\n- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`\n- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout\n\n## References\n\n- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)";
schema:headline "SHACL";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:SHACL a schema:TechArticle;
schema:description "Shapes Constraint Language for validating RDF graphs.";
schema:articleBody "# SHACL\n\nThe **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.\n\nIn this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.\n\n## Defining custom SHACL shapes (validation)\n\nSHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:\n\n```yaml\nwiki:\n input:\n - wiki\n - shapes\n```\n\nMarkdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).\n\nThe validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference=\"rdfs\"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.\n\nTo constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):\n\n```yaml\n---\ntype: sh:NodeShape\nrdfs:label: Project Shape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:string\n sh:message: Project must have exactly one name string.\n - sh:path: schema:startDate\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:date\n sh:message: Project must have a startDate in YYYY-MM-DD format.\n---\n```\n\nWhen you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.\n\n### Lists and property paths\n\nA YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:status\n sh:in:\n - schema:ActiveActionStatus\n - schema:CompletedActionStatus\n - sh:path: [schema:author, schema:name]\n sh:minCount: 1\n - sh:path:\n sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]\n sh:minCount: 1\n---\n```\n\nHere the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.\n\n### Shape page checks\n\n`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:\n\n- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.\n- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).\n- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.\n- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).\n\nWhile any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.\n\nSeparately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.\n\nShapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.\n\n### JSON Schema (optional)\n\nOn the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nwazoo:jsonSchema: schemas/project.json\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n---\n```\n\n`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.\n\nSee [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.\n\nPure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.\n\n## Related\n\n- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation\n- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)\n- [Style Guide](Style_Guide.md) — shape authoring and filenames\n- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`\n- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout\n\n## References\n\n- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)";
schema:headline "SHACL";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
<https://wazootech.github.io/wiki/SHACL> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/description> "Shapes Constraint Language for validating RDF graphs." .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/articleBody> "# SHACL\n\nThe **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.\n\nIn this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.\n\n## Defining custom SHACL shapes (validation)\n\nSHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:\n\n```yaml\nwiki:\n input:\n - wiki\n - shapes\n```\n\nMarkdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).\n\nThe validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference=\"rdfs\"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.\n\nTo constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):\n\n```yaml\n---\ntype: sh:NodeShape\nrdfs:label: Project Shape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:string\n sh:message: Project must have exactly one name string.\n - sh:path: schema:startDate\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:date\n sh:message: Project must have a startDate in YYYY-MM-DD format.\n---\n```\n\nWhen you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.\n\n### Lists and property paths\n\nA YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:status\n sh:in:\n - schema:ActiveActionStatus\n - schema:CompletedActionStatus\n - sh:path: [schema:author, schema:name]\n sh:minCount: 1\n - sh:path:\n sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]\n sh:minCount: 1\n---\n```\n\nHere the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.\n\n### Shape page checks\n\n`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:\n\n- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.\n- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).\n- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.\n- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).\n\nWhile any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.\n\nSeparately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.\n\nShapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.\n\n### JSON Schema (optional)\n\nOn the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nwazoo:jsonSchema: schemas/project.json\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n---\n```\n\n`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.\n\nSee [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.\n\nPure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.\n\n## Related\n\n- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation\n- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)\n- [Style Guide](Style_Guide.md) — shape authoring and filenames\n- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`\n- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout\n\n## References\n\n- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)" .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/headline> "SHACL" .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/dateCreated> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/dateModified> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:SHACL a schema:TechArticle;
schema:description "Shapes Constraint Language for validating RDF graphs.";
schema:articleBody "# SHACL\n\nThe **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.\n\nIn this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.\n\n## Defining custom SHACL shapes (validation)\n\nSHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:\n\n```yaml\nwiki:\n input:\n - wiki\n - shapes\n```\n\nMarkdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).\n\nThe validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference=\"rdfs\"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.\n\nTo constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):\n\n```yaml\n---\ntype: sh:NodeShape\nrdfs:label: Project Shape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:string\n sh:message: Project must have exactly one name string.\n - sh:path: schema:startDate\n sh:minCount: 1\n sh:maxCount: 1\n sh:datatype: xsd:date\n sh:message: Project must have a startDate in YYYY-MM-DD format.\n---\n```\n\nWhen you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.\n\n### Lists and property paths\n\nA YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nsh:property:\n - sh:path: schema:status\n sh:in:\n - schema:ActiveActionStatus\n - schema:CompletedActionStatus\n - sh:path: [schema:author, schema:name]\n sh:minCount: 1\n - sh:path:\n sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]\n sh:minCount: 1\n---\n```\n\nHere the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.\n\n### Shape page checks\n\n`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:\n\n- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.\n- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).\n- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.\n- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).\n\nWhile any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.\n\nSeparately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.\n\nShapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.\n\n### JSON Schema (optional)\n\nOn the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:\n\n```yaml\n---\ntype: sh:NodeShape\nsh:targetClass: schema:Project\nwazoo:jsonSchema: schemas/project.json\nsh:property:\n - sh:path: schema:name\n sh:minCount: 1\n---\n```\n\n`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.\n\nSee [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.\n\nPure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.\n\n## Related\n\n- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation\n- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)\n- [Style Guide](Style_Guide.md) — shape authoring and filenames\n- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`\n- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout\n\n## References\n\n- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)";
schema:headline "SHACL";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
<https://wazootech.github.io/wiki/SHACL> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/description> "Shapes Constraint Language for validating RDF graphs." .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/articleBody> """# SHACL
The **Shapes Constraint Language (SHACL)** is a W3C recommendation for validating [RDF](RDF.md) graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph itself.
In this wiki, SHACL is used to enforce structure via the [wiki](wiki.md) validation engine.
## Defining custom SHACL shapes (validation)
SHACL shapes load from the wiki graph. Add a dedicated `shapes/` tree to [Wiki Configuration](Wiki_Configuration.md) `wiki.input` so shape documents stay separate from prose pages:
```yaml
wiki:
input:
- wiki
- shapes
```
Markdown and data files under `shapes/` compile into the same wiki graph as wiki articles; `wiki check` extracts `sh:NodeShape` triples and validates every document against them with [rdf-validate-shacl](https://github.com/zazuko/rdf-validate-shacl).
The validator applies `rdfs:subClassOf` when it resolves `sh:targetClass`, so a shape on a class also targets instances of its subclasses. It does not run a full RDFS inference pass first, which the pre-0.2.0 Python engine (PySHACL with `inference="rdfs"`) did. A constraint whose meaning depends on inferred triples, such as `sh:class` over an inferred type or `sh:path` over an `rdfs:subPropertyOf`, only sees triples the wiki states explicitly. This repository keeps shapes alongside articles under `wiki/` instead ([Software Application Shape](Software_Application_Shape.md)); both layouts work.
To constrain a class (for example `schema:Project`), create `shapes/Project_Shape.md` using a [Style Guide](Style_Guide.md) Wikipedia-style filename and frontmatter like [Software Application Shape](Software_Application_Shape.md):
```yaml
---
type: sh:NodeShape
rdfs:label: Project Shape
sh:targetClass: schema:Project
sh:property:
- sh:path: schema:name
sh:minCount: 1
sh:maxCount: 1
sh:datatype: xsd:string
sh:message: Project must have exactly one name string.
- sh:path: schema:startDate
sh:minCount: 1
sh:maxCount: 1
sh:datatype: xsd:date
sh:message: Project must have a startDate in YYYY-MM-DD format.
---
```
When you run `wiki check`, any page with `type: Project` is automatically validated against these constraints.
### Lists and property paths
A YAML list in frontmatter usually means one triple per item. The SHACL parameters whose value the [SHACL](https://www.w3.org/TR/shacl/) specification defines as a list compile to an RDF list instead, at any depth: `sh:in`, `sh:languageIn`, `sh:ignoredProperties`, `sh:and`, `sh:or`, `sh:xone`, and `sh:alternativePath`. Under `sh:path` (and `sh:inversePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, `sh:zeroOrOnePath`), a list of two or more items is a sequence path, and a one-item list is the same as the bare item:
```yaml
---
type: sh:NodeShape
sh:targetClass: schema:Project
sh:property:
- sh:path: schema:status
sh:in:
- schema:ActiveActionStatus
- schema:CompletedActionStatus
- sh:path: [schema:author, schema:name]
sh:minCount: 1
- sh:path:
sh:alternativePath: [schema:alternateName, [schema:author, schema:name]]
sh:minCount: 1
---
```
Here the second property checks the author's name (a sequence path), and the third accepts either an `alternateName` or an author's name.
### Shape page checks
`wiki check` lints every shape page before it validates anything with it (`check.shape_definition`, default `error`). It follows the [SHACL Core](https://www.w3.org/TR/shacl/) rules for well-formed shapes:
- **Vocabulary.** Every `sh:` key must be a property the [SHACL vocabulary](http://www.w3.org/ns/shacl.ttl) defines, and every `sh:` type or value must be one of its terms. `sh:patern` or `type: sh:NodeShap` fails instead of silently doing nothing.
- **Property shapes** need exactly one `sh:path` (SHACL §2.3), whether they are a page typed `sh:PropertyShape` or an item under `sh:property`. A node shape, including a value of `sh:node`, cannot have one (§2.2, §4.7.1).
- **Paths** must be well-formed (§2.3.1): an IRI, a list of paths (a sequence), or a mapping with exactly one of `sh:inversePath`, `sh:alternativePath`, `sh:zeroOrMorePath`, `sh:oneOrMorePath`, or `sh:zeroOrOnePath`. `sh:alternativePath` needs at least two paths. A CURIE whose prefix the wiki does not declare compiles to a plain string, not an IRI, so it is rejected.
- **IRI-valued parameters** (`sh:targetClass`, `sh:targetSubjectsOf`, `sh:targetObjectsOf`, `sh:class`, `sh:datatype`, `sh:equals`, `sh:disjoint`, `sh:lessThan`, `sh:lessThanOrEquals`, and each member of `sh:ignoredProperties`) must be IRIs, and `sh:nodeKind` must be one of its six kinds (§4.1.3).
While any of these fail as errors, `wiki check` skips SHACL validation and says so with a `shacl_skipped` warning: a broken shape makes the SHACL verdict meaningless, so fix the shapes first.
Separately, `check.shape_unused` (default `warning`) flags a node shape page that validates nothing: it has no target, is not also a class, and no other shape reaches it through `sh:node`, `sh:property`, `sh:qualifiedValueShape`, `sh:not`, `sh:and`, `sh:or`, or `sh:xone` (§2.1). SHACL allows such a shape, so this is a warning rather than an error; set it to `error` to enforce it or `off` to silence it.
Shapes written in RDF get the same checks over their triples: fenced `turtle` blocks, and RDF data files under `wiki.input` (`.ttl`, `.trig`, `.nt`, `.nq`, `.rdf`, `.xml`, `.jsonld`). With no frontmatter key to point at, a finding names the source and the shape instead: an IRI, or the triples that reach a blank node from one, for example `In shapes/Person.ttl: ex:PersonShape sh:property [ ] sh:minCont: …` or `In Person_Shape (turtle block 1): …`. A prefix declared only inside the Turtle prints as a full IRI. Shapes from installed sources are not linted; their own wiki's `wiki check` covers them.
### JSON Schema (optional)
On the same shape document, add `wazoo:jsonSchema` beside `sh:targetClass` to validate frontmatter with [JSON Schema](https://json-schema.org/) in parallel with SHACL:
```yaml
---
type: sh:NodeShape
sh:targetClass: schema:Project
wazoo:jsonSchema: schemas/project.json
sh:property:
- sh:path: schema:name
sh:minCount: 1
---
```
`wiki init` scaffolds an empty `wiki/` folder — add your own shape documents (e.g. a `sh:NodeShape` frontmatter page for your domain) when you need SHACL validation. Optionally bind JSON Schema on shape documents with `wazoo:jsonSchema` beside `sh:targetClass`, or append per-page schemas with their own `wazoo:jsonSchema` key (string or list). Shape binding documents are not validated as instances — only their schema refs are checked for loadability.
See [Tech Article Shape](Tech_Article_Shape.md) in this wiki for a dogfooded example.
Pure `.ttl` or `.trig` files in `shapes/` also load when that directory is listed in `wiki.input`; markdown frontmatter is the default authoring style in this wiki.
## Related
- [wiki check](wiki_check.md) — SHACL and JSON Schema frontmatter validation
- [wiki lint](wiki_lint.md) — prose and link conventions (separate from shapes)
- [Style Guide](Style_Guide.md) — shape authoring and filenames
- [Software Application Shape](Software_Application_Shape.md) — example `sh:NodeShape`
- [Wiki Configuration](Wiki_Configuration.md) — `wiki.input` and shapes layout
## References
- [SHACL — Shapes Constraint Language](https://www.w3.org/TR/shacl/)""" .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/headline> "SHACL" .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/dateCreated> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<https://wazootech.github.io/wiki/SHACL> <https://schema.org/dateModified> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .