-
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
Policy around using COB identifiers vs other OBO Ontology identifiers #224
Comments
It's a good question to ask at the COB seminar today! I think we should align to the mapped ids and not the COB ids, but I may not see the whole picture here. |
There's a COB seminar today!? I had no idea.
…On Wed, Jan 25, 2023 at 6:15 AM Nico Matentzoglu ***@***.***> wrote:
It's a good question to ask at the COB seminar today! I think we should
align to the mapped ids and not the COB ids, but I may not see the whole
picture here.
—
Reply to this email directly, view it on GitHub
<#224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYJ7TX5PRD7ZELXUY2YAFDWUEDN5ANCNFSM6AAAAAAUFOJRGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Went out to obo discuss yesterday by James! And also on slack. |
Chris is presenting on COB today at noon Eastern as part of the 2023 Ontology Summit, which I am co-organizing: https://ontologforum.org/index.php/ConferenceCall_2023_01_25. I've done my best to advertise this on OBO Discuss, OBO Tools, and Slack over the past month, but I hate advertising things and I may not have done a good job. |
Thanks @jamesaoverton ! Unfortunately, I can't make it today. My dance card is full. |
Ok. A recording of the session should be available at that link promptly. If it isn't let me know and I'll sort it out. |
I plan to ask the question at today's seminar. |
Here is a link to the bridge document: http://obofoundry.org/COB/obo-bridge/. |
Summary of @cmungall's answer from today's workshop: This is more a less a bug in the process. They plan on swapping out COB object properties for the original RO object properties. Chris said they would fix this in a new release, so we can just use the original OPs. So perhaps this ticket can now serve as a request to fix the OP release process to use the original RO terms not the COB prefixes. Much obliged! |
I think this is simply a bug in |
Should I assume that if I see a COB term and its COB id that originates from another OBO ontology term, that in adopting COB in an ontology, I can/should switch to the COB id? I understand that the SSSOM mapping file must indicate equivalency between the two.
And is this true too of properties? For example "is specified input of" is COB_0000027, and SSSOM file makes equivalency to OBI_0000295. I was puzzled because I thought COB would still stay away from minting common properties, instead leaving that to RO's domain.
The text was updated successfully, but these errors were encountered: