< Note 1: remove/replace all instructions given within "< >" > < ❗ Note 2: you really need to look at this in raw / editing mode 😃 >
| SEP | |
|---|---|
| Title | <Your short descriptive title (44 character max)> |
| Authors | <Author1 name (author1mail at xxmail com), Author2 name (author mail at yyy com)> |
| Editor | |
| Type | |
| SBOL Version | <SBOL version this proposal should apply to; remove line if Type==Procedure> |
| Replaces | <list SEP(s) this proposal would replace, otherwise remove line. E.g. SEP #1> |
| Status | Draft |
| Created | 08-Oct-2015 |
| Last modified | 15-Jan-2021 |
| Issue | #2 |
< insert short summary >
- 1. Rationale <or, if you prefer, 'Motivation'>
- 2. Specification
- 2.1 optional sub-point
- 2.2 optional sub-point
- 3. Example or Use Case
- 4. Backwards Compatibility
- 5. Discussion
- 5.1 discussion point
- 5.2 discussion point
- 6. Competing SEPs
- References
- Copyright
< insert motivation / rationale, keep it brief >
< give detailed specification, can be split up into more than one section if useful > < refer to other SEPs like this: This SEP is much better than SEP #1>
< sub-divide specification section if useful >
< sub-divide specification section if useful >
< Describe brief examples or use cases >
< discuss compatibility issues and how to solve them; remove this section if this doesn't apply > < e.g. in case of procedure SEP >
< Summarize discussion, also represent dissenting opinions >
< list competing SEP #'s >
< list references as follows >
< refer to these references in the text as, e.g. SBOL or 1 >
< SEPs should generally be public domain; replace names as needed. If necessary, change to a different license (typically another CC license) >
To the extent possible under law,
SBOL developers
has waived all copyright and related or neighboring rights to
SEP 002.
This work is published from:
United States.