- From: Holger Knublauch <holger@topquadrant.com>
- Date: Fri, 30 Oct 2015 15:22:23 +1000
- To: public-data-shapes-wg@w3.org
One way of resolving this would be to drop sh:annotationVarName and rely on sh:annotationProperty only, using the same NCName mechanism as used elsewhere. This would slightly limit the use cases, because variable and property names would have to be always aligned. I have no strong opinion, and this feature was mainly driven by Dimitris, so I would like him to make a proposal. Holger On 10/30/2015 6:51, Arthur Ryman wrote: > +1 > > Also, the definition of the local name of results in an NCName. This > is safe as a SPARQL variable. I assume it is safe enough for > Javascript. > > -- Arthur > > On Wed, Oct 28, 2015 at 10:58 PM, RDF Data Shapes Working Group Issue > Tracker <sysbot+tracker@w3.org> wrote: >> shapes-ISSUE-107 (annotations v. arguments): annotations and arguments use different mechanisms for specifying the SPARQL variable name [SHACL Spec] >> >> http://www.w3.org/2014/data-shapes/track/issues/107 >> >> Raised by: Peter Patel-Schneider >> On product: SHACL Spec >> >> Annotation properties use sh:annotationVarName to provide the SPARQL variable name to use. Arguments use the local part of their IRI. It would be better to have one mechanism. >> >> >>
Received on Friday, 30 October 2015 05:23:00 UTC