-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
13 additions
and
2 deletions.
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 |
---|---|---|
@@ -1,3 +1,14 @@ | ||
# Variant Query Types and Components | ||
# Beacon Variant Scouts | ||
|
||
==TBD== | ||
**Variant Query Types and Components** | ||
|
||
The Beacon protocol has demonstrated the general feasibility of federated queries and aggregated responses for genomic sequence variations, over distributed and disparate resources when supporting a common protocol. The final Beacon v1 standard added the option to query some for some types of structural variations - notably CNVs; and during the design of the Beacon v2 standard a "Variant Scouts" group documented an extended set of supported query patterns, while the development team implemented the necessary parameters (such as aminoacidAlteration, variantMaxLength, geneId…) into the Beacon default data model. However, several aspects had to be left open or have arisen since the original definitions - frequently not concerning necessary query parameter extensions but rather definition of standardized vocabularies and usage practices. | ||
|
||
The Beacon Varians Scouts work will focus on: | ||
|
||
* Establishing an extended set of use case driven variant query needs and document how to express them through current Beacon parameters | ||
* Suggesting extensions to the current specification where use cases, after triage against borderline scenarios and with a conservative view towards extending the vocabulary | ||
* Develop use cases into typed queries (e.g. deletion, fusion, translocation request) implemented through schema documents, following the previous points | ||
* Evaluate solutions for scenarios requiring identification of compound variants | ||
|
||
The outcome of this scout would be a document summarising points 1-3, and building on the previous Genomic variants document. It could, for example, take the form of a submitted article. Importantly, we envision that the group - in coordination with other standards groups from GA4GH and beyond - will provide solid "variant query standard blocks" - not necessarily limited to Beacon implementations; thereby providing an overarching harmonization of federated variant discovery tools and implementations. |