Difference between revisions of "Part:BBa K257003:Design"
(→Design Notes) |
(→Design Notes) |
||
| Line 9: | Line 9: | ||
* In our project we use g3p as a fusion to OmpA-Linker (BBa_K103996) which need SacI restriction site for inframe fusion. | * In our project we use g3p as a fusion to OmpA-Linker (BBa_K103996) which need SacI restriction site for inframe fusion. | ||
* So we design g3p with SacI site at the N-terminal. SacI (GAGCT^C) site is shared with XbaI (T^CTAGA) in order to have SacI site for fusion and standard sites. | * So we design g3p with SacI site at the N-terminal. SacI (GAGCT^C) site is shared with XbaI (T^CTAGA) in order to have SacI site for fusion and standard sites. | ||
| + | |||
| + | The prefix used to create this parts conform to the std 10 guidelines for coding DNA. | ||
===Source=== | ===Source=== | ||
Latest revision as of 15:54, 21 October 2009
Outer membrane protein A (partial) fused to linker
Assembly Compatibility:
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000COMPATIBLE WITH RFC[1000]
Design Notes
- In our project we use g3p as a fusion to OmpA-Linker (BBa_K103996) which need SacI restriction site for inframe fusion.
- So we design g3p with SacI site at the N-terminal. SacI (GAGCT^C) site is shared with XbaI (T^CTAGA) in order to have SacI site for fusion and standard sites.
The prefix used to create this parts conform to the std 10 guidelines for coding DNA.
Source
Standardisation of BBa_K103006 from Warshaw 2008.