From: Angel P. <an...@ma...> - 2008-02-14 16:00:15
|
On Thu, Feb 14, 2008 at 10:50 AM, Lennart Martens <len...@eb...> wrote: > Hi Angel, > > > > 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.) > > Seems like a very reasonable suggestion to me. Currently not implemented > in the CV, but I'll make another tentative note on CV development. > > One thing that I just thought of: what if a piece of software can > perform multiple functions (i.e.: 'acquisition' as well as 'peakpicking' > -- doable in the CV through simple multi-parenting), but is used in only > one capacity (say 'acquisition') while another piece of software is used > for the other functionality (e.g., I used 'Mascot Distiller' for > 'peakpicking'). > > Do we want to keep track of such things, and is this possibly an > argument against CV encoding here? > meh... As long as it fulfills the role in the from where it is referenced, I see no problem with software that has multiple functionality. -angel |