Ontology meeting 2022-02-14
- Group members: Pascale, Karen, Harold, Raymond, Peter, Jim, Tanya, Kimberly, David, Chris, Paul
- Present: Pascale, Karen, Harold, Raymond, Peter, Jim, Tanya, Kimberly, Chris,
- Regrets: Paul, David
Announcements
Discussion points
Definitions
Cardiac jelly development: https://github.com/geneontology/go-ontology/issues/22616
- For now: add more text as recommended by Ruth
- Ideally, terms from external ontology would be shown somehow to users, see https://github.com/geneontology/go-ontology/issues/22866
Ontology Curator Pathway book
Chris Book by Nico Matentzoglu & others https://oboacademy.github.io/obook/
In particular this section: https://oboacademy.github.io/obook/pathways/ontology-curator/
InterPro file out of date
See ticket https://github.com/geneontology/go-site/issues/1786 and https://github.com/geneontology/goontology/blob/7e1c1691c31dfc25b4ce6149c016c1c188d98683/src/ontology/Makefile
The file generated by InterPro is more recent: https://ftp.ebi.ac.uk/pub/databases/interpro/interpro2go
Actions
- Change the Makefile (in go-ontology/src/ontology/Makefile )
- Check with InterPro for mappings of the databases they represent - are these maintained ? See also: https://github.com/geneontology/go-ontology/issues/16989
Next calls
Focus on specific topics?
- taxon constraints
- boomer tickets
- any other suggestion
- relations - review work that needs to be done for 'transports or maintains localization of' as outlined in ticket
Other Business
https://github.com/geneontology/go-ontology/projects/1
Points from previous meetings not yet addressed
Next Priorities for Ontology group
- GO-RHEA:
- Finish Boomer tickets
- strategy to create new GO terms
- New taxon constraints
- Review single step BPs + BP refactoring
- Jamboree to close tickets?
- Design patterns: implement new design patterns and enforce usage in the ontology
- Ongoing:
- Multi-org
- transcription
- roles
- aging
- Content meetings?
Following up on previous items
- ChEBI: Chris, Paul: Make a list of requests for ChEBI - including requesting 'developer' versions of ChEBI so we can test it ahead of releases
- Design patterns
- DONE Pascale: document how to deal with 'conforms to dp' during term obsoletion and merge - updated Obsoleting_an_Existing_Ontology_Term and Merging_Ontology_Terms pages
Changing the relation for transport and transporter activity from 'transports or maintains localization of' to 'has input'
- ACTIONS Decision is to use 'has primary input' -> https://github.com/geneontology/go-ontology/issues/22721
- See ticket for outline of steps needed to implement.
New taxon constraints
Property range violations
- Looks like an issue in GO, where 'cavity development' may be redundant with the equivalent 'tube' terms, or the 'tube terms are missing'?
ACTIONS: Review 'cavity terms
- subarachnoid space development | subarachnoid space
- tube lumen cavitation | tube lumen: https://github.com/geneontology/go-ontology/issues/22784
- neural rod cavitation | neural tube lumen: https://github.com/geneontology/go-ontology/issues/22784
- pronephric sinus development | pronephric sinus: see https://github.com/obophenotype/uberon/issues/2274
- 'neural rod cavitation' <http://purl.obolibrary.org/obo/GO_0014024>
- 'tube lumen cavitation' <http://purl.obolibrary.org/obo/GO_0060605>
- 'salivary gland cavitation' <http://purl.obolibrary.org/obo/GO_0060662> (no LD, so not causing problems in Jim's PR, but still needs reviewing)
- 'mammary gland duct cavitation' <http://purl.obolibrary.org/obo/GO_0060604> (no LD, so not causing problems in Jim's PR, but still needs reviewing)
- 'regulation of tube lumen cavitation' <http://purl.obolibrary.org/obo/GO_1903132>
- 'secondary neural tube rod cavitation' <http://purl.obolibrary.org/obo/GO_0014027>
- 'negative regulation of tube lumen cavitation' <http://purl.obolibrary.org/obo/GO_1903133>
- 'apoptotic process involved in tube lumen cavitation' <http://purl.obolibrary.org/obo/GO_0060609>
- 'apoptotic process involved in salivary gland cavitation' <http://purl.obolibrary.org/obo/GO_0060663>
Sinus terms: Not sure why only 'pronephric sinus development' is causing problems others do have LDs:
Chris: only 'pronephric sinus development' describes a sinus; other describe valves, venosus
- 'sinus venosus development' <http://purl.obolibrary.org/obo/GO_0003235>
- 'sinus venosus formation' <http://purl.obolibrary.org/obo/GO_0003237>
- 'sinus venosus morphogenesis' <http://purl.obolibrary.org/obo/GO_0003236>
- 'coronary sinus valve development' <http://purl.obolibrary.org/obo/GO_0003178>
- 'coronary sinus valve formation' <http://purl.obolibrary.org/obo/GO_0003191>
- 'coronary sinus valve morphogenesis' <http://purl.obolibrary.org/obo/GO_0003182>
- 'pronephric sinus development' <http://purl.obolibrary.org/obo/GO_0039012>
- 'left horn of sinus venosus development' <http://purl.obolibrary.org/obo/GO_0061079>
- 'right horn of sinus venosus development' <http://purl.obolibrary.org/obo/GO_0061080>
Protein-complex organization/assembly/disassembly
Problem with relations used in logical definition https://github.com/geneontology/go-ontology/issues/22488
RO has been changed, so that the logical issue is fixed; however do we want to use 'results in assembly of' or 'has output' for protein-containing complex assembly? This decision impacts the relations used in GO-CAM and extensions, since we aim to align them.