Idea: checksums for policies / configs

[poikilotherm]

Should we create checksums for configs and policies to detect in HERMES if someone overloaded a parameter?

This not so much about safeguarding to avoid someone tuning stuff, more like give a curator a chance to learn that something has gone awry or needed special treatment.

[zyzzyxdonta]

Alternative idea: Rather than using checksums, the mechanism used to configure/override values should directly lead to a note of this in the validation graph. I think we could use SHACLs severity system (sh:Severity, see also: #2) for this. E.g., whenever a parameter is overwritten, a violation of severity sc:PolicyConfigured is created.

[zyzzyxdonta]

SHACL defines sh:ValidationResult as a subclass of sh:AbstractResult to report individual SHACL validation results. SHACL implementations may use other SHACL subclasses of sh:AbstractResult, for example, to report successfully completed constraint checks or accumulated results.

https://www.w3.org/TR/shacl/#results-validation-result

That sounds even better 😄