-
Notifications
You must be signed in to change notification settings - Fork 8
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
Added hierarchy of ontology module types #36
Added hierarchy of ontology module types #36
Conversation
This can be used for injecting ontology header axioms in tools such as ROBOT, see ontodev/robot#6 This is also useful for the atomic module proposal see INCATools/ontology-development-kit#50 Unclear if IAO is the best home for this, see information-artifact-ontology#35
@cmungall current ID ranges are indicated in the IAO ontology comments, like: I think we'd use a better way than it. But I have no idea how. |
https://github.com/INCATools/ontology-starter-kit/ IAO presents a challenge as IDs split across 2 repos |
I have also added a new class for representing "obo basic" subsets, see http://owlcollab.github.io/oboformat/doc/obo-syntax.html#6.2 |
It's a good idea. The proposed terms make sense. There are some that I can't imagine using myself. Tools such as ROBOT will be able to automatically annotate some of these terms, but some will require manual assertion. I'm fine with the proposed definitions, but not all the proposed terms have definitions. 'ontology module' is undefined, for one. Minor point: there's alternation between 'subset ontology module' and 'ontology subset module', but I don't understand what the difference could be. |
Should be consistently There are some notes on |
Change component to base cc @balhoff
if the owldiff is hard to read, I added classes in the 8x range:
@zhengj2007 I took 8x onwards, how do I claim an IAO range? See #35
Comments welcome @jamesaoverton @balhoff @alanruttenberg @mcourtot @dosumis @drseb @matentzn @rctauber @simonjupp
See also
I would like to axiomatize the above (this would not be intended for use in the actual ontologies that use these, more as a documentation feature). What do we think of using PROV-O here?