This PR introduces support for specifying the severity of a requirement check through dedicated properties:
SHACL requirements can use the SHACL sh:severity property (where sh: is the prefix for SHACL, i.e., http://www.w3.org/ns/shacl#) to define the severity of a constraint violation. The allowed severity values in SHACL are sh:Violation (default), sh:Warning, and sh:Info, which correspond to the severity levels REQUIRED, RECOMMENDED, and OPTIONAL, respectively.
Python scripts can now define the severity of a requirement check by using the severity parameter in the check decorator. The allowed values are Severity.REQUIRED, Severity.RECOMMENDED, and Severity.OPTIONAL.
As before, the severity of a requirement check can also be specified by placing the requirement within one of the folders, must, should, or may, of the corresponding profile.
This PR introduces support for specifying the severity of a requirement check through dedicated properties:
SHACL requirements can use the SHACL
sh:severityproperty (wheresh:is the prefix for SHACL, i.e., http://www.w3.org/ns/shacl#) to define the severity of a constraint violation. The allowed severity values in SHACL aresh:Violation(default),sh:Warning, andsh:Info, which correspond to the severity levelsREQUIRED,RECOMMENDED, andOPTIONAL, respectively.Python scripts can now define the severity of a requirement check by using the
severityparameter in the check decorator. The allowed values areSeverity.REQUIRED,Severity.RECOMMENDED, andSeverity.OPTIONAL.As before, the severity of a requirement check can also be specified by placing the requirement within one of the folders,
must,should, ormay, of the corresponding profile.