Open mengdawn025 opened 1 year ago
I guess this is a problem coming from owlready, the message is a bit confusing I must agree :-) Are you getting the same error when loading the ontology with Protege or the same owlready?
This error did not occur when I used Protege to load the ontology. And I have found that under the same environment configuration, when I use OWL2Vec * for different ontologies, different errors will occur. Could the reason be that the ontology I use is incorrect? @ernestojimenezruiz
We depend a bit on what owlready can process. In case the ontologies were not created in Protege, one potential trick is to load the ontologies in Protege and then save them from the editor. The saved ontologies from Protege may be easier to process for owlready.
Thank you very much, I will give it a try.
Hi , I wander to know why the following error occurs when I use OWL2Vec * for other ontologies. @ernestojimenezruiz error : metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases