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

how to represent post translational modifications #47

Closed
goodb opened this issue Feb 12, 2019 · 2 comments
Closed

how to represent post translational modifications #47

goodb opened this issue Feb 12, 2019 · 2 comments
Assignees
Labels

Comments

@goodb
Copy link
Contributor

goodb commented Feb 12, 2019

Reactome has entities like p-2T-MAP2K1 that are combinations of proteins with different modifications. For p-2T-MAP2K1 it is actually a set of two proteins with the same id (UniProt:Q02750) but with different PTMs.

Currently the GO-CAM view of this entity is a single instance of a UniProt:Q02750 without any PTM information. This leads to representations of function/reaction nodes that have the same entities as both input and output (apart from ATP->ADP).

Is this a desirable representation for GO-CAM models?

Note that the BioPAX export does contain information about the specific sequence locations that are modified. In principal, this information could be captured in the GO-CAM model.

@goodb
Copy link
Contributor Author

goodb commented Sep 17, 2019

Noting here that I have currently adopted the pattern applied by PRO for capturing modifications in the reactome entity ontology (reo). PRO and REO consider modified forms of proteins subclasses of the canonical protein, distinguished by the addition of subclass_of (has_part modification class) axioms. Modification classes come from the protein modification ontology http://purl.obolibrary.org/obo/mod.owl .

@goodb
Copy link
Contributor Author

goodb commented Oct 14, 2019

Conversion to use of reactome entities closes this issue (in the context of the go-cams). May re-emerge during specific export processes but those will be new issues.

@goodb goodb closed this as completed Oct 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants