Team:Groningen/Info standard
From 2010.igem.org
(New page: <br> ==Information Standard== Information standards are required to save information in such a way that it is easily obtainable. At this moment there doesn't exist a standard which specif...) |
(→Information Standard) |
||
Line 2: | Line 2: | ||
==Information Standard== | ==Information Standard== | ||
- | Information standards are required to save information in such a way that it is easily | + | Information standards are required to save information in such a way that it is easily readable. In other industries we already see a lot of standardized documents. Take for example electrical chips where every chip is documented on exactly the same manner or the internet standards from the IETF. |
- | Reasons to build a new standard where that the information which could be obtained | + | At this moment there doesn't exist a standard which specifies what information needs to be stored with an BioBrick part not yet. So our team took the initiative to build an information standard for BioBrick parts. |
+ | |||
+ | A standard needs to be registered at a standards office. Then it will receive a number under which its content can be seen. In this case the BioBrick Foundation maintains the standards and the BioBrick Foundation standards are called BBF RFC. RFCs are Request For Comments. | ||
+ | |||
+ | Reasons to build a new standard where that the information which could be obtained from the partsregistry is in many cases very limited. This standard will try to improve the information in such a way that no contact is needed when you want to use a BioBrick part/device. However the user needs to use the standard himself to really document it the way the standard suggests. | ||
+ | |||
+ | Possibilies which will arise after such an information standard are that it will be easier to build a database cause there is already a lot of information available. |
Revision as of 12:53, 25 August 2010
Information Standard
Information standards are required to save information in such a way that it is easily readable. In other industries we already see a lot of standardized documents. Take for example electrical chips where every chip is documented on exactly the same manner or the internet standards from the IETF.
At this moment there doesn't exist a standard which specifies what information needs to be stored with an BioBrick part not yet. So our team took the initiative to build an information standard for BioBrick parts.
A standard needs to be registered at a standards office. Then it will receive a number under which its content can be seen. In this case the BioBrick Foundation maintains the standards and the BioBrick Foundation standards are called BBF RFC. RFCs are Request For Comments.
Reasons to build a new standard where that the information which could be obtained from the partsregistry is in many cases very limited. This standard will try to improve the information in such a way that no contact is needed when you want to use a BioBrick part/device. However the user needs to use the standard himself to really document it the way the standard suggests.
Possibilies which will arise after such an information standard are that it will be easier to build a database cause there is already a lot of information available.