[Psidev-qc-dev] Upcoming teleconference 7/10

[Wout B. <wbi...@he...>]

Dear colleagues,

We have our next teleconference tomorrow, Wednesday October 7, at 14h00 
GMT (15h00 London, 16h00 Western Europe, 16h00 Cape Town, 17h00 Turkey, 
7h00 San Diego).

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

I propose the following agenda items:

# Specification document

I've gone through (part of) the specification document again and tried 
to make some things clearer and improve legibility. It would be useful 
if people could have a look at the specification document before the 
call and especially check the comments.

Here are some of the major topics to discuss:

- Is the switch from XML to JSON (section 2.1) sufficiently motivated 
and is the introduction to JSON sufficient/too detailed/not detailed enough?
- Difference between mzQC and qcML (section 5.1): This needs to be very 
convincing to warrant a new file format.
- Is the QC CV adequately and correctly described (section 5.3)?
     - Special note to Julian: there are a few outstanding comments that 
require your attention.
     - Should we include an example of a correct CV term request or is 
this not necessary in this document?
     - Please check whether the text on CV term creation is more clear 
now, as it was remarked last time that this was hard to understand. I'm 
not sure whether the text on values is fully correct and would 
appreciate a close check thereof.
     - Do we need to provide detailed information about the value types 
the CV terms can take? I think yes. For example, in the CV example I've 
added now, the type is `corresponding lists`, but this is not explained 
anywhere.
     - Additionally, more information on the `is_a` and `relationship` 
links is probably useful.
- Important! We need to make sure that all information about the CV is 
up to date, as some changes happened since the initial version of the 
specification document.

# Metrics that can't be directly traced back to a raw file (Chris)

Chris asked a question on Slack about how to store metrics that don't 
directly refer to a raw file.

# State of mzqc-pylib (Mathias)

Chris and Yasset have inquired as to the status of mzqc-pylib.

# CV requests (Julian)

Several issues open requesting new CV terms.


Please communicate other agenda items to the mailing list.

Best,
Wout