Closed GoogleCodeExporter closed 9 years ago
Andy has moved the mzML cvParam model to the schema. Issue that in mzML you can
either have cv in line, or cv referenced. For the moment, Andy suggests keep
them
in-line, and then follow mzML if they come up with a better solution. Issue to
be
moved to Andy
Original comment by dcre...@gmail.com
on 13 May 2008 at 1:13
From andy's email: 6th June 2008:
One minor problem. On the call we discussed using XSD style inheritance for
cvParam,
where an entity e.g. SearchType uses the cvParamType complexType.
Unfortunately, this
does not work with also using the other style of inheritance where you can give
the
option of a userParam or cvParam by giving a reference to an abstract
superclass e.g.
ParamType.
So... we either go back to the old style of having e.g.
<SearchType>
<cvParam ...>
Or we ditch the option of having cvParam or userParam as an option, and only
user
cvParam. We could for example make cvRef and accession optional, so a userParam
is
just a cvParam without the reference. I can give examples if I haven't
explained this
clearly enough.
Original comment by dcre...@gmail.com
on 11 Jun 2008 at 5:35
Cannot subclass both userParam and cvParam in the same element, so need to find
places where cvParams are mandated - these are the only places where
subclassing can
be used.
Original comment by eisena...@googlemail.com
on 17 Jun 2008 at 11:41
[deleted comment]
changed ModName deriving not from PropertyValueType, but from cvParamType;
others seem to be okay.
Original comment by eisena...@googlemail.com
on 10 Jul 2008 at 4:12
documented the 4 types of Params/Values on wiki page.
Original comment by eisena...@googlemail.com
on 14 Jul 2008 at 11:19
Original comment by eisena...@googlemail.com
on 15 Jul 2008 at 1:33
Original issue reported on code.google.com by
dcre...@gmail.com
on 28 Apr 2008 at 11:26