on lists

Lists are used in several places in SHACL but there is no definition of
what constitutes an acceptable list or an acceptable well-formed list or
what is a list member or what is list containment.  This is yet another
example of loose terminology.


Peter F. Patel-Schneider
Nuance Communications



"2. If the graph contains a triple of the form p rdf:first elt, the path must
be a well-formed RDF list with a at least two members. Each member must be
valid SHACL property path that is converted into a sequence of either
SequencePath or AlternativePath elements.
3. If the graph contains a triple of the form p sh:alternativePath elt, the
value of path must be a well-formed RDF list with a at least two
members. All members must be valid SHACL property paths that become a series
of AlternativePath elements."

"Property  Value Type  Summary
sh:languageIn  rdf:List  A list of language ranges (list members are xsd:string)"

"Property  Value Type  Summary
sh:and  rdf:List (members: sh:Shape)  List of shapes to validate the value
nodes against"

"Property  Value Type  Summary
sh:or  rdf:List (members: sh:Shape)  List of shapes to validate the value
nodes against"

"The value of the sh:partition constraint parameter MUST be an rdf:List that
contains zero or more resources."

"Each member of the list is used by the SHACL processor to match a subset of
the value nodes. "

"Property  Value Type  Summary
sh:closed  xsd:boolean  Set to true to close the shape
sh:ignoredProperties  rdf:List (members: rdf:Property)  Optional
list of properties that are also permitted in addition to those explicitly
enumerated via sh:property "

"Property  Value Type  Summary
sh:in  rdf:List  Enumeration of allowed values"

"The values of sh:in must be well-formed rdf:Lists. The members of that
rdf:List must not be blank nodes. A validation result must be produced for
every value node that is not a member of the given list. "

Received on Friday, 14 October 2016 01:47:26 UTC