Skip to content

Latest commit

 

History

History
91 lines (59 loc) · 2.71 KB

sep_023.md

File metadata and controls

91 lines (59 loc) · 2.71 KB

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

Revoked

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

Abstract

This SEP proposes adding a best practice that there should be at most one sequence per ComponentDefinition.

  1. Motivation

Multiple sequences per ComponentDefinition raise a lot of issues - for example, which sequence do SequenceAnnotations apply to?

  1. Specification

A ComponentDefinition SHOULD be associated with at most one Sequence.

  1. Backwards Compatibility

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.

  1. Discussion

5.1 Related SEPs

  1. Competing SEPs

None.

References

Copyright

CC0
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.