ISSUE-148: non-uniform syntax in scopes

scope syntax

non-uniform syntax in scopes

State:
CLOSED
Product:
SHACL - Core
Raised by:
Peter Patel-Schneider
Opened on:
2016-04-15
Description:
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 .

Related Actions Items:
No related actions
Related emails:
  1. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-20)
  2. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-20)
  3. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-19)
  4. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-19)
  5. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-19)
  6. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-19)
  7. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-19)
  8. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-19)
  9. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-18)
  10. Re: Shall we redo the 1.3 example (was: Simplification of scopes section (see also ISSUE-148)) (from irene@topquadrant.com on 2016-05-16)
  11. Shall we redo the 1.3 example (was: Simplification of scopes section (see also ISSUE-148)) (from holger@topquadrant.com on 2016-05-16)
  12. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-16)
  13. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-16)
  14. Re: Simplification of scopes section (see also ISSUE-148) (from irene@topquadrant.com on 2016-05-15)
  15. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-15)
  16. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-15)
  17. Re: Simplification of scopes section (see also ISSUE-148) (from irene@topquadrant.com on 2016-05-15)
  18. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-15)
  19. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-15)
  20. Re: Simplification of scopes section (see also ISSUE-148) (from irene@topquadrant.com on 2016-05-15)
  21. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-15)
  22. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-15)
  23. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-15)
  24. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-15)
  25. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-15)
  26. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-15)
  27. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-15)
  28. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-14)
  29. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-14)
  30. Re: Simplification of scopes section (see also ISSUE-148) (from irene@topquadrant.com on 2016-05-14)
  31. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-14)
  32. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-14)
  33. Re: Simplification of scopes section (see also ISSUE-148) (from irene@topquadrant.com on 2016-05-14)
  34. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-14)
  35. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-14)
  36. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-14)
  37. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-13)
  38. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-13)
  39. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-13)
  40. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-13)
  41. Re: Simplification of scopes section (see also ISSUE-148) (from pfpschneider@gmail.com on 2016-05-13)
  42. Re: Simplification of scopes section (see also ISSUE-148) (from kontokostas@informatik.uni-leipzig.de on 2016-05-13)
  43. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-13)
  44. Re: Simplification of scopes section (see also ISSUE-148) (from holger@topquadrant.com on 2016-05-13)
  45. Re: Simplification of scopes section (see also ISSUE-148) (from kcoyle@kcoyle.net on 2016-05-12)
  46. Re: shapes-ISSUE-148 (scope syntax): non-uniform syntax in scopes [SHACL - Core] (from holger@topquadrant.com on 2016-04-16)
  47. shapes-ISSUE-148 (scope syntax): non-uniform syntax in scopes [SHACL - Core] (from sysbot+tracker@w3.org on 2016-04-15)

Related notes:

RESOLUTION: For propertyScope and inverse property scopes, do not use sh:scope but the dedicated properties sh:scopeProperty and sh:scopeInverseProperty that point to a property directly. e.g. ex:shape sh:propertyScope ex:myPredicate
See: https://www.w3.org/2016/05/26-shapes-minutes.html#resolution08

RESOLUTION: Delete AllObjectsScope and AllSubjectsScope from Core, not to become Advanced. Anyone who wants this functionality is left to write their own SPARQL.
See http://www.w3.org/2016/06/02-shapes-minutes.html#resolution02

RESOLUTION: Close ISSUE-148, resolved given previous resolutions
See http://www.w3.org/2016/06/02-shapes-minutes.html#resolution03

Arnaud Le Hors, 3 Jun 2016, 03:41:42

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 148.html,v 1.1 2018/11/26 09:03:30 carine Exp $