Michael Baudis

Great! Example: * https://beacon.progenetix.org/beaconplus-server/beaconresponse.cgi?datasetIds=&referenceName=17&assemblyId=GRCh38&start=7577121&referenceBases=G&alternateBases=A ... works, but some errors in the response, info have to be ironed out.

Why isn't the `alleleRequest` being interpolated? Is returned by the server: ``` { "beaconId": "progenetix-beacon", "alleleRequest": { "start": "7577121", "referenceName": "17", "referenceBases": "G", "alternateBases": "A" }, "exists": true, "datasetAlleleResponses": [...

O.k. However, the problem w/ directly delivering the variants in the response is that it easily gets out of hand, especially for wildcard range matches. While this may be partially...

@teemukataja @juhtornr ... so if you want to build an interface which demonstrates/provides the functionality you have shown (and which is certainly nice for different use cases), I suggest that...

@blankdots Regarding ontologies: See my last notes on https://github.com/ga4gh-beacon/specification/pull/230. The example in the PR is a bit misleading so far, since it doesn't demonstrate a "technical/data" ontology (like the `"id"...

@mfiume I am against `files` as part of the Beacon response, but in support of a generic mechanism, announcing / linking to a DOS response. It could be an object...

... which would be based on the general concept to keep data delivery outside of the Beacon schema itself, but allow co-opting of other standards to fulfil the same purpose...

We now provide an example of how this could look like on the backend in the [GA4GH Schema Building Blocks](https://ga4gh-metadata.github.io/schemas/), e.g. in `callsets`, `biosamples` ... ``` 'data_use_conditions' : { 'id'...

+1 for a specific response (not overloading `info`).

Parsing this I see 2 differences * the added `"referenceBases": "string", "alternateBases": "string",` * the removal of the placeholder key/value texts from `info` So: The ref/alt values in the response...