From: Randy J. <rkj...@in...> - 2006-01-26 21:15:09
|
The minutes from the last two PSI-MS teleconferences are now on the PSI DocStore: 10 Jan 2006: http://psidev.sourceforge.net/docstore/download.php?sess=0&parent=4&expand=1&order=name&binary=1&id=59 24 Jan 2006: http://psidev.sourceforge.net/docstore/download.php?sess=0&parent=4&expand=1&order=name&binary=1&id=60 The next teleconference is scheduled for Feb 7 at 1600 GMT - please forward any agenda items for discussion. The mzData specification is being completed so that review can occur at the April PSI meeting. We are collecting "Use Cases", "Goals" and "Non-Goals" for the document so that common uses of the format can be explained. Our idea of 'use case' is more like a scenario than a formal document. Goals should state what the specification should achieve and non-goals should describe what is considered out of scope for the specification Some examples that have been collected so far: _Use cases for mzData: _ Store spectral data collected from an HPLC-MS experiment Store tandem mass spectrum Store processed peak list Store Time-domain data supporting TOF peak list Store FID data from FTICR to support peak list Store continuous, high resolution spectra Store selected ion monitoring experimental data Compare spectra from the same sample analysed by two instruments from different manufacturers using a third party tool. _Goals:_ Provide a vendor-independent representation of mass spectral data collected for use in proteomics analysis Allow new experiments and new instruments to be represented via an expansion of a controlled vocabulary rather than a format change Provide a controlled vocabulary derived from the standard IUPAC terminology for analytical chemistry and other standards groups _Non-Goals:_ Representation of sample preparation methods and steps Representation of biological sample origins The format is not intended to be suitable as an internal file format for a mass spectrometry application that works with peak lists and/or raw mass spec data. Please either post to this list, or send comments to Randy Julian rkj...@in... Thanks, Randy |