We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
message
(Related to #27, inspired by w3c/data-shapes#158) https://www.w3.org/TR/shacl/#x5.3.2-mapping-of-solution-bindings-to-result-properties specifies how {?vars} are interpolated into the message, but only for SPARQL constraints.
{?vars}
It would be useful to allow this for all shapes. Why should standard constraint components lack this feature?
What vars can be used in interpolation?
?this
?value
?maxExclusive
BTW, is it ok to use {$value} in sh:message, or should it be spelled as {?value}?
{$value}
sh:message
{?value}
The text was updated successfully, but these errors were encountered:
Both {$value} and {?value} can be used interchangeably.
Sorry, something went wrong.
I support improvements for message handling, so that other languages have also access to the valuable information in their messages.
No branches or pull requests
(Related to #27, inspired by w3c/data-shapes#158)
https://www.w3.org/TR/shacl/#x5.3.2-mapping-of-solution-bindings-to-result-properties specifies how
{?vars}
are interpolated into the message, but only for SPARQL constraints.It would be useful to allow this for all shapes. Why should standard constraint components lack this feature?
What vars can be used in interpolation?
?this
?value
?maxExclusive
BTW, is it ok to use
{$value}
insh:message
, or should it be spelled as{?value}
?The text was updated successfully, but these errors were encountered: