W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2003

RE: XInclude and MTOM

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Mon, 15 Sep 2003 11:06:19 -0700
Message-ID: <7C083876C492EB4BAAF6B3AE0732970E0CA5A16F@red-msg-08.redmond.corp.microsoft.com>
To: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>, <xml-dist-app@w3.org>

By canonical form I mean as per XML Schema datatypes ( or in this case,
the soon to be published errata document ).

Apologies for any confusion.

Gudge

> -----Original Message-----
> From: Elliotte Rusty Harold [mailto:elharo@metalab.unc.edu] 
> Sent: 15 September 2003 18:26
> To: Martin Gudgin; xml-dist-app@w3.org
> Subject: Re: XInclude and MTOM
> 
> At 8:31 AM -0700 9/15/03, Martin Gudgin wrote:
> 
> >1.	Defined a parse type value of base64Binary that allows binary
> >data to be merged into an Infoset.
> >
> >2.	Define whether the character information items merged in 1. are
> >to be in canonical form or not.
> 
> Why would this be an issue? Base 64 values only use the ASCII 
> character set (and not all of that). I think this is always 
> Unicode normalized. Or did you mean something else by 
> canonical form? If you're talking about XML canonicalization, 
> that's not really relevant to the Infoset view. It's very 
> unclear to me what your concern is.
> 
> -- 
> 
>    Elliotte Rusty Harold
>    elharo@metalab.unc.edu
>    Processing XML with Java (Addison-Wesley, 2002)
>    http://www.cafeconleche.org/books/xmljava
>    http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA
> 
> 
Received on Monday, 15 September 2003 14:06:22 GMT

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