Team:Groningen/Info standard

From 2010.igem.org

(Difference between revisions)
(Information Standard)
 
(2 intermediate revisions not shown)
Line 1: Line 1:
-
===Information Standard===
+
==Information Standard==
An information standard for BioBricks is needed to provide the specified information in a standardized layout, which improves the quality of information and reduces the chance of forgetting information. In many industries we already see such standards, however such a standard doesn't exist yet in synthetic biology. It was our purpose to build a standard which easily allows improvement the documentation for BioBricks which are published on the partsregistry.
An information standard for BioBricks is needed to provide the specified information in a standardized layout, which improves the quality of information and reduces the chance of forgetting information. In many industries we already see such standards, however such a standard doesn't exist yet in synthetic biology. It was our purpose to build a standard which easily allows improvement the documentation for BioBricks which are published on the partsregistry.
-
An standard has to be published at a standardization office. The standardization office for synthetic biology is the BioBrick Foundation. They assigned us standard number 52 and can be referred to as <nowiki>BBF RFC 52</nowiki>.
+
A standard has to be published at a standardization office. The standardization office for synthetic biology is the BioBrick Foundation. They assigned us standard number 52 and can be referred to as <nowiki>BBF RFC 52</nowiki>.
Reasons to design such an information standard is that the information on the partsregistry is often brief and often insufficient. We would like to see more information available and we hope it will be more easily searchable. This way it will be easier to determine if a BioBrick is suitable for the purposes you are looking for.
Reasons to design such an information standard is that the information on the partsregistry is often brief and often insufficient. We would like to see more information available and we hope it will be more easily searchable. This way it will be easier to determine if a BioBrick is suitable for the purposes you are looking for.
Line 14: Line 14:
<html><a href="https://static.igem.org/mediawiki/2010/9/95/BBF_RFC_52.pdf">RFC 52 final version</a></html>
<html><a href="https://static.igem.org/mediawiki/2010/9/95/BBF_RFC_52.pdf">RFC 52 final version</a></html>
 +
 +
To see an example of how the standard could be used: <html><a href="https://2010.igem.org/Team:Groningen/create_desc">click here</a>

Latest revision as of 18:31, 26 October 2010

Information Standard

An information standard for BioBricks is needed to provide the specified information in a standardized layout, which improves the quality of information and reduces the chance of forgetting information. In many industries we already see such standards, however such a standard doesn't exist yet in synthetic biology. It was our purpose to build a standard which easily allows improvement the documentation for BioBricks which are published on the partsregistry.

A standard has to be published at a standardization office. The standardization office for synthetic biology is the BioBrick Foundation. They assigned us standard number 52 and can be referred to as BBF RFC 52.

Reasons to design such an information standard is that the information on the partsregistry is often brief and often insufficient. We would like to see more information available and we hope it will be more easily searchable. This way it will be easier to determine if a BioBrick is suitable for the purposes you are looking for.

Our standard is based on the currently available information in the Partsregistry and by thinking about which information is important and relevant for all BioBricks.


Future work This standard is general so it will be easy to extend in the future. For example, it should be easy to add specific information for negators and promotors by making a new standard which extends the current standards in such a way that it provides all information needed.


RFC 52 final version

To see an example of how the standard could be used: click here