Re: shapes-ISSUE-229 (results included in a validation report): Respond to the comment about what results to be included in a validation report [SHACL - Core]

This text in Peter’s comment doesn’t parse:

> For
> example, there is the requirement that "A validation report has exactly one
> value for the property sh:conforms that is of datatype xsd:boolean."
> However, the result of validation is an RDF graph and RDF graphs so this
> requirement doesn't make sense.

But I think what he may be trying to say is that the following sentence in section 3.6.1.1 doesn’t parse either.

A validation report has exactly one value for the property sh:conforms that is of datatype xsd:boolean.

I believe it is intended to say:

A validation report must have exactly one value for the property sh:conforms and the value must be of datatype xsd:boolean.

Irene

> On Feb 9, 2017, at 7:53 PM, RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org> wrote:
> 
> shapes-ISSUE-229 (results included in a validation report): Respond to the comment about what results to be included in a validation report [SHACL - Core]
> 
> http://www.w3.org/2014/data-shapes/track/issues/229
> 
> Raised by: Irene Polikoff
> On product: SHACL - Core
> 
> In this email
> 
> https://lists.w3.org/Archives/Public/public-rdf-shapes/2017Feb/0001.html
> 
> Peter has some issues with validation reports. This issue is about part three of the validation report comments:
> 
> what validation results are to be included in a validation report and which of these are to be values of sh:result for the single node in the graph that is a SHACL instance of sh:ValidationReport.
> 
> There is "Only the validation results that are not object of any sh:details
> triple in the results graph are top-level results." and "The property
> sh:detail may link a (parent) result with one or more other (child) results
> that provide further details about the cause of the (parent) result."
> So a validation process has to produce validation results which then end up
> in the validation report if they are not values for sh:details triples.
> What happens if a validation result comes from violation of a constraint
> that is both directly at top level (e.g., from a property shape that is value of
> sh:property for a shape that has targets) and not at top level (e.g., from
> the same property shape as before that is linked to the shape with targets
> via a combination of sh:node and sh:property triples)?  Can a SHACL
> processor use sh:detail to collect that otherwise might be top-level
> validation results?
> 
> There are also some other minor problems with validation reports.  For
> example, there is the requirement that "A validation report has exactly one
> value for the property sh:conforms that is of datatype xsd:boolean."
> However, the result of validation is an RDF graph and RDF graphs so this
> requirement doesn't make sense.
> 
> 
>