-
Notifications
You must be signed in to change notification settings - Fork 39
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
intra/extracellular ribonucleoprotein complex, merge? #15303
Comments
How about
|
That works. |
+1 |
Dear all, The proposal has been made to obsolete 'GO:1990903 extracellular ribonucleoprotein complex’. The reason for obsoletion is that there are no known extracellular ribonucleoprotein complexes. There are no annotations or mappings to this term. Any comments can be added to this issue: #15303 We are opening a comment period for this proposed obsoletion. We'd like to proceed and obsolete this term on March 16, 2018. Unless objections are received by March 16, 2018 we will assume that you agree to this change. Thanks, Pascale |
merged intracellular ribonucleoprotein complex into parent for #15303
|
@pgaudet |
Hi @paolaroncaglia sure, no worries. The difficulty is that there is no reference, and I cannot find anything in google. Let me know. Best wishes, Pascale |
ribonucleoprotein complex (or specific child) occurs_in(extracellular vesicle)? |
GO:1990903 ‘extracellular ribonucleoprotein complex’ was added in 2015 as part of the extracellular vesicles/exRNA project. The project resulted in a publication (https://www.ncbi.nlm.nih.gov/pubmed/27076901). I’m not sure why a reference was not provided by the experts at the time I was adding the terms, but figure 1 in our paper points to PMID:21383194 for ‘extracellular ribonucleoprotein complex’. I had a brief look and that sounds quite sensible. What’s more, GO:1990903 ‘extracellular ribonucleoprotein complex’ is explicitly shown in figure 2 (“The list of exRNA-related terms, synonyms and relationships that have been added to GO”). The paper is less than 2 years old; we should probably keep that term.
Lastly, a general comment. The fact that that term was created as part of a focused ontology project is visible from its dbxref ‘GOC:vesicle’. In similar cases, when feasible, I’d suggest checking directly with the editor(s) who was/were responsible for the specific project. I don’t look at all GO GitHub tickets anymore for obvious reasons, so it was only the obsoletion email that drew my attention. If my suggestions above end up being accepted, I could have saved Pascale some time. Thanks, and a nice weekend to all :-) |
I will also chime in here. The collaboration with GOA and ExoCarta/Vesiclepedia is still ongoing. Seeing as this is an active collaboration, I think we should keep the term. |
Hi @ggeorghiou @paolaroncaglia Thanks for the feedback. ‘extracellular ribonucleoprotein complex’ is odd in that there is no equivalent term for extracellular protein complex. All I could find is 'GO:1990563 extracellular exosome complex', which is a direct child of extracellular space. So if this miRNA-protein complex is important, I could rename the term 'GO:1990903 ‘extracellular ribonucleoprotein complex’ as such and add the reference. Would that be an acceptable compromise? It seems to me that the grouping term (extracellular ribonucleoprotein complex) is unnecessary and inconsistent with the current structure of the ontology. Thanks, Pascale |
Hi @pgaudet , I’d still prefer to keep the general term ‘extracellular ribonucleoprotein complex’, on the grounds that the extracellular RNA community considered it important to have as such in the ontology. Our paper describes the process that many members of that community went through to find consensus on terms they wished to be in GO, so it’s not like one single person asked for the term without thinking too much about it. I can relate to the dislike of not having a ’symmetrical’ ‘extracellular protein complex’ term ;-), but clearly the presence of ‘extracellular ribonucleoprotein complex' reflects the wish of one particular community we serve, rather than the broader way we try to have regular patterns in GO. Also, an implication of what @ggeorghiou wrote is that ExoCarta/Vesiclepedia are still in the process of getting their annotations in shape for submission to GO. I’m no longer involved in that, but I suspect that they may well be using/have used ‘extracellular ribonucleoprotein complex’ already. Thanks, |
But we only add complexes to GO if there is functional information, and there is no functional information in PMID:21383194, so we would not annotate that complex in GO? The authors say quite clearly in the abstract: So, we should wait for evidence for such a role, otherwise it will make much work for later...There is enough to do (and too much to fix), already. v |
@ValWood @pgaudet |
For the records: I emailed Kei-Hoi Cheung, Louise Laurent and Shivakumar Keerthikumar today. |
Question for editors: the pattern 'organelle x complex' is not widely used; most of the instances I found are when a complex type exists in two different organelles, for example 'mitochondrial DNA-directed RNA polymerase complex', under 'mitochondrial protein complex' (there is no equivalent 'nuclear protein complex grouping term, but there is a term 'nuclear DNA-directed RNA polymerase complex'). In which direction do we want to go? It seems difficult to classify complexes based on where they are located. Thanks, Pascale |
Good question, Pascale. |
My opinion is point 2 here ;) I don't think we need a grouping term for 'mitochondrial protein complex' I also think we should get rid of organelle specific instances of identical complexes (i.e nuclear proteasome, cytosolic proteasome), and use extensions. |
@ValWood The alternative (keeping organelle-specific grouping terms) seems unmaintainable. |
...and unnecessary. If the same complex is found in multiple locations, an occurs_in extension works best ( and a co-annotation to the location, but this could be inferred longer term...) |
@ValWood @pgaudet @bmeldal |
Hi paola, The point was that there was no evidence for functional significance of this particular association at present which is a pre-requisite for a complex in GO.... This abstract says: Could you ask about functional significance? |
Hi @ValWood, |
Hi @paolaroncaglia, I'm only trying to establish if there is any additional evidence to provide biological justification for keeping the term (i.e any other RNA complex, or publication that we overlooked). So far, we have only established that none of the papers supplied so far describe the existence of an ‘extracellular ribonucleoprotein complex’ with a biological role, so there does not seem to be, based on the current data. It does not even appear to be part of the extracellular exosome according to the authors who clearly state in the abstract: This term does not fit normal design pattern (see above). GO is not a static resource, so inclusion in a paper (GOC or not) does not seem to be a valid reason to keep a term which is not biologically meaningful, and would not be used in annotation? I'm sure we all have publications with obsoleted terms by now ;) |
Hi @ValWood As I mentioned before, we have an ongoing collaboration with Vesiclepedia/ExoCarta. I am still waiting to hear back from them regarding how their GO annotations are progressing, but given the deadline for deciding what to do with these terms, I am going to have a look at a previous GPAD they have sent us to see how the term has been used and where it has been referenced. Seeing as they do not have the opportunity to hear about changes to the GO unless we feed it back to them, I ask for a bit of time to allow them to update us and see if this term is still useful to them. There may be annotations that support this term being kept and I would hate for them to not have their say. |
Hi @ValWood, |
Waiting to see the data submission is a good plan...there is no hurry. Other extracellular terms are not affected as they are functionally relevant. |
Hello, I see at least two issues being discussed here:
WRT the first point: in GO we have only two grouping terms by organelle for protein complexes, 'extracellular ribonucleoprotein' and 'mitochondrial protein complex'. @paolaroncaglia So, are you OK with renaming ''extracellular ribonucleoprotein' to extracellular miRNA-protein complex', and adding the reference you mentioned ? Thanks, Pascale |
Yes, we said we need to have at least some idea of its function to curate a complex. In many cases we know it exists and which process it affects but don't know its actual MF so we just annotate to BP. But we can say something about its role.
There are more, like GO:0098796 membrane protein complex. They were introduced by David OS for grouping and logical defs. We have a call in a little over an hour! |
Thanks @bmeldal, this is useful. We didn't manage to discuss this at the last call - I would still like to get clarification from the editors about what GO captures WRT complexes: from #12782 I thought we wanted to have as little overhead as possible in managing protein complexes, which is why I merged 'protein complex' into 'macromolecular complex'. To be consistent with that logic we should NOT classify complexes by organelle/localization either. Thanks, Pascale |
As I have said before. I am always concerned when we make changes or remove terms that have resulted from consulting experts in a field. |
I agree David, but this case is a bit different, as these terms were not proposed by experts for functional annotation but for experiment metadata annotation. Are the exosome terms labeled in the ontology? Maybe we need a GO-function-slim to support our major use case, that would exclude the exosome terms unless they've been demonstrated to be functionally relevant. |
Also - I am not disputing the term, but the impact on the ontology structure. I would expect the experts did not take that into account when proposing terms - right? |
From the papers supplied for this particular term, the authors say that is likely a result of |
Editors discussion March 19:
|
So @paolaroncaglia : since you already published the ID I can merge the term 'extracellular ribonucleoprotein complex' into the parent 'ribonucleoprotein complex', or rename it 'extracellular miRNA-Ago2 complex' (@bmeldal would that be a valid term?) Thanks, Pascale |
Hi all, in reply to some of your questions: @pgaudet wrote Actually, looking at figures 1 and 2 in https://www.ncbi.nlm.nih.gov/pubmed/27076901, they did put some thought into the ontology structure. Sure, you may still consider them less ‘ontology conscious’ than professional GO editors. See below for other comments please. @thomaspd wrote GO:0070062 ‘extracellular exosome’ is not labeled not-for-annotation, but the whole point of exosome research from the past few years is exactly that (at least some) extracellular vesicles seem to play roles in cancer and other diseases… How to differentiate functionally relevant exosomes from ones that aren’t, in the ontology, is a complex discussion that I’m not going into now :-) I agree that the miRNA-Ago2 complex doesn’t come with good functional evidence in the 2 papers we know of (in response to @ValWood “From the papers supplied for this particular term, the authors say that is likely a result of "in the most part by-products of dead cells that remain in extracellular space due to the high stability of the Ago2" so this isn't exosome.”). So ok with merging 'extracellular ribonucleoprotein complex' into its parent 'ribonucleoprotein complex’. Paola |
merged extracellular ribonucleoprotein complex into parent fixes #15303
do we need?
GO:1990903 extracellular ribonucleoprotein complex | is_a
GO:0030529 intracellular ribonucleoprotein complex
extracellular has no annotations....
The text was updated successfully, but these errors were encountered: