-
Notifications
You must be signed in to change notification settings - Fork 2
Is transports\_or\_maintains\_localization\_of needed for MF AE? #8
Comments
Using the transports relation for MFs follows patterns used in ontology => correct folding. e.g. of term in ontolgy: May be a case for pushing annotators to use TermGenie templates here? |
Hi David thanks for breaking down all these queries. Great to have this use confirmed. Our problem is that the information associated with this relationship is incomplete: I don't understand what the subsets are supposed to refer to, and I would question the inclusion of GO:cellular_component, as many of these should be 'moved' using the relationship 'results_in_movement_of' see very end of message. When revising the documentation for transports_or_maintains_localization_of, would it be possible too provide a more specific GO CC term such as GO:0032991 macromolecular complex? This would also help with limiting the use of this relationship in the Protein2GO tool. To be honest I am not sure why there needs to be these 2 relationships: If keeping both relationships is a definite final decision I will create the wiki page with MF and BP examples of use and errors in use. I'll wait for your confirmation before proceeding with this though. Best Ruth Compared with documentation for |
(Ticket extracted from notes written by @RLovering & Rachael Huntley)
Looks like this is for processes only therefore annotations of transporters (MF) keep as has_direct_input ?
The text was updated successfully, but these errors were encountered: