Re: [Psidev-ms-dev] attributes vs cvParams

[Matthew C. <mat...@va...>]

Oh, I understand now.  I am not familiar with what GPM/CPAS/SBEAMS do 
with MS data when they parse it, but I can certainly conceive of simply 
reading the cvParams in as key-value pairs and storing them as text.  
Like I said earlier, it's adding support in signal processing software 
for the new terms that has the greatest cost, and very little of that 
cost needs to go toward supporting the new terms in the software's 
parser.  If the cvParam takes the form of method A in the spec, though, 
then a manually written, CV-unaware parser could potentially require 
significant changes, whereas method B or C (or my modified proposal of 
C) would not.

-Matt

Angel Pizarro wrote:
> Y, I guess that it was not too clear, sorry about that. I did not mean 
> to imply users can add terms and accession on the fly. That would be a 
> userParam. cvParams need a source CV and that source CV would be the 
> portal for submitting new terms.
>
> Shameless plug for PSI: all of the working groups have a CV 
> development component, so if an area is important to you, please 
> review the CV's and send additions / amendments to the group for review!
>
> By my reply,  I only meant that parsers written for data loading into 
> a repository ( e.g. theGPM / CPAS / SBEAMS) have a different set of 
> requirements than other tools. New terms (e.g. not in the repositories 
> catalog yet) should not be show-stoppers for those types of parsers.
>
> -angel
> On 10/4/07, *Matthew Chambers* < mat...@va... 
> <mailto:mat...@va...>> wrote:
>
>     I'm not sure what you're saying here.  Users can programmatically
>     (via a
>     web service, I presume) add terms to the CV without going through a
>     community approval process?  If it's something else, please elaborate.
>
>     -Matt
>
>     Angel Pizarro wrote:
>     >
>     > WRT to my point about operational vs. repository data formats.
>     For a
>     > repository, it is completely valid (and desirable) for the
>     software to
>     > parse this new value and add it to the list of possible values
>     for the
>     > ontology category.
>     >
>     > -angel
>     >
>     >
>
>