[data-shapes] Perhaps change handling of failures in sh:or, sh:and etc (#553)

HolgerKnublauch has just created a new issue for https://github.com/w3c/data-shapes:

== Perhaps change handling of failures in sh:or, sh:and etc ==
@HolgerKnublauch the informative part matches `sh:or`, but there is a mismatch in the textual definition. That should be aligned. Your definition for `sh:someValue` matches the informative parts, and probably also the reality of current implementations. I can confirm that shacl-engine skips any validations for `sh:or` after the first successful validation, unless debug mode is enabled.

_Originally posted by @bergos in https://github.com/w3c/data-shapes/pull/524#discussion_r2312078820_

The same question may apply to sh:and and maybe even general validation order of constraints within the same shape: what happens if one of them "passes" - does the engine still need to evaluate all others and maybe run into a failure.

Care needs to be taken as this may be a breaking change compared to 1.0 yet it may also be a poorly defined corner case.

Please view or discuss this issue at https://github.com/w3c/data-shapes/issues/553 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 31 August 2025 07:54:15 UTC