shapes-ISSUE-75 (error vs violation): How to distinguish constraint violations from errors [SHACL Spec] from RDF Data Shapes Working Group Issue Tracker on 2015-07-13 (public-data-shapes-wg@w3.org from July 2015)

From: RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 13 Jul 2015 18:43:34 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <E1ZEihS-0000eq-LN@maia.w3.org>

shapes-ISSUE-75 (error vs violation): How to distinguish constraint violations from errors [SHACL Spec]

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

Raised by: Peter Patel-Schneider
On product: SHACL Spec

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 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.

Received on Monday, 13 July 2015 18:43:36 UTC