David Steinberg

Yes, my apologies! I had been inspecting serialized JSON which uses camelcase, when the schemas themselves use underscores. So this issue will close with a change of `term` to `term_label`...

Yep! https://developers.google.com/protocol-buffers/docs/style > Use CamelCase (with an initial capital) for message names – for example, SongServerRequest. Use underscore_separated_names for field names – for example, song_name.

Hi @GuilhemSempere looks like the documentation needs to be updated since we have changed this endpoint to a POST in the proto. Thanks! https://github.com/ga4gh/ga4gh-schemas/blob/master/src/main/proto/ga4gh/reference_service.proto#L61

If we accept the premise that the use cases we ought to support are for data interchange, we ought to restrict the query endpoints to the minimum useful functionality. It...

Now that we have a development page in the documentation we can ameliorate this with some code there.

https://github.com/ga4gh/ga4gh-schemas/blob/master/src/main/proto/ga4gh/variants.proto#L75 Callsets are still allowed to be in multiple variant sets. We should remove this. The biosample ID tag on callsets is what allows you to compare calls in multiple...

@kozbo I think this feature needs to be rebooted. Currently, if you want unmapped reads you query without a reference_name and position. However, this returns all reads, useful for regenerating...

Thanks @jjfarrell ! It seems like we might provide an enumeration of filters for flags in the search reads interface. ``` enum Mapping { BOTH_MAPPED = 1; PAIR_MAPPED = 2;...

The genesymbol search in sequence annotations currently accepts a string. This should be upgraded to an ontology term so that a constrained vocabulary can be used.

Thanks for all of the input! I am trying to get to putative changes to the schemas that allow for this tracking because I believe it is not in place....