This document defines SHACL Rules.
SHACL, the Shapes Constraint Language, is a language for describing the structure of RDF graphs. SHACL may be used for a variety of purposes such as validating, inferencing, modeling domains, generating ontologies to inform other agents, building user interfaces, generating code, and integrating data.
SHACL Rules provides inferencing with the generation of new RDF data from a combination of a set of rules and a base data graph. Rules can be expressed as RDF or in the SHACL Rules Language (SRL).
This specification is published by the Data Shapes Working Group.
This document introduces the concept of inference rules for SHACL 1.2, a mechanism for deriving new RDF triples from existing data using declarative rules defined in shapes graphs. This extends SHACL’s capabilities beyond validation, enabling reasoning and data enrichment.
This document complements other SHACL 1.2 specifications, such as SHACL Core, by defining the syntax and semantics of rule-based inference. While SHACL Core focuses on constraint validation, the SHACL Rules specification provides a standardized way to express and evaluate rules that generate new data.
Connect to definitions in RDF 1.2 Concepts.
The following definitions from other specifications are used in this document: @@
Some examples in this document use Turtle [[turtle]]. The reader is expected to be familiar with SHACL [[shacl]] and SPARQL [[sparql-query]].
Within this document, the following namespace prefix bindings are used:
| Prefix | Namespace |
|---|---|
rdf: |
http://www.w3.org/1999/02/22-rdf-syntax-ns# |
rdfs: |
http://www.w3.org/2000/01/rdf-schema# |
sh: |
http://www.w3.org/ns/shacl# |
shrl: |
http://www.w3.org/ns/shacl-rules# |
shnex: |
http://www.w3.org/ns/shacl-node-expr# |
xsd: |
http://www.w3.org/2001/XMLSchema# |
ex: |
http://example.com/ |
Throughout the document, color-coded boxes containing RDF graphs in Turtle will appear. These fragments of Turtle documents use the prefix bindings given above.
TODO
RFC 2119 language should be automatically inserted here.
SHACL rules infer new triples. The input is a data graph and a set of rules. The output is a graph of inferred triples that do not occur in the data graph.
:A :fatherOf :X . :B :motherOf :X . :C :motherOf :A .
RULE { ?x :childOf ?y } WHERE { ?y :fatherOf ?x }
RULE { ?x :childOf ?y } WHERE { ?y :motherOf ?x }
RULE { ?x :descendedFrom ?y } WHERE { ?x :childOf ?y }
RULE { ?x :descendedFrom ?y } WHERE { ?x :childOf ?z . ?z :childOf ?y }
The above rules, applied to the data, will conclude that: `:X` is the `:childOf` `:A` and `:B`, and that `:X` is `:descendedFrom` `:C`.
RULE { ?x :ancestorOf ?y } WHERE { ?y :descendedFrom ?x }
RULE { ?a :ancestorOf ?b } WHERE { ?a :ancestorOf ?c . ?c :ancestorOf ?b }
# Default value - calculate a name
RULE { ?x :name ?FN } WHERE {
?x rdf:type :Person
NOT { ?x :name ?someName }
?x :givenName ?name1 ;
:familyName ?name2 .
BIND(concat(?name1, " ", ?name2) AS ?FN)
}
`IMPORTS`
Gives some modularity/sharing of rules.
"IMPORTS" vs "IMPORT" (c.f. `owl:imports`)
Generating new terms without restriction can lead to unbounded inferred triples. There are function-like forms that do not have repeatable results: `BNODE`, `UUID`. Blank nodes in the rule head behave like SPARQL `CONSTRUCT`. Assignment can be used to have an incrementing counter.
At risk:
Rule tuples are workspace elements and are disjoint from triples. They are tuples of RDF terms (no variables).
Syntax of tuple patterns, templates and tuples:
Often, the first argument will be a fixed name.
There is a tuple store which holds tuples for the lifetime of the evaluation. The tuple store holds duplicate data tuples (unlike an RDF graph which is a set).
Should we include attaching SHACL (1.2) Rules to shapes? If so, what does it mean given the difference in execution semantics?
In practice, how often are constriants and AF-rules written on the same shape? If they are, how are the rules being used, in practice, to influence the validation?
Sketch:
[] rdf:type sh:NodeShape ;
sh:rule ## Different property?
[ a srl:SHACLRule ;
srl:ruleSet "..."; ## SRL syntax
sh:prefixes ... ;
];
[] rdf:type sh:NodeShape ;
sh:rule
[ a srl:SHACLRule ;
srl:ruleSet [ ... RDF syntax ... ] ;
];
The Shape Rules Abstract Syntax
An [=expression=] is a function, or functional form. It's arguments are [=RDF terms=]. An expression is evaluated with respect to a [=solution mapping=] to give an [=RDF term=] as the result. Expressions are compatible with SHACL list parameter functions and with SPARQL expressions.
In a [=triple pattern=] or a [=triple template=], position 1 of the tuple is informally called the subject, position 2 is informally called the predicate, and position 3 is informally called the object.
Well-formedness is a set of conditions on the abstract syntax of SHACL rules. Together, these conditions ensure that a [=variable=] in the [=head=] of a rule has a value defined in the [=body=] of the rule; that each variable in an [=condition expression=] or [=assignment expression=] has a value at the point of evaluation; and that each assignment in a rule introduces a new variable, one that has not been used earlier in the rule body.
A [=rule=] is a well-formed rule if all of the following conditions are met:
A [=rule set=] is "well-formed" if and only if all of the [=rules=] of the rule set are "well-formed".
Notes:
A [=triple template=] with components `ts`, `tp`, `to` can possibly generate a triple with component RDF terms `s`, `p`, `o` if `ts` is a variable or `ts` is the same RDF term as `s`, `tp` is a variable or `tp` is the same RDF term as `p`, and `to` is a variable or `to` is the same RDF term as `o`.
In addition, if any pair of `ts`, `tp`, and `to` are the same variable, then the corresponding pair of `s`, `p`, and `o` must be the same.
Revise
Examples:
@@ Examples of triple patttern dependencies.
@@ Examples of rule dependencies.
[=Stratification=] is the process of partitioning a [=rule set=] into an ordered sequence of [=stratification layers=] (also known as "strata", singular "stratum="), forming a [=stratification=]. Rules in lower [=strata=] are evaluated before rules in higher [=strata=].
[=Stratification=] imposes constraints on dependencies between [=rules=] to ensure that [=negation elements=] depend only on results computed in earlier [=strata=], guaranteeing a single, well-defined outcome from the evaluation of a [=rule set=] over a given [=base graph=].
A stratification process may also be used to make other evaluation decisions. This document describes the necessary conditions for consistent evaluation and gives one possible way to form a stratification. Implementations need to meet the conditions described here in order to get compatible behavior but are not required to implement the algorithm as presented.
[=Stratification=] is only defined when the following condition is satisfied. If a [=rule set=] does not meet this condition, then this specification does not define the outcome of [=rule set=] evaluation.
In other words, there is no `NOT` used in any rule that transitively depends on itself.
The following algorithm gives one possible stratification based solely on the rule set.
@@ one possible stratification algorithm
A consequence of the [=stratification condition=] is that when a rule containing a [=negation element=] is evaluated, the data used to determine the outcome of that [=negation element=], whether in the [=base graph=] or the [=inference graph=], is fixed and will not change during evaluation.
There are two concrete syntaxes.
Shape Rules Language:
PREFIX : <http://example/>
DATA { :x :p 1 ; :q 2 . }
RULE { ?x :bothPositive true . }
WHERE { ?x :p ?v1 FILTER ( ?v1 > 0 ) ?x :q ?v2 FILTER ( ?v2 > 0 ) }
RULE { ?x :oneIsZero true . }
WHERE { ?x :p ?v1 ; :q ?v2 FILTER ( ( ?v1 = 0 ) || ( ?v2 = 0 ) ) }
RDF Rules syntax:
PREFIX : <http://example/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX sh: <http://www.w3.org/ns/shacl#>
PREFIX shrl: <http://www.w3.org/ns/shacl-rules#>
PREFIX sparql: <http://www.w3.org/ns/sparql#>
:ruleSet-1
rdf:type shrl:RuleSet;
shrl:data (
<<( :x :p 1 )>>
<<( :x :q 2 )>>
);
shrl:ruleSet (
[
rdf:type shrl:Rule;
shrl:head (
[ shrl:subject [ shrl:var "x" ] ; shrl:predicate :bothPositive; shrl:object true ]
) ;
shrl:body (
[ shrl:subject [ shrl:var "x" ]; shrl:predicate :p; shrl:object [ shrl:var "v1" ] ]
[ shrl:expr [ sparql:greaterThan ( [ shrl:var "v1" ] 0 ) ] ]
[ shrl:subject [ shrl:var "x" ] ; shrl:predicate :q; shrl:object [ shrl:var "v2" ] ]
[ shrl:expr [ sparql:greaterThan ( [ shrl:var "v2" ] 0 ) ] ]
);
]
[
rdf:type shrl:Rule;
shrl:head (
[ shrl:subject [ shrl:var "x" ] ; shrl:predicate :oneIsZero ; shrl:object true ]
) ;
shrl:body (
[ shrl:subject [ shrl:var "x" ] ; shrl:predicate :p ; shrl:object [ shrl:var "v1" ] ]
[ shrl:subject [ shrl:var "x" ] ; shrl:predicate :q ; shrl:object [ shrl:var "v2" ] ]
[ shrl:expr [ sparql:function-or (
[ sparql:equals ( [ shrl:var "v1" ] 0 ) ]
[ sparql:equals ( [ shrl:var "v2" ] 0 ) ]
) ]
]
);
]
) .
The grammar is given below.
Mapping the AST to the abstract syntax.
Additional helpers (short-hand abbreviations):
These allow for well-known rule patterns and also specialised implementations in basic engines.
TRANSITIVE(uri)SYMMETRIC(uri)INVERSE(uri)At risk:
`TRANSITIVE` has both implementation and concise expression advantages. Implementation advantages for `SYMMETRIC` and `INVERSE` are not clear.
Vocabulary: shacl-rules.ttl.
Well-formedness:
Describe how the abstract model maps to triples.
Process : accumulators, bottom up/ Walk the structure.
All triples not in the syntax are ignored. No other "shrl:" predicates are allowed (??).
This section defines the outcome of evaluating a rule set on given data. It does not prescribe the algorithm as the method of implementation. An implementation can use any algorithm that generates the same outcome.
Inputs: data graph G, called the base graph, and a rule set RS. Output: an RDF graph GI of inferred triples
The inferred triples do not include triples present in the set of triples of the [=base graph=].
μ : V → T,
where V is the set of all variables
and T is the set of all [=RDF terms=].
The domain of μ is denoted
by dom(μ), and it is the subset
of V for which μ is defined. We use the term
[=solution=] where it is clear that a [=solution mapping=] is meant.
Write μ0 for the solution mapping such that
dom(μ0) is the empty set.
subst(μ, [=triple pattern=])
that returns a [=triple pattern=]
where each occurrence in the [=triple pattern=] of a variable that is in the
dom(μ)
is replaced by the [=RDF term=] given by the
[=solution mapping=] for var.
If the triple pattern result has no variables, then it is an [=RDF Triple=].
Let G be an [=RDF graph=] and TP be a triple pattern. The function `graphMatch(G, TP)` returns a set of all possible solutions that, when applied to the triple pattern, produce a triple that is in the [=evaluation graph=]
Let G be an [=RDF graph=] and TP be a triple pattern.
graphMatch(G, TP) = { μ | subst(μ, TP) is a triple in G }
Let S1 and S2 be solutions.
compatible(μ1, μ2) = true
if forall v in dom(μ1) intersection dom(μ2)
μ1(v) = μ2(v)
compatible(μ1, μ2) = false otherwise
merge(μ1, μ2) = { μ |
μ(v) = μ1(v) if v in dom(μ1)
μ(v) = μ2(v) otherwise }
merge(S1, S2) = { μ |
μ1 in S1, μ2 in S2
and compatible(μ1, μ2)
μ(v) = merge(μ1, μ2)
Say the domain is `dom(S1) ∪︀ dom(S2)`.
Say that two solutions that have no variables in common are compatible.
Sketch
@@ Reference SPARQL expression evaluation Expression Evaluation
@@ Reference SPARQL EBV Effective Boolean Value (EBV)
define evalFunction(F, μ):
Let [x/μ] be
if x is an RDF term, then [x/row] is x
if x is a variable, then [x/row] is μ(x)
## By well-formedness, it is an error if x is not in the row.
eval(F(expr1, expr2 ...), row) = F(eval(expr1, row), eval(expr2, row), ...)
eval(FF(expr1, expr2) , row) = ... things that are not functions like `IF`
let R be a well-formed rule.
let rule R = (H, B) where
H is the sequence of triple templates in the head
B is the sequence of triple patterns,
condition expressions, negation elements,
and assignments in the body
# Solution sequence of one solution that does not map any variables.
let SEQ0: Solution sequence = { μ0 }
let G = evaluation graph
# Evaluate rule body
# This function returns a sequence of solutions
define evalRuleElements(B, SEQ, G):
for each rule element rElt in B:
if rElt is a triple pattern TP:
X = graphMatch(G, TP)
SEQ1 = {}
for each μ1 in X:
for each μ2 in SEQ:
if compatible(μ1, μ2)
μ3 = merge(μ1, μ2)
add μ3 to SEQ1
endfor
endif
if rElt is a condition expression with expression F:
SEQ1 = {}
for each solution μ in SEQ:
if evalFunction(F, μ) is true:
add μ to SEQ1
endif
endfor
endif
if rElt is a negation expression with body elements N:
SEQ1 = {}
for each solution μ in SEQ:
S = sequence{ μ }
NEG = evalRuleElements(N, S, G)
if NEG is empty
add μ to SEQ1
endif
endfor
endif
if rElt is an assignment with variable V and expression expr
SEQ1 = {}
for each solution S in SEQ:
let x = eval(expr, S)
add(V, x) to S
add S to SEQ1
endfor
endif
if SEQ1 is empty
SEQ = {}
return SEQ
endif
SEQ = SEQ1
endfor
return SEQ
enddefine
let SEQ = evalRuleElements(B, SEQ0, G)
# Evaluate rule head
let H = empty set
for each μ in SEQ:
let S = {}
for each triple template TT in head
let triple = subst(μ, TT)
Add triple to S
H = H union S
endfor
result eval(R, G) is H
Note that `H` may contain triples that are also in the data graph.
Sketch
let G0 be the input base graph
let RS be the rule set
let D be the graph of all DATA triples in RS
Apply stratification to RS
let L be the sequence of layers after stratification
# Inference graph
let GI = { t ∈D | t ∉ in G0 }
# Evaluation graph.
let GE = G0 ∪︀ D
for each layer in L:
let finished = false
while !finished:
finished = true
for each rule in layer:
let X = eval(rule, GE)
let Y = { t ∈ X | t ∉ in GE }
if Y is not empty:
finished = false
GI = Y ∪︀ GI
GE = Y ∪︀ GE
endif
endfor
endwhile
endfor
the result is GI
[1] |
RuleSet |
::= | RuleOrDataBlock |
[2] |
RuleOrDataBlock |
::= | Prologue ( ( Rule | Data )+ ( Prologue1 ( Rule | Data )? )* )? |
[3] |
Prologue |
::= | Prologue1* |
[4] |
Prologue1 |
::= | BaseDecl | PrefixDecl | VersionDecl | ImportsDecl |
[5] |
BaseDecl |
::= | 'BASE' IRIREF |
[6] |
PrefixDecl |
::= | 'PREFIX' PNAME_NS IRIREF |
[7] |
VersionDecl |
::= | 'VERSION' VersionSpecifier |
[8] |
VersionSpecifier |
::= | STRING_LITERAL1 | STRING_LITERAL2 |
[9] |
ImportsDecl |
::= | 'IMPORTS' iri |
[10] |
Rule |
::= | Rule1 | Rule2 | Declaration |
[11] |
Rule1 |
::= | 'RULE' HeadTemplate 'WHERE' BodyPattern |
[12] |
Rule2 |
::= | 'IF' BodyPattern 'THEN' HeadTemplate |
[13] |
Declaration |
::= | ( 'TRANSITIVE' '(' iri ')' | 'SYMMETRIC' '(' iri ')' | 'INVERSE' '(' iri ',' iri ')' ) |
[14] |
Data |
::= | 'DATA' TriplesTemplateBlock |
[15] |
HeadTemplate |
::= | TriplesTemplateBlock |
[16] |
BodyPattern |
::= | '{' BodyPattern1 '}' |
[17] |
BodyPattern1 |
::= | BodyTriplesBlock? ( BodyNotTriples BodyTriplesBlock? )* |
[18] |
BodyNotTriples |
::= | Filter | Negation | Assignment |
[19] |
BodyTriplesBlock |
::= | TriplesBlock |
[20] |
Negation |
::= | 'NOT' '{' BodyBasic '}' |
[21] |
BodyBasic |
::= | BodyTriplesBlock? ( Filter BodyTriplesBlock? )* |
[22] |
TriplesTemplateBlock |
::= | '{' TriplesTemplate? '}' |
[23] |
TriplesTemplate |
::= | TriplesSameSubject ( '.' TriplesTemplate? )? |
[24] |
TriplesBlock |
::= | TriplesSameSubjectPath ( '.' TriplesBlock? )? |
[25] |
ReifiedTripleBlock |
::= | ReifiedTriple PropertyList |
[26] |
ReifiedTripleBlockPath |
::= | ReifiedTriple PropertyListPath |
[27] |
Assignment |
::= | 'BIND' '(' Expression 'AS' Var ')' |
[28] |
Reifier |
::= | '~' VarOrReifierId? |
[29] |
VarOrReifierId |
::= | Var | iri | BlankNode |
[30] |
Filter |
::= | 'FILTER' Constraint |
[31] |
Constraint |
::= | BrackettedExpression | BuiltInCall | FunctionCall |
[32] |
FunctionCall |
::= | iri ArgList |
[33] |
ArgList |
::= | NIL | '(' Expression ( ',' Expression )* ')' |
[34] |
ExpressionList |
::= | NIL | '(' Expression ( ',' Expression )* ')' |
[35] |
TriplesSameSubject |
::= | VarOrTerm PropertyListNotEmpty | TriplesNode PropertyList | ReifiedTripleBlock |
[36] |
PropertyList |
::= | PropertyListNotEmpty? |
[37] |
PropertyListNotEmpty |
::= | Verb ObjectList ( ';' ( Verb ObjectList )? )* |
[38] |
Verb |
::= | VarOrIri | 'a' |
[39] |
ObjectList |
::= | Object ( ',' Object )* |
[40] |
Object |
::= | GraphNode Annotation |
[41] |
TriplesSameSubjectPath |
::= | VarOrTerm PropertyListPathNotEmpty | TriplesNodePath PropertyListPath | ReifiedTripleBlockPath |
[42] |
PropertyListPath |
::= | PropertyListPathNotEmpty? |
[43] |
PropertyListPathNotEmpty |
::= | ( VerbPath | VerbSimple ) ObjectListPath ( ';' ( ( VerbPath | VerbSimple ) ObjectListPath )? )* |
[44] |
VerbPath |
::= | Path |
[45] |
VerbSimple |
::= | Var |
[46] |
ObjectListPath |
::= | ObjectPath ( ',' ObjectPath )* |
[47] |
ObjectPath |
::= | GraphNodePath AnnotationPath |
[48] |
Path |
::= | PathSequence |
[49] |
PathSequence |
::= | PathEltOrInverse ( '/' PathEltOrInverse )* |
[50] |
PathEltOrInverse |
::= | PathElt | '^' PathElt |
[51] |
PathElt |
::= | PathPrimary |
[52] |
PathPrimary |
::= | iri | 'a' | '(' Path ')' |
[53] |
TriplesNode |
::= | Collection | BlankNodePropertyList |
[54] |
BlankNodePropertyList |
::= | '[' PropertyListNotEmpty ']' |
[55] |
TriplesNodePath |
::= | CollectionPath | BlankNodePropertyListPath |
[56] |
BlankNodePropertyListPath |
::= | '[' PropertyListPathNotEmpty ']' |
[57] |
Collection |
::= | '(' GraphNode+ ')' |
[58] |
CollectionPath |
::= | '(' GraphNodePath+ ')' |
[59] |
AnnotationPath |
::= | ( Reifier | AnnotationBlockPath )* |
[60] |
AnnotationBlockPath |
::= | '{|' PropertyListPathNotEmpty '|}' |
[61] |
Annotation |
::= | ( Reifier | AnnotationBlock )* |
[62] |
AnnotationBlock |
::= | '{|' PropertyListNotEmpty '|}' |
[63] |
GraphNode |
::= | VarOrTerm | TriplesNode | ReifiedTriple |
[64] |
GraphNodePath |
::= | VarOrTerm | TriplesNodePath | ReifiedTriple |
[65] |
VarOrTerm |
::= | Var | iri | RDFLiteral | NumericLiteral | BooleanLiteral | BlankNode | NIL | TripleTerm |
[66] |
ReifiedTriple |
::= | '<<' ReifiedTripleSubject Verb ReifiedTripleObject Reifier? '>>' |
[67] |
ReifiedTripleSubject |
::= | Var | iri | RDFLiteral | NumericLiteral | BooleanLiteral | BlankNode | ReifiedTriple |
[68] |
ReifiedTripleObject |
::= | Var | iri | RDFLiteral | NumericLiteral | BooleanLiteral | BlankNode | ReifiedTriple | TripleTerm |
[69] |
TripleTerm |
::= | '<<(' TripleTermSubject Verb TripleTermObject ')>>' |
[70] |
TripleTermSubject |
::= | Var | iri | RDFLiteral | NumericLiteral | BooleanLiteral | BlankNode |
[71] |
TripleTermObject |
::= | Var | iri | RDFLiteral | NumericLiteral | BooleanLiteral | BlankNode | TripleTerm |
[72] |
TripleTermData |
::= | '<<(' TripleTermDataSubject ( iri | 'a' ) TripleTermDataObject ')>>' |
[73] |
TripleTermDataSubject |
::= | iri | RDFLiteral | NumericLiteral | BooleanLiteral |
[74] |
TripleTermDataObject |
::= | iri | RDFLiteral | NumericLiteral | BooleanLiteral | TripleTermData |
[75] |
VarOrIri |
::= | Var | iri |
[76] |
Var |
::= | VAR1 | VAR2 |
[77] |
Expression |
::= | ConditionalOrExpression |
[78] |
ConditionalOrExpression |
::= | ConditionalAndExpression ( '||' ConditionalAndExpression )* |
[79] |
ConditionalAndExpression |
::= | ValueLogical ( '&&' ValueLogical )* |
[80] |
ValueLogical |
::= | RelationalExpression |
[81] |
RelationalExpression |
::= | NumericExpression ( '=' NumericExpression | '!=' NumericExpression | '<' NumericExpression | '>' NumericExpression | '<=' NumericExpression | '>=' NumericExpression | 'IN' ExpressionList | 'NOT' 'IN' ExpressionList )? |
[82] |
NumericExpression |
::= | AdditiveExpression |
[83] |
AdditiveExpression |
::= | MultiplicativeExpression ( '+' MultiplicativeExpression | '-' MultiplicativeExpression | ( NumericLiteralPositive | NumericLiteralNegative ) ( ( '*' UnaryExpression ) | ( '/' UnaryExpression ) )* )* |
[84] |
MultiplicativeExpression |
::= | UnaryExpression ( '*' UnaryExpression | '/' UnaryExpression )* |
[85] |
UnaryExpression |
::= | '!' PrimaryExpression |
[86] |
PrimaryExpression |
::= | BrackettedExpression | BuiltInCall | iriOrFunction | RDFLiteral | NumericLiteral | BooleanLiteral | Var | ExprTripleTerm |
[87] |
ExprTripleTerm |
::= | '<<(' ExprTripleTermSubject Verb ExprTripleTermObject ')>>' |
[88] |
ExprTripleTermSubject |
::= | iri | RDFLiteral | NumericLiteral | BooleanLiteral | Var |
[89] |
ExprTripleTermObject |
::= | iri | RDFLiteral | NumericLiteral | BooleanLiteral | Var | ExprTripleTerm |
[90] |
BrackettedExpression |
::= | '(' Expression ')' |
[91] |
BuiltInCall |
::= | 'STR' '(' Expression ')' |
[92] |
iriOrFunction |
::= | iri ArgList? |
[93] |
RDFLiteral |
::= | String ( LANG_DIR | '^^' iri )? |
[94] |
NumericLiteral |
::= | NumericLiteralUnsigned | NumericLiteralPositive | NumericLiteralNegative |
[95] |
NumericLiteralUnsigned |
::= | INTEGER | DECIMAL | DOUBLE |
[96] |
NumericLiteralPositive |
::= | INTEGER_POSITIVE | DECIMAL_POSITIVE | DOUBLE_POSITIVE |
[97] |
NumericLiteralNegative |
::= | INTEGER_NEGATIVE | DECIMAL_NEGATIVE | DOUBLE_NEGATIVE |
[98] |
BooleanLiteral |
::= | 'true' | 'false' |
[99] |
String |
::= | STRING_LITERAL1 | STRING_LITERAL2 | STRING_LITERAL_LONG1 | STRING_LITERAL_LONG2 |
[100] |
iri |
::= | IRIREF | PrefixedName |
[101] |
PrefixedName |
::= | PNAME_LN | PNAME_NS |
[102] |
BlankNode |
::= | BLANK_NODE_LABEL | ANON |
Productions for terminals:
[103] |
IRIREF |
::= | '<' ([^<>"{}|^`\]-[#x00-#x20])* '>' |
[104] |
PNAME_NS |
::= | PN_PREFIX? ':' |
[105] |
PNAME_LN |
::= | PNAME_NS PN_LOCAL |
[106] |
BLANK_NODE_LABEL |
::= | '_:' ( PN_CHARS_U | [0-9] ) ((PN_CHARS|'.')* PN_CHARS)? |
[107] |
VAR1 |
::= | '?' VARNAME |
[108] |
VAR2 |
::= | '$' VARNAME |
[109] |
LANG_DIR |
::= | '@' [a-zA-Z]+ ('-' [a-zA-Z0-9]+)* ('--' [a-zA-Z]+)? |
[110] |
INTEGER |
::= | [0-9]+ |
[111] |
DECIMAL |
::= | [0-9]* '.' [0-9]+ |
[112] |
DOUBLE |
::= | ( ([0-9]+ ('.'[0-9]*)? ) | ( '.' ([0-9])+ ) ) [eE][+-]?[0-9]+ |
[113] |
INTEGER_POSITIVE |
::= | '+' INTEGER |
[114] |
DECIMAL_POSITIVE |
::= | '+' DECIMAL |
[115] |
DOUBLE_POSITIVE |
::= | '+' DOUBLE |
[116] |
INTEGER_NEGATIVE |
::= | '-' INTEGER |
[117] |
DECIMAL_NEGATIVE |
::= | '-' DECIMAL |
[118] |
DOUBLE_NEGATIVE |
::= | '-' DOUBLE |
[119] |
STRING_LITERAL1 |
::= | "'" ( ([^#x27#x5C#xA#xD]) | ECHAR )* "'" |
[120] |
STRING_LITERAL2 |
::= | '"' ( ([^#x22#x5C#xA#xD]) | ECHAR )* '"' |
[121] |
STRING_LITERAL_LONG1 |
::= | "'''" ( ( "'" | "''" )? ( [^'\] | ECHAR ) )* "'''" |
[122] |
STRING_LITERAL_LONG2 |
::= | '"""' ( ( '"' | '""' )? ( [^"\] | ECHAR ) )* '"""' |
[123] |
ECHAR |
::= | '\' [tbnrf\"'] |
[124] |
NIL |
::= | '(' WS* ')' |
[125] |
WS |
::= | #x20 | #x9 | #xD | #xA |
[126] |
ANON |
::= | '[' WS* ']' |
[127] |
PN_CHARS_BASE |
::= | [A-Z] | [a-z] | [#x00C0-#x00D6] | [#x00D8-#x00F6] | [#x00F8-#x02FF] | [#x0370-#x037D] | [#x037F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] | [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF] |
[128] |
PN_CHARS_U |
::= | PN_CHARS_BASE | '_' |
[129] |
VARNAME |
::= | ( PN_CHARS_U | [0-9] ) ( PN_CHARS_U | [0-9] | #x00B7 | [#x0300-#x036F] | [#x203F-#x2040] )* |
[130] |
PN_CHARS |
::= | PN_CHARS_U | '-' | [0-9] | #x00B7 | [#x0300-#x036F] | [#x203F-#x2040] |
[131] |
PN_PREFIX |
::= | PN_CHARS_BASE ((PN_CHARS|'.')* PN_CHARS)? |
[132] |
PN_LOCAL |
::= | (PN_CHARS_U | ':' | [0-9] | PLX ) ((PN_CHARS | '.' | ':' | PLX)* (PN_CHARS | ':' | PLX) )? |
[133] |
PLX |
::= | PERCENT | PN_LOCAL_ESC |
[134] |
PERCENT |
::= | '%' HEX HEX |
[135] |
HEX |
::= | [0-9] | [A-F] | [a-f] |
[136] |
PN_LOCAL_ESC |
::= | '\' ( '_' | '~' | '.' | '-' | '!' | '$' | '&' | "'" | '(' | ')' | '*' | '+' | ',' | ';' | '=' | '/' | '?' | '#' | '@' | '%' ) |
@@see the Turtle registration for format
The Internet Media Type (formerly known as MIME Type) for @@ is "text/shape-rules".
The information that follows has been submitted to the Internet Engineering Steering Group (IESG) for review, approval, and registration with IANA.
TODO
TODO
TODO
Many people contributed to this document, including members of the RDF Data Shapes Working Group.