OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Some comments on the 1.1 draft

[ Lists Home | Date Index | Thread Index ]

> From: Rick Jelliffe [mailto:ricko@allette.com.au]
> Sent: Wednesday, December 19, 2001 11:00 AM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Some comments on the 1.1 draft
>  From: "Julian Reschke" <julian.reschke@gmx.de>
>  > I think the pressure to extend the XML character set to
> control characters
> > could be minimized if there would be a "common" way to embed these
> > characters without changing XML. Maybe the SOAP WG, the WebDAV
> WG and other
> > affected parties should try to come up with a common proposal
> (which could
> > then be implemented as SAX filter).
> If your data is not text, then don't transmit it as text.

I guess it depends on the definition of "text". You are right that those who
defined WebDAV should have thought of this, but they didn't.

Besides, if something is "almost always" XML text, making the payload hex-
or base64-encoded  would make the protocol messages much harder to read (and
more inefficient to process).

> Transmit it as binary,
> such as using a bin64 encoding.
> More to the point, why do you want to encourage author names with
> control characters in them?  Surely they would break receiving systems

I don't want to.

> that want to display anyway--or are the control character performing
> some kind of formatting?

How could I know? A property in WebDAV can be *anything*.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS