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

Part-of should be treated as a hierarchical relationship #160

Open
cmungall opened this issue Sep 22, 2021 · 4 comments
Open

Part-of should be treated as a hierarchical relationship #160

cmungall opened this issue Sep 22, 2021 · 4 comments

Comments

@cmungall
Copy link

When ontologies such as GO, Uberon, ENVO are viewed in ontobee there is no visual indication of the partonomy

ontobee should show part-ofs (formally A subClassOf part-of some B) in the hierarchy, as OLS and Bioportal do

I also recommend standardizing with OLS on various kinds of ontology metadata that drive configuration:

https://www.ebi.ac.uk/ols/docs/installation-guide

@yongqunh
Copy link
Member

This is a good suggestion. We will consider it carefully. Thanks.

@cmungall
Copy link
Author

I don't suppose there are any plans to implement this? I am happy to help with providing a more detailed specification, with testing, etc. I also have both python and java code that will do the necessary transform.

I can't over-emphasize how important this feature is for a lot of ontologies. Seeing the ontology without the partonomy is really misleading for users.

@yongqunh
Copy link
Member

Hi Chris, sorry that we do not have a timeline to implement it yet since our previous effort was to update the automatic ontobee updating program. Given the automatic updating program is basically done, we may come back to focus on this issue.
Probably we can schedule a meeting to discuss this?
Thanks!

@cmungall
Copy link
Author

I'm happy to schedule a meeting, but maybe we should do as much prelim work as possible async ahead of time?

I think the first part is coming up with requirements and specification of intended behavior. this should be easy as we can look to OLS and bioportal. I like to think of it in terms of graphs - consider a graph G with edges:

  • S subClassOf O, where S and O are named classes, the edge label is rdfs:subClassOf
  • S subClassOf R some O, where S and O are named classes, and the label is R

We would only do this for select values of R, typically part_of, but this could be configurable

Then figure the best way to implement this is in the context of ontobee. I can help given some documentation. E.g. for the current method to draw the hierarchy, do you use SPARQL property paths, do you cache graphs in advance, etc

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