Mark Diekhans

Jerome Kelleher [email protected] writes: > 1. We make end nullable, and make this mean 'until the end of the reference'. This is clear and precise. Making up a large number...

This seems well worth trying out (as in +1). Is there any reason to leave the array of call in a Variant object with this endpoint? Kevin Osborn [email protected] writes:...

@bartgrantham one problem with asserting a ReST API is that there is no agreed upon definition of ReSTful. It goes from simply `stateless' to`1-to-1 correspondence to HTTP verbs'. We need...

MUST - A compliant client or server must be fully implementable given only the GA4GH API specification and other referenced public, stable specifications.

all stale branches own by @diekhans should be removed

Personally, I would like to clamp down hard on consistent data. However the realities of being an interoperable data exchange API conflict on this. Early efforts to standardize data identification...

sigh While we need to deal with data interoperability, the last thing we need is another task team that doesn't write anything down. I think the example data is 1000...

It's very important to prototype any change in the model before codifying it in the API. adamnovak [email protected] writes: > As per @richarddurbin 's discussion today, which of these models...

This think called `sample' is really the display name of variant calls on an alignment of read groups. Calling this `sample; in a display to a user is a prefect...

@mlin my personal litmus tests for the design of the GA4GH API is if we can cleanly and accurately represent TCGA and ICGA data. Hopeful far more cleanly than the...