Closed GoogleCodeExporter closed 9 years ago
Heidelberg: Maybe easier for a semantic validator to have a mandatory attribute
in place. default attributes may complicate things.
Original comment by eisena...@googlemail.com
on 12 Apr 2011 at 10:06
I'm not sure this rule would be too difficult to implement in a semantic
validator, but it does make the schema a bit more complicated. I'd be
interested in the API developers' viewpoints - how much difference could this
make for saving memory on really big files? - Florian, any comment?
Original comment by andrewro...@googlemail.com
on 12 Apr 2011 at 10:47
Worst case scenario is a peptide database with millions of entries. A redundant
attribute in that case would be significantly inefficient. Of course, the fact
that DBSequence and Peptide are nearly duplicates in that case doesn't help
either.
Original comment by matt.cha...@gmail.com
on 12 Apr 2011 at 1:21
As far as "difficulty" goes, the semantic validators already must deal with
this for mzML, so there is no additional difficulty.
Original comment by matt.cha...@gmail.com
on 12 Apr 2011 at 1:21
Agreement in TeleCon 21.4.2011:
Having attributes repeated will reduce XML file space, but not object model
space (in memory), the API programming gets a little bit more complicated (not
too much).
XML file space from repeated attributes will probably not be as significant as
other parts of the file (like sequences, scores) and should be efficiently
zipped. So for the moment we leave it like it is.
No action point.
Original comment by eisena...@googlemail.com
on 21 Apr 2011 at 4:22
Original issue reported on code.google.com by
matt.cha...@gmail.com
on 7 Apr 2011 at 3:57