Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Clarify in PATO the distinction between mislocalised and dislocated #501

Closed
rays22 opened this issue Jun 16, 2022 · 2 comments · Fixed by #503
Closed

Clarify in PATO the distinction between mislocalised and dislocated #501

rays22 opened this issue Jun 16, 2022 · 2 comments · Fixed by #503
Assignees
Labels
upheno uPheno related tickets

Comments

@rays22
Copy link
Collaborator

rays22 commented Jun 16, 2022

Clarify the distinction between mislocalised PATO:0000628 and dislocated PATO:0001852.
See [comment]((obophenotype/upheno#829 (comment))

  • position PATO:0000140 A spatial quality inhering in a bearer by virtue of the bearer's spatial location relative to other objects in the vicinity.
    • displaced PATO:0002181 A positional quality inhering in a bearer by virtue the bearer's being changed in position.
      • mislocalised PATO:0000628 A positional quality inhering in a bearer by virtue the bearer's being changed in abnormal position.
      • dislocated PATO:0001852 A positional quality inhering in a bearer by virtue of the bearer's being out of its usual or proper place, or position.
@rays22
Copy link
Collaborator Author

rays22 commented Jun 16, 2022

  • need a report of usage of
    mislocalised PATO:0000628 A positional quality inhering in a bearer by virtue the bearer's being changed in abnormal position.
    dislocated PATO:0001852 A positional quality inhering in a bearer by virtue of the bearer's being out of its usual or proper place, or position.

@dosumis
Copy link
Contributor

dosumis commented Jun 16, 2022

Ticket can be closed on merge #503. New issue #505

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
upheno uPheno related tickets
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants