Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] SHACL Severity

Hello Håvard



well, I'm hoping to be able to spend some more time on testing SHACL next week.

(un)fortunately I've about half a million triples that need to be validated,

so that might produce some interesting test scenarios...



Best regards


Bart


From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Thursday, March 21, 2019 10:00:33 AM
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] SHACL Severity
 
Attaching a “validation report handler” could be a decent pattern :)

The ShaclSail is supposed to report all violations and not stop on the first one. But I remember seeing an edge case a while back where it didn’t do that correctly. Don’t really have any test for that. Want to add some?

Håvard

On 21 Mar 2019, at 09:42, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Hi,



would also be useful to offer the possibility to only report sh:Violation and not fail on first error

(use case: sending validation reports of several DCAT-AP feeds to their respective sources)


Not sure about log (unless there is a specific log handler that could write a report to a file,

using marker to differentiate between the SHACL violations and internal SHACL engine errors,

but this seems )


Maybe a method that takes an RDFHandler as argument,

so that the triples of the validation report can be written during the validation ?



Best regards


Bart


From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Thursday, March 21, 2019 8:07:42 AM
To: rdf4j developer discussions
Subject: [rdf4j-dev] SHACL Severity
 
Hi,

In SHACL you can have a number of severity levels for a shape (rule). Currently we do not support these.

Does anyone have any recommendation for how to support this?


An example:

A shape with severity sh:Warning is violated. This should not cause the commit() to fail, but there should still be some way for the developer to get hold of the validation report. Currently that report is tucked away in the exception that is thrown by commit(), but in this case no exception should be thrown.

I have been thinking about a few options, all rather bad:
 - log sh:Warning and sh:Info level violations, and do nothing else
 - add a method to the SHACL connection to retrieve the current validation report
 - add a return type to the commit() or prepare() method

Anyone have a better suggestion, or maybe feel that one of the above is good enough?

Cheers,
Håvard



_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev

Back to the top