David Steinberg

Given it is a nested message we can safely remove the identifier and optinally provide a `name`. https://github.com/ga4gh/schemas/blob/97144152feb09e94027a0b80684f93104eac28cf/src/main/proto/ga4gh/common.proto#L169

+1 to this. Strawman proposal to handle versions would be to put it in a content negotiation header, e.g. abuse `Accept-Version` when someone wants to version down, otherwise serve them...

Really awesome to see this getting put together. I think Denis mentioned this in a meeting, but if you parsed the content of a CWL or WDL I believe you...

@bvizzier-ucsc ran into this issue when trying to add someone to an org via this screen 

Came back here because I saw this on HPRC https://dockstore.org/organizations/HumanPangenome/collections/Hifiasm

Thanks @kee007ney for making this issue. We should work towards scoping out exactly what to expect in the feature. A good first step would be getting a workflow into Dockstore...

Should individuals be able to be assigned to multiple cohorts? Proposal, add a cohort message and a list of `cohort_ids` to the `Individual` message.

Yes and in the data it will, but in terms of interchange we can probably satisfy membership through queries of individuals by cohort ID in a method similar to the...

Hi @mcourtot, of course, thank you for asking! The idea is that a cohort message doesn't say which individuals are a member, since that message might be very large. Like,...

Thanks @mbaudis ! I am happy to revoke my premature optimization of message size. The `Cohort` message itself I consider to be the metadata like "samples sequenced using this technique."...