Re: [Psidev-ms-dev] mzML 0.99.0 comments

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

Fair points, Brian.  But the XSD attributes for minOccurs, maxOccurs, 
and required can easily be added to the relevant terms in the CV via 
trailing modifiers.  Whatever is necessary to autogenerate the XSD can 
be added to the CV without over complicating it (indeed, doing so would 
only serve to further disambiguate it).  However, I'll grant that the 
more XSD functionality that the CV supports, the less difference there 
is between autogenerating the XSD from the hand-maintained CV and 
hand-maintaining the XSD itself. Half a dozen of one and 6 of another...

-Matt

Brian Pratt wrote:
> Hi Matt,
>
> I can only speculate on the history of PSI CV as a subset of OBO, my guess
> is they just wanted to keep it simple as it was never intended to provide
> the kind of granularity we need for fully automated semantic validation.
>
> So, I disagree on your point of CV being nearly there as an XSD replacement.
> It doesn't seem to have, for example, any means of saying whether an element
> or attribute is required or not, or how many times it can occur, etc etc.
> That's why that whole crazy xsd-like infrastructure that the java validator
> uses was built up (the ms-mapping.xml schema file is attached, for those who
> don't want to dig for it), and even that I have already shown to be
> inadequate.  I don't want to see us follow previous groups down that rabbit
> hole.
>   
>