has_part  : a new twist Original thinking gene products would  not  propagate over  has_part has_part  used as a navigational aid or in  probabilistic  inference has_part  could be omitted from main ontology files with no loss of information In fact: There are situations where  has_part  can be used in annotation propagation
Motivation for  has_part : An example of an incorrect use of  part_of chromosome nucleus mitochondrion part_of part_of all chromosome part_of some nucleus all chromosome part_of some mitochondrion
Current GO: part-specific subtypes chromosome nucleus mitochondrion part_of nuclear chromosome miotchondrial chromosome part_of ABF1 MGM101 is_a is_a
propagation over  part_of chromosome nucleus mitochondrion part_of nuclear chromosome miotchondrial chromosome part_of ABF1 MGM101 is_a is_a ABF1 MGM101
part-specific subtype pattern A common ‘design pattern’ in GO If p is located in w 1  or w 2  then create part-specific subtypes: p-in-w 1  is_a p and part_of w 2 p-in-w 2  is_a p and part_of w 2 Cons: ‘ clutters up’ ontology but terms can be managed automatically using reasoner Annotators may not see subtypes and annotate too generally Easy to fix with correct tooling? Pros: greater discriminative power, more specific annotations Logically coherent, easy to implement rules Then why not implement this universally?
Another example: erroneous use of part_of with complexes core TFIIH complex holo TFIIH complex NEF3 complex part_of TFB1 part_of we would not do this!!
core TFIIH complex (CURRENT GO) core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a
Problem: annotations to more generic term core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a
Problem: additional semi-redundant annotations required to capture necessary gene products core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a TFB1 TFB1 ABF1 MGM101
core TFIIH with  has_part core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 Logically correct Can we propagate gene products?
We would like to propagate gene products  in this case  – but can we do this  universally ? core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 TFB1 TFB1
thought experiment: use  has_part  for location-specific chromosomes chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
no reliable propagation of gene products over  has_part chromosome nucleus mitochondrion has_part has_part ABF1 MGM101 ABF1 MGM101 MGM101 ABF1
So what’s the difference in ontology structure? core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
So what’s the difference in ontology structure? there is no structural difference the computer needs some additional knowledge that is currently IMPLICIT core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
What’s the difference in annotations? core TFIIH complex TFB1 chromosome ABF1 MGM101 SOME instances of MGM10  proteins are part of SOME chromosomes SOME instances of TFB1 proteins are part of SOME core TFIIH complexes
What’s the difference in annotations? core TFIIH complex TFB1 chromosome ABF1 MGM101 SOME instances of MGM10  proteins are part of SOME chromosomes SOME instances of TFB1 proteins are part of SOME core TFIIH complexes ALL instances of core TFIIH complexes proteins has_part SOME TFB1 protein (in this species) TFB1  is integral to  core TFIIH complex  complex  This crucial piece of knowledge is IMPLICIT NOT  ALL instances of chromosome has_part SOME MGM10
Solution Add additional qualifier to GAF name TBD. integral_to? Semantics: ALL instances of this complex in this species have this gene product as part This is stronger than an existing annotation: some instance of this gene product in this species are found in this complex Also works for BP ALL instances of this process in this species require this gene product Example: spermatogenesis, meiosis, MSH standard annotation: some instance of this gene product actively participate in this process Works using standard DL reasoning technology Requires change in annotation practice

More Related Content

PPT
PPT
Presentacion de Tic por Juli, Axel B. y Tomi
PPT
OBO Foundry
PDF
BUILDING THE OBO FOUNDRY – ONE POLICY AT A TIME
PPTX
Emerging Tools in HE: Ignite at SXSW 2013
PPTX
JIT Faculty Development
PPT
Digital World
PPT
Why Hybrid Courses?
Presentacion de Tic por Juli, Axel B. y Tomi
OBO Foundry
BUILDING THE OBO FOUNDRY – ONE POLICY AT A TIME
Emerging Tools in HE: Ignite at SXSW 2013
JIT Faculty Development
Digital World
Why Hybrid Courses?

Similar to has_part in GO (20)

