[Psidev-qc-dev] Upcoming teleconference 5/5

[Bittremieux, W. <wbi...@he...>]

Dear colleagues,

We have our next teleconference tomorrow, Wednesday May 5, at 14h00 GMT (15h00 London, 16h00 Western Europe, 7h00 San Diego).

Note that we have decided to meet bi-weekly to finish the specification document and manuscript(s) discussed during the Spring Meeting.

You can connect to our teleconference on Zoom through the following link: https://uchealth.zoom.us/j/92419363577?pwd=WVp5Q3FXNU9vaVdJT0ZNRllXWlN3Zz09 (Password: 012575)

Agenda items:

Action points from the last call:

✔️ Section 9.3: Specify how non-computable numbers (NaN, Inf) should be encoded.
✔️ Section 4.1: Add a brief introduction to OBO and OBO Foundry.
✔️ Section 4.1: Specify that the MS CV and QC CV are developed in parallel (but not planned to be merged).
✔️ Section 4.1.1: Refer to the GitHub issue tracker to request new CV terms.
- @julian: Figure out how we can submit the CV to the Ontology Lookup Service.
- Mention that an mzML file may report that a corresponding mzQC file has been developed that incorporates it. Create a small mzML–mzQC example file on GitHub.
- Include examples with both nativeID and USI specifiers.
✔️ Section 5.3: Mention directly including metrics in an mzTab file.
✔️ Section 5.5: SDRF can help to define the study design to inform the calculation of QC metrics.
✔️ PR 128: Provide a userParam type for temporary metrics that don't have a CV term (yet). Please review!
✔️ Specify the type of arrays by replacing "array" by "array of TYPE".
- @mwalzer: Address syntactic and semantic validation of mzQC files.
✔️ @wout: Change to a CC BY-NC license.

Depending on whether we have more time:

- Evaluate examples on GitHub. Which examples are still missing and do we need more?
- Semantic validation (see Slack and issue 51).

Please communicate other agenda items to the mailing list.

Best,
Wout