H3K4me3 in promoter regions, which are free of nucleosomes
1
0
Entering edit mode
4.7 years ago

Hello!

I'm trying to deal with histone mark and their localization on the genome. I read that marks H3K4me3 are localized in the promoter regions. But I know that promoters are free of nucleosomes. How is this possible? Do I understand correctly that the presence of histone marks from an experiment Chip-seq means the presence of a nucleosome in this region? I read several articles, but did not find the answer.

I will be glad to any answer, especially useful articles on this topic.

H3K4me3 promoter nucleosome ChIP-Seq • 2.8k views
ADD COMMENT
1
Entering edit mode
4.7 years ago
ATpoint 81k

Promoters are not free of nucleosomes but there is a nucleosome-free stretch of DNA at which the DNA-binding machinery assembles. This is flanked by histones that undergo modifications at, e.g. their lysin tails (K4).

enter image description here

ADD COMMENT
0
Entering edit mode

Thank you very much! It becomes clearer. So, is it true that the data from the Chip-seq experiment correspond to the active state? Or is it an inactive state, but with histone marks that are there all the time?

ADD REPLY
1
Entering edit mode

There is some research that has found H3K4me3 is generally found in all high CpG promoters (the majority in human) regardless of transcriptional activity, but are only present at low CpG promoters when the gene is actively transcribed (https://www.nature.com/articles/nature06008 ). H3K27ac may be more predictive of active transcription at promoters/TSS than H3K4me3 (see https://www.pnas.org/content/107/7/2926 ).

ADD REPLY
0
Entering edit mode

Thank you for these articles! Exactly what is needed!

ADD REPLY
0
Entering edit mode

From what I understand H3K4me3 is often referred to as a "promoter mark", even though it boils down to an indication for active transcription.

ADD REPLY

Login before adding your answer.

Traffic: 1575 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6