W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2004

Re: [XML11TF] (on the "restrictive" option)

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Tue, 16 Mar 2004 10:29:25 -0800
Message-Id: <DA8060AC-7777-11D8-B5F3-000A95BD86C0@bea.com>
Cc: Noah Mendelsohn <noah_mendelsohn@us.ibm.com>, Herve Ruellan <herve.ruellan@crf.canon.fr>, "'XMLP Dist App'" <xml-dist-app@w3.org>
To: Yves Lafon <ylafon@w3.org>

I think that's a separate issue; it's on the receiving side. The 
problem here is on the sending side; you might have a message that's 
perfectly legal, but can't be sent by a binding, because it doesn't 
support some of the characters in it.

On Mar 15, 2004, at 9:04 AM, Yves Lafon wrote:

> Also, if you have a XML 1.0 happy infoset and a serialization in
> iso-8859-1 with some non ascii characters in it, how will react a 
> node, as
> only UTF-8 and UTF-16 encoding are required to be supported?
>
> Restricting to XML 1.0 at the infoset level may not be enough.

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Tuesday, 16 March 2004 13:31:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:16 GMT