Added parser for the KinAce database of kinase-substrate phosphorylat…

[beasleyjonm]

…ion reactions.

I submitted a request to update infores with KinAce database, so the edges won't normalize until that is updated.

[EvanDietzMorris]

we might want to use this as the predicate: RO:0002447
right now it normalizes to directly_physically_interacts_with, whereas biolink:phosphorylates would just be related_to

then we could work on getting biolink model to adopt phosphorylates with RO:0002447 as a mapping if we want

[beasleyjonm]

I definitely think we want to have “phosphorylates” as its own relationship in Biolink because directly_physically_interacts_with isn’t specific enough. I’ll take a look at trying to add this to Biolink today. From: Evan Morris ***@***.***> Sent: Monday, March 11, 2024 10:47 AM To: RobokopU24/ORION ***@***.***> Cc: Beasley, Jon-Michael ***@***.***>; Author ***@***.***> Subject: Re: [RobokopU24/ORION] Added parser for the KinAce database of kinase-substrate phosphorylat… (PR #205) we might want to use this as the predicate: RO:0002447 right now it normalizes to directly_physically_interacts_with, whereas biolink:phosphorylates would just be related_to then we could work on getting biolink model to adopt phosphorylates with RO:0002447 as a mapping if we want — Reply to this email directly, view it on GitHub<#205 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUNCRUMIDU3SQJTSMNTFWUDYXXGXDAVCNFSM6AAAAABEQNDA3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGYYTMOBVGI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[EvanDietzMorris]

that's the nice part about using a different ontology, especially RO - because it's more resilient to changes in the biolink model.. if we put in a biolink model predicate directly it might break, but the mappings for RO should in theory only get better over time (assuming the RO doesn't change hah)