Team:TU-Munich/Results/RFC

From 2013.igem.org

(Difference between revisions)
(→RFC 96: The AutoAnnotator - Standardized Annotation of Protein-encoding BioBricks)
 
(13 intermediate revisions not shown)
Line 6: Line 6:
<!-- Start des Inhalts -->
<!-- Start des Inhalts -->
-
==<nowiki>BBF RFC 96:</nowiki> The AutoAnnotator - Standardized Annotation of Protein-encoding BioBricks==
+
==Standardized Annotation of Protein-encoding BioBricks==
-
<div class="box-center">[[File:TUM13_RFC96_1.png]]</div>
+
-
<div class="box-left">Text</div>
+
-
<div class="box-right">figure</div>
+
-
<br><br>
+
-
 
+
-
==References:==
+
-
<div class="box-center">
+
-
<!-- Kopiervorlagen -->
+
-
[[http://www.ncbi.nlm.nih.gov/pubmed/6327079 Edens et al., 1984]]
+
-
#[[http://www.ncbi.nlm.nih.gov/pubmed/6327079 Edens et al., 1984]] Edens, L., Bom, I., Ledeboer, A. M., Maat, J., Toonen, M. Y., Visser, C., and Verrips, C. T. (1984). Synthesis and processing of the plant protein thaumatin in yeast. ''Cell'', 37(2):629–33.
+
-
<!-- Ab hier richtige Referenzen einfügen -->
+
-
#
+
-
</div>
+
-
 
+
 +
A central idea of iGEM and BioBricks is standardization. However, the part descriptions in the Registry are not really standardized and every team provides different information in different places (if at all). This makes finding and assessing BioBricks for a new project very time-consuming and frustrating, since one may have to search through the description or turn to external sources. Especially for protein-encoding Bricks there is a lot of information, which can be calculated directly from the DNA sequence. So in the [http://openwetware.org/wiki/The_BioBricks_Foundation:RFC#BBF_RFC_96:_The_AutoAnnotator_-_Standardized_annotation_of_protein-encoding_BioBricks RFC 96] we propose a standard table containing basic parameters, characteristics and predictions for protein-encoding BioBricks. Furthermore we developed a tool, the [https://2013.igem.org/Team:TU-Munich/Results/AutoAnnotator '''AutoAnnotator'''], with which this table can easily be created, so it only needs to be pasted into the part description. For more information on how the AutoAnnotator works, please see our [https://2013.igem.org/Team:TU-Munich/Results/Software Software page].
 +
You can view the full BBF RFC 96 as a [https://static.igem.org/mediawiki/2013/c/ca/TUM13_RFC96.pdf PDF document] or in the gallery below.
 +
<html>
 +
<ul class="bxslider">
 +
    <li><img src="https://static.igem.org/mediawiki/2013/0/0b/TUM13_RFC96_1.png" /></li>
 +
    <li><img src="https://static.igem.org/mediawiki/2013/7/71/TUM13_RFC96_2.png" /></li>
 +
    <li><img src="https://static.igem.org/mediawiki/2013/b/be/TUM13_RFC96_3.png" /></li>
 +
</ul>
 +
</html>
<!-- Ende des Inhalts -->
<!-- Ende des Inhalts -->

Latest revision as of 01:10, 5 October 2013


Standardized Annotation of Protein-encoding BioBricks

A central idea of iGEM and BioBricks is standardization. However, the part descriptions in the Registry are not really standardized and every team provides different information in different places (if at all). This makes finding and assessing BioBricks for a new project very time-consuming and frustrating, since one may have to search through the description or turn to external sources. Especially for protein-encoding Bricks there is a lot of information, which can be calculated directly from the DNA sequence. So in the RFC 96 we propose a standard table containing basic parameters, characteristics and predictions for protein-encoding BioBricks. Furthermore we developed a tool, the AutoAnnotator, with which this table can easily be created, so it only needs to be pasted into the part description. For more information on how the AutoAnnotator works, please see our Software page.

You can view the full BBF RFC 96 as a PDF document or in the gallery below.

Retrieved from "http://2013.igem.org/Team:TU-Munich/Results/RFC"