Behaviour of GraphShacl validation

[AuPath]

Currently, when an incoming RDFGraph fails SHACL validation, the route continues executing, with the failure only logged and a validation report written to disk. It might be useful to introduce a "strict" URI parameter that allows users to decide whether such a failure should stop route execution, which would be valuable in scenarios where a failed SHACL validation indicates that the RDF data is invalid or unexpected.

@marioscrock what do you think? What was the reasoning behind the current behaviour?

[marioscrock]

I agree with your proposal 👍 the idea behind the current behaviour was not to "lose data" (i.e., do not stop the route) in case of validation errors that often are "acceptable". However, I can imagine scenarios in which a more strict behaviour is desirable. An even better possibility would be to let the user specify the "severity" of violation that should stop the route (cf., https://www.w3.org/TR/shacl/#severity)