Skip to content
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

Open
mengdawn025 opened this issue Mar 29, 2023 · 4 comments
Open

metaclass conflict: #12

mengdawn025 opened this issue Mar 29, 2023 · 4 comments

Comments

@mengdawn025
Copy link

mengdawn025 commented Mar 29, 2023

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

@ernestojimenezruiz
Copy link
Collaborator

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?

@mengdawn025
Copy link
Author

mengdawn025 commented Mar 30, 2023

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

@ernestojimenezruiz
Copy link
Collaborator

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.

@mengdawn025
Copy link
Author

Thank you very much, I will give it a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants