Since e10d26d6add2a3bfcc29f5e6b7e83c7fe1b767ab and 2fd764f8f636c4c66245fe1d044a307dd3f98282, all OB SHACL validation errors are fixed.
However the changes still need to be discussed with the domain experts.
@FranziskaJahn as this has been open for over two years, can you confirm whether those fixes are OK? Or shall I just close this issue and assume everything is as intended?
Since e10d26d6add2a3bfcc29f5e6b7e83c7fe1b767ab and 2fd764f8f636c4c66245fe1d044a307dd3f98282, all OB SHACL validation errors are fixed. However the changes still need to be discussed with the domain experts.