Re: shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values

I have attempted to clarify this via

https://github.com/w3c/data-shapes/commit/1ffa8cd3225d2cc340ae3883abd5411913d7a7d4

Please let me know if this helps. I had started to use the term "value" 
because I thought that "object" is less clear to newcomers who are not 
too familiar with RDF technology. Yet for a formal spec, using the term 
"object" may indeed be less objectionable.

Holger


On 4/6/2015 2:08, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-40 (Property Cardinality): sh:min/max constrains properties, not values
>
> http://www.w3.org/2014/data-shapes/track/issues/40
>
> Raised by: Karen Coyle
> On product:
>
> 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 .
>
>
>
>
>

Received on Tuesday, 7 April 2015 02:01:50 UTC