W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > May 2016

Re: Simplification of scopes section (see also ISSUE-148)

From: Holger Knublauch <holger@topquadrant.com>
Date: Sun, 15 May 2016 10:59:09 +1000
To: public-data-shapes-wg@w3.org
Message-ID: <65e1539c-b0cd-20b1-14a5-26cd1a63e52c@topquadrant.com>

On 14/05/2016 22:07, Dimitris Kontokostas wrote:
> Another gap that sh:AllSubjectsScope came to fill is sh:scopeClass 
> rdfs:Resource that was available in very early versions of SHACL
> In general this scope gives shacl core the flexibility to define 
> complex focus nodes using all subjects + filters that will not be easy 
> otherwise
> so I would be keen on keeping this in core

Do you have a specific example? For the general mechanism, there are 
various syntaxes using the extension mechanism. We need to decide 
whether a use case is common enough to warrant its inclusion into the 
Core. Things in the Core have the special status that every tool must 
support them. But this also comes with a cost. I can certainly see that 
property scopes are common, and the tools that I would build around this 
would have special hard-coded treatment of sh:scopeProperty, e.g. in 
form building. I cannot tell that I would want to do the same for 
something like AllSubjects unless there are compelling use cases. And: 
why stop at AllSubjects/AllObjects. Why not AllPredicates, AllNodes. But 
just because we can define all these cases in the core, doesn't mean we 
should. Some things are sufficiently well left to extensions.

Received on Sunday, 15 May 2016 00:59:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:33 UTC