Michael Baudis
Michael Baudis
@david4096 @kozbo @ejacox Any comments/way forward on this?
The `BioCharacteristic` object wraps around OntologyTerm lists (positive and negated): * https://github.com/ga4gh/ga4gh-schemas/blob/metadata-modify-biocharacteristics/src/main/proto/ga4gh/bio_metadata.proto#L140 ``` // BioCharacteristic is a prototype wrapper object for single instances // of phenotypes, diseases ... which may...
@david4096 Logically, Callsets should only refer to one Variantset, since they can be thought of as an ordered list with the length == no. of variants described. So Variantsets would...
But please be aware that this type of metadata isn't treated by the MTT ("everything but the sequence"); though we'll jump in upon specific requests ...
+1 Great & fast response - thanks @kozbo & @david4096!
An implementor doesn't need to return timestamps ... needs to be a possible field Exactly. We cannot force complex data scenarios, but have to enable their implementation.
@ejacox The specification "underlying data" is a good change, to separate from server timestamps. Apart from that, any record should have these as optional; however, the API may be designed...
Modification: Created, Updated don't have to be part of Variant (but Variantset, Callset). The comments were not specific enough to make this clear.
We have this format in preparation at https://github.com/ga4gh/metadata-team/blob/master/avro-playground/metadata_redo.avdl: ``` /** Phenotypes for this individual. */ array phenotypes = []; ``` This is a working doc for collecting comments on different...