The BioBricks Foundation:RFC

From OpenWetWare

(Difference between revisions)
Jump to: navigation, search
Line 21: Line 21:
*Blank templates for drafting a BBF RFC are available
*Blank templates for drafting a BBF RFC are available
**[[Media:BBF RFC blank.doc | Word]] (.doc)
**[[Media:BBF RFC blank.doc | Word]] (.doc)
 +
**[[Media:BBF RFC blank.ott | Open Document Format (ODF)]] (.ott)
 +
**[[Media:BBF RFC blank.stw | OpenOffice.org]] (.stw)
The complete list of all assigned RFC numbers and RFC documents (for those submitted) is listed below.
The complete list of all assigned RFC numbers and RFC documents (for those submitted) is listed below.

Revision as of 16:28, 20 March 2009


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.

  • BBF RFC 0: Instructions to BBF RFC Authors
    • by Chris Anderson, Austin Che, Mackenzie Cowell, Alistair Elfick, Kim de Mora, Drew Endy, Chris French, Tom Knight, Antonia Mayer, George McArthur, Randy Rettberg, Douglas Ridgway, Reshma Shetty, Sean Sleight, and Daniel Tarjan
  • BBF RFC 1: Definition of the nature of a part
    • requested by Kristian Müller and Katja Arndt
  • BBF RFC 2: The information stored with a with a part
    • requested by Kristian Müller and Katja Arndt
  • BBF RFC 3: Restriction sites for the construction of fusion proteins
    • requested by Kristian Müller and Katja Arndt
  • BBF RFC 4: Synthetic Biology Diagram Standard
    • requested by Mackenzie Cowell
  • BBF RFC 5: BioBrick Placeholders
    • requested by George McArthur IV and Daniel R Tarjan
  • BBF RFC 6: Synthetic Terminators for Transcription Attenuation
    • requested by George McArthur IV and Daniel R Tarjan
  • BBF RFC 7: Original Biobrick distribution data sheet, May 22, 2002
    • This is the data sheet accompanying the first public Biobrick distribution
    • Tom Knight
  • BBF RFC 8: Early Biobrick standard design
    • Early description of a (now defunct) Biobrick standard
    • Tom Knight
  • BBF RFC 9: Idempotent vector design for the standard assembly of Biobricks
    • Initial detailed motivation and definition of the Biobrick standard
    • Tom Knight, Randall Rettberg, Leon Chan, Drew Endy, Reshma Shetty, Austin Che
  • BBF RFC10: Draft standard for Biobrick biological parts
    • Formal description of the initial Biobrick standard
    • Tom Knight, May 3, 2007
  • BBF RFC 11: Biobrick assembly standard modifications
    • Proposed modification of enzymes to facilitate protein fusions (SpeI/NheI replaces XbaI/SpeI)
    • Tom Knight, July 8, 2008
  • BBF RFC12: Draft Biobrick BB-2 standard for biological parts
    • Formal description of the Biobrick BB-2 standard
    • Tom Knight, November 19, 2008
  • BBF RFC13: Rethinking the boundaries and composition of coding regions
    • Logical split of the protein coding region into domains
    • Tom Knight
  • BBF RFC14: Protein domain fusions in BB-2 assembly
    • Application of the RFC13 ideas to assembly with BB-2
    • 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
    • requested by Julie Norville, Angela Belcher and Tom Knight
  • BBF RFC 16: BioBrick Open Graphical Language (BOGL)
    • requested by Cesar Rodriguez, Drew Endy, and others TBA
  • BBF RFC 17: BioBrick Open Language (BOL)
    • 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
    • DSpace, PDF (direct link), doi: 1721.1/44640
Personal tools