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

Generalizing HPO morphology patterns to remove redundant part #7388

Closed
anna-anagnostop opened this issue Mar 17, 2022 · 11 comments
Closed

Generalizing HPO morphology patterns to remove redundant part #7388

anna-anagnostop opened this issue Mar 17, 2022 · 11 comments
Assignees
Labels
logical definition OWL-DL statements and external ontologies

Comments

@anna-anagnostop
Copy link

anna-anagnostop commented Mar 17, 2022

While reviewing MP-HPO logical mappings, it came to my attention that the EQ for Abnormal cardiac atrium morphology HP:0005120 uses:

has part some (morphology and (inheres in some (cardiac atrium and (part of some heart))) and (has modifier some abnormal))

There are additional terms under Abnormal heart morphology HP:0001627 branch (e.g. Abnormal heart valve morphology HP:0001654 -- and possibly elsewhere -- that use the redundant part.

EQ for the matching MP term (abnormal heart atrium morphology MP:0003105 does not include the (part of some heart) bit.

Please consider generalizing these patterns to remove the redundant part in the HPO.

Thank you,

Anna

@anna-anagnostop anna-anagnostop added the logical definition OWL-DL statements and external ontologies label Mar 17, 2022
@pnrobinson
Copy link
Contributor

@matentzn @LCCarmody I think this should be simply

has part some (morphology 
and (inheres in some and (part of some cardiac atrium)) 
and (has modifier some abnormal))

does that sound about right (the atrium is part of the heart and not the entire atrium needs to be abnormal).

@matentzn
Copy link
Contributor

matentzn commented Mar 18, 2022

@LCCarmody: EQ should be according to what Peter suggests here:

has part some (morphology 
and (inheres in part of some cardiac atrium) 
and (has modifier some abnormal))
  • @rays22 Please make sure there is a pattern that uses inheres in part of with morphology (not just inheres in)

@anna-anagnostop
Copy link
Author

anna-anagnostop commented Mar 18, 2022

Peter's suggestion sounds correct to me.
@rays22 Please note there is a pattern available for abnormalMorphologyOfPartOfAnatomicalEntity

@rays22 rays22 self-assigned this Mar 18, 2022
@nicolevasilevsky nicolevasilevsky removed their assignment Dec 20, 2022
@pnrobinson
Copy link
Contributor

@LCCarmody @matentzn @anna-anagnostop @rays22
Can we close this issue? What was the outcome?

I think that the documentation of these patterns is currently rather opaque and suggest that we make an entry for each pattern like this in http://obophenotype.github.io/human-phenotype-ontology/ ?

@rays22
Copy link
Contributor

rays22 commented Jan 3, 2024

@pnrobinson, I think the outcome is a consensus on the suggestion to change the logical definitions of Abnormal cardiac atrium morphology and Abnormal heart valve morphology
to:

has part some (morphology 
and (inheres in part of some cardiac atrium) 
and (has modifier some abnormal))

However, it looks like the suggestion has not been actioned yet.

I also think that it is a good idea to document the pattern and reference the description section of the uPheno pattern abnormalMorphologyOfPartOfAnatomicalEntity.

@LCCarmody
Copy link
Collaborator

just so we are cleare 'inheres in part of' is actually now 'characterstic of part of'

@rays22
Copy link
Contributor

rays22 commented Jan 4, 2024

just so we are cleare 'inheres in part of' is actually now 'characterstic of part of'

Yes, the current label for inheres in part of is characteristic of part of.

has part some (morphology 
and (characteristic of part of some cardiac atrium) 
and (has modifier some abnormal))

@pnrobinson
Copy link
Contributor

@rays22
it would be good to start to have English language definitions of all of the patterns, but that is outside of my wheelhouse (the yaml files are only good if you know what you want to look for; it would be great to have a table of related patterns).
I will add the corresponding definitions to the hp-edit file. Thanks!

@rays22
Copy link
Contributor

rays22 commented Feb 12, 2024

@rays22 it would be good to start to have English language definitions of all of the patterns, but that is outside of my wheelhouse (the yaml files are only good if you know what you want to look for; it would be great to have a table of related patterns). I will add the corresponding definitions to the hp-edit file. Thanks!

  1. it would be good to start to have English language definitions of all of the patterns

I have just double checked, and the good news is that every uPheno pattern has an English language definition and also a description. However, I acknowledge that the English of some of the free text definitions and descriptions is weird. I would be happy to implement any suggested improvements on a case-by case basis.

  1. it would be great to have a table of related patterns).

@pnrobinson , by a table of related patterns, do you mean like a tabular format representation of the browsable uPheno pattern ontology here ?

@pnrobinson
Copy link
Contributor

@rays22 -- it would be nice to have a more intuitive and compact summary of available terms. I think it would be good for the HPO project to have some publication that describes all of this work and how it relates to MPO. I do not want to lead such a manuscript but would be happy to contribute, and it would be great for the R24 project @mellybelly @cmungall
As is, the resources are very opaque and it would be a major project to explore and understand!

@matentzn
Copy link
Contributor

We are working on the uPheno 2 manuscript and all of this will be explained as part of that paper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logical definition OWL-DL statements and external ontologies
Projects
Status: Done
Development

No branches or pull requests

7 participants