Thanks for kicking of the idea, I was wondering if the scope could also include for example sample information e.g. host/lat/lon/temperature environmental type etc… or is this only to make a setup for industrial partners to get that more or less standardised and to incorporate this schema into a larger overarching one?
On a machine level when running specific instruments for example on a miseq should this also include information about the output? read length, number of reads, ...
The idea is to have this serve ALL of the MIxS checklist fields. Going with industrial vendors is just a starting point. For your second point, open a new issue for that....
Thanks for kicking of the idea, I was wondering if the scope could also include for example sample information e.g. host/lat/lon/temperature environmental type etc… or is this only to make a setup for industrial partners to get that more or less standardised and to incorporate this schema into a larger overarching one?
On a machine level when running specific instruments for example on a miseq should this also include information about the output? read length, number of reads, ...