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

Policy around using COB identifiers vs other OBO Ontology identifiers #224

Open
ddooley opened this issue Jan 24, 2023 · 10 comments
Open

Policy around using COB identifiers vs other OBO Ontology identifiers #224

ddooley opened this issue Jan 24, 2023 · 10 comments

Comments

@ddooley
Copy link
Contributor

ddooley commented Jan 24, 2023

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.

@matentzn
Copy link
Contributor

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.

@wdduncan
Copy link
Member

wdduncan commented Jan 25, 2023 via email

@matentzn
Copy link
Contributor

Went out to obo discuss yesterday by James! And also on slack.

@jamesaoverton
Copy link
Member

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.

@wdduncan
Copy link
Member

Thanks @jamesaoverton !
You've done a great job getting the word out about the 2023 Ontology Summit. I just didn't make the connection that COB was part of the summit today. Sorry for my confusion.

Unfortunately, I can't make it today. My dance card is full.

@jamesaoverton
Copy link
Member

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.

@kaiiam
Copy link

kaiiam commented Jan 25, 2023

I plan to ask the question at today's seminar.

@jamesaoverton
Copy link
Member

Here is a link to the bridge document: http://obofoundry.org/COB/obo-bridge/.

@kaiiam
Copy link

kaiiam commented Jan 25, 2023

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!

@matentzn
Copy link
Contributor

I think this is simply a bug in sssom toolkit: mapping-commons/sssom-py#339

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

5 participants