-
Notifications
You must be signed in to change notification settings - Fork 34
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
Seqref updates #573
base: 2.x
Are you sure you want to change the base?
Seqref updates #573
Conversation
$ref: "#/$defs/SequenceString" | ||
description: >- | ||
A :ref:`SequenceString` that is a literal representation of the referenced sequence. | ||
moleculeType: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cmprocknow concern about "molecule type"; perhaps "molecularContext" would be cleaner.
moleculeType: | ||
type: string | ||
enum: | ||
- genomic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
general discussion on genomic expressed concerns, possible alternate is "template"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
except "template" is a total non-starter. There are genomic variants that are not necessarily going to be involved as template sequence (e.g. variants in regulatory elements)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Group consensus: we should cover the same concept types that RefSeq uses.
Addresses #567 and #568. For discussion.