Michael Baudis

> I am hesitant to use the 'karyotypicSex' field as it implies that a formal karyotype was done Yes. But having this as an optional field for this purpose &...

The general problem with filters is that they are over-designed & under-engineered; but I'm not sure if it is necessary to solve by engineering vs. by documentation? IMO we can...

I'm for the removal of custom filters from the public API, or just do them as placeholder object (_i.e._ only definition as `object` since they should not been though of...

A solution for stricter typing is the use of `filterType`, e.g. `filterType: alphanumeric` as a required parameter. VRS is doing something similar then with `if` conditions (though it gets ......

That's actually a VRS question in the first place - how do I express genotypes in VRS, which is not yet part of "stable": https://vrs.ga4gh.org/en/latest/terms_and_model.html?#genotype The current Beacon v2.0 explicitly...

It usually would be implicit, by not being reported/found, since being the default (if it is a homozygous case of the predominant allele). Which isn’t a very robust assumption. The...

@daisieh I'll try to summarize this in the [FAQ](http://docs.genomebeacons.org/FAQ/) soonish... Edit: Note here ; please extend/fix at https://github.com/ga4gh-beacon/beacon-v2/blob/main/docs/FAQ.md ...

A development relating to this is the proposal to create a `multiVariantParameters` (name TBD...) query object which is just a list of basic current `g_variant` query objects and where the...

@surchs IMO yes! Would probably look at it for other projects, too :-)

@dglemos I'm +1 for this; logical addition (although we at some point have to comb over the whole variant model anyway, especial regarding its integration w/ VRS 1.3++). ``` VariantLevelData:...