ShEx Essentials
This document uses a running example illustrated by the following graph in which an Issue is submitted by some person and may be reproduced by the same person or someone else.
These issues can have a status of unassigned or assigned.
Node Constraints
The following node constraints can be used alone, or in combination.
- literal datatype
- A node constraint that identifies the datatype of an RDF literal.
my:UserShape { foaf:name xsd:string }
{ "my:UserShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "foaf:name", "value": { "type": "NodeConstraint", "datatype": "xsd:string" } } } } - literal facet
- A node constraint that applies XML Schema constraining facets, including numeric facets, which apply only to numeric RDF literals (
MinInclusive,MinExclusive,MaxInclusive,MaxExclusive,TotalDigits,FractionDigits) and string facets, which apply to all RDF literals (Length,MinLength,MaxLength,Pattern). In the ShExC syntax, facet names are not case-sensitive.my:UserShape { ex:shoeSize xsd:float MinInclusive 5.5 MaxInclusive 12.5 }
{ "my:UserShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "ex:shoeSize", "value": { "type": "NodeConstraint", "datatype": "http://www.w3.org/2001/XMLSchema#float", "mininclusive": 5.5, "maxinclusive": 12.5 } } } } - node kind
- A node constraint that specifies whether an RDF data node is of kind
Literal,IRI,BNode, orNonLiteral, a union of the kindsIRIandBNode. In the ShExC syntax, node kinds are not case-sensitive.my:UserShape { foaf:mbox IRI }
{ "my:UserShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "foaf:mbox", "value": { "type": "NodeConstraint", "nodeKind": "IRI" } } } } - value set
- Enumerates a set of specific expected values.
my:IssueShape { ex:state [ex:unassigned ex:assigned] }
{ "my:IssueShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "ex:status", "value": { "type": "NodeConstraint", "values": [ "ex:unassigned", "ex:assigned" ] } } } }my:IssueShape { ex:state ["unassigned" "assigned"] }
{ "my:IssueShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "ex:status", "value": { "type": "NodeConstraint", "values": [ { "value": "unassigned" }, { "value": "assigned" } ] } } } }my:IssueShape { ex:state [0 1] }
{ "my:IssueShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "ex:status", "value": { "type": "NodeConstraint", "values": [ { "value": "0", "type": "http://www.w3.org/2001/XMLSchema#integer" }, { "value": "1", "type": "http://www.w3.org/2001/XMLSchema#integer" } ] } } } } - value shape
- Asserts that the value is described by another shape, e.g.
my:IssueShape { ex:reportedBy @my:UserShape }
{ "my:IssueShape": { "type": "Shape", "expression": { "type": "TripleConstraint", "predicate": "ex:reportedBy", "value": "my:PersonShape" } } }
Triple Constraints
Triple constraints are evaluated against all of the triples in an RDF graph that touch a given data node. The RDF data node examined during validation is called the focus node. Triple constraints identify a predicate and describe matching triples as having the focus node as the subject (or object). (The exception is the inverse triple constraint, which describes matching triples as having the focus node as the object.) Triple constraints specify a cardinality (how many matching triples are expected or permitted). They may include a value constraint, which is a node constraint describing the object of matching triples (or subject, in the case of inverse triple constraints).
The following simple example has one shape, my:UserShape, with a single triple constraint on the property foaf:name. A value constraint within the triple constraint says that the object of a foaf:name triple must be an RDF literal with a datatype of xsd:string. A conforming node in an RDF data graph will have exactly one such triple.
PREFIX ex: <http://ex.example/#> PREFIX my: <http://my.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> my:UserShape { foaf:name xsd:string }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#UserShape",
"type": "Shape",
"expression": {
"type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"datatype": "http://www.w3.org/2001/XMLSchema#string" } } }
] }
PREFIX ex: <http://ex.example/#> PREFIX inst: <http://example.com/users/> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> inst:User1 foaf:name "Joe Jones"^^xsd:string . inst:User2 foaf:name "Bob Smith" . try it
inst:User3 foaf:name "Joe Jones"^^xsd:string ; foaf:name "J. Jones"^^xsd:string . inst:User4 foaf:name "Bob Smith"^^xsd:anyURI . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:User1 | my:UserShape | pass | |
| inst:User2 | my:UserShape | pass | Literals in Turtle have a default datatype of xsd:string. |
| inst:User3 | my:UserShape | fail | Expected exactly one foaf:name arc. |
| inst:User4 | my:UserShape | fail | Expected an xsd:string, not a xsd:anyURI. |
The following regular expression conventions are used to specify cardinalities other than the default of "exactly one" (see the example in Quick Start, with cardinality "one or two").
- "+" - one or more
- "*" - zero or more
- "?" - zero or one
- "{m}" - exactly m
- "{m,n}" - at least m, no more than n
Grouping Triple Constraints in Shapes
The examples above show just one triple constraint per shape. In practice, most shape declarations will include multiple constraints. In the ShExC syntax, triple constraints are separated by a semi-colon. In the following example, the shape my:IssueShape will match:
- exactly one data triple with predicate ex:state and a value in the value set ex:unassigned or ex:assigned,
- exactly one data triple with predicate ex:reportedBy and a value matching the shape labeled my:UserShape.
The shape labeled my:UserShape must have:
- exactly one triple constraint on predicate foaf:name with a value of the literal datatype xsd:string
- one or more triple constraints on predicate foaf:mbox with a
node kindof IRI.
PREFIX ex: <http://ex.example/#> PREFIX my: <http://my.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> my:IssueShape { ex:state [ex:unassigned ex:assigned]; ex:reportedBy @my:UserShape } my:UserShape { foaf:name xsd:string; foaf:mbox IRI+ }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#state",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://ex.example/#unassigned",
"http://ex.example/#assigned"
] } },
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#reportedBy",
"valueExpr": "http://my.example/#UserShape" }
] } },
{ "id": "http://my.example/#UserShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"datatype": "http://www.w3.org/2001/XMLSchema#string" } },
{ "type": "TripleConstraint", "min": 1, "max": -1,
"predicate": "http://xmlns.com/foaf/0.1/mbox",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "iri" } }
] } }
] }
PREFIX ex: <http://ex.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> inst:Issue1 a ex:Issue ; ex:state ex:unassigned ; ex:reportedBy inst:User2 . inst:User2 a foaf:Person ; foaf:name "Bob Smith" ; foaf:mbox <mailto:bob@example.org> ; foaf:mbox <mailto:rs@example.org> . try it
PREFIX ex: <http://ex.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> inst:Issue3 a ex:Issue ; ex:state ex:unsinged ; # <-- typo ex:reportedBy inst:User4 . inst:User4 a foaf:Person ; foaf:name "Bob Smith", "Robert Smith" ; foaf:mbox <mailto:bob@example.org> ; foaf:mbox <mailto:rs@example.org> . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:Issue1 | my:IssueShape | pass | |
| inst:User2 | my:UserShape | pass | |
| inst:Issue3 | my:IssueShape | fail | ex:unsinged not in range of ex:status. |
| inst:User4 | my:UserShape | fail | Max cardinality of foaf:name exceeded. |
Note that a shape composed of triple expressions with a minimum cardinality of zero will trivially match any RDF node that does not have outgoing arcs.
PREFIX my: <http://my.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX ex: <http://ex.example/#> my:IssueShape { ex:state [ex:unassigned ex:assigned]; ex:reportedBy @my:UserShape } my:UserShape { foaf:name LITERAL?; foaf:mbox IRI* }
{ "@context": "https://shexspec.github.io/context.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#state",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://ex.example/#unassigned",
"http://ex.example/#assigned"
] } },
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#reportedBy",
"valueExpr": "http://my.example/#UserShape" }
] } },
{ "id": "http://my.example/#UserShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint", "min": 0, "max": 1,
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" }
},
{ "type": "TripleConstraint", "min": 0, "max": -1,
"predicate": "http://xmlns.com/foaf/0.1/mbox",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "iri" } }
] } }
] }
PREFIX inst: <http://inst.example/#> PREFIX ex: <http://ex.example/#> inst:Issue1 a ex:Issue ; ex:state ex:unassigned ; ex:reportedBy "Bob Smith" . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:Issue1 | my:IssueShape | pass | |
| "Bob Smith" | my:UserShape | pass | Matched 0 foaf:name and 0 foaf:mbox arcs. |
For both properties in my:UserShape, the minimum number of triples is zero. Any RDF data node will match this shape as long as it does not have conflicting ex:state or ex:reportedBy properties. Since no RDF literal may be the subject of RDF triples, any literal would satisfy this shape. This can lead to unintended results and confusing errors.
Combining Value Constraints
Value constraints can be combined, for example to say that an issue conforms to a given shape and is identified by an IRI matching a certain pattern.
PREFIX ex: <http://ex.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> PREFIX my: <http://my.example/#> my:IssueShape { ex:state [ex:accepted ex:resolved]; ex:reproducedBy @my:EmployeeShape } my:EmployeeShape IRI /^http:\/\/hr\.example\/id#[0-9]+/ { foaf:name LITERAL; ex:department [ex:ProgrammingDepartment] }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#state",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://ex.example/#accepted",
"http://ex.example/#resolved"
]
} },
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#reproducedBy",
"valueExpr": "http://my.example/#EmployeeShape" }
] } },
{ "id": "http://my.example/#EmployeeShape",
"type": "ShapeAnd",
"shapeExprs": [
{ "type": "NodeConstraint",
"nodeKind": "iri",
"pattern": "^http://hr.example/id#[0-9]+" },
{ "type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{
"type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" } },
{
"type": "TripleConstraint",
"predicate": "http://ex.example/#department",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://ex.example/#ProgrammingDepartment"
] } }
] } }
] }
] }
PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> PREFIX ex: <http://ex.example/#> inst:Issue1 ex:state ex:accepted ; ex:reproducedBy <http://hr.example/id#123> . <http://hr.example/id#123> foaf:name "Bob Smith" ; ex:department ex:ProgrammingDepartment . try it
PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> PREFIX ex: <http://ex.example/#> inst:Issue1 ex:state ex:accepted ; ex:reproducedBy <http://hr.example/id#abc> . <http://hr.example/id#abc> foaf:name "Bob Smith" ; ex:department ex:ProgrammingDepartment . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:User1 | my:UserShape | pass | |
| <http://hr.example/id#123> | my:EmployeeShape | pass | |
| inst:User3 | my:UserShape | fail | Object of ex:reproducedBy does not match my:EmployeeShape. |
| <http://hr.example/id#abc> | my:EmployeeShape | fail | <http://hr.example/id#abc> does not match regular expression. |
Nesting Shapes
In the examples above, value expressions referenced shape expressions with the '@' symbol. It is also possible to write "anonymous" shapes directly in the value expression. In the example below, the value of the triple constraint on predicate ex:reportedBy is a shape comprised of triples constraints on the predicates foaf:name and foaf:mbox. In ShExC syntax, this anonymous shape is enclosed in curly brackets. In ShExJ, it is contained in the triple constraint's valueExpr property.
PREFIX my: <http://my.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX ex: <http://ex.example/#> my:IssueShape { ex:state [ex:unassigned ex:assigned]; ex:reportedBy { foaf:name LITERAL; foaf:mbox IRI+ } }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#state",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://ex.example/#unassigned",
"http://ex.example/#assigned"
] } },
{ "type": "TripleConstraint",
"predicate": "http://ex.example/#reportedBy",
"valueExpr": {
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" } },
{
"type": "TripleConstraint", "min": 1, "max": -1,
"predicate": "http://xmlns.com/foaf/0.1/mbox",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "iri" } }
] } } }
] } }
] }
Expressions with Choices
Most schema languages offer a way to express choices. In the following example, a user has either a simple name (foaf:name), or a composite name (foaf:familyName with one or more foaf:givenNames). The user must have exactly one foaf:mbox.
PREFIX my: <http://my.example/#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> my:UserShape { ( foaf:name LITERAL | foaf:givenName LITERAL+; foaf:familyName LITERAL ); foaf:mbox IRI }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#UserShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "OneOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/name",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" } },
{ "type": "EachOf",
"expressions": [
{ "type": "TripleConstraint", "min": 1, "max": -1,
"predicate": "http://xmlns.com/foaf/0.1/givenName",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" } },
{ "type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/familyName",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "literal" } }
] }
] },
{ "type": "TripleConstraint",
"predicate": "http://xmlns.com/foaf/0.1/mbox",
"valueExpr": {
"type": "NodeConstraint",
"nodeKind": "iri" } }
] } }
] }
PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> inst:User1 a foaf:Person ; foaf:name "Alice Walker" ; foaf:mbox <mailto:awalker@example.org> . inst:User2 a foaf:Person ; foaf:givenName "Robert" ; foaf:givenName "Paris" ; foaf:familyName "Moses" ; foaf:mbox <mailto:rpmoses@example.org> . try it
PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX inst: <http://inst.example/#> inst:User3 a foaf:Person ; foaf:givenName "Smith" ; foaf:mbox <mailto:bobs@example.org> . inst:User4 a foaf:Person ; foaf:name "A" ; foaf:givenName "B" ; foaf:familyName "C" ; foaf:mbox <mailto:bobs@example.org> . inst:User5 a foaf:Person ; foaf:name "A" ; foaf:givenName "B" ; foaf:mbox <mailto:bobs@example.org> . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:User1 | my:UserShape | pass | |
| inst:User2 | my:UserShape | pass | |
| inst:User3 | my:UserShape | fail | Expected a foaf:familyName arc. |
| inst:User4 | my:UserShape | fail | Expected only one disjunction to pass. |
| inst:User5 | my:UserShape | fail | Extra foaf:givenName arc. |
Value Sets
A value set is a value constraint for enumerating the set of permissible RDF nodes.
The values can be IRIs, literals or language tags.
In the example below, "[@en @fr]" matches any RDF literal with a language tag of "en" or "fr".
my:IssueShape { ex:state [ex:unassigned ex:assigned] }
{ "id": "http://a.example/my#IssueShape", "type": "Shape",
"expression": { "type": "TripleConstraint", "predicate": "http://a.example/ex#state",
"valueExpr": { "type": "NodeConstraint", "values": [
"http://a.example/ex#unassigned",
"http://a.example/ex#assigned"
] } } }
my:IssueShape { ex:state ["unassigned" "assigned"] }
{ "id": "http://a.example/my#IssueShape", "type": "Shape",
"expression": { "type": "TripleConstraint", "predicate": "http://a.example/ex#state",
"valueExpr": { "type": "NodeConstraint", "values": [
{ "value": "unassigned" },
{ "value": "assigned" }
] } }
my:IssueShape { ex:label [@en @fr] }
{ "id": "http://a.example/my#IssueShape", "type": "Shape",
"expression": { "type": "TripleConstraint", "predicate": "http://a.example/ex#state",
"valueExpr": { "type": "NodeConstraint", "values": [
{ "type": "Language", "languageTag": "en" },
{ "type": "Language", "languageTag": "fr" }
] } } }
Fixed values are represented as value sets with one member. For example, a required type triple can be expressed in the following two ways using the ShExC syntax:
my:UserShape { rdf:type [foaf:Person] }
{ "id": "http://schema.example/my#UserShape", "type": "Shape",
"expression": { "type": "TripleConstraint",
"predicate": "http://www.w3.org/1999/02/22-rdf-syntax-ns#type",
"valueExpr": {
"type": "NodeConstraint", "values": [
"http://xmlns.com/foaf/0.1/Person"
] }
} }
my:UserShape { a [foaf:Person] }
A value set can also contain stems for IRIs, strings and language tags.
An IRI orx string stem matches any IRI or string that starts with the stem.
A language tag stem matches any literal with a language tag that starts with the stem.
These are flagged as stems by appending a tilde ("~").
The last triple constraint in my:IssueShape below is an inverse triple constraint. These are described in the next section. This inverse triple constraint states that every my:IssueShape must have an incoming arc from one of two nodes: my:Product1 or my:Product2.
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> my:IssueShape { ex:status [ excodes:~ auxterms:~ ]; ex:mood [ @en~ - @en-fr ]; ^ex:hasIssue [ my:Product1 my:Product2 ] }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "EachOf",
"expressions": [
{ "type": "TripleConstraint",
"predicate": "http://a.example/#status",
"valueExpr": {
"type": "NodeConstraint",
"values": [
{ "type": "IriStemRange",
"stem": "http://a.example/codes#" },
{ "type": "IriStemRange",
"stem": "http://aux.example/terms#" }
] } },
{ "type": "TripleConstraint",
"predicate": "http://a.example/#mood",
"valueExpr": {
"type": "NodeConstraint",
"values": [
{
"type": "LanguageStemRange",
"stem": { "value": "en" },
"exclusions": [
{ "value": "en-fr" }
] }
] } },
{ "type": "TripleConstraint",
"inverse": true,
"predicate": "http://a.example/#hasIssue",
"valueExpr": {
"type": "NodeConstraint",
"values": [
"http://my.example/#Product1",
"http://my.example/#Product2"
] } }
] } }
] }
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> PREFIX inst: <http://inst.example/#> inst:Issue1 ex:status excodes:resolved ; ex:mood "hungry"@en-gb . my:Product2 ex:hasIssue inst:Issue1 . try it
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> PREFIX inst: <http://inst.example/#> inst:Issue2 ex:status ex:done ; ex:mood "angry"@en-fr . my:Product1 ex:hasIssue inst:Issue2 . inst:Issue3 ex:status auxterms:done. my:Product3 ex:hasIssue inst:Issue3 . try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:Issue1 | my:IssueShape | pass | |
| inst:Issue2 | my:IssueShape | fail | ex:done not in range of ex:status. Excluded language tag for ex:mood. |
| inst:Issue3 | my:IssueShape | fail | my:Product3 not in range of ex:hasIssue. |
While IRI, string and language tag stems match any terms starting with the stem, one may wish to exclude specific terms or term stems.
Stem exclusions are expressed by following a stem with one or more exclusions.
An exclusion consists of a minus ("-") followed by an IRI, IRI stem, string, string stem, language tag, or language tag stem.
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> my:IssueShape { ex:status [ excodes:~ - excodes:unassigned - excodes:assigned auxterms:~ - <http://aux.example/terms#med_>~ ] }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "TripleConstraint",
"predicate": "http://a.example/#status",
"valueExpr": {
"type": "NodeConstraint",
"values": [
{ "type": "IriStemRange",
"stem": "http://a.example/codes#",
"exclusions": [
"http://a.example/codes#unassigned",
"http://a.example/codes#assigned"
] },
{ "type": "IriStemRange",
"stem": "http://aux.example/terms#",
"exclusions": [
{ "type": "IriStem",
"stem": "http://aux.example/terms#med_" }
] }
] } } }
] }
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> PREFIX inst: <http://inst.example/#> inst:Issue2 ex:status excodes:resolved . inst:Issue3 ex:status excodes:assigned. inst:Issue4 ex:status auxterms:med_sniffles. inst:Issue5 ex:status ex:done. try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:Issue2 | my:IssueShape | pass | |
| inst:Issue3 | my:IssueShape | fail | excodes:assigned excluded. |
| inst:Issue4 | my:IssueShape | fail | auxterms:med_… terms excluded. |
| inst:Issue5 | my:IssueShape | fail | ex:done not in range of ex:status. |
A period (.) can be used with exclusions to say that any term is permitted except the exclusions.
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> my:IssueShape { ex:status [ . - excodes:retracted - excodes:assigned ] }
{ "@context": "http://www.w3.org/ns/shex.jsonld",
"type": "Schema",
"shapes": [
{ "id": "http://my.example/#IssueShape",
"type": "Shape",
"expression": {
"type": "TripleConstraint",
"predicate": "http://a.example/#status",
"valueExpr": {
"type": "NodeConstraint",
"values": [
{ "type": "IriStemRange",
"stem": {
"type": "Wildcard" },
"exclusions": [
"http://a.example/codes#retracted",
"http://a.example/codes#assigned"
] }
] } } }
] }
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> PREFIX inst: <http://inst.example/#> inst:Issue1 ex:status ex:random . try it
PREFIX ex: <http://a.example/#> PREFIX my: <http://my.example/#> PREFIX excodes: <http://a.example/codes#> PREFIX auxterms: <http://aux.example/terms#> PREFIX inst: <http://inst.example/#> inst:Issue2 ex:status excodes:assigned. try it
| Node | Shape | Result | Reason |
|---|---|---|---|
| inst:Issue1 | my:IssueShape | pass | |
| inst:Issue2 | my:IssueShape | fail | excodes:assigned is excluded. |