The BioBricks Foundation:RFC: Difference between revisions
No edit summary |
No edit summary |
||
Line 54: | Line 54: | ||
**[[Media:BBFRFC9.pdf | RFC Draft]] | **[[Media:BBFRFC9.pdf | RFC Draft]] | ||
** Tom Knight, Randall Rettberg, Leon Chan, Drew Endy, Reshma Shetty, Austin Che | ** Tom Knight, Randall Rettberg, Leon Chan, Drew Endy, Reshma Shetty, Austin Che | ||
* Draft standard for Biobrick biological parts | * BBF RFC<nowiki></nowiki> 10: Draft standard for Biobrick biological parts | ||
** Formal description of the initial Biobrick standard | ** Formal description of the initial Biobrick standard | ||
**[[The_BioBricks_Foundation:BBFRFC10| RFC Draft]] | |||
** Tom Knight, May 3, 2007 | ** Tom Knight, May 3, 2007 | ||
* BBF RFC 11: Biobrick assembly standard modifications | * BBF RFC<nowiki></nowiki> 11: Biobrick assembly standard modifications | ||
** Proposed modification of enzymes to facilitate protein fusions (SpeI/NheI replaces XbaI/SpeI) | ** Proposed modification of enzymes to facilitate protein fusions (SpeI/NheI replaces XbaI/SpeI) | ||
**[[Media:BBFRFC11.pdf | RFC Draft]] | **[[Media:BBFRFC11.pdf | RFC Draft]] | ||
** Tom Knight, July 8, 2008 | ** Tom Knight, July 8, 2008 | ||
* BBF | * BBF RFC<nowiki></nowiki> 12: Draft Biobrick BB-2 standard for biological parts | ||
** Formal description of the Biobrick BB-2 standard | ** Formal description of the Biobrick BB-2 standard | ||
**[[The_BioBricks_Foundation:BBFRFC12 |RFC draft]] | |||
** Tom Knight, November 19, 2008 | ** Tom Knight, November 19, 2008 | ||
* BBF | * BBF RFC<nowiki></nowiki> 13: Rethinking the boundaries and composition of coding regions | ||
** Logical split of the protein coding region into domains - [[BBRFC13 | RFC draft]] | ** Logical split of the protein coding region into domains - [[BBRFC13 | RFC draft]] | ||
** Tom Knight | ** Tom Knight | ||
Line 70: | Line 72: | ||
** Application of the RFC13 ideas to assembly with BB-2 - [[BBRFC14 | RFC draft]] | ** Application of the RFC13 ideas to assembly with BB-2 - [[BBRFC14 | RFC draft]] | ||
** Tom Knight | ** Tom Knight | ||
* | * BBF RFC 15: Innovations Mean Nothing Unless You Use Them -- The New BioScaffold Family of BioBrick Parts To Enable Manipulations Such as Protein Fusions, Library Construction, and Part Domestication | ||
**[[The BioBricks Foundation:BBFRFC15 | RFC Draft]] | |||
**by Julie Norville, Angela Belcher and Tom Knight | **by Julie Norville, Angela Belcher and Tom Knight | ||
* BBF RFC 16: BioBrick Open Graphical Language (BOGL) | * BBF RFC 16: BioBrick Open Graphical Language (BOGL) | ||
Line 76: | Line 79: | ||
* BBF RFC 17: BioBrick Open Language (BOL) | * BBF RFC 17: BioBrick Open Language (BOL) | ||
** requested by Cesar A. Rodriguez, Herbert M. Sauro and Drew Endy | ** requested by Cesar A. Rodriguez, Herbert M. Sauro and Drew Endy | ||
* | * BBF RFC 18: Proposed Conceptual Guidelines for the Design of a BioBrick Graphical Language & an Example | ||
** Eric Fernandez | ** by Eric Fernandez | ||
**[http://hdl.handle.net/1721.1/44640 DSpace], [http://dspace.mit.edu/bitstream/handle/1721.1/44640/BBF_RFC_18.pdf PDF] (direct link), doi: 1721.1/44640 | **[http://hdl.handle.net/1721.1/44640 DSpace], [http://dspace.mit.edu/bitstream/handle/1721.1/44640/BBF_RFC_18.pdf PDF] (direct link), doi: 1721.1/44640 | ||
**[[BBRFC18 | Add comments here]] | |||
* BBF RFC 19: Measuring the Activity of BioBrick Promoters Using an In Vivo Reference Standard | * BBF RFC 19: Measuring the Activity of BioBrick Promoters Using an In Vivo Reference Standard | ||
**requested by Jason R Kelly and Drew Endy | **requested by Jason R Kelly and Drew Endy | ||
Line 89: | Line 93: | ||
**requested by Julie Norville, Angela Belcher and Tom Knight | **requested by Julie Norville, Angela Belcher and Tom Knight | ||
* BBF RFC 23: A New Biobrick Assembly Strategy Designed for Facile Protein Engineering | * BBF RFC 23: A New Biobrick Assembly Strategy Designed for Facile Protein Engineering | ||
**requested Ira Phillips and Pamela Silver | **requested by Ira Phillips and Pamela Silver | ||
**Original technical report available at [http://hdl.handle.net/1721.1/32535 DSpace], [http://dspace.mit.edu/bitstream/handle/1721.1/32535/PhillipsSilverFusion.pdf?sequence=1 PDF] (direct link) | **Original technical report available at [http://hdl.handle.net/1721.1/32535 DSpace], [http://dspace.mit.edu/bitstream/handle/1721.1/32535/PhillipsSilverFusion.pdf?sequence=1 PDF] (direct link) | ||
* BBF RFC 24: Conversion of Freiburg (Fusion) Biobricks to the Silver (BioFusion) format | * BBF RFC 24: Conversion of Freiburg (Fusion) Biobricks to the Silver (BioFusion) format |
Revision as of 11:23, 30 March 2009
RFCs An RFC might
RFC's are static documents or digital objects like video's intended to get an idea, proposed standard, or method out to the rest of the community for comment. RFC's are numbered, for ease of referencing, and the numbers are assigned by the BBF. Instructions for requesting a BBF RFC number, preparing an RFC, and submitting an RFC to the BBF are described in BBF RFC 0.
The complete list of all assigned RFC numbers and RFC documents (for those submitted) is listed below.
|