ISSUE-99: special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere)

special cases

special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere)

State:
CLOSED
Product:
SHACL Spec
Raised by:
Peter Patel-Schneider
Opened on:
2015-10-02
Description:
The definition of sh:valueClass says:

A validation result must be produced for each triple that has the focus node as its subject, the sh:predicate as its predicate and where the object is either a literal or a non-literal without a matching rdf:type. A non-literal matches a type if it has an rdf:type value that is the type or one of its (transitive) subclasses, via rdfs:subClassOf. If the value class is rdfs:Resource then all resources match, including untyped resources. Finally, if the value class is rdf:List then the object matches if it has an rdf:first triple. Each produced validation result must have the focus node as its sh:subject, the sh:predicate as its sh:predicate and the respective violating value as its sh:object.

Both rdfs:Resource and rdf:List are special cases in this definition. Special cases increase the effort required to implement SHACL, the effort to write SHACL shapes, and the effort to understand SHACL shapes. The special cases here are not needed, as they can easily be replaced with equivalent versions. The special case for rdf:List also leaves out rdf:nil.

These special cases should be removed from SHACL.


Special cases elsewhere in SHACL should be examined and also removed if there is not an overriding reason for keeping them.
Related Actions Items:
No related actions
Related emails:
  1. Re: RDF Data Shapes WG agenda for 3 March 2016 (from holger@topquadrant.com on 2016-03-03)
  2. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from holger@topquadrant.com on 2016-02-24)
  3. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from holger@topquadrant.com on 2016-02-20)
  4. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from kontokostas@informatik.uni-leipzig.de on 2016-02-19)
  5. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from holger@topquadrant.com on 2016-02-19)
  6. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from holger@topquadrant.com on 2016-02-19)
  7. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from pfpschneider@gmail.com on 2016-02-18)
  8. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from pfpschneider@gmail.com on 2016-02-18)
  9. Re: shapes-ACTION-35: Proposal for lists (ISSUE-99 and ISSUE-119) (from pfpschneider@gmail.com on 2016-02-18)
  10. Re: shapes-ISSUE-99 (special cases): special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) [SHACL Spec] (from arthur.ryman@gmail.com on 2015-10-29)
  11. Re: shapes-ISSUE-99 (special cases): special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) [SHACL Spec] (from holger@topquadrant.com on 2015-10-23)
  12. Re: shapes-ISSUE-99 (special cases): special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) [SHACL Spec] (from arthur.ryman@gmail.com on 2015-10-22)
  13. shapes-ISSUE-99 (special cases): special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) [SHACL Spec] (from sysbot+tracker@w3.org on 2015-10-02)

Related notes:

Resolution: Close ISSUE-99, issue has been addressed, related proposals on handling of rdf:List should be made related to ISSUE-119, which would then need to be re-opened
See http://www.w3.org/2016/03/31-shapes-minutes.html#resolution03

Arnaud Le Hors, 1 Apr 2016, 23:33:10

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 $