ISSUE-139: Can all constraint properties be applied in all scenarios?

Universal applicability

Can all constraint properties be applied in all scenarios?

State:
CLOSED
Product:
SHACL - Core
Raised by:
Holger Knublauch
Opened on:
2016-03-18
Description:
Proposal 4 claims that all property constraints (such as sh:minCount, sh:class, sh:minInclusive) can be applied in all contexts, i.e. with sh:constraint, sh:property and sh:inverseProperty (or even with arbitrary paths).

I believe this makes no sense, e.g. sh:minCount does not make sense at Shape-level (only for sh:property/sh:inverseProperty), and sh:minInclusive does not make sense for sh:inverseProperty. Even worse, the property pair constraints such as sh:equals only work on sh:property, definitely not for node constraints.
Related Actions Items:
No related actions
Related emails:
  1. ISSUE-139: Some parameters now lead to ill-formed node shapes (from holger@topquadrant.com on 2017-02-09)
  2. Re: declaring (practically) insensible shapes to be ill-formed (from simon.steyskal@wu.ac.at on 2017-02-08)
  3. Re: declaring (practically) insensible shapes to be ill-formed (from holger@topquadrant.com on 2017-02-08)
  4. declaring (practically) insensible shapes to be ill-formed (from irene@topquadrant.com on 2017-02-07)
  5. Re: ISSUE-133: Wiki page with syntax examples (from kontokostas@informatik.uni-leipzig.de on 2016-07-19)
  6. Re: ISSUE-133: Wiki page with syntax examples (from holger@topquadrant.com on 2016-07-19)
  7. Re: ISSUE-133: Wiki page with syntax examples (from kontokostas@informatik.uni-leipzig.de on 2016-07-19)
  8. Re: ISSUE-133: Wiki page with syntax examples (from holger@topquadrant.com on 2016-07-19)
  9. Re: ISSUE-133: Wiki page with syntax examples (from kontokostas@informatik.uni-leipzig.de on 2016-07-18)
  10. Re: ISSUE-139: Compromise (from kontokostas@informatik.uni-leipzig.de on 2016-07-18)
  11. ISSUE-139: Compromise (from holger@topquadrant.com on 2016-07-18)
  12. Re: List of open SHACL Core Syntax ISSUEs (from holger@topquadrant.com on 2016-07-14)
  13. Re: List of open SHACL Core Syntax ISSUEs (from kontokostas@informatik.uni-leipzig.de on 2016-07-14)
  14. List of open SHACL Core Syntax ISSUEs (from holger@topquadrant.com on 2016-07-12)
  15. Re: ISSUE-139 proposal for today's telco (from holger@topquadrant.com on 2016-06-17)
  16. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-17)
  17. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from kcoyle@kcoyle.net on 2016-06-16)
  18. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from holger@topquadrant.com on 2016-06-16)
  19. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from holger@topquadrant.com on 2016-06-16)
  20. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from pfpschneider@gmail.com on 2016-06-15)
  21. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from kcoyle@kcoyle.net on 2016-06-15)
  22. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from kontokostas@informatik.uni-leipzig.de on 2016-06-15)
  23. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from holger@topquadrant.com on 2016-06-15)
  24. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from kontokostas@informatik.uni-leipzig.de on 2016-06-15)
  25. Re: Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from holger@topquadrant.com on 2016-06-15)
  26. Re: ISSUE-139 proposal for today's telco (from kontokostas@informatik.uni-leipzig.de on 2016-06-12)
  27. Re: ISSUE-139 proposal for today's telco (from pfpschneider@gmail.com on 2016-06-10)
  28. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-10)
  29. Boierplate macro (Was: Re: ISSUE-139: single implementations of all core constraint components) (from kontokostas@informatik.uni-leipzig.de on 2016-06-10)
  30. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from irene@topquadrant.com on 2016-06-10)
  31. scopeNode and scopeClass (was: ISSUE-139: uniform descriptions and implementations of constraint components) (from holger@topquadrant.com on 2016-06-10)
  32. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-09)
  33. ISSUE-139: single implementations of all core constraint components (from pfpschneider@gmail.com on 2016-06-09)
  34. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from irene@topquadrant.com on 2016-06-09)
  35. Re: RDF Data Shapes agenda for 9 June 2016 (from lehors@us.ibm.com on 2016-06-09)
  36. Re: ISSUE-139: The primary keys use case (from irene@topquadrant.com on 2016-06-09)
  37. Re: ISSUE-139: The primary keys use case (from pfpschneider@gmail.com on 2016-06-09)
  38. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-09)
  39. ISSUE-139 proposal for today's telco (from kontokostas@informatik.uni-leipzig.de on 2016-06-09)
  40. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-09)
  41. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-09)
  42. Re: RDF Data Shapes agenda for 9 June 2016 (from holger@topquadrant.com on 2016-06-09)
  43. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-08)
  44. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-08)
  45. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-08)
  46. RDF Data Shapes agenda for 9 June 2016 (from lehors@us.ibm.com on 2016-06-08)
  47. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from irene@topquadrant.com on 2016-06-08)
  48. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from irene@topquadrant.com on 2016-06-08)
  49. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-08)
  50. ISSUE-139: Minimizing development costs by reusing SPARQL code in SHACL functions (from holger@topquadrant.com on 2016-06-08)
  51. ISSUE-139: Minimal number of implementations of constraint components (from holger@topquadrant.com on 2016-06-08)
  52. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-08)
  53. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-08)
  54. ISSUE-139: The primary keys use case (from holger@topquadrant.com on 2016-06-08)
  55. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-07)
  56. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kcoyle@kcoyle.net on 2016-06-07)
  57. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-07)
  58. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-07)
  59. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-07)
  60. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-07)
  61. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-06)
  62. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-06)
  63. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-06)
  64. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from irene@topquadrant.com on 2016-06-06)
  65. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-06)
  66. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-06)
  67. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-06)
  68. ISSUE-139: Use case for sh:context in form generation (from holger@topquadrant.com on 2016-06-06)
  69. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-06)
  70. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-06)
  71. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from holger@topquadrant.com on 2016-06-06)
  72. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-05)
  73. Re: ISSUE-139: implementing (core) constraint components universally (from pfpschneider@gmail.com on 2016-06-05)
  74. Re: ISSUE-139: uniform descriptions and implementations of constraint components (from kontokostas@informatik.uni-leipzig.de on 2016-06-05)
  75. ISSUE-139: uniform descriptions and implementations of constraint components (from pfpschneider@gmail.com on 2016-06-05)
  76. Re: ISSUE-139: implementing (core) constraint components universally (from kontokostas@informatik.uni-leipzig.de on 2016-06-05)
  77. Re: ISSUE-139: implementing (core) constraint components universally (from holger@topquadrant.com on 2016-06-05)
  78. Re: ISSUE-139: implementing (core) constraint components universally (from holger@topquadrant.com on 2016-06-05)
  79. Re: ISSUE-139: implementing (core) constraint components universally (from kcoyle@kcoyle.net on 2016-06-04)
  80. Re: ISSUE-139: implementing (core) constraint components universally (from kcoyle@kcoyle.net on 2016-06-04)
  81. Re: ISSUE-139: implementing (core) constraint components universally (from holger@topquadrant.com on 2016-06-04)
  82. Re: ISSUE-139: implementing (core) constraint components universally (from pfpschneider@gmail.com on 2016-06-03)
  83. Re: ISSUE-139: implementing (core) constraint components universally (from holger@topquadrant.com on 2016-06-03)
  84. Re: eliminating the need for three SPARQL queries for constraint components (from holger@topquadrant.com on 2016-06-03)
  85. ISSUE-41: Yet another take on property paths (from holger@topquadrant.com on 2016-06-03)
  86. ISSUE-139: implementing (core) constraint components universally (from pfpschneider@gmail.com on 2016-06-02)
  87. Re: shapes-ISSUE-141 (Mixed ranges): How to represent mixed datatype-or-class ranges [SHACL - Core] (from holger@topquadrant.com on 2016-04-12)
  88. Re: ISSUE-139: Cases where constraint components do not make sense (from holger@topquadrant.com on 2016-04-10)
  89. Re: ISSUE-139: Cases where constraint components do not make sense (from pfpschneider@gmail.com on 2016-04-08)
  90. ISSUE-139: Cases where constraint components do not make sense (from holger@topquadrant.com on 2016-04-08)
  91. How to make progress on syntax and metamodel? (from holger@topquadrant.com on 2016-03-18)
  92. shapes-ISSUE-139 (Universal applicability): Can all constraint properties be applied in all scenarios? [SHACL - Core] (from sysbot+tracker@w3.org on 2016-03-18)

Related notes:

RESOLUTION: Close ISSUE-139, adopt Holger's compromise proposal https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Jul/0062.html
See https://www.w3.org/2016/07/21-shapes-minutes.html#resolution02

Arnaud Le Hors, 22 Jul 2016, 16:55:45

reopen ISSUE-139, motivated by surrounding changes in SHACL spec
CLOSE ISSUE-139 by declaring that NodeShapes are ill-formed if they use any of the properties listed in https://lists.w3.org/Archives/Public/public-data-shapes-wg/2017Feb/0012.html

https://www.w3.org/2017/02/08-shapes-minutes.html

Irene Polikoff, 9 Feb 2017, 22:51:48

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: 139.html,v 1.1 2018/11/26 09:03:29 carine Exp $