shapes-ISSUE-231 (sh:message in components): Could we allow sh:message for constraint components, not just validators? [SHACL - SPARQL]

shapes-ISSUE-231 (sh:message in components): Could we allow sh:message for constraint components, not just validators? [SHACL - SPARQL]

http://www.w3.org/2014/data-shapes/track/issues/231

Raised by: Holger Knublauch
On product: SHACL - SPARQL

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.

Received on Wednesday, 15 February 2017 07:02:13 UTC