ISSUE-211: Eliminate property constraints

property constraints

Eliminate property constraints

State:
CLOSED
Product:
SHACL Spec
Raised by:
Karen Coyle
Opened on:
2016-11-20
Description:
Peter's email: https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0018.html

Begins: "SHACL currently has shapes, constraints, constraint components, parameters,
and the special property sh:property. This leads to a complex formalism
that the SHACL document continues to struggle to adequately describe.

This complexity is not necessary. Both shapes and constraints can be merged
into a single notion of shapes. The special property sh:property can be
turned into the single parameter of a new constraint component."

Follow-up email with two proposals
https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0053.html
Related Actions Items:
No related actions
Related emails:
  1. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-02-01)
  2. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-01-26)
  3. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from holger@topquadrant.com on 2017-01-26)
  4. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-01-26)
  5. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from holger@topquadrant.com on 2017-01-26)
  6. shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from sysbot+tracker@w3.org on 2017-01-25)
  7. ISSUE-170: EXISTS removed (from holger@topquadrant.com on 2017-01-12)
  8. Proposed next steps (was: Re: core remaining issues) (from kontokostas@informatik.uni-leipzig.de on 2017-01-09)
  9. Re: core remaining issues (from holger@topquadrant.com on 2017-01-08)
  10. Re: core remaining issues (from kontokostas@informatik.uni-leipzig.de on 2017-01-06)
  11. Re: Process Question: How to clean up meeting minutes (from eric@w3.org on 2017-01-06)
  12. Re: core remaining issues (from irene@topquadrant.com on 2017-01-06)
  13. core remaining issues (from kontokostas@informatik.uni-leipzig.de on 2017-01-06)
  14. Re: Process Question: How to clean up meeting minutes (from holger@topquadrant.com on 2017-01-06)
  15. Re: WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-04)
  16. Re: WG Meeting 2017-01-04 (from bart_van_leeuwen@netage.nl on 2017-01-03)
  17. Re: WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-03)
  18. Re: WG Meeting 2017-01-04 (from pano.maria@gmail.com on 2017-01-02)
  19. WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-02)
  20. Re: ISSUE-211: Should we turn sh:property and sh:sparql into constraint components? (from holger@topquadrant.com on 2016-12-17)
  21. ISSUE-211: Should we turn sh:property and sh:sparql into constraint components? (from holger@topquadrant.com on 2016-12-16)
  22. Re: Please vote on ISSUE-211 (from holger@topquadrant.com on 2016-12-13)
  23. Re: Please vote on ISSUE-211 (from irene@topquadrant.com on 2016-12-12)
  24. Re: Please vote on ISSUE-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-12)
  25. Re: Please vote on ISSUE-211 (from irene@topquadrant.com on 2016-12-12)
  26. Re: Please vote on ISSUE-211 (from kcoyle@kcoyle.net on 2016-12-12)
  27. Re: Please vote on ISSUE-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-12)
  28. Re: Please vote on ISSUE-211 (from kcoyle@kcoyle.net on 2016-12-12)
  29. Please vote on ISSUE-211 (from lehors@us.ibm.com on 2016-12-12)
  30. Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-09)
  31. Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-09)
  32. Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-09)
  33. Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-08)
  34. Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-08)
  35. Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-08)
  36. Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-08)
  37. Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
  38. Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
  39. Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
  40. Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
  41. Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-07)
  42. Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
  43. Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-07)
  44. proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
  45. Re: shapes-ISSUE-211 (property constraints): Eliminate property constraints [SHACL Spec] (from holger@topquadrant.com on 2016-11-22)
  46. shapes-ISSUE-211 (property constraints): Eliminate property constraints [SHACL Spec] (from sysbot+tracker@w3.org on 2016-11-20)

Related notes:

RESOLUTION: Close ISSUE-211 as already discussed (extensively) and too late for such a fundamental change, see https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Nov/0117.html
See https://www.w3.org/2016/12/14-shapes-minutes.html#resolution03

Arnaud Le Hors, 15 Dec 2016, 19:06:04

RESOLUTION: close issue-211 as essentially solved, with Dimitris putting remaining fragmentary concern in a fresh issue (220)

https://www.w3.org/2017/01/25-shapes-minutes.html

Irene Polikoff, 9 Feb 2017, 23:56:39

Display change log ATOM feed


Chair, Eric Prud'hommeaux <eric@w3.org>, 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: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $