ISSUE-40: sh:min/max constrains properties, not values
Property Cardinality
sh:min/max constrains properties, not values
- State:
- CLOSED
- Product:
- Raised by:
- Karen Coyle
- Opened on:
- 2015-04-05
- Description:
- The spec at https://w3c.github.io/data-shapes/shacl/ currently reads:
"The properties sh:minCount and sh:maxCount restrict the number of values of the given property at the focus node."
It should read:
"The properties sh:minCount and sh:maxCount restrict the cardinality of properties of the focus node."
The cardinality of the value of a triple is always min=1 max=1. It is the cardinality of the properties in the node that can be constrained, e.g.
sh:property [
sh:predicate foaf:name ;
sh:minCount 1 ;
sh:maxCount 1 ]
- Related Actions Items:
- No related actions
- Related emails:
- Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from kcoyle@kcoyle.net on 2015-04-07)
- Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from holger@topquadrant.com on 2015-04-07)
- Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from holger@topquadrant.com on 2015-04-07)
- Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from kcoyle@kcoyle.net on 2015-04-06)
- Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from kcoyle@kcoyle.net on 2015-04-06)
- shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values (from sysbot+tracker@w3.org on 2015-04-05)
Related notes:
No additional notes.
Display change log