Taxon constraint: JUN kinase activity

[ValWood]

Please provide as much information as you can:

• GO term ID label:

GO:0004705 | JUN kinase activity | IEA with 2.7.11.24

• Request to add a taxon constraint:

• • **only in taxon: **
• • **never in taxon: **

never in yeast (need to check this) @edwong57 do you agree?

• Request to remove a taxon constraint:
  Please specify

• Supporting evidence if available (e.g PMID):

[edwong57]

@ValWood, yes, this seems fine.

[cmungall]

no objection to the constraint but if this is done to prevent false propagation from EC this should not be necessary as the EC term is broader than the GO term, cc @balhoff

…

On Thu, Oct 24, 2024 at 5:56 AM Val Wood ***@***.***> wrote: Please provide as much information as you can: - *GO term ID label:* GO:0004705 | JUN kinase activity | IEA with 2.7.11.24 - *Request to add a taxon constraint:* - - **only in taxon: ** - - **never in taxon: ** never in yeast (need to check this) @edwong57 <https://github.com/edwong57> do you agree? - *Request to remove a taxon constraint:* Please specify - *Supporting evidence if available (e.g PMID):* — Reply to this email directly, view it on GitHub <#29099>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMMOKZ3PCADJUI6JMWRNTZ5DU63AVCNFSM6AAAAABQRA7DA2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYTCNJQHEZDCMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ValWood]

propagation from EC this should not be necessary as the EC term is broader

but the EC itself would not be blocked and isn't used for the taxon contains. Isn't the broad EC a separate unrelated issue?

[cmungall]

My point is that if you see

GO:0004705 | JUN kinase activity | IEA with 2.7.11.24

There is a bug in someone's EC2GO propagation as this should never propagate as we should never propagate broad to narrow

[pgaudet]

I agree. I made the ticket high priority: #28763

[ValWood]

I'll close this then since it should get fixed by another route