In GO we use SO to refer to the various types of transcript that arre the input and output transcription and transcript maturation. We also need to be able of distinguish process acting on RNA that lead to its maturation from processes that do not. SO currently almost fulfills our needs, but not quite.
You currently have:
transcript
. % mature transcript
. . % mRNA
. . % ncRNA
. . . % rRNA
. % primary transcript
. % protein_coding_primary_transcript
. . % nc_primary_transcript
. . . etc
If you also had terms for immature transcripts and perhaps also terms that are neutral as to maturation state, this would make our axiomatisation much easier, more complete and more useful for automated classification. However, I can see that, if you did this, you would also need a way to keep these various semi-duplicate branches in sync. At the risk of circularity, refering to some GO process terms might help. Happy to a meeting to discuss how you could do that.
Grr, sourceforge lost my original comment... concise version below:
Pre versions exist for many, see figure, relationships don't seem to be applied consistently.
Adding neutral groupings may be a bigger change, do this on a branch first?
Primary transcript versions are there, but these refer to transcripts prior to splicing. No terms for post-splicing immature transcripts (e.g. immature mRNA - prior to capping and polyadenylation.) Didn't realise there were derives_from relations. Could be useful.
We still need to have that phone call.