Remove-must-should-may-folders-for-5rc-profile

[EttoreM]

No description provided.

[EttoreM]

There is some SHACL code that was problematic and has been commented out for now (together with the corresponding tests.

Commented SHACL code

• five-safes-crate:RootDataEntityShouldMentionCheckValueObject (in file 12_check_phase.ttl).

Commented python tests

• test_5src_12_check_phase.py::test_5src_root_data_entity_does_not_mention_check_value_entity

[EttoreM]

I noticed the following behaviour. When a SHACL rule includes SPARQL constraint, the validator ignores the explicit sh:severity value, and the severity is inferred from the folder structure (may/ / should/ / must/). If the file containing such SHACL code is placed outside those folders, the validator defaults the severity to sh:Violation.

This becomes problematic when trying to move rules away from the may/should/must folder layout. One way to address this is to replace SPARQL-based constraints in property shapes with equivalent “pure SHACL” statements, so that sh:severity is respected regardless of where the file lives.

This commit applies this approach for the rule five-safes-crate:RootDataEntityShouldMentionCheckValueObject in 12_check_phase.ttl.

SPARQL used in node shapes (to define the target node/class) seems not to introduce this issue.