specifications
specifications copied to clipboard
Issue tracker, technical wiki, and example markup
Add Bioschemas description to the gender property in the BioSample profile to state that it should be used to capture the biological sex of the sample. Due to the nature...
This could be a link to a donor record with the respective ID.
This came as a suggestion from the EBISC team. May be too specific for Bioschemas/Schema.org. For now they will proceed with either an `additionalProperty` or using a domain property directly.
This came as a suggestion from the EBISC team with expected values of Yes or No. May be too specific for Bioschemas/Schema.org. For now they will proceed with either an...
This came as a suggestion from the EBISC team. May be too specific for Bioschemas/Schema.org. For now they will proceed with either an `additionalProperty` or using a domain property directly.
This came as a suggestion from the EBISC team. May be too specific for Bioschemas/Schema.org. For now they will proceed with either an `additionalProperty` or using a domain property directly.
For the EBISC collection, there may not be a single age associated with a sample. The current solution is to include a range of values for the `samplingAge` property. Need...
The new type [SequenceRange](http://bio.sdo-bioschemas-227516.appspot.com/SequenceRange) needs a descriptive definition.
The status could be attached to the underlying biological sample, or the study context.
Discussion from [Community Call on 24 May](https://docs.google.com/document/d/1kd5F97ogdiPNhLTnkei-RVR8TC8Ohpc5QSPX3KsfDrk/edit#heading=h.5resupdh3177): - Alan looked at live deploys, numerous incorrect ([analysis document](https://docs.google.com/document/d/1_UpLfoE38bu9NxHJ57twZcvUbEX7cnpZ6EnpEMVwc-I/edit?usp=sharing)) - Valid / wrong, no distinction on website - List is manual -...