ISSUE-181: SHACL conformance for partial validation reports

SHACL conformance for partial validation reports

State:
CLOSED
Product:
SHACL Spec
Raised by:
Jose Emilio Labra Gayo
Opened on:
2016-09-29
Description:
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.
Related Actions Items:
No related actions
Related emails:
  1. Re: WG Meeting 2017-01-04 (from tthibodeau@openlinksw.com on 2017-01-03)
  2. Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from kcoyle@kcoyle.net on 2016-10-05)
  3. Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from kontokostas@informatik.uni-leipzig.de on 2016-10-05)
  4. Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from kcoyle@kcoyle.net on 2016-10-04)
  5. Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from kcoyle@kcoyle.net on 2016-10-03)
  6. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from lehors@us.ibm.com on 2016-10-03)
  7. Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from irene@topquadrant.com on 2016-10-02)
  8. Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]) (from kontokostas@informatik.uni-leipzig.de on 2016-10-02)
  9. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-10-02)
  10. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2016-10-02)
  11. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-09-30)
  12. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-09-30)
  13. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kontokostas@informatik.uni-leipzig.de on 2016-09-30)
  14. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from holger@topquadrant.com on 2016-09-30)
  15. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from holger@topquadrant.com on 2016-09-30)
  16. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from holger@topquadrant.com on 2016-09-30)
  17. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from holger@topquadrant.com on 2016-09-30)
  18. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-09-29)
  19. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-09-29)
  20. Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from kcoyle@kcoyle.net on 2016-09-29)
  21. shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec] (from sysbot+tracker@w3.org on 2016-09-29)

Related notes:

RESOLUTION: Close ISSUE-181 adopting proposal 2 in the wiki - engines must be able to return all results

https://www.w3.org/2017/01/18-shapes-minutes.html

Irene Polikoff, 10 Feb 2017, 00:05:28

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 181.html,v 1.1 2018/11/26 09:03:32 carine Exp $