[
Lists Home |
Date Index |
Thread Index
]
The normalization of CR, LF and CRLF can be avoided by using their
character entities. So I still can preserve fidelity.
hexBinary and base64Binary does not scale to the user (mostly text data
with a few low ASCII characters intermingled, so people want to be able
to read the data) and high-performance scenarios (no time to
encode/decode into binary) needed in the database and SOAP scenarios.
Best regards
Michael
> -----Original Message-----
> From: MURATA Makoto [mailto:murata@hokkaido.email.ne.jp]
> Sent: Wednesday, December 19, 2001 8:17 AM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Some comments on the 1.1 draft
>
> From: "Michael Rys" <mrys@microsoft.com>
> Subject: RE: [xml-dev] Some comments on the 1.1 draft
> Date: Tue, 18 Dec 2001 16:54:39 -0800
>
> > Tim, with all due respect, but allowing #x0-@x1F inside element and
> > attribute content would tremedeously help users of XML that use
non-XML
> > string sources for their data and map it into XML without loosing
> > fidelity and without having to base 64 encode otherwise normal
strings.
>
> Since CR and LF are normalized to CRLF by the XML parser, how can you
> expect fidelity? Allowing C0 control functions to not provide any
> fidelity. It merely causes problems.
>
> I think that we should rely on hexBinary and base64Binary of
> XML Schema. :-)
>
> Cheers,
>
> Makoto
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
|
