- From: Holger Knublauch <holger@topquadrant.com>
- Date: Mon, 19 Oct 2015 10:00:50 +1000
- To: public-data-shapes-wg@w3.org
On 10/18/2015 11:23, Karen Coyle wrote:
> Thanks, Holger. The difference wasn't clear to me in the spec. For
> now, the definitions are:
>
> sh:hasValue: The property sh:hasValue can be used to verify that the
> focus node has a given RDF node among the values of the given predicate.
>
> sh:allowedValues: The property sh:allowedValues can be used to
> enumerate the values a property can have. When specified, the value of
> the given property must be members of the specified set.
>
> With some hindsight I see the meanings, but I must say it possibly
> could be clearer. Also "value... must be members... set" has some
> mixing of singular and plural that makes it harder to understand. Is
> there some reason why we can't say what you say below? (Maybe Arthur
> could add this to his edits?)
Thanks for pointing this out. Changed to
The property <code>sh:in</code> can be used to exclusively
enumerate the values a property can have.
When specified, all values of the given property must be members of
the specified set.
In general, there is a trade-off between tutorial-style writing and
compactness of a spec. So yes, many things could be explained much more
thoroughly, but whether this document here is the right place is another
question.
Holger
Received on Monday, 19 October 2015 00:01:27 UTC