ISSUE-210: value types and expected types

Expected type

value types and expected types

Raised by:
Karen Coyle
Opened on:
Peter's email:

"The value type, i.e., expected type, of sh:minCount is xsd:integer. The
definition of expected type is:

"Expected Type
In a shapes graph, the values of a property or a property path can have an
expected type. These nodes are treated as instances of specific classes,
even when these nodes are not SHACL instances of these classes. For example,
the objects of triples with sh:shape as predicate have sh:Shape as expected
type and there does not need to be a triple with the object node as the
subject, rdf:type as predicate and sh:Shape as object in the shapes graph."

This means any node can be the object of sh:minCount in a constraint so that

s:s1 rdf:type sh:Shape ;
sh:property [ sh:predicate ex:child ;
sh:minCount ex:John ] .

is a valid shape.

All constraint parameters with a value type that is a datatype have similar
Related Actions Items:
No related actions
Related emails:
  1. Re: shapes-ISSUE-210 (Expected type): value types and expected types [SHACL Spec] (from on 2016-11-22)
  2. shapes-ISSUE-210 (Expected type): value types and expected types [SHACL Spec] (from on 2016-11-20)

Related notes:

RESOLUTION: Close ISSUE-210, as addressed in the latest editor's draft, where the definitions of expected types have been updated and explicitly exclude the troublesome values

Arnaud Le Hors, 2 Dec 2016, 15:38:17

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 210.html,v 1.1 2018/11/26 09:03:35 carine Exp $