-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add list of known attributes that can be included in the digest #12
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,3 +17,22 @@ Should a wider GA4GH standard appear from [TASC issue 5](https://github.com/ga4g | |
### Known limitations | ||
|
||
- There have been a handful of reports of old sequences with disallowed characters in the sequence name rows (`>`) of FASTA files, particularly from the microbiome community. These sequence collections would have to be changed to include only SAM-compatible ASCII characters, which could restrict usage of the sequence collections protocols and delay uptake. | ||
|
||
## 2021-09-22 - Controlled vocabulary for the supported fields | ||
|
||
### Decision | ||
|
||
The attributes allowed to be used in the sequence collection digest construction are: | ||
- lengths: the length of the sequences | ||
- sequences: the Refget digests of the sequences | ||
- names: the given name of the sequence in this collection | ||
- topologies: the topology of each sequence (can be either linear or circular) | ||
- priorities: importance of the sequence in the assembly | ||
|
||
### Linked issues | ||
|
||
- https://github.com/ga4gh/seqcol-spec/issues/8 | ||
|
||
### Known limitations | ||
|
||
- After long discussion, we decided that storing an order array to explicitely was going to bring too many complications so we decided against it. This will limit (but not negate) our ability to find collections that have the same content but where the element. are in a different. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think I would just leave this for the other ADR entry that discusses it in detail. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I'm not sure if 'allowed' is the right word here -- since we allow everything, really. I think it's more like, these are the controlled vocabulary terms for the basic, universal seqcol spec....
Maybe:
"The initial set of controlled vocabulary terms for sequence collection attributes included in the digest construction are: "
And then I think I'd also add to this ADR the decision that additional custom attributes are allowed.