ISSUE-231: Could we allow sh:message for constraint components, not just validators?

sh:message in components

Could we allow sh:message for constraint components, not just validators?

State:
CLOSED
Product:
SHACL - SPARQL
Raised by:
Holger Knublauch
Opened on:
2017-02-15
Description:
This detail arose during my implementation of SHACL-SPARQL. See

https://www.w3.org/TR/shacl/#sparql-constraints-variables

Currently, the values of sh:resultMessage are populated based on either the values of ?message as returned by the SELECT query or the sh:message stored in the validator of the constraint component. Some constraint components have multiple validators (esp with other languages like JavaScript). In those cases it is redundant to have to repeat the message for each validator. Instead, the constraint component could define a default message for all validators.

PROPOSAL: Change the rule for sh:resultMessage in section 5.3.2 to fall back to sh:message at the constraint component if no other message has been found.
Related Actions Items:
No related actions
Related emails:
  1. shapes-ISSUE-231 (sh:message in components): Could we allow sh:message for constraint components, not just validators? [SHACL - SPARQL] (from sysbot+tracker@w3.org on 2017-02-15)

Related notes:

RESOLVED 2017-02-15: CLOSE issue-231 by: in section 5.3.2, add sh:message to constraint component; that may be over-ridden by a more specific sh:message attached to a specific validator within that constraint component

Holger Knublauch, 15 Feb 2017, 23:43:47

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 $