ISSUE-223: Should we disallow shapes with mismatching type

Shapes mismatching type

Should we disallow shapes with mismatching type

State:
CLOSED
Product:
SHACL - Core
Raised by:
Holger Knublauch
Opened on:
2017-02-05
Description:
See https://lists.w3.org/Archives/Public/public-rdf-shapes/2017Feb/0001.html it was pointed out that cases like

ex:s1 rdf:type sh:NodeShape ;
sh:targetClass ex:Person ;
sh:path ex:child ;
sh:nodeKind sh:IRI .

can be confusing to users because it's really a property shape despite having sh:NodeShape as type.

While this is an artificially constructed example, a reasonable addition would be to add two syntax rules:

a) SHACL instances of sh:NodeShape cannot have values for sh:path
b) SHACL instances of sh:PropertyShape must have a value for sh:path

making such cases ill-formed shapes.
Related Actions Items:
No related actions
Related emails:
  1. shapes-ISSUE-223 (Shapes mismatching type): Should we disallow shapes with mismatching type [SHACL - Core] (from sysbot+tracker@w3.org on 2017-02-05)

Related notes:

RESOLUTION: CLOSE issue-223 by adding two syntax rules: a) SHACL instances of sh:NodeShape cannot have values for sh:path; b) SHACL instances of sh:PropertyShape must have a value for sh:path

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

Irene Polikoff, 9 Feb 2017, 22:49:02

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 $