diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000..fded6d94 --- /dev/null +++ b/.gitignore @@ -0,0 +1,75 @@ +*.py[cod] +target +*~ +#* +doc/source/schemas/*.avpr +build + +#********** windows template********** + +# Windows image file caches +Thumbs.db + +# Folder config file +Desktop.ini + +# Recycle Bin used on file shares +$RECYCLE.BIN/ + + +#********** osx template********** + +.DS_Store + +# Thumbnails +._* + +# Files that might appear on external disk +.Spotlight-V100 +.Trashes + + +#********** linux template********** + +.* +!.gitignore +*~ + +# KDE +.directory + + +#********** emacs template********** + +*~ +\#*\# +/.emacs.desktop +/.emacs.desktop.lock +.elc +auto-save-list +tramp +.\#* + +# Org-mode +.org-id-locations +*_archive + + +#********** vim template********** + +.*.sw[a-z] +*.un~ +Session.vim + + +#********** maven template********** + +target/ + +#********** Travis CI ********** + +!.travis.yml + +#********** IntelliJ files ****** +*.iml + diff --git a/.gitmodules b/.gitmodules deleted file mode 100644 index 3c496c87..00000000 --- a/.gitmodules +++ /dev/null @@ -1,9 +0,0 @@ -[submodule "beaconizer"] - path = beaconizer - url = https://github.com/mcupak/beaconizer.git -[submodule "beacon-of-beacons"] - path = beacon-of-beacons - url = https://github.com/mcupak/beacon-of-beacons.git -[submodule] - beaconizer = master - beacon-of-beacons = master diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..d3140113 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,89 @@ +# How to contribute + +Thank you for taking the time to contribute. We appreciate it! + +There are two ways to contribute - via issues, which are used for discussion, and pull requests, which are concrete proposals of change. + +## Issues + +The project's [Issues Page](https://github.com/ga4gh/beacon-team/issues) is a forum to discuss both major and minor issues related to developing the Beacon API. It also serves as the means for collaborating with the group and discussing contributions that will ultimately lead to changes to the API. See the [Issue](#issue_resolution) section below for specifics on how issues are resolved by the community. + +## Pull Requests + +The way to contribute development effort and code to the project is via GitHub pull requests. GitHub provides a nice [overview on how to create a pull request](https://help.github.com/articles/creating-a-pull-request). + +Some general rules to follow: + +- [Fork](https://help.github.com/articles/fork-a-repo) the main project into your personal GitHub space to work on. +- Create a branch for each update that you're working on. These branches are often called "feature" or "topic" branches. Any changes that you push to your feature branch will automatically be shown in the pull request. +- Keep your pull requests as small as possible. Large pull requests are hard to review. Try to break up your changes into self-contained and incremental pull requests. +- The first line of commit messages should be a short (<80 character) summary, followed by an empty line and then any details that you want to share about the commit. +- Please try to follow the [existing syntax style](#syntax_style). + +## Issue Resolution + +Once a pull request or issue have been submitted, anyone can comment or vote on to express their opinion following the Apache voting system. Quick summary: + +- **+1** something you agree with +- **-1** if you have a strong objection to an issue, which will be taken very seriously. A -1 vote should provide an alternative solution. +- **+0** or **-0** for neutral comments or weak opinions. +- It's okay to have input without voting. +- Silence gives assent. + +A pull request with at least two **+1** votes, no **-1** votes, that has been open for at least 3 days is ready to be merged. We sometimes waive the 3 days for cosmetic-only changes -- use good judgment. If an issue gets any **-1** votes, the comments on the issue need to reach consensus before the issue can be resolved one way or the other. There isn't any strict time limit on a contentious issue. + +The project will strive for full consensus on everything until it runs into a problem with this model. + +## Syntax Style and Conventions + +The current code conventions for the source files are as follows: + +- Use two-space indentation, and no tabs. +- Hard-wrap code to 80 characters per line. +- Use `UpperCamelCase` for object or record names. +- Use `lowerCamelCase` for attribute or method names. +- Use `CONSTANT_CASE` for global and constant values. +- Comments: + - Comments should be indented at the same level as the surrounding code. + - Comments should precede the code that they make a comment on. Documentation comments will not work otherwise. + - Documentation comments, which are intended to be processed by avrodoc and displayed in the user-facing API documentation, must use the `/** ... */` style, and must not have a leading `*` on each internal line: + + /** + This documentation comment will be + processed correctly by avrodoc. + */ + + /** + * This documentation comment will have a + * bullet point at the start of every line + * when processed by avrodoc. + */ + + - Block and multi-line non-documentation comments, intended for schema developers only, must use the `/* ... */` style. + + /* + This multi-line comment will not appear in the + avrodoc documentation and is intended for + schema developers. + */ + + - All multi-line comments should have the comment text at the same indent level as the comment delimeters. + - One-line non-documentation comments, intended for schema developers only, must use the `// ...` style. + +## Gitflow Workflow + +Our workflow is based on [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow), which defines a strict branching model designed around the project release. This workflow uses two branches to record the history of the project. The master branch stores the official release history, and the develop branch serves as an integration branch for features. Aside from these two main branches, the workflow utilizes topic and release branches. + +### Topic Branches + +If you wish to collaborate on a new feature with other GA4GH members you can ask that a topic branch be created. Since Github does not allow pull requests against branches that do not yet exist, you will have to create an issue asking for the topic branch to be created. + +Once a topic branch exists, pull requests can be made against it in the usual way. It may also be brought up to date with new changes merged into develop by anyone with commit access, if the changes produce merely a fast-forward merge for each constituent branch. However, if changes from the develop branch create a new merge commit in or or more of the repositories, that commit needs to be reviewed in a pull request. + +Changes made in a topic branch can be merged into develop by creating and then [resolving in the normal way](#issue_resolution) a pull request against the develop branch. + +Topic branches that have been merged into develop and that are no longer being developed upon should be [deleted](https://github.com/blog/1335-tidying-up-after-pull-requests) (they will still appear in the git history). + +### Release Branches + +From time to time the group will make a release. This is achieved by creating a branch named "release-foo", where foo is the release name. Only bug fixes are allowed to release branches. To refer to a specific version of a release branch either the commit id can be used, or alternatively (better), a tag can be created (which should be replicated across repositories). diff --git a/README.md b/README.md index c4d02aef..6ffc8f23 100644 --- a/README.md +++ b/README.md @@ -1,49 +1,25 @@ -# Beacon Project Repository +# Beacon Schemas -## What's a Beacon? +## What is a Beacon? -A “Beacon” is a web-accessible service that can be queried for information about a specific allele. A user of a Beacon can pose queries of the form “Have you observed this nucleotide (e.g. C) at this genomic location (e.g. position 32,936,732 on chromosome 13)?” to which the Beacon must respond with either “yes” or “no.” In this way, a Beacon allows allelic information of interest to be discovered by a remote querier with no reference to a specific sample or patient the allele was observed in. +A _Beacon_ is a web-accessible service that can be queried for information about a specific allele. A user of a Beacon can pose queries of the form _Have you observed this nucleotide (e.g. C) at this genomic location (e.g. position 32,936,732 on chromosome 13)?_ to which the Beacon must respond with either _yes_ or _no_. -## Related Links +## Beacon Project -* GA4GH Beacon Site: http://ga4gh.org/#/beacon -* Beacon Network: http://beacon-network.org +The Beacon project is a project to test the willingness of international sites to share genetic data in the simplest of all technical contexts. For more information, visit [GA4GH Data Working Group](http://ga4gh.org/#/beacon). -## How to light a Beacon +## Tools -If you are a data steward, please consider lighting a Beacon. There are three options of varying complexity for lighting beacons: -* From scratch (hardest): develop a Beacon compliant with the specification(s) in the schemas directory of this repository -* Reference impementation (easier): use a free to download and install implementation of Beacon, which you host on your network or on a cloud instance you own -* Managed solutions (easiest): use an implementation of Beacon that is implemented and maintained by a third-party +A list of related tools and projects developed by the community is maintained on the [Resources](https://github.com/ga4gh/beacon-team/wiki/Resources) wiki page. -Please contact us for support in lighting a Beacon. +## How to contribute -## Developers +Guidelines for contributing to this repository are listed in the [CONTRIBUTING.md](CONTRIBUTING.md) document. -### Development Model +## License -We adopt the Gitflow development model as outlined here: http://nvie.com/posts/a-successful-git-branching-model/ +See the [LICENSE](LICENSE) file. -### Developer FAQs +## More information -#### What are the valid responses for a beacon? - -A: Yes or No - -Yes means, "I have information about the queried variant" and No means, either (i) "I don't have information about the queried variant" or (ii) "I don't know if I have information about the queried variant". - -The decision to support either Yes or No, and not an additional Null option, was due to complexities in distinguishing between "I don't have information about the queried variant" and "I don't know if I have information about the queried variant". For example, if a beacon is served from a VCF file that has reference alleles omitted, it is impossible to determine whether the reference allele was observed but not recorded, or not observed at all. - -It was decided that an additional set of Evidence Codes could be returned if this information is available. - -### Is the position in a Beacon query 0-based or 1-based? - -A: 0-based - -The decision to use 0-based coordinates for the position in the Beacon query was based on alignment with the core GA4GH APIs. Of course, when designing clients (e.g. websites) which query beacons, developers should use descretion about what the end-user expects. The Beacon Network, for example, takes 1-based coordinates as input and queries connected Beacons in 0-based coordinates, as appropriate. - -### How are queries against complex mutations treated? - -A: For insertions and deletions exact match is required for a Yes response. More complex mutations (e.g. inversions, duplications) are not yet supported. - -Queries for insertions or deletions must be sepcified using ref and alt strings of bases. For insertions and deletions exact match is required for a Yes response. More complex mutations (e.g. inversions, duplications) are not yet supported. +More information for developers is available on [our wiki](https://github.com/ga4gh/beacon-team/wiki). diff --git a/beacon-of-beacons b/beacon-of-beacons deleted file mode 160000 index 46f5adf6..00000000 --- a/beacon-of-beacons +++ /dev/null @@ -1 +0,0 @@ -Subproject commit 46f5adf623ac91f063fde91c094f56f3355719b4 diff --git a/beaconizer b/beaconizer deleted file mode 160000 index 2869cde7..00000000 --- a/beaconizer +++ /dev/null @@ -1 +0,0 @@ -Subproject commit 2869cde70107b99f0c55ec52498eef45443a63c6 diff --git a/pom.xml b/pom.xml new file mode 100644 index 00000000..079d0485 --- /dev/null +++ b/pom.xml @@ -0,0 +1,252 @@ + + + 4.0.0 + org.ga4gh + beacon + jar + 0.3.0 + + Beacon + Beacon data models and APIs + https://github.com/ga4gh/beacon-team + 2014 + + Global Alliance for Genomics and Health + http://genomicsandhealth.org + + + + The Apache Software License, Version 2.0 + http://www.apache.org/licenses/LICENSE-2.0.txt + + + + scm:git:https://github.com/ga4gh/beacon-team + scm:git:https://github.com/ga4gh/beacon-team + https://github.com/ga4gh/beacon-team + + + + GA4GH developers + https://github.com/orgs/ga4gh/people + Global Alliance Data Working Group + http://ga4gh.org/ + + + + + 1.8.0 + [1.6,) + [3.0.4,) + UTF-8 + UTF-8 + + + + + + + org.apache.avro + avro-maven-plugin + ${avro.version} + + + org.apache.maven.plugins + maven-clean-plugin + 2.6.1 + + + org.apache.maven.plugins + maven-compiler-plugin + 3.3 + + + org.apache.maven.plugins + maven-deploy-plugin + 2.8.2 + + + org.apache.maven.plugins + maven-enforcer-plugin + 1.4 + + + org.apache.maven.plugins + maven-gpg-plugin + 1.6 + + + org.apache.maven.plugins + maven-install-plugin + 2.5.2 + + + org.apache.maven.plugins + maven-jar-plugin + 2.6 + + + org.apache.maven.plugins + maven-javadoc-plugin + 2.9.1 + + true + true + true + + + + org.apache.maven.plugins + maven-release-plugin + 2.5.1 + + true + false + release + deploy + + + + org.apache.maven.plugins + maven-resources-plugin + 2.7 + + + org.apache.maven.plugins + maven-source-plugin + 2.4 + + + org.apache.maven.plugins + maven-surefire-plugin + 2.18.1 + + + + + + org.apache.avro + avro-maven-plugin + + + schemas + generate-sources + + schema + protocol + idl-protocol + + + ${project.basedir}/src/main/resources/avro + String + + + + + + org.apache.maven.plugins + maven-enforcer-plugin + + + enforce-java + + enforce + + + + + ${maven.enforcer.maven-version} + + + ${maven.enforcer.jdk-version} + + + + + + + + + + + + org.apache.avro + avro + ${avro.version} + + + org.apache.avro + avro-ipc + ${avro.version} + + + + + + org.apache.avro + avro + compile + + + org.apache.avro + avro-ipc + compile + + + + + ossrh + https://oss.sonatype.org/content/repositories/snapshots + + + ossrh + https://oss.sonatype.org/service/local/staging/deploy/maven2/ + + + + + release + + + + org.apache.maven.plugins + maven-gpg-plugin + + + sign-artifacts + verify + + sign + + + + + + org.apache.maven.plugins + maven-javadoc-plugin + + + attach-javadocs + + jar + + + + + + org.apache.maven.plugins + maven-source-plugin + + + attach-sources + + jar-no-fork + + + + + + + + + diff --git a/schema/beacon.avdl b/schema/beacon.avdl deleted file mode 100644 index c58de834..00000000 --- a/schema/beacon.avdl +++ /dev/null @@ -1,170 +0,0 @@ -@namespace("org.ga4gh.beacon") - -/** -A Beacon is a web service for genetic data sharing that can be queried for -information about specific alleles. -*/ -protocol BEACON { - -/** -A request for information about a specific site -*/ -record QueryResource { - /** - The reference bases for this variant, starting from `position`, in the genome - described by the field `reference`. (see variants.avdl) - */ - string referenceBases; - - /** - The bases that appear instead of the reference bases. (see variants.avdl) - */ - string alternateBases; - - /** The chromosome of the request */ - string chromosome; - - /** 0-based allele locus */ - long position; - - /** The version of the reference */ - string reference; - - /** The name of the targeted population */ - union{ null, string } dataset = null; -} - -/** -ErrorResource -*/ -record ErrorResource { - /** Error name/code, e.g. "bad_request" or "unauthorized". */ - string name; - - /** Error message. */ - union{ null, string } description = null; -} - -/** -DataUseRequirementResource -*/ -record DataUseRequirementResource { - /** Data Use requirement */ - string name; - - /** Description of Data Use requirement. */ - union{ null, string } description = null; -} - -/** -DataUseResource -*/ -record DataUseResource { - /** Data Use category.*/ - string category; - - /** Description of Data Use category. */ - union{ null, string } description = null; - - /** Data Use requirements. */ - array requirements = []; -} - -/** -DataSetSizeResource -*/ -record DataSizeResource { - /** Total number of variant positions in the data set */ - int variants; - - /** Total number of samples in the data set */ - int samples; -} - -/** -DataSetResource -*/ -record DataSetResource { - /** Dataset name */ - string id; - - /** Reference genome */ - string reference; - - /** Dataset description */ - union{ null, string } description = null; - - /** Dimensions of the data set. Should be provided if the beacon reports allele frequencies. */ - union{ null, DataSizeResource } size = null; - - /** Data use limitations, specified as a set of DataUseResource. */ - array data_use = []; -} - -/** -BeaconInformationResource -*/ -record BeaconInformationResource { - /** (Unique) beacon ID. Recommended pattern: [organization]-[beacon] (no special characters). */ - string id; - - /** Name of the owning organization. */ - string organization; - - /** Beacon description. */ - string description; - - /** Datasets served by the beacon. */ - array datasets = []; - - /** Beacon API version supported. */ - string api; - - /** URL to the homepage for this beacon. */ - union{ null, string } homepage = null; - - /** An email address for contact. */ - union{ null, string } email = null; - - /** Auth type. Expected value is OAUTH2. Defaults to NONE. */ - union{ null, string } auth = null; - - /** Examples of interesting queries, e.g. a few queries demonstrating different types of responses. */ - union{ null, array } queries = null; -} - -/** -The response to the Beacon query -*/ -record ResponseResource { - /** Indicator of whether the beacon has observed the variant. */ - union{ null, boolean } exists; - - /** Frequency of this allele in the dataset. Between 0 and 1, inclusive. */ - union{ null, double } frequency = null; - - /** Number of observations of this allele in the dataset. */ - union{ null, int } observed = null; - - /** Additional message. OK if request succeeded. */ - union{ null, string } info = null; - - /** Error details. Provided if a beacon encountered an error. */ - union{ null, ErrorResource } err = null; -} - -/** -The response from the Beacon -*/ -record BeaconResponseResource { - /** Beacon ID */ - string beacon; - - /** Query */ - QueryResource query; - - /** Response */ - ResponseResource response; -} - -} \ No newline at end of file diff --git a/src/main/resources/avro/beacon.avdl b/src/main/resources/avro/beacon.avdl new file mode 100644 index 00000000..0fbee28c --- /dev/null +++ b/src/main/resources/avro/beacon.avdl @@ -0,0 +1,276 @@ +@namespace("org.ga4gh.beacon") + +/** +A Beacon is a web service for genetic data sharing that can be queried for +information about specific alleles. +*/ +protocol Beacons { + +/** +Query for information about a specific allele. + +Based on `org.ga4gh.models.Variant`. +*/ +record BeaconAlleleRequest { + /** + Reference name (chromosome). + + Accepted values: 1-22, X, Y. + */ + string referenceName; + + /** + Position, allele locus (0-based). + + Accepted values: non-negative integers smaller than reference length. + */ + long start; + + /** + Reference bases for this variant (starting from `start`). + + Accepted values: see the REF field in VCF 4.2 specification + (https://samtools.github.io/hts-specs/VCFv4.2.pdf). + */ + string referenceBases; + + /** + The bases that appear instead of the reference bases. + + Accepted values: see the ALT field in VCF 4.2 specification + (https://samtools.github.io/hts-specs/VCFv4.2.pdf). + */ + string alternateBases; + + /** Assembly identifier (GRC notation, e.g. `GRCh37`). */ + string assemblyId; + + /** + Identifiers of datasets, as defined in `BeaconDataset`. + + If this field is null/not specified, all datasets should be queried. + */ + union{ null, array } datasetIds = null; + + /** + Indicator of whether responses for individual datasets + (`datasetAlleleResponses`) should be included (not null) in the response + (`BeaconAlleleResponse`) to this request. + + If null (not specified), the default value of false is assumed. + */ + union{ null, boolean } includeDatasetResponses = null; +} + +/** Dataset of a beacon. */ +record BeaconDataset { + /** Unique identifier of the dataset. */ + string id; + + /** Name of the dataset. */ + string name; + + /** Description of the dataset. */ + union{ null, string } description = null; + + /** Assembly identifier (GRC notation, e.g. `GRCh37`). */ + string assemblyId; + + /** The time the dataset was created (ISO 8601 format). */ + string createDateTime; + + /** The time the dataset was updated in (ISO 8601 format). */ + string updateDateTime; + + /** Version of the dataset. */ + union{ null, string } version = null; + + /** Total number of variants in the dataset. */ + union{ null, long } variantCount = null; + + /** Total number of calls in the dataset. */ + union{ null, long } callCount = null; + + /** Total number of samples in the dataset. */ + union{ null, long } sampleCount = null; + + /** URL to an external system providing more dataset information (RFC 3986 format). */ + union{ null, string } externalUrl = null; + + /** Additional structured metadata, key-value pairs. */ + union{ null, map } info = null; +} + +/** Organization owning a beacon. */ +record BeaconOrganization { + /** Unique identifier of the organization. */ + string id; + + /** Name of the organization. */ + string name; + + /** Description of the organization. */ + union{ null, string } description = null; + + /** Address of the organization. */ + union{ null, string } address = null; + + /** URL of the website of the organization (RFC 3986 format). */ + union{ null, string } welcomeUrl = null; + + /** + URL with the contact for the beacon operator/maintainer, e.g. link to + a contact form (RFC 3986 format) or an email (RFC 2368 format). + */ + union{ null, string } contactUrl = null; + + /** + URL to the logo (PNG/JPG format) of the organization (RFC 3986 format). + */ + union{ null, string } logoUrl = null; + + /** Additional structured metadata, key-value pairs. */ + union{ null, map } info = null; +} + +/** Beacon. */ +record Beacon { + /** Unique identifier of the beacon. */ + string id; + + /** Name of the beacon. */ + string name; + + /** Version of the API provided by the beacon. */ + string apiVersion; + + /** Organization owning the beacon. */ + BeaconOrganization organization; + + /** Description of the beacon. */ + union{ null, string } description = null; + + /** Version of the beacon. */ + union{ null, string } version = null; + + /** URL to the welcome page for this beacon (RFC 3986 format). */ + union{ null, string } welcomeUrl = null; + + /** + Alternative URL to the API, e.g. a restricted version of this beacon + (RFC 3986 format). + */ + union{ null, string } alternativeUrl = null; + + /** The time the beacon was created (ISO 8601 format). */ + union{ null, string } createDateTime; + + /** The time the beacon was updated in (ISO 8601 format). */ + union{ null, string } updateDateTime; + + /** + Datasets served by the beacon. Any beacon should specify at least one + dataset. + */ + array datasets = []; + + /** + Examples of interesting queries, e.g. a few queries demonstrating different + responses. + */ + union{ null, array } sampleAlleleRequests = null; + + /** Additional structured metadata, key-value pairs. */ + union{ null, map } info = null; +} + +/** Beacon-specific error representing an unexpected problem. */ +record BeaconError { + /** Numeric error code. */ + int errorCode; + + /** Error message. */ + union{ null, string } message = null; +} + +/** Dataset's response to a query for information about a specific allele. */ +record BeaconDatasetAlleleResponse { + /** Identifier of the dataset, as defined in `BeaconDataset`. */ + string datasetId; + + /** + Indicator of whether the given allele was observed in the dataset. + + This should be non-null, unless there was an error, in which case + `error` has to be non-null. + */ + union{ null, boolean } exists; + + /** + Dataset-specific error. + + This should be non-null in exceptional situations only, in which case + `exists` has to be null. + */ + union{ null, BeaconError } `error` = null; + + /** Frequency of this allele in the dataset. Between 0 and 1, inclusive. */ + union{ null, double } frequency = null; + + /** Number of variants matching the allele request in the dataset. */ + union{ null, long } variantCount = null; + + /** Number of calls matching the allele request in the dataset. */ + union{ null, long } callCount = null; + + /** Number of samples matching the allele request in the dataset. */ + union{ null, long } sampleCount = null; + + /** Additional note or description of the response. */ + union{ null, string } note = null; + + /** + URL to an external system, such as a secured beacon or a system providing + more information about a given allele (RFC 3986 format). + */ + union{ null, string } externalUrl = null; + + /** Additional structured metadata, key-value pairs. */ + union{ null, map } info = null; +} + +/** Beacon's response to a query for information about a specific allele. */ +record BeaconAlleleResponse { + /** Identifier of the beacon, as defined in `Beacon`. */ + string beaconId; + + /** + Indicator of whether the given allele was observed in any of the datasets + queried. + + This should be non-null, unless there was an error, in which case + `error` has to be non-null. + */ + union{ null, boolean } exists; + + /** + Beacon-specific error. + + This should be non-null in exceptional situations only, in which case + `exists` has to be null. + */ + union{ null, BeaconError } `error` = null; + + /** Allele request as interpreted by the beacon. */ + union{ null, BeaconAlleleRequest } alleleRequest; + + /** + Indicator of whether the given allele was observed in individual datasets. + + This should be non-null if `includeDatasetResponses` in the corresponding + `BeaconAlleleRequest` is true, and null otherwise. + */ + union{ null, array } datasetAlleleResponses = null; +} + +} diff --git a/src/main/resources/avro/beaconmethods.avdl b/src/main/resources/avro/beaconmethods.avdl new file mode 100644 index 00000000..af434aae --- /dev/null +++ b/src/main/resources/avro/beaconmethods.avdl @@ -0,0 +1,45 @@ +@namespace("org.ga4gh.beacon") + +protocol BeaconMethods { + +import idl "beacon.avdl"; + +/**************** / *******************/ +/** +Gets beacon information. + +`GET /` (root of the beacon API) returns a representation of `Beacon`. +*/ +Beacon getBeacon(); + +/**************** /query *******************/ +/** +Gets response to a beacon query for allele information. + +GET and POST HTTP verbs must be supported. `GET /query` accepts fields of +`BeaconAlleleRequest` as URL parameters and returns a JSON representation of +`BeaconAlleleResponse`. `POST /query` accepts a JSON representation of +`BeaconAlleleRequest` as the request body and returns a JSON representation +of `BeaconAlleleResponse`. + +Examples: +GET /query?referenceName=1&start=1000&referenceBases=A&alternateBases=C +&assemblyId=GRCh37&datasetIds=d1&datasetIds=d2 + +POST /query +{ + "referenceName": "1", + "start": 1000, + "referenceBases": "A", + "alternateBases": "C", + "assemblyId": "GRCh37", + "datasetIds": [ + "d1", + "d2" + ] +} +*/ +BeaconAlleleResponse getBeaconAlleleResponse( + BeaconAlleleRequest beaconAlleleRequest); + +}