|
From: sneumann <sne...@ip...> - 2008-01-15 09:36:27
|
Hi,
we'vre just experienced a problem with an mzData converter,
and that kind of bug might easily slip into mzML converters,
so we'd like to mention that here.
We have a PC setup for our Qstar with Analyst and wiff2mzData converter,
which works fine. Recently we set up a new PC, which now has german setting=
s
as default. Guess what, in the XML we find
<spectrumInstrument msLevel=3D"1" mzRangeStart=3D"75,00" mzRangeS=
top=3D"1000,00">
<cvParam cvLabel=3D"psi" accession=3D"PSI:1000038" name=3D"Time=
InMinutes" value=3D"0,033" />
In the mzdata.xsd value is a string, so (syntactically) 0,033 is fine:
<xs:attribute name=3D"value" type=3D"xs:string" use=3D"optional">
and mzRange is defined as float:
<xs:attribute name=3D"mzRangeStart" type=3D"xs:float" use=3D"optional"/>
The character encoding is defined in the first line of the XML files,
<?xml version=3D"1.0" encoding=3D"utf-8"?>
but how are different locales (supposed to be) handled ?=20
I know this is a very implementation-related question,=20
but I'd suggest to at least mention this kind of issue=20
in the documentation.
Yours,
Steffen
--=20
IPB Halle AG Massenspektrometrie & Bioinformatik
Dr. Steffen Neumann http://www.IPB-Halle.DE
Weinberg 3 http://msbi.bic-gh.de
06120 Halle Tel. +49 (0) 345 5582 - 1470
+49 (0) 345 5582 - 0
sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
|