-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metaclass conflict: #12
Comments
I guess this is a problem coming from owlready, the message is a bit confusing I must agree :-) |
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
The text was updated successfully, but these errors were encountered: