Relations to link MF to BP in GO-CAMs and annotations

[pgaudet]

Project link

https://github.com/orgs/geneontology/projects/130

Project description

Continuing the work on https://github.com/geneontology/project-management/issues/7 where relations to link MF to MF were refined and usage was documented. This project will document usage of MF to BP relations, including examples, and update RO if needed.

PI

Paul

Product owner (PO)

Kimberly

Technical lead (TL)

NA

Other personnel (OP)

David, Jim, Pascale

Technical specs

TBD (template: https://docs.google.com/document/d/111UqtS3G0aJZpAijZYI3Da0t94OQpGePlPJsqZE4Tio/edit)

Other comments

N/A

[vanaukenk]

• [x] Review SheX for MF shape
• [x] Document MF to BP for GO-CAMs (causal models)
• [x] Document MF to BP for standard annotation (annotation extensions)
• [ ] Update Protein2GO to reflect current guidelines (this will be rolled into the gorel retirement project)
• [ ] Review and clean up existing annotations that don't conform to current guidelines (this will be moved to a separate, complementary project in the go-annotation tracker)

[kltm]

@vanaukenk Just to confirm: there is no TL or technical doc needed here, right?

[pgaudet]

GORELs left in Noctua graph: are these being used?

• results_in (obo:GOREL_0000040)
• results_in_division_of (obo:GOREL_0001019)
• results in distribution of (obo:GOREL_0002003)
• results_in_fission_of (obo:GOREL_0002004)
• results_in_maintenance_of (obo:GOREL_0012006)
• lego relation (obo:LEGOREL_0000000)

Note that there are 2 GORELs in Noctua graph for which there is a RO ID:

• acts_on_population_of (obo:GOREL_0001006) RO_0012003
• results_in_fusion_of (obo:GOREL_0002005) RO_0012008

@balhoff can you help us by querying the GO-CAM data store for any models that use any gorel relation? We're close to retiring gorel, so will want to clean up any remaining gorel relations that have been used in Noctua.

See: https://github.com/geneontology/project-management/issues/51