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
The credit terms have no information in CRO, so CRO is not usable in absence of CREDIT.
It means that to use CRO, one needs to access both ontologies and merge them before starting to play around.
Is there a way to make CRO independent of CREDIT?
The text was updated successfully, but these errors were encountered:
how are you consuming CRO? The OWL file imports credit_import, so you should see it if you are using owl tooling. But nevertheless I recommend CRO uses a standard pipeline and merge imports prior to release
Getting the CrediT import to work in ODK was a huge hacky hassle because we chose not to submit it as an OBO ontology. I don't know if newer ODK releases do a better job of handling non-OBO imports. I'm hoping another data2health team member might be able to weigh in on the possibility of updating things, because I am not currently funded to work on it.
The credit terms have no information in CRO, so CRO is not usable in absence of CREDIT.
It means that to use CRO, one needs to access both ontologies and merge them before starting to play around.
Is there a way to make CRO independent of CREDIT?
The text was updated successfully, but these errors were encountered: