ISSUE-75: How to distinguish constraint violations from errors
error vs violation
How to distinguish constraint violations from errors
- State:
- CLOSED
- Product:
- SHACL Spec
- Raised by:
- Peter Patel-Schneider
- Opened on:
- 2015-07-13
- Description:
- There are two kinds of things that can happen when running SHACL:
1/ A constraint violation can happen, e.g., the name of a person is a number.
2/ An error can occur, perhaps because an illegal recursion is discovered, or some SPARQL macro tries to do an operation on an unbound variable.
Currently constraint violations produce sh:Error and documents talk about these violations being errors. This can easily lead to a confusion between constraint violations and the other kinds of errors. This did not use to be much of a problem because it was possible to treat errors locally, but the handling of illegal recursion may require treating errors very differently from constraint violations. - Related Actions Items:
- No related actions
- Related emails:
- Re: review of SHACL document (First pass of responses) (from holger@topquadrant.com on 2015-09-02)
- Re: proposal to close ISSUE-75 with a result vocabulary extension (from pfpschneider@gmail.com on 2015-08-04)
- Re: proposal to close ISSUE-75 with a result vocabulary extension (from holger@topquadrant.com on 2015-08-04)
- Re: proposal to close ISSUE-75 with a result vocabulary extension (from kontokostas@informatik.uni-leipzig.de on 2015-08-03)
- Re: Proposal to close ISSUE-51 as specified in shacl-ref (from kontokostas@informatik.uni-leipzig.de on 2015-08-03)
- Re: proposal to close ISSUE-75 with a result vocabulary extension (from holger@topquadrant.com on 2015-08-03)
- Re: Proposal to close ISSUE-51 as specified in shacl-ref (from holger@topquadrant.com on 2015-08-03)
- proposal to close ISSUE-75 with a result vocabulary extension (from kontokostas@informatik.uni-leipzig.de on 2015-08-01)
- Re: shapes-ISSUE-75 (error vs violation): How to distinguish constraint violations from errors [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2015-07-14)
- shapes-ISSUE-75 (error vs violation): How to distinguish constraint violations from errors [SHACL Spec] (from sysbot+tracker@w3.org on 2015-07-13)
Related notes:
Resolution: Close ISSUE-75 with F2F resolution "limit reporting to validation results, and not include runtime errors"
See: http://www.w3.org/2015/09/17-shapes-minutes.html#resolution05
Display change log
