Nils Hoffmann

@LucieLamothe @sneumann The mzTab-M format comes with separate parser and validator implementations. Generic CSV readers may read both formats, but the metadata sections and specifically the content sections are **not**...

@matuskalas Is there anything that we need to change / update to get this PR merged?

Pinging @matuskalas to kindly ask to proceed with the merging of mzTab-M

And pinging @matuskalas again to kindly ask to proceed with the merging of mzTab-M. Not sure why the CI build failed, the logs are no longer available.

@matuskalas @LucieLamothe What is the status of this PR? Is there a timeline when it might be merged?

@matuskalas @cb2993 What is the status on mzTab-M? Is there anything more to do before it can be added?

> Hi - I agree that it would not need to be in the XCMS package to not further increase dependencies - also I think the XCMS object is quite...

> +1 for not adding these dependencies. That's why I suggested a kind of XcmsExprtiment-BackendMzTabM in the mid-term. rmzTab-M was initially generated through code generation from an OpenAPI specification. Maybe...

Each object already has toDataFrame and fromDataFrame methods available, see the Instrument class as an example: https://github.com/lifs-tools/rmzTab-m/blob/master/R/instrument.R#L173 https://github.com/lifs-tools/rmzTab-m/blob/master/R/instrument.R#L218

So converting this to S4 reference classes, or what alternative class type would you recommend, should be doable?