Difference between revisions of "Part:BBa K3788026"
(One intermediate revision by the same user not shown) | |||
Line 7: | Line 7: | ||
Sequence was optimised for E. coli K12. | Sequence was optimised for E. coli K12. | ||
+ | https://static.igem.org/mediawiki/parts/5/51/T--Aix-Marseille--Figure1_K3788026.jpeg | ||
− | |||
Figure coming from <i>The Autodisplay Story, from Discovery to Biotechnical and Biomedical Applications</i> | Figure coming from <i>The Autodisplay Story, from Discovery to Biotechnical and Biomedical Applications</i> |
Latest revision as of 16:05, 20 October 2021
pelB_sfGFP (without stop) _ aida-I
BBa_K3788026 is coding for pelB, sfGFP and AidaA. pelB is a leader sequence that allows the protein to join the periplasm via the SEC system (unfolded proteins). Aida-I, on the other hand, is an autotransporter from the T5SS; it allow the addressing to the extracellular medium. In this contruction sfGFP permit to understand the mechanism, this protein can at the end be replaced by an other protein. sfGFP is supposed to be addressed to the preriplasm thanks to pelB leader sequence and the T5SS system will address sfGFP to the extracellular medium by making it go through a beta-barrel that lead it outside of the cell and then to cleave it. Sequence was optimised for E. coli K12.
Figure coming from The Autodisplay Story, from Discovery to Biotechnical and Biomedical Applications
A. representation of the mRNA coding for an autotransporter system.
B. representation of the events of translation, folding in the periplasm and export of the passenger sequence to the extracellular medium.
This figure explains how is constituted a gene coding for an autotransporter such as aidaI. We replaced the signal peptide (SP) by PelB leader sequence and the passenger sequence by sfGFP sequence so that this protein should be transported to the periplasm and then pass to the extracellular medium by the autotransporter AidaI.
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal NgoMIV site found at 54
Illegal AgeI site found at 1864 - 1000INCOMPATIBLE WITH RFC[1000]Illegal SapI.rc site found at 79