- From: Dimitris Kontokostas <kontokostas@informatik.uni-leipzig.de>
- Date: Thu, 14 Apr 2016 13:44:55 +0300
- To: Holger Knublauch <holger@topquadrant.com>
- Cc: public-data-shapes-wg <public-data-shapes-wg@w3.org>
- Message-ID: <CA+u4+a2wSz_sGZzyQpAfQ7cNt+VkDyMO+R2ovUH542d8aMq=2w@mail.gmail.com>
I propose we close this issue with the updated spec I removed the sentence "In the following SPARQL query, the variable $predicate is assumed to be substituted with the given value of sh:predicate." completely this is implied from the SHACL/SPARQL section Dimitris On Sun, Apr 10, 2016 at 5:39 AM, Holger Knublauch <holger@topquadrant.com> wrote: > I don't understand this ISSUE. In the sh:PropertyScope case you mention, > either substitution or pre-binding would have exactly the same effect. I > see no need to complicate this further with another forward reference to > pre-binding. > > Holger > > > > On 9/04/2016 4:13, RDF Data Shapes Working Group Issue Tracker wrote: > >> shapes-ISSUE-144 (substitution): substition is sometimes used instead of >> pre-binding [SHACL Spec] >> >> http://www.w3.org/2014/data-shapes/track/issues/144 >> >> Raised by: Peter Patel-Schneider >> On product: SHACL Spec >> >> The current document uses substitution in some places where it appears >> that pre-binding is meant. >> >> For example, >> >> 2.1.3.1 Property scopes (sh:PropertyScope) >> >> The scope class sh:PropertyScope selects all subjects that have at least >> one value for a given property sh:predicate. In the following SPARQL query, >> the variable $predicate is assumed to be substituted with the given value >> of sh:predicate. >> >> >> >> > > -- Dimitris Kontokostas Department of Computer Science, University of Leipzig & DBpedia Association Projects: http://dbpedia.org, http://rdfunit.aksw.org, http:// http://aligned-project.eu Homepage:http://aksw.org/DimitrisKontokostas Research Group: AKSW/KILT http://aksw.org/Groups/KILT
Received on Thursday, 14 April 2016 10:45:49 UTC