[
Lists Home |
Date Index |
Thread Index
]
- To: "Rick Jelliffe" <ricko@allette.com.au>,<xml-dev@lists.xml.org>
- Subject: RE: [xml-dev] Some comments on the 1.1 draft
- From: "Michael Rys" <mrys@microsoft.com>
- Date: Wed, 19 Dec 2001 18:53:27 -0800
- Thread-index: AcGI/lksznoq4A7cQOWRTX1pANOeKQAAwINw
- Thread-topic: [xml-dev] Some comments on the 1.1 draft
They would all mean nothing in the context of the markup (ie they are
exposed as a character information item with their Unicode code point)
and display is left to the output device.
Best regards
Michael
> -----Original Message-----
> From: Rick Jelliffe [mailto:ricko@allette.com.au]
> Sent: Wednesday, December 19, 2001 18:39 PM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Some comments on the 1.1 draft
>
> From: "John Cowan" <jcowan@reutershealth.com>
>
> > Gavin Thomas Nicol wrote:
> >
> > > If you don't do this, your binary data *cannot* be reliably
> transferred,
> > > especially in the face of transcoding.
> >
> > I agree that it is inappropriate to embed binary (octet) data into
> > XML documents. In practice, forbidding #&0; would achieve that
> > purpose.
>
> What about ^D and ^Z?? These have been end-of-file markers for
> text files in various operating systems. What about ^S and ^Q, used
> for flow control in serial comms. What about backspace: what does
> that mean in markup, and how should it be displayed?
>
> Cheers
> Rick Jelliffe
>
>
> -----------------------------------------------------------------
> 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>
|