The BioBricks Foundation:RFC: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
No edit summary
Line 60: Line 60:
** 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
* 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
** Julie Norville, Angela Belcher and Tom Knight
** requested by Julie Norville, Angela Belcher and Tom Knight


</div>
</div>

Revision as of 16:14, 2 December 2008


RFCs

The BioBricks Foundation is dedicated to promoting and protecting the open development, sharing, and reuse of BioBrick™ standard biological parts. Taking inspiration from the Internet Engineering Task Force, we are now implementing a Request for Comments process. A Request for Comments, abbreviated RFC, is a short document that is intended for review by the rest of the community.

An RFC might

  • propose a standard of some sort (i.e. Tom Knight's 2003 BioBrick physical assembly standard or the Freiburg protein fusion assembly standard)
  • describe best practices or protocols (i.e. a protocol for assembling two parts)
  • provide information (i.e. a description of how to design transcriptional terminators)
  • simply comment, extend, or replace an earlier RFC

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.