SEP 002 -- <Your short descriptive title>
===================================

< Note 1: remove/replace all instructions given within "< >" >
< :exclamation: Note 2: you really need to look at this in raw / editing mode :smiley:  >

SEP                     | <leave empty>
----------------------|--------------
**Title**                | <Your short descriptive title (44 character max)>
**Authors**           | <Author1 name (author1mail at xxmail com), Author2 name (author mail at yyy com)>
**Editor**            | <leave empty>
**Type**               | <choose from: Procedure OR Data Model>
**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 <current date>
**Last modified**  | 15-Jan-2021 <leave empty if this is the first submission>
**Issue**          | [#2](https://github.com/SynBioDex/SEPs/issues/2)

Abstract
-----------

< insert short summary >

Table of Contents  <remove TOC if SEP is rather short>
---------------------

* [1. Rationale](#rationale) <or, if you prefer, 'Motivation'>
* [2. Specification](#specification)
  * 2.1 optional sub-point
  * 2.2 optional sub-point
* [3. Example or Use Case](#example)
* [4. Backwards Compatibility](#compatibility)
* [5. Discussion](#discussion)
  * 5.1 discussion point
  * 5.2 discussion point
* [6. Competing SEPs](#competing_seps)
* [References](#references)
* [Copyright](#copyright)

1. Rationale <a name="rationale"></a>
----------------

< insert motivation / rationale, keep it brief >


2. Specification <a name="specification"></a>
----------------------------------------------

< 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 <a name='example'></a>
-------------------------------

< Describe brief examples or use cases >

4. Backwards Compatibility <a name='compatibility'></a>
-----------------

< 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 <a name='discussion'></a>
-----------------

### 5.1 discussion point

< Summarize discussion, also represent dissenting opinions >

### 5.2 discussion point

6. Competing SEPs <a name='competing_seps'></a>
-----------------

< list competing SEP #'s >

References <a name='references'></a>
----------------

< list references as follows >

[SBOL]: http://sbolstandard.org
[1]: https://www.python.org/dev/peps/pep-0001

< refer to these references in the text as, e.g. [SBOL] or [1] >

Copyright <a name='copyright'></a>
-------------
< SEPs should generally be public domain; replace names as needed.  If necessary, change to a different license (typically another CC license) >

<p xmlns:dct="http://purl.org/dc/terms/" xmlns:vcard="http://www.w3.org/2001/vcard-rdf/3.0#">
  <a rel="license"
     href="http://creativecommons.org/publicdomain/zero/1.0/">
    <img src="http://i.creativecommons.org/p/zero/1.0/88x31.png" style="border-style: none;" alt="CC0" />
  </a>
  <br />
  To the extent possible under law,
  <a rel="dct:publisher"
     href="sbolstandard.org">
    <span property="dct:title">SBOL developers</span></a>
  has waived all copyright and related or neighboring rights to
  <span property="dct:title">SEP 002</span>.
This work is published from:
<span property="vcard:Country" datatype="dct:ISO3166"
      content="US" about="sbolstandard.org">
  United States</span>.
</p>