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

Reference to DOID_4 #5

Open
rushtong opened this issue Feb 24, 2017 · 1 comment
Open

Reference to DOID_4 #5

rushtong opened this issue Feb 24, 2017 · 1 comment
Assignees

Comments

@rushtong
Copy link
Collaborator

@mcourtot
I don't have any clear evidence of a problem here, but I am concerned about replicating the exact owl class of http://purl.obolibrary.org/obo/DOID_4. There are some differences between the DUO version of that class and the DOID version in http://www.obofoundry.org/ontology/doid.html

Is there a need to duplicate (and potentially override some values of) that DOID term? I can envision potential issues when a system needs to use both ontologies and there now exist two classes with the same ID. Which one takes precedence?

@mcourtot
Copy link
Collaborator

mcourtot commented Mar 7, 2017

Hi @rushtong - very valid point. We actually should use only the URI of the DO class and import the metadata at release time. This is my mistake and I'll fix the Makefile. This may take a little while as I'm on leave atm.

For the details if interested we are using the MIREOT guideline which is implemented by our release tool ROBOT

@mcourtot mcourtot self-assigned this Mar 7, 2017
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

2 participants