anchor.diff:  All these will log as `INFO`.
   
   First step to debugging and understanding an unexpected violation is to enable `shaclSail.setLogValidationViolations(true);`.
  +
  +Logging for unsupported SHACL features and for internal processes in the SHACL sail are logged at `DEBUG`.
   
   ==== Log validation plans
   
  
positive.code: 
  === Logging and debugging
  
  By default there is no logging enabled in the ShaclSail. There are three methods for enabling
  logging:
  
   - `shaclSail.setLogValidationPlans(true);`
  
negative.code: `sh:or` is limited to statement based restrictions, such as `sh:datatype`, or aggregate based restrictions, such as `sh:minCount`,
  but not both at the same time.
  
  Predicates that are not supported are logged at the `DEBUG` logging level.
  
  === Validation results
  
  On `commit()` the ShaclSail will validate your changes and throw an exception if there are
  