-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEP 002 -- SEP Template Document #2
Comments
Since normal users won't have editing rights on this issue tracker, and thus won't be able to see the markdown code, I have checked in a copy of the raw markdown file as |
Labelling as CC0 rather than public domain for better legal compatibility, per discussion with Raik. |
Added "Editor" field to preamble. Following Michal's suggestion (see SEP #1). |
changed Type : Procedure -> Type: Process |
Voting closed on March 10th 2016. This SEP was accepted together with SEP #1. |
Closing in accordance with changes to SEP issue tracking rules detailed in SEP 001 bcbbcab#diff-44cec2aabf4c066f9a54ac4ef6634b9b |
SEP 002 -- SEP Template Document
< Note 1: remove/replace all instructions given within "< >" >
< β Note 2: you really need to look at this in raw / editing mode π >
< Note 3: download the raw template from: https://raw.githubusercontent.com/SynBioDex/SEPs/master/sep_002_template.md >
Abstract
< insert short summary >
Table of Contents
1. Rationale
< insert motivation / rational, keep it brief >
2. Specification
< 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>
2.1 optional sub-point
< sub-divide specification section if useful >
2.2 optional sub-point
< sub-divide specification section if useful >
3. Example or Use Case
< Describe brief examples or use cases >
4. Backwards Compatibility
< discuss compatibility issues and how to solve them; remove this section if this doesn't apply >
< e.g. in case of procedure SEP >
5. Discussion
5.1 discussion point
< Summarize discussion, also represent dissenting opinions >
5.2 discussion point
References
< list references as follows >
< refer to these references in the text as, e.g. SBOL or 1 >
Copyright
< 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.
The text was updated successfully, but these errors were encountered: