[Home] [By Thread] [By Date] [Recent Entries]

  • To: Richard Tobin <richard@c...>
  • Subject: Re: Quick Review of XML 1.1 Candidate Recommendation
  • From: Tim Bray <tbray@t...>
  • Date: Wed, 16 Oct 2002 14:22:40 -0700
  • Cc: xml-dev@l...
  • References: <200210162112.WAA10077@s...>
  • User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826

Richard Tobin wrote:
>>By my reading, none of the characters in the 
>>ranges 0-#x7, #xb, #xe-#x1a have any agreed-upon semantics de jure or de 
>>facto (let's go down to the mall and do some &#x16;).

By the way &#x16; is the ASCII character "Synchronous Idle".  I use it 
all the time.

> The only reasonable use I've thought of for these characters is so
> that you can directly refer to them *as characters*.  For example, if
> I want to encode the termcap file in XML, it seems quite reasonable to
> be able to refer to escape as &#27;.  

In the general case where you want to wrap up weird bits of binary 
gibberish to control hardware, why don't you just base64 it and not have 
to worry about which of them are magic C0 Controls and which aren't...

I'm sorry, these things are just on a different planet from respectable 
Unicode characters that aren't a bend-sinister by-blow of the flirtation 
of ASCII with Bell System 201 acoustic couplers.  And you know perfectly 
well that the people who want these aren't trying to exchange termcaps, 
they're trying to wrap binary gibberish in the trappings of XML 
interoperability.  Bah. -Tim


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member