Open beaudet opened 2 years ago
See if inferencing is having an effect on this behavior and circle back - otherwise, using a SPARQL selector should probably work.
I think you'd need to turn off inferencing. For example the "Abstract Work" idea from the Yale F2F would break all of the other works as PropositionalObject is a super-class of them all.
In validating all instances of E33_Linguistic_Object, the SHACL validator is also finding E33_E41_Linguistic_Appelation since that's a subclass of E33 and therefore reporting that the Name should be classified as a category of information as per the API specs for E33 and that that term should be further classified.
Is this check accurate? Since E33 is a top level LA entity, we'll need an sh:targetClass check for E33. Should I find a way to ignore E33_E41 with these checks or should fully formed E33_E41 data actually contain these concepts as well as E33?