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 V002: Alternative Glyphs #5

jakebeal opened this Issue Jul 21, 2017 · 0 comments


None yet
1 participant

jakebeal commented Jul 21, 2017

SEP V002: Alternative Glyphs

Authors Jacob Beal (
Type Specification
SBOL Visual Version 1.1
Status Draft
Created 21-Jul-2017
Last modified


Sometimes there is more than one way of drawing a diagram that is accepted by the community and no strong reason to attempt to force a choice of only one. In such cases, SBOL Visual should recommend one symbol, but also endorse good alternatives.

1. Rationale

In some cases, the community has come up with more than one good symbol for a given concept. Rather than declaring only one valid and the others "bad," SBOL should support the use of good alternatives.

2. Specification

There may be more than one glyph sharing the same definition: in this case, these glyphs form a family of variants, of which precisely one MUST be designated as the RECOMMENDED variant.

For example, a CDS may be represented by either a pentagonal glyph or an arrow glyph, but the pentagon is the RECOMMENDED variant, and so it is preferred. In specific cases, however, there may be reasons to use one of the other applicable glyphs instead.

3. Examples

RECOMMENDED CDS glyph from SBOL Visual 1.0:

Alternative "arrow" CDS glyph

4. Backwards Compatibility

No backwards compatibility issues.

5. Discussion


To the extent possible under law, SBOL developers has waived all copyright and related or neighboring rights to SEP V002. This work is published from: United States.

@jakebeal jakebeal added Accepted and removed Draft labels Sep 14, 2017

@jakebeal jakebeal added this to the SBOLv 1.1 milestone Sep 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment