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

orthogonal_to relation #5

Open
GoogleCodeExporter opened this issue Apr 7, 2015 · 0 comments
Open

orthogonal_to relation #5

GoogleCodeExporter opened this issue Apr 7, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Hi,

There is a previous discussion on the orthogonal_to relation at [2]. 

In BSPO the property orthogonal_to
 - has domain 'anatomical axis' and range 'anatomical plane'.
 - is not symmetric

My considerations:
 a) In my opinion orthogonal_to has to be a symmetric property. This would require that the domain and range are the same: either both undefined or bot the same class. 
 b) In [2] Melissa said, that they need the existing domain and range definitions. So one solution would be to rename the property to has_orthogonal_complement_in_3D and make it a subproperty of orthogonal_to. But even this property should be symmetric in the ideal case.

What do you think?

Best regards,
Heiner

[2] 
http://sourceforge.net/p/obo/common-anatomy-reference-ontology-caro-requests/11/

Original issue reported on code.google.com by Heiner.O...@gmail.com on 27 Sep 2014 at 1:43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant