Michael Baudis

@mfiume Also with regards to yesterday's call - Some of the issues (e.g. what data v2 is supposed to support _in protocol_, how you can already use {S}[B] for payload...

@sdelatorrep @juhtornr @jrambla Could you please move this forward? Such documentation changes should be processed fast (w/ possible improvement etc.).

@sabela @juhtornr Can you please take care of this? Such doc changes should be merged immediately.

@blankdots Maybe open an issue about this, in general? Another issue to address is: https://github.com/ga4gh-beacon/specification/blob/master/beacon.yaml#L119 usage or `alternateBases` and `variantType` i think https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/#oneof should be used. It is my understanding...

@sdelatorrep Thanks for starting this - and driving a great topic for standardisation & documentation! I have problems mostly with the `variantCount` definition - but this may be me, coming...

@juhtornr @jrambla I've added some notes & an example. Region queries are used to determine the existence of any/all variants in a genomic range. A typical example would be the...

@jrambla @juhtornr Great - I'll be happy o help, developing this further. For now, the query example still works ... @teemukataja This also reports the short-form "digest" of the matched...

@cyenyxe A problem here is the support at the resource level, especially when doing federated queries. With the original Beacon being more a "social experiment", it was easier to provide...

@sdelatorrep @juhtornr As mentioned in the call, "results" is strange since the dataset responses/handovers are also results; there, the method name describes the scope... Logically, one could use`aggregateHandover`, in contrast...

@sdelatorrep @jrambla O.k., makes sense for that purpose (Beacon information). Then Also, a Beacon response (i.e. the typical "exists") should be an aggregateResponse. Do we want to implement this (&...