- From: Holger Knublauch <holger@topquadrant.com>
- Date: Mon, 17 Oct 2016 15:25:40 +1000
- To: public-data-shapes-wg@w3.org
On 2/10/2016 22:54, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-184 (paths & value nodes): Property paths and value nodes [SHACL - Core]
>
> http://www.w3.org/2014/data-shapes/track/issues/184
>
> Raised by: Dimitris Kontokostas
> On product: SHACL - Core
>
> While addressing some public comments the SHACL editors made some edits in the spec that should have been approved by the WG.
> One of these cases is the effort to address the comment on the "divergence of sh:minCount"
> https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Sep/0045.html
>
> The previous behaviour was approved by the WG with this resolution
> https://www.w3.org/2016/06/30-shapes-minutes.html#resolution04
>
> The commenter was correct to note that the approved by the WG solution was not consistent with the rest of SHACL that works on RDF nodes and not values
>
> Proposal: on property constraints with sh:path the value nodes are a set with no duplicate value nodes.
I second this proposal and had made corresponding edits to various
places in the spec, switching to SELECT DISTINCT. I also just clarified
the terminology's sentence by adding the word "distinct" to:
The values of a property path <code>path</code>
for a given node <code>s</code> are the distinct bindings produced by a
SPARQL processor for the variable <code>o</code> from a
<a
href="https://www.w3.org/TR/sparql11-query/#rTriplesBlock"><code>TriplesBlock</code></a>
of the form <code>s path ?o</code>.
Holger
Received on Monday, 17 October 2016 05:26:13 UTC