Team:Cambridge/Gibson/RFC

From 2010.igem.org

(Difference between revisions)
 
(4 intermediate revisions not shown)
Line 1: Line 1:
{{:Team:Cambridge/Templates/headerMinimalprototype}}
{{:Team:Cambridge/Templates/headerMinimalprototype}}
{{:Team:Cambridge/Templates/headerbar|colour=#fb5c2b|title=Gibson Assembly: RFC}}
{{:Team:Cambridge/Templates/headerbar|colour=#fb5c2b|title=Gibson Assembly: RFC}}
-
{{:Team:Cambridge/Templates/RightImage|image=Cambridge-RFC.JPG|caption=RFC-57, submitted by the Cambridge team}}
+
{{:Team:Cambridge/Templates/RightImage|image=Cambridge-RFC.JPG|caption=[http://www.cambridgeigem.org/RFC57.pdf RFC 57], submitted by the Cambridge team}}
-
The BioBrick foundation uses documents known as RFCs to document standard techniques in synthetic biology.  Until now no such RFC existed for Gibson Assembly.  The Cambridge team created such a document, providing standard protocols for the technique.
+
The [http://bbf.openwetware.org/ BioBrick Foundation] uses documents known as [http://bbf.openwetware.org/RFC.html RFC]s to document standard techniques in synthetic biology.  Until now no such RFC existed for Gibson Assembly.  The Cambridge team created [http://www.cambridgeigem.org/RFC57.pdf '''RFC 57'''] to provide standard protocols for the technique.
 +
 +
Gibson assembly allows joining any sequences using appropriate overlaps. As no restriction enzymes are used, this assembly method technically does not require the assembled parts to be in BioBrick format. It must however be emphasised that it is still necessary to comply with existing RFCs in terms of prefixes, suffixes and illegal sites for all new parts that are entered into the registry. Gibson assembly can be used as an alternative to BioBrick Standard Assembly, while retaining full backwards compatibility.
{{:Team:Cambridge/Templates/footer}}
{{:Team:Cambridge/Templates/footer}}

Latest revision as of 16:57, 27 October 2010