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

RO part of not reflexive in GO plus #14502

Closed
alanruttenberg opened this issue Nov 5, 2017 · 3 comments
Closed

RO part of not reflexive in GO plus #14502

alanruttenberg opened this issue Nov 5, 2017 · 3 comments
Assignees

Comments

@alanruttenberg
Copy link

alanruttenberg commented Nov 5, 2017

There are two relations "part of" in GO-Plus. Neither is reflexive.

@alanruttenberg alanruttenberg changed the title part of in go-plus is SO part of - should be RO part of RO part of not reflexive in GO plus Nov 5, 2017
@alanruttenberg
Copy link
Author

There are also 3 has part relations. It's rather confusing in protege. I'd suggest either unifying them (with equivalentProperties), or naming them distinctly.

@cmungall
Copy link
Member

cmungall commented Nov 6, 2017

Thanks. As to the first part, looks like we need to do more tidying of our import chain (though really some of this needs to be pushed upstream, e.g. to SO).

For the reflexivity axiom (which must be local reflexivity) see oborel/obo-relations#151

@balhoff
Copy link
Member

balhoff commented Apr 24, 2020

With the import pipeline we have now, GO will reflect whatever property characteristics are defined in RO. I only find one 'has part' now. There does seem to be rogue 'part of' defined by DDANAT; I opened a ticket there (dictyBase/migration-data#12).

@balhoff balhoff closed this as completed Apr 24, 2020
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

3 participants