Michael Baudis

@heuermh I'm neutral on locking vs. plastering deprecation notes all over the repo. However, regarding the "pick up & make it work": The problem wasn't the ability/willingness of people to...

Thanks @ksens; I have no idea where the errors come from Also not able to get https://github.com/ga4gh/ga4gh-schemas/pull/875 processed. @david4096 @kozbo ...?

Yes. But we have to document this better. Also to make it very explicit that the "disease" is inherent in the sample, with examples. E.g. peripheral blood from a patient...

Thanks for pointing this out. We'll have to look into this, but on a first glance e.g. the AssociationType is way too rigid/overspecified. Also, we're getting rid of ENUMS if...

Samples don't have to be children of individuals; they can be pooled, environmental ... There is a larger scope, not only specific to human disease etc. But my comment is...

Note for later: Tweet your query to @ga4ghapi... > On 31 Mar 2015, at 23:08, Mark Diekhans [email protected] wrote: > > Yes, +1 for Deanna's view. No result returned is...

I am very much +n on @haussler 's comments. I would support moving all web API parts to a different repository. This would also greatly facilitate the schema development, which...

... also, we had some discussions on how to coordinate Beacon with the GA4GH schema; and one obstacle clearly is the current "proto w/ methods" style to handle things.

I'm +1 regarding `ga4gh.schemas.datamodel` and `ga4gh.schemas.methods`. The current mix is awkward; and splitting in different repos may be detrimental to the required coherence, due to the varying nature/maturity/activity of all...

@andrewjesaitis From previous discussions and the documentation it is actually clear that `created` and `updated` refer to record specific dates; there is no indication that they have to do anything...