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

Credit and CRO #126

Open
jcolomb opened this issue Jun 26, 2020 · 3 comments
Open

Credit and CRO #126

jcolomb opened this issue Jun 26, 2020 · 3 comments

Comments

@jcolomb
Copy link

jcolomb commented Jun 26, 2020

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?

@cmungall
Copy link
Contributor

cmungall commented Jun 9, 2021

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

@StroemPhi
Copy link

@cmungall may that be due to not having the most recent ODK for the release pipeline?

@marijane
Copy link
Member

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.

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

4 participants