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

metaclasses as species #2

Open
wdduncan opened this issue Jul 16, 2020 · 2 comments
Open

metaclasses as species #2

wdduncan opened this issue Jul 16, 2020 · 2 comments

Comments

@wdduncan
Copy link

Using metaclasses for species is interesting. Some questions that come to mind are:

  1. What advantages do you get using metaclasses instead subclasses? For example, in your sides, you have nickel atom as a instance of the atom metaclass. What not have nickel as a subclass of atom?
  2. In the OWL representation, the metaclass instances would be punned classes/individuals. I didn't think that reasoners worked on punned entities. Is that an acceptable loss? Or would not have an OWL version, and only have an RDF version?
@cmungall
Copy link
Collaborator

  1. I think this is all now answered by the documentation? The entire purpose of chemrof is to put specific entities like nickel or nickel ions in the domain of discourse. The linkml classes are for structuring
  2. reasoners work on punned classes/individuals, this is valid DL. And in any case there is no reliance on punning. You would run reasoners on the generated TBox. See https://chemkg.github.io/chemrof/ontology/

@wdduncan
Copy link
Author

Ok. The linkml is generating the OWL.
I'm not sure how some of the OWL classes are generated from the linkml schema. For example, berkelium (symbol Bk) is one of the OWL classes. But I can't find either berkelium or Bk in chemrof.yaml.

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