PPT
Introduction to Ontologies for Environmental Biology
PPTX
Light Intro to the Gene Ontology
PPTX
2015 bioinformatics go_hmm_wim_vancriekinge
PPTX
Bioinformatics t8-go-hmm v2014
PDF
Automated Prokaryotic Annotation at JCVI
PDF
Cross Product Extensions to the Gene Ontology
PPT
Chado introduction
PDF
bioinformatics enabling knowledge generation from agricultural omics data
PPTX
Structural annotation................pptx
PPTX
Mungall keynote-biocurator-2017
PPT
Gene Ontology Project
PPT
Information Integration and Knowledge Acquisition from Semantically Heterogen...
PPTX
Use of Uberon in the Bgee database: How to deal with a complex, large, dynami...
PDF
A Genome Sequence Analysis System Built with Hypertable
PPT
Basic Formal Ontology (BFO) and Disease
PPTX
Triplifier talk
PDF
Connecting life sciences data at the European Bioinformatics Institute
PPTX
Bioinformatics t8-go-hmm wim-vancriekinge_v2013
PPT
Bioinformatica 08-12-2011-t8-go-hmm
PPTX
Ontologies: Necessary, but not sufficient
Introduction to Ontologies for Environmental Biology
Light Intro to the Gene Ontology
2015 bioinformatics go_hmm_wim_vancriekinge
Bioinformatics t8-go-hmm v2014
Automated Prokaryotic Annotation at JCVI
Cross Product Extensions to the Gene Ontology
Chado introduction
bioinformatics enabling knowledge generation from agricultural omics data
Structural annotation................pptx
Mungall keynote-biocurator-2017
Gene Ontology Project
Information Integration and Knowledge Acquisition from Semantically Heterogen...
Use of Uberon in the Bgee database: How to deal with a complex, large, dynami...
A Genome Sequence Analysis System Built with Hypertable
Basic Formal Ontology (BFO) and Disease
Triplifier talk
Connecting life sciences data at the European Bioinformatics Institute
Bioinformatics t8-go-hmm wim-vancriekinge_v2013
Bioinformatica 08-12-2011-t8-go-hmm
Ontologies: Necessary, but not sufficient
Ad

More from Chris Mungall (20)

PPTX
MADICES Mungall 2022.pptx
PPTX
Scaling up semantics; lessons learned across the life sciences
PPTX
LinkML Intro July 2022.pptx PLEASE VIEW THIS ON ZENODO
PPTX
Ontology Access Kit_ Workshop Intro Slides.pptx
PPTX
LinkML Intro (for Monarch devs)
PPTX
LinkML presentation to Yosemite Group
PPTX
Experiences in the biosciences with the open biological ontologies foundry an...
PPTX
All together now: piecing together the knowledge graph of life
PPTX
Collaboratively Creating the Knowledge Graph of Life
PPTX
Representation of kidney structures in Uberon
PPTX
SparqlProg (BioHackathon 2019)
PPTX
Ontology Development Kit: Bio-Ontologies 2019
PPTX
US2TS: Reasoning over multiple open bio-ontologies to make machines and human...
PPTX
Uberon: opening up to community contributions
PPTX
Modeling exposure events and adverse outcome pathways using ontologies
PPTX
Causal reasoning using the Relation Ontology
PPTX
US2TS presentation on Gene Ontology
PPTX
Introduction to the BioLink datamodel
PPTX
Computing on Phenotypes AMP 2015
PPTX
ENVO GSC 2015
MADICES Mungall 2022.pptx
Scaling up semantics; lessons learned across the life sciences
LinkML Intro July 2022.pptx PLEASE VIEW THIS ON ZENODO
Ontology Access Kit_ Workshop Intro Slides.pptx
LinkML Intro (for Monarch devs)
LinkML presentation to Yosemite Group
Experiences in the biosciences with the open biological ontologies foundry an...
All together now: piecing together the knowledge graph of life
Collaboratively Creating the Knowledge Graph of Life
Representation of kidney structures in Uberon
SparqlProg (BioHackathon 2019)
Ontology Development Kit: Bio-Ontologies 2019
US2TS: Reasoning over multiple open bio-ontologies to make machines and human...
Uberon: opening up to community contributions
Modeling exposure events and adverse outcome pathways using ontologies
Causal reasoning using the Relation Ontology
US2TS presentation on Gene Ontology
Introduction to the BioLink datamodel
Computing on Phenotypes AMP 2015
ENVO GSC 2015
Ad

has_part in GO

  • 1. has_part : a new twist Original thinking gene products would not propagate over has_part has_part used as a navigational aid or in probabilistic inference has_part could be omitted from main ontology files with no loss of information In fact: There are situations where has_part can be used in annotation propagation
  • 2. Motivation for has_part : An example of an incorrect use of part_of chromosome nucleus mitochondrion part_of part_of all chromosome part_of some nucleus all chromosome part_of some mitochondrion
  • 3. Current GO: part-specific subtypes chromosome nucleus mitochondrion part_of nuclear chromosome miotchondrial chromosome part_of ABF1 MGM101 is_a is_a
  • 4. propagation over part_of chromosome nucleus mitochondrion part_of nuclear chromosome miotchondrial chromosome part_of ABF1 MGM101 is_a is_a ABF1 MGM101
  • 5. part-specific subtype pattern A common ‘design pattern’ in GO If p is located in w 1 or w 2 then create part-specific subtypes: p-in-w 1 is_a p and part_of w 2 p-in-w 2 is_a p and part_of w 2 Cons: ‘ clutters up’ ontology but terms can be managed automatically using reasoner Annotators may not see subtypes and annotate too generally Easy to fix with correct tooling? Pros: greater discriminative power, more specific annotations Logically coherent, easy to implement rules Then why not implement this universally?
  • 6. Another example: erroneous use of part_of with complexes core TFIIH complex holo TFIIH complex NEF3 complex part_of TFB1 part_of we would not do this!!
  • 7. core TFIIH complex (CURRENT GO) core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a
  • 8. Problem: annotations to more generic term core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a
  • 9. Problem: additional semi-redundant annotations required to capture necessary gene products core TFIIH complex holo TFIIH complex NEF3 complex TFB1 part_of part_of core TFIIH portion of holo TFIIH complex core TFIIH portion of NEF3 complex is_a is_a TFB1 TFB1 ABF1 MGM101
  • 10. core TFIIH with has_part core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 Logically correct Can we propagate gene products?
  • 11. We would like to propagate gene products in this case – but can we do this universally ? core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 TFB1 TFB1
  • 12. thought experiment: use has_part for location-specific chromosomes chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
  • 13. no reliable propagation of gene products over has_part chromosome nucleus mitochondrion has_part has_part ABF1 MGM101 ABF1 MGM101 MGM101 ABF1
  • 14. So what’s the difference in ontology structure? core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
  • 15. So what’s the difference in ontology structure? there is no structural difference the computer needs some additional knowledge that is currently IMPLICIT core TFIIH complex holo TFIIH complex NEF3 complex has_part has_part TFB1 chromosome nucleus mitochondrion has_part has_part ABF1 MGM101
  • 16. What’s the difference in annotations? core TFIIH complex TFB1 chromosome ABF1 MGM101 SOME instances of MGM10 proteins are part of SOME chromosomes SOME instances of TFB1 proteins are part of SOME core TFIIH complexes
  • 17. What’s the difference in annotations? core TFIIH complex TFB1 chromosome ABF1 MGM101 SOME instances of MGM10 proteins are part of SOME chromosomes SOME instances of TFB1 proteins are part of SOME core TFIIH complexes ALL instances of core TFIIH complexes proteins has_part SOME TFB1 protein (in this species) TFB1 is integral to core TFIIH complex complex This crucial piece of knowledge is IMPLICIT NOT ALL instances of chromosome has_part SOME MGM10
  • 18. Solution Add additional qualifier to GAF name TBD. integral_to? Semantics: ALL instances of this complex in this species have this gene product as part This is stronger than an existing annotation: some instance of this gene product in this species are found in this complex Also works for BP ALL instances of this process in this species require this gene product Example: spermatogenesis, meiosis, MSH standard annotation: some instance of this gene product actively participate in this process Works using standard DL reasoning technology Requires change in annotation practice

Editor's Notes

  • #9: Problem: annotations to more generic term
  • #10: This is a big problem
  • #11: should we show all 5+ gene products
  • #12: should we show all 5+ gene products
  • #13: this is logically coherent
  • #14: we may not want to do this for this specific example; just illustrative