ISSUE-23: Shapes as classes

ShapeClass

Shapes as classes

State:
CLOSED
Product:
SHACL Spec
Raised by:
Richard Cyganiak
Opened on:
2015-03-28
Description:
Some people want to apply different shapes to the same class.
Some peope want to apply shapes to data that doesn't include type statements.
Some people want to associate shapes directly with class definitions.
Some people want to “inherit” shapes down existing class hierarchies.
Some people want to “specialise” shapes where there are no existing class hierarchies.
Some people don't want shapes to have anything to do with classes at all to avoid reinventing RDFS, badly.

No proposal seems to satisfy all people.
Related Actions Items:
No related actions
Related emails:
  1. Re: RDF Data Shapes WG Minutes for 28 January 2016 (from holger@topquadrant.com on 2016-01-29)
  2. RDF Data Shapes WG Minutes for 28 January 2016 (from lehors@us.ibm.com on 2016-01-28)
  3. Re: when is a node a class, when is a node a shape, when is a node an instance of a class (from arthur.ryman@gmail.com on 2016-01-28)
  4. Re: ISSUE-23 implicit scopeClass text updated (from arthur.ryman@gmail.com on 2016-01-25)
  5. Re: ISSUE-23 implicit scopeClass text updated (from pfpschneider@gmail.com on 2016-01-22)
  6. Re: ISSUE-22 and ISSUE-23 (from arthur.ryman@gmail.com on 2016-01-22)
  7. ISSUE-23 implicit scopeClass text updated (from arthur.ryman@gmail.com on 2016-01-21)
  8. Re: ISSUE-22 and ISSUE-23 (from pfpschneider@gmail.com on 2016-01-21)
  9. Re: ISSUE-22 and ISSUE-23 (from arthur.ryman@gmail.com on 2016-01-20)
  10. Re: ISSUE-23: Where should we query for class and subClassOf? (from holger@topquadrant.com on 2016-01-20)
  11. Re: ISSUE-23: Where should we query for class and subClassOf? (from holger@topquadrant.com on 2016-01-20)
  12. Re: ISSUE-23: Dropped sh:ShapeClass, elaborated on sh:scopeClass rule (from holger@topquadrant.com on 2016-01-20)
  13. Re: ISSUE-22 and ISSUE-23 (from pfpschneider@gmail.com on 2016-01-19)
  14. Re: ISSUE-23: Dropped sh:ShapeClass, elaborated on sh:scopeClass rule (from arthur.ryman@gmail.com on 2016-01-19)
  15. Re: ISSUE-23: Where should we query for class and subClassOf? (from arthur.ryman@gmail.com on 2016-01-19)
  16. Re: ISSUE-23: Where should we query for class and subClassOf? (from irene@topquadrant.com on 2016-01-19)
  17. Re: ISSUE-23: Dropped sh:ShapeClass, elaborated on sh:scopeClass rule (from arthur.ryman@gmail.com on 2016-01-19)
  18. ISSUE-22 and ISSUE-23 (from arthur.ryman@gmail.com on 2016-01-19)
  19. ISSUE-23: Where should we query for class and subClassOf? (from arthur.ryman@gmail.com on 2016-01-19)
  20. ISSUE-23: Dropped sh:ShapeClass, elaborated on sh:scopeClass rule (from holger@topquadrant.com on 2016-01-11)
  21. Re: ISSUE-23: SHACL is already a modeling language (from lehors@us.ibm.com on 2015-12-18)
  22. Re: ISSUE-23: SHACL is already a modeling language (from pfpschneider@gmail.com on 2015-12-17)
  23. Re: ISSUE-23: SHACL is already a modeling language (from holger@topquadrant.com on 2015-12-17)
  24. Re: ISSUE-23: SHACL is already a modeling language (from irene@topquadrant.com on 2015-12-17)
  25. Re: ISSUE-23 example on proposal (d) (from pfpschneider@gmail.com on 2015-12-17)
  26. Re: ISSUE-23: SHACL is already a modeling language (from pfpschneider@gmail.com on 2015-12-17)
  27. Re: ISSUE-23: SHACL is already a modeling language (from irene@topquadrant.com on 2015-12-17)
  28. Re: ISSUE-23: SHACL is already a modeling language (from pfpschneider@gmail.com on 2015-12-17)
  29. Re: ISSUE-23: SHACL is already a modeling language (from irene@topquadrant.com on 2015-12-17)
  30. Re: ISSUE-23: SHACL is already a modeling language (from pfpschneider@gmail.com on 2015-12-17)
  31. ISSUE-23: SHACL is already a modeling language (from holger@topquadrant.com on 2015-12-17)
  32. ISSUE-23 example on proposal (d) (from jimkont@gmail.com on 2015-12-16)
  33. ISSUE-23: Another attempt to compromise (from holger@topquadrant.com on 2015-11-21)
  34. Re: RDF Data Shapes WG agenda for 15 October 2015 (from pfpschneider@gmail.com on 2015-10-16)
  35. Re: RDF Data Shapes WG agenda for 15 October 2015 (from kontokostas@informatik.uni-leipzig.de on 2015-10-15)
  36. Re: review of SHACL document (Second pass of responses) (from holger@topquadrant.com on 2015-09-03)
  37. Re: modelling using SHACL - a bad idea - ISSUE-23 (from holger@topquadrant.com on 2015-08-05)
  38. Re: modelling using SHACL - a bad idea - ISSUE-23 (from holger@topquadrant.com on 2015-08-05)
  39. modelling using SHACL - a bad idea - ISSUE-23 (from pfpschneider@gmail.com on 2015-08-04)
  40. Proposal to close ISSUE-23 as currently specified (from holger@topquadrant.com on 2015-07-28)
  41. Re: Fwd: Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-15)
  42. Re: Fwd: Re: ISSUE-23: sh:ShapeClass? (from kontokostas@informatik.uni-leipzig.de on 2015-05-15)
  43. Re: Fwd: Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-15)
  44. Fwd: Re: ISSUE-23: sh:ShapeClass? (from kontokostas@informatik.uni-leipzig.de on 2015-05-14)
  45. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-14)
  46. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-13)
  47. Re: ISSUE-23: sh:ShapeClass? (from kontokostas@informatik.uni-leipzig.de on 2015-05-12)
  48. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-11)
  49. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-11)
  50. Re: ISSUE-23: sh:ShapeClass? (from kcoyle@kcoyle.net on 2015-05-10)
  51. Re: ISSUE-23: sh:ShapeClass? (from jimkont@gmail.com on 2015-05-08)
  52. Re: ISSUE-23: sh:ShapeClass? (from kcoyle@kcoyle.net on 2015-05-08)
  53. Re: ISSUE-23: sh:ShapeClass? (from kontokostas@informatik.uni-leipzig.de on 2015-05-08)
  54. Re: ISSUE-23: A proposal to not mingle shapes and classes (from arthur.ryman@gmail.com on 2015-05-07)
  55. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-05-07)
  56. RDF Data Shapes WG agenda for 07 May 2015 (from eric@w3.org on 2015-05-06)
  57. Re: ISSUE-23: sh:ShapeClass? (from kcoyle@kcoyle.net on 2015-04-30)
  58. Re: ISSUE-23: sh:ShapeClass? (from holger@topquadrant.com on 2015-04-30)
  59. Re: ISSUE-23: A proposal to not mingle shapes and classes (from michel.dumontier@gmail.com on 2015-04-29)
  60. Re: ISSUE-23: A proposal to not mingle shapes and classes (from jimkont@gmail.com on 2015-04-29)
  61. Re: ISSUE-23: A specific proposal (from jimkont@gmail.com on 2015-04-29)
  62. Re: ISSUE-23: A proposal to not mingle shapes and classes (from holger@topquadrant.com on 2015-04-29)
  63. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-29)
  64. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-29)
  65. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-29)
  66. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-29)
  67. Re: ISSUE-23: A proposal to not mingle shapes and classes (from michel.dumontier@stanford.edu on 2015-04-28)
  68. ISSUE-23: A proposal to not mingle shapes and classes (from pfpschneider@gmail.com on 2015-04-28)
  69. Re: ISSUE-23: A specific proposal (from irene@topquadrant.com on 2015-04-28)
  70. Re: ISSUE-23: A specific proposal (from pfpschneider@gmail.com on 2015-04-28)
  71. Re: ISSUE-23: A specific proposal (from pfpschneider@gmail.com on 2015-04-28)
  72. Re: ISSUE-23: A specific proposal (from pfpschneider@gmail.com on 2015-04-28)
  73. Re: ISSUE-23: A specific proposal (from arthur.ryman@gmail.com on 2015-04-28)
  74. Re: ISSUE-23: A specific proposal (from kontokostas@informatik.uni-leipzig.de on 2015-04-28)
  75. Re: ISSUE-23: A specific proposal (from simon.steyskal@wu.ac.at on 2015-04-28)
  76. Re: ISSUE-23: A specific proposal (from kontokostas@informatik.uni-leipzig.de on 2015-04-28)
  77. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-28)
  78. Re: ISSUE-23: A specific proposal (from kontokostas@informatik.uni-leipzig.de on 2015-04-28)
  79. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-28)
  80. Re: ISSUE-23: A specific proposal (from kontokostas@informatik.uni-leipzig.de on 2015-04-27)
  81. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-27)
  82. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-27)
  83. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-27)
  84. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-26)
  85. Re: ISSUE-23: A specific proposal (from pfpschneider@gmail.com on 2015-04-26)
  86. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-26)
  87. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-26)
  88. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-26)
  89. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-25)
  90. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-24)
  91. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  92. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  93. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  94. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  95. Re: ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  96. ISSUE-23: A specific proposal (from holger@topquadrant.com on 2015-04-24)
  97. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-23)
  98. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-23)
  99. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-23)
  100. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-23)
  101. Re: ISSUE-23: A specific proposal (from michel.dumontier@stanford.edu on 2015-04-23)
  102. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from holger@topquadrant.com on 2015-04-09)
  103. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from lehors@us.ibm.com on 2015-04-08)
  104. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from holger@topquadrant.com on 2015-04-04)
  105. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from pfpschneider@gmail.com on 2015-04-03)
  106. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2015-04-03)
  107. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from pfpschneider@gmail.com on 2015-04-03)
  108. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-03)
  109. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-03)
  110. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2015-04-03)
  111. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from pfpschneider@gmail.com on 2015-04-03)
  112. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2015-04-03)
  113. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-03)
  114. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2015-04-03)
  115. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-03)
  116. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from holger@topquadrant.com on 2015-04-03)
  117. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-02)
  118. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from arthur.ryman@gmail.com on 2015-04-02)
  119. Re: shapes-ISSUE-24 (specialisation): Can shapes specialise other shapes? [SHACL Spec] (from arthur.ryman@gmail.com on 2015-04-02)
  120. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from richard@cyganiak.de on 2015-04-02)
  121. Re: shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from arthur.ryman@gmail.com on 2015-04-02)
  122. Re: shapes-ISSUE-24 (specialisation): Can shapes specialise other shapes? [SHACL Spec] (from pfpschneider@gmail.com on 2015-03-28)
  123. shapes-ISSUE-24 (specialisation): Can shapes specialise other shapes? [SHACL Spec] (from sysbot+tracker@w3.org on 2015-03-28)
  124. shapes-ISSUE-23 (punning): Shapes, classes and punning [SHACL Spec] (from sysbot+tracker@w3.org on 2015-03-28)

Related notes:

RESOLUTION: drop ShapeClass
See https://www.w3.org/2016/01/07-shapes-minutes.html#resolution03

RESOLUTION: In the case where a shape is also a class, a SHACL processor MUST include all the instances of the class in the scope of the shape, exactly as if an explicit sh:scopeClass triple was present. An explicit sh:scopeClass triple is not required but MAY be included for clarity.
See https://www.w3.org/2016/01/28-shapes-minutes.html#resolution04

RESOLUTION: Close ISSUE-23, based on resolution regarding ShapeClass (dropped) and implicit scopeClass
See https://www.w3.org/2016/01/28-shapes-minutes.html#resolution05

Arnaud Le Hors, 28 Jan 2016, 22:21:13

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