You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @jmillanacosta - excellent point! The transforms are not currently doing anything with imports, though the corresponding Bioportal page shows all base and imported classes. There are certainly positives and negatives about including imports, with one positive being that application ontologies like ENM will look much more complete with imports vs. without. In this case I can use one of the alternate serializations of the ontology as they contain the imported classes.
Hi @caufieldjh, thank you for your explanation, I think that's a good rule of thumb for application ontologies. However, we import a few hundred internally developed classes into the main enanomapper.owl class hierarchy that we would like to see reflected in the KG stats. I can get back to you soon when the next release is out to discuss which subset works better for this KG.
Hi, I came across this project and saw this:
The eNM ontology uses owl imports and you are probably only capturing the ontology annotations.
The text was updated successfully, but these errors were encountered: