The BioBricks Foundation:RFC: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
No edit summary
Line 5: Line 5:
|width="750px"|
|width="750px"|
<div style="clear: left; text-align: left; float: left; padding: .4em .9em .9em">
<div style="clear: left; text-align: left; float: left; padding: .4em .9em .9em">
<font face="Arial" size=5 style="color:#0B1165">RFCs</font><br>
<font face="Arial" size=3 style="color:#0B1165">RFCs</font><br>
<br>
<br>
The BioBricks Foundation is dedicated to promoting and protecting the open development, sharing, and reuse of BioBrick&trade; standard biological parts. Taking inspiration from the Internet Engineering Task Force, we are now implementing a Request for Comments (RFC) process.
The BioBricks Foundation is dedicated to promoting and protecting the open development, sharing, and reuse of BioBrick&trade; standard biological parts. Taking inspiration from the Internet Engineering Task Force, we are now implementing a Request for Comments process.


Instructions for requesting a BBF RFC number, preparing an RFC, and submitting an RFC are described in [[Media:BBFRFC0.pdf|BBF RFC 0]].
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 [[Media:BBFRFC0.pdf|BBF RFC 0]].


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 17:21, 10 November 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.

  • 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 Ridgeway, 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