Skip to content
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

RNA helicase EC issue #29781

Open
sjm41 opened this issue Feb 24, 2025 · 0 comments
Open

RNA helicase EC issue #29781

sjm41 opened this issue Feb 24, 2025 · 0 comments

Comments

@sjm41
Copy link
Contributor

sjm41 commented Feb 24, 2025

GO currently has this hierarchy, which appears to conflict with the EC hierarchy:

RNA helicase activity (GO:0003724) xref: EC:3.6.4.13
    |_5'-3' RNA helicase activity (GO:0032574) xref: EC:5.6.2.5
    |_3'-5' RNA helicase activity (GO:0034458) xref: EC:5.6.2.6

id: GO:0003724
name: RNA helicase activity
namespace: molecular_function
alt_id: GO:0004004
def: "Unwinding of an RNA helix, driven by ATP hydrolysis." [GOC:jl, PMID:19158098]
synonym: "ATP-dependent RNA helicase activity" EXACT []
xref: EC:3.6.4.13
xref: MetaCyc:RXN-11109
is_a: GO:0004386 ! helicase activity
is_a: GO:0140098 ! catalytic activity, acting on RNA
property_value: term_tracker_item "#21612" xsd:anyURI

The GO:0003724 term is using the EC xref from EXPASY/ENZYME:
https://enzyme.expasy.org/EC/3.6.4.13
EC 3.6.4.13
Accepted Name: RNA helicase
Reaction: ATP + H2O = ADP + phosphate + H(+)

But in ExplorEnz (the official IUBMB source), we see EC:3.6.4.13 was transferred and deleted in 2024:
https://www.enzyme-database.org/query.php?ec=3.6.4.13
EC | 3.6.4.13
Transferred entry: Now covered by EC 5.6.2.5, RNA 5′-3′ helicase, EC 5.6.2.6, RNA 3′-5′ helicase and EC 5.6.2.7, DEAD-box RNA helicase

So, as we've discussed before, this is a specific (probably extreme) example of the occasional discrepancy between EXPASY/ENZYME and ExplorEnz.
And again raises the question of which EC source should be used by GO.

Simple solution here would be to just remove EC:3.6.4.13 from GO:0003724.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant