From: Angel P. <an...@ma...> - 2008-02-14 14:35:30
|
I would have thought the ontology entry for XCalibur would have qualified it as acquisition software (e.g. this should have been encoded into the CV element and hence referencing the accession MS:1000532 would suffice to identify it as acquisition software.) -angel On Thu, Feb 14, 2008 at 6:21 AM, Lennart Martens <len...@eb...> wrote: > Hi Darren, hi PSI-MS enthousiasts, > > > I have included the ability to use cvParams in the 'software' element in > a new schema iteration as per your suggestion. > Find it here: > > http://www.ebi.ac.uk/~lmartens/mzML/20080214_mzML0.99.9_SNAPSHOT.xsd<http://www.ebi.ac.uk/%7Elmartens/mzML/20080214_mzML0.99.9_SNAPSHOT.xsd> > > Kessner, Darren E. wrote: > > Hi all, > > > > > > > > Please excuse me if this has been discussed before. > > > > > > > > In mzXML, the <software> element is encoded as follows: > > > > <software type="acquisition" > > > > name="Xcalibur" > > > > version="1.3 alpha 8"/> > > > > > > > > In mzML, we have: > > > > <software id="Xcalibur"> > > > > <softwareParam cvLabel="MS" accession="MS:1000532" > > name="Xcalibur" version="2.0.5"/> > > > > </software> > > > > > > > > Note that the name and version are encodable, but there is no convenient > > place to save the "type" attribute, since the <software> element does > > not have <cvParam> or <userParam> sub-elements. > > > > > > |