Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]

Hi Jose

others may correct me, but my understanding is that all conformant SHACL 
validation engines need to produce all the "mandatory" fields of the 
results format. They may decide to return less, but that should only be 
an option.

Our test cases should also include the full info, because engines that 
only produce true or false can still use these test cases, while the 
inverse is not the case.

Holger


On 29/09/2016 19:59, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]
>
> http://www.w3.org/2014/data-shapes/track/issues/181
>
> Raised by: Jose Emilio Labra Gayo
> On product: SHACL Spec
>
> When preparing the test-suite, it is not clear to me if we have to declare/check all the validation reports that must be returned by a SHACL processor or just a true/false.
>
> The spec contains the following phrase:
>
> "The validation process returns a validation report containing all validation results. For simpler validation scenarios, SHACL processors SHOULD provide an additional validation interface that returns only true for valid or false for invalid."
>
> A SHACL processor that wants to handle use case 3.31 (https://www.w3.org/TR/shacl-ucr/#uc34-large-scale-dataset-validation) about validating very large datasets may decide to return just the first violation it finds, instead of continue processing/generating all the possible violations.
>
> Is that SHACL processor conformant with the spec? In that case, when defining the test-suite, is it enough if we just declare true/false as the possible result of SHACL validation? Or if a SHACL processor returns just the first violation report that it finds?
>
> In any case, I think the spec should be more clear about when a SHACL processor is conformant or not if it doesn't return all the violation reports and just returns the first one or signals that there was an error.
>
>
>
>

Received on Thursday, 29 September 2016 22:54:56 UTC