- From: Holger Knublauch <holger@topquadrant.com>
- Date: Sat, 16 Apr 2016 08:23:47 +1000
- To: public-data-shapes-wg@w3.org
Hi Peter, the reason for the chosen syntax is that it aligns with the extension mechanism, i.e. sh:PropertyScope is used in the same syntax that any future extension would be written too (and only one implementation needs to be created). I cannot tell whether property scopes are common enough to have their own (hard-coded) syntax. So far it seems that sh:scopeClass is by far the most common use case, but I welcome discussion on this. Holger On 15/04/2016 23:18, RDF Data Shapes Working Group Issue Tracker wrote: > shapes-ISSUE-148 (scope syntax): non-uniform syntax in scopes [SHACL - Core] > > http://www.w3.org/2014/data-shapes/track/issues/148 > > Raised by: Peter Patel-Schneider > On product: SHACL - Core > > The syntax for SHACL scopes is non-uniform. > > For class scopes the syntax is > ex:s1 a sh:Shape ; > sh:scopeClass ex:Person . > For property subject scopes the syntax is > ex:s2 a sh:Shape ; > sh:scope [ > a sh:PropertyScope ; > sh:predicate ex:knows ; > ] . > The difference does not seem to serve any purpose and property subject scopes could be written instead as > ex:s2 a sh:Shape ; > sh:propertyScope ex:knows . > > > > >
Received on Friday, 15 April 2016 22:24:23 UTC