ISSUE-221: Simplify the class hierarchy of shapes

sh:Shape hierarchy

Simplify the class hierarchy of shapes

State:
CLOSED
Product:
SHACL - Core
Raised by:
Dimitris Kontokostas
Opened on:
2017-01-25
Description:
as a task from today;s resolution on ISSUE-211 I created this issue

The current editors draft defines three classes for shapes:
sh:Shape with the following subclasses
-> sh:NodeShape
-> sh:PropertyShape

However, all shape-expecting constraint components (sh:shape, sh:or, sh:and) use only sh:Shape and do not distinguish between the two subclasses.

The only exception is sh:property that expects a property shape.
This, however, creates redundancy in the shape definitions e.g.

ex:a a sh:Shape
sh:shape [
sh:path ex:name;
sh:minCount 1;
]

is the equivalent shape for

ex:a a sh:Shape
sh:property [
sh:path ex:name;
sh:minCount 1;
]

In addition, property shapes, as a separate subclass of sh:shape, are not needed anywhere else in the spec. There very few occurrences can be easily reworded.

This indicates that the only reason for this hierarchy is sh:property and this is something that can be defined with sh:shape.

It would be a great simplification if we removed both subclasses and kept only sh:Shape as defined in
https://jimkont.github.io/data-shapes/shacl/core.html#shacl-shapes
https://jimkont.github.io/data-shapes/shacl/core.html#value-nodes
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-220 (what is a shape): defining shapes in a shapes graph [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-01-26)
  6. Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from holger@topquadrant.com on 2017-01-26)
  7. shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from sysbot+tracker@w3.org on 2017-01-25)

Related notes:

[ipolikoff]: Simplify the class hierarchy of shapes

1 Feb 2017, 13:15:20

RESOLUTION: CLOSE ISSUE-221 by renaming sh:shape to sh:node and changing its range, the values of sh:node must be well-formed node shapes.

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

Irene Polikoff, 9 Feb 2017, 22:55:12

Display change log ATOM feed


Irene Polikoff <irene@topquadrant.com>, Ted Thibodeau <tthibodeau@openlinksw.com>, Chairs, Sandro Hawke <sandro@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 $