- From: Williams, Stuart <skw@hplb.hpl.hp.com>
- Date: Thu, 6 Feb 2003 05:21:28 -0000
- To: Martin Duerst <duerst@w3.org>
- Cc: Michel Suignard <michelsu@microsoft.com>, www-international@w3.org, www-tag@w3.org
Hello Martin, > -----Original Message----- > From: Martin Duerst [mailto:duerst@w3.org] > Sent: 04 February 2003 23:20 > To: Williams, Stuart > Cc: Michel Suignard; www-international@w3.org; www-tag@w3.org > Subject: RE: proposed text on IRIEverywhere-27 > > > Hello Stuart, > > At 12:19 03/02/04 +0000, Williams, Stuart wrote: > >Hi Martin, > > > >In the 2nd comparision, if the fully escaped sequences are for comparison > >only, I'm not sure why you protected these 14 characters from being % > >escaped. Is there a reason why excluding them from the expansion is > >neccessary? > > Yes, there is a very clear reason. These characters are reserved. > RFC 2396, in "2.2. Reserved Characters", lists the following as > reserved: > > reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" | > "$" | "," > > To this, we have to add [ and ] for ipv6 literals, and # and > % which are in effect reserved, but treated differently in the > syntax. Escaping them would leave to strange results, > http://www.example.org/path/file > is definitely NOT the same as > http://www.example.org/path%2Ffile . Ok... I've got it... prevents the 'reserved' characters and friends matching their escaped forms. Thanks... <snip/> > > Regards, Martin. > Stuart
Received on Thursday, 6 February 2003 00:25:45 UTC