Re: shapes-ISSUE-118 (syntax errors): syntax errors should not be confusable with validation results [SHACL Spec]

I'd like to see SHACL errors not mixed in with data validation errors.
We previously agreed that other runtime errors would be reported
separately. Why not report SHACL errors that way too?

-- Arthur

On Mon, Jan 11, 2016 at 10:06 AM, RDF Data Shapes Working Group Issue
Tracker <sysbot+tracker@w3.org> wrote:
> shapes-ISSUE-118 (syntax errors): syntax errors should not be confusable with validation results [SHACL Spec]
>
> http://www.w3.org/2014/data-shapes/track/issues/118
>
> Raised by: Peter Patel-Schneider
> On product: SHACL Spec
>
> SHACL syntax errors should not be easily confusable with validation results.
>
> Something like the following is not suitable as the report of a syntax error.
>
> [ a       <http://www.w3.org/ns/shacl#ValidationResult> ;
>   <http://www.w3.org/ns/shacl#message>
>           "Required minimum value count 1 but found 0"^^<http://www.w3.org/2001/XMLSchema#string> ;
>   <http://www.w3.org/ns/shacl#predicate>
>           <http://peoplepetsontology.example.com/pet> ;
>   <http://www.w3.org/ns/shacl#severity>
>           <http://www.w3.org/ns/shacl#Violation> ;
>   <http://www.w3.org/ns/shacl#sourceConstraint>
>           []  ;
>   <http://www.w3.org/ns/shacl#sourceShape>
>           []  ;
>   <http://www.w3.org/ns/shacl#sourceTemplate>
>           <http://www.w3.org/ns/shacl#AbstractMinCountPropertyConstraint>
> ] .
>
>
>

Received on Thursday, 21 January 2016 19:14:14 UTC