SEP 023 [REVOKED] -- Add a best practice to associate at most one sequence with a ComponentDefinition
| SEP | 024 [REVOKED] |
|---|---|
| Title | Add a best practice to associate at most one sequence with a ComponentDefinition |
| Authors | James Alastair McLaughlin ([email protected]); Chris Myers ([email protected]) |
| Editor | |
| Type | Data Model |
| SBOL Version | 2.3 |
| Replaces | |
| Status | Withdrawn |
| Issue | #55 |
| Created | 19-Jun-2018 |
| Last modified | 19-Jun-2018 |
This SEP has been revoked in favour of an upcoming SEP to add a link from locations to sequences, which would avoid the ambiguity of SequenceAnnotations.
In discussion we identified cases where multiple sequences are appropriate:
- Different encodings of the same thing (e.g. smiles and inchi)
- DNA sequence + methylation patterns
This SEP proposes adding a best practice that there should be at most one sequence per ComponentDefinition.
- Motivation
Multiple sequences per ComponentDefinition raise a lot of issues - for example, which sequence do SequenceAnnotations apply to?
- Specification
A ComponentDefinition SHOULD be associated with at most one Sequence.
Most, if not all, SBOL observed in the wild only has one Sequence per ComponentDefinition and will not be affected. Any SBOL in violation of this best practice will still be valid SBOL due to the nature of best practices.
None.
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 Kingdom.