OWLTopLevel

OWL Top Level

Clean up top level in OWL edition

Problem: browsers like OLS mirror what is seen in Protege, including ugly floater classes etc

For releases, we can be aggressive in doing a cascading delete of axioms that don't point to subclasses of some expected root classes.

We should also try and be watchful in the edit file, and proactively fix:

• if we reference an obsoleted classes, we should rewire
• there is a subtle issue whereby module extraction may end up missing a subclass axiom if the axiom has a complex equivalence axioms. E.g. glabella is equivalent to bone area and connects exactly 2 supra-orbital ridges. This goes away as upstreams move to standard robot release pipelines which always ensures the subclass graph has one direct named class parent
• we may want to explore importing or making a small upper ontology to group things