W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > August 2007

Re: Remarks on W3C Editor's Draft 6 August 2007

From: Innovimax SARL <innovimax@gmail.com>
Date: Thu, 16 Aug 2007 22:45:41 +0200
Message-ID: <546c6c1c0708161345i67f3377etbafe003330c23897@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: public-xml-processing-model-wg@w3.org

On 8/16/07, Norman Walsh <ndw@nwalsh.com> wrote:
> / Jeni Tennison <jeni@jenitennison.com> was heard to say:
> | I think we should switch to using 'true'/'false' everywhere for option
> | values, since that's what boolean true/false get converted to as
> | strings. If we do that, it makes sense (to me) to switch to true/false
> | everywhere.
>
> We agreed to this on the call, but as I set out to implement it, it became
> pretty clear to me that using xsd:boolean was both easier to specify
> and consistent with other types, so I did that instead.

But I fear we will have to choose our way for "inherited from
Serialisation Spec" options (especially standalone and
omit-declaration)

Mohamed


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 16 August 2007 20:45:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:54 GMT