-
Notifications
You must be signed in to change notification settings - Fork 8
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
COB changes preferred labels of several ontologies #243
Comments
This was originally by design but doesn't make sense in light of the merge strategy
we should pursue this. But for now I suggest:
|
Do you mean like: removing the labels from COB edit, and importing them instead? Or just hardcoding the current authoritative labels in COB?
Is there any real hope here? :D |
I proposed we rename "molecular_function" (the actual label) to "molecular function", and haven't gotten very far with that. 😂 |
To be honest, the ditching of COB ids was a surprise to me.
The definition of SDC requires that there exist at least one IC that the SDC
A
If you take
A question to address here is whether
The definition of
The definitions for To sum up, I don't think characteristics are the same as SDCs if:
|
Let's try and keep this issue focused on the general issue at hand To discuss SDC specifically, use #264 The fact that names are different is a feature not a bug. It indicates something is not aligned. Make issues for the specific issues, here or in the external ontology linked to here. We will align eventually. Each case will be different. The GO nucleus one should be an easy one. A non GO person should make an issue |
COB changes preferred labels of several ontologies, which is kinda "injection".
Examples:
id: GO:0005634
name: cell nucleus (instead of nucleus)
id: GO:0003674
name: gene product or complex activity (instead of molecular function)
id: BFO:0000020
name: characteristic (instead of specifically dependent continuant)
This is related to the question of "who owns COB terms".
I am beginning to question a bit if adopting URIs is really the right way in COB, vs just using clean new COB ids with sssom mappings..
The text was updated successfully, but these errors were encountered: