SHACL implementation ignoring owl:class?

[uahic]

Quick question regarding SHACL in RDF4J.

We started our project using OWL but after figuring out that there is actually no OWL reasoner in RDF4J I switched to SHACL (which I like more at least so far) and right now trying to write some PropertyShapes for an imported external ontology (Units of measurements ontology)

http://purl.obolibrary.org/obo/uo.owl

but my PropertyShape (applied on a relation which contains " hasUnit http://purl.obolibrary.org/obo/UO_0000185") seems not to be able to follow the rdfs:subclassof link chain as specified in the uo.owl until it hits the class UO_0000000 (the basec class of all unit definitions)

@prefix uo: <http://purl.obolibrary.org/obo/> .
myProject:hasUnitShape
    a sh:PropertyShape ;
    sh:path myProject:hasUnit ;
    sh:class uo:UO_0000000 ; # Class of all units
    sh:name "hasUnit" .

The owl:class in the uo.owl looks like this:

    <!-- http://purl.obolibrary.org/obo/UO_0000185 -->

    <owl:Class rdf:about="http://purl.obolibrary.org/obo/UO_0000185">
        <owl:equivalentClass>
            <owl:Class>
                <owl:oneOf rdf:parseType="Collection">
                    <rdf:Description rdf:about="http://purl.obolibrary.org/obo/UO_0000185"/>
                </owl:oneOf>
            </owl:Class>
        </owl:equivalentClass>
        <rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/UO_1000185"/>
    </owl:Class>

printing all RDF statements in RDF4J starting with UO_0000185 results in:

(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/1999/02/22-rdf-syntax-ns#type, http://www.w3.org/2002/07/owl#Class) [null]
(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/2002/07/owl#equivalentClass, _:7048efc2fb96887c) [null]
(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/2000/01/rdf-schema#subClassOf, http://purl.obolibrary.org/obo/UO_1000185) [null]
(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/1999/02/22-rdf-syntax-ns#type, http://www.w3.org/2002/07/owl#NamedIndividual) [null]
(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/2000/01/rdf-schema#comment, ""A plane angle unit which is equal to 1/360 of a full rotation or 1.7453310^[-2] rad." [Wikipedia:Wikipedia]") [null]
(http://purl.obolibrary.org/obo/UO_0000185, http://www.w3.org/2000/01/rdf-schema#label, "degree") [null]

I also did that for all parent classes following manually up the chain. All the data is definitely existing.
Can somebody confirm or deny my suspicion in this case? or did I make an error somewhere?
Please dont say this isnt implemented ... :(

[uahic]

I found this issue
#4513

ok now I really wonder: isn't that a feature that is extremely common to check for parent class memberships and almost nobody bothered so far? o.0 Really what I want to do here is to tell the Constraint it should only accept classes as objects which have the basetype 'UO_0000000' (=is a unit, dont matter which one). That's it. Again, I think this is a superduper standard use case and nothing exotic.

I just tried to replace OWL.CLASS by RDFS.CLASS via the RDF4J API but this also does not work.

This is only loosely related but also shows that other SHACL implementations can climb up the inheritance ladder. It also gets mentioned in a couple of blog posts etc.
https://stackoverflow.com/questions/71457495/impossible-to-define-restriction-inheritance-in-shacl-shapes-graph-only-in-data