IAO import side effects

[marijane]

I imported the IAO ontology metadata namespace in order to get access to annotations like obo:definition. The corresponding classes for these properties show up in the class tree in Protege. I'm not clear if this is something I should work around with a MIREOT of this namespace.

[cmungall]

did you manage to get around this?

[marijane]

Hi @cmungall,

I think this might be a legacy ticket from when I created this repo with the original Ontology Starter Kit. RIght now we have both BFO and IAO import files and I think they were generated by the ODK?

If I recall correctly, my original concerns were about the CRO being tied to BFO. I have this idea that I would like there to be different versions of the CRO that work with various ontologies and vocabularies that include Role concepts. For example, I'd like a version of CRO that can work with schema.org, and in those cases, I wouldn't want to import IAO. I am not sure this can be accomplished within the bounds of a single ODK-generated repository, though. I can imagine a Makefile with several different kinds of build targets but I'm guessing I would have to make some serious modifications in order to make things work the way I think I'd like them to.

[cmungall]

What I would do is import the IAO classes you need via MIREOT in ROBOT, and don't take anything higher level than you need. You can then release alternate bridge files for different UOs