W3C home > Mailing lists > Public > public-rdf-shapes@w3.org > February 2017

RE: Question on Handling of Ill-formed Shapes Graphs

From: Svensson, Lars <L.Svensson@dnb.de>
Date: Mon, 20 Feb 2017 10:32:41 +0000
To: Irene Polikoff <irene@topquadrant.com>, Holger Knublauch <holger@topquadrant.com>
CC: "public-rdf-shapes@w3.org" <public-rdf-shapes@w3.org>
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D2BE4E1@dnbf-ex1.AD.DDB.DE>

On Monday, February 20, 2017 2:17 AM, Irene Polikoff [mailto:irene@topquadrant.com] wrote:

> The spec says that a SHACL Core processor must be able to validate data against any
> shape in the shapes graph that is expressed using SHACL Core and is well formed.


> The spec does not place a conformance requirement on the SHACL Core processor with
> respect to the shapes that are ill formed. For example, the processor could silently
> ignore such a shape and move on with validating data against all the well formed
> shapes in the shapes graph. It could also ignore it and move on with other validations,
> but issue a warning that one of the shapes was ill formed. Or it could stop any further
> processing and perform no validation against the shapes graph if it contains an ill
> formed shape. Which option to take is left to implementations. The spec doesn’t
> mandate anything.

Thanks. Yes, makes sense to me. And (as I wrote in the reply to Holger's answer), I propose to add the requirement that if a SHACL processor does not produce a failure in the case of an ill-formed graph, it MUST NOT produce a result with the value sh:conforms true. (I. e. the default result of such an processor must be sh:conforms false). That would make the whole system more robust since it would never produce false positives which I think could be fatal.



Received on Monday, 20 February 2017 10:49:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:48 UTC