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

Make design pattern and template for nuclear receptor #42

Open
dosumis opened this issue Feb 17, 2017 · 4 comments
Open

Make design pattern and template for nuclear receptor #42

dosumis opened this issue Feb 17, 2017 · 4 comments

Comments

@dosumis
Copy link
Contributor

dosumis commented Feb 17, 2017

General classification for ligand activated transcription factors:
https://en.wikipedia.org/wiki/Nuclear_receptor

Dependency: Needs pattern for (DNA binding) transcription factor activity first

@thomaspd
Copy link

A start:

has_part ligand binding occurs in cytosol
activates
has_part transcription factor activity occurs in nucleus

@dosumis
Copy link
Contributor Author

dosumis commented Feb 20, 2017

Some notes on what we have

We have no single term for nuclear receptors. We do have:

"RNA polymerase II transcription factor activity, ligand-activated sequence-specific DNA binding" ; GO:0004879
'ligand-activated RNA polymerase II transcription factor binding transcription factor activity" ; GO:0038049'

These have related synonym: 'nuclear receptor activity'. Neither of these terms maps up to receptor, although all subclasses do.

The second term seems dubious. There is only a single annotation with experimental evidence in this branch: UniProtKB P04150 NR3C1 GO:0038051 PMID:17635946. As far as I can gather, all nuclear receptors bind DNA and most also bind co-activators etc. This term was probably intended to capture the latter activity, but that's certainly not how it's being used.

Proposal: Collapse this down into a single class

'nuclear receptor activity' EquivalentTo 'receptor activity' that has_effector some 'sequence-specific DNA binding transcription factor activity'

If we want to capture the cofactor/TF binding activity this can be done in LEGO at annotation time. We could also consider adding a specific term for the binding event in question.

@dosumis
Copy link
Contributor Author

dosumis commented Feb 20, 2017

General policy issue: In defining molecular transducer (#31 ), we suggested a pattern in which the effector function was a biochemical activity. In this case we have a compound function as an effector. The molecular transducer pattern should therefore be broadened. We should also make it an explicit policy that we can nest compound functions. This needs to be taken into account when designing LEGO -> GPAD inference rules.

@pgaudet
Copy link
Contributor

pgaudet commented Mar 25, 2019

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

No branches or pull requests

3 participants