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
@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?
The text was updated successfully, but these errors were encountered:
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
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.htmlIs 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?
The text was updated successfully, but these errors were encountered: