- From: John Kemp <john.kemp@nokia.com>
- Date: Thu, 2 Apr 2009 11:32:45 -0400
- To: "ext noah_mendelsohn@us.ibm.com" <noah_mendelsohn@us.ibm.com>
- Cc: "www-tag@w3.org" <www-tag@w3.org>
On Apr 1, 2009, at 6:25 PM, ext noah_mendelsohn@us.ibm.com wrote: > Reading the draft F2F minutes at [1] I'm reminded that one of the > concerns > we had about the draft we're considering publishing [2] is that its > title > is: > > "Usage Patterns For Client-Side URL parameters" > > and that throughout the text URL is used where URI might be more > appropriate. What would a '#' mean in a URN? RFC2141[1] suggests that '#' is a reserved character, and would thus require escaping. - johnk [1] http://www.ietf.org/rfc/rfc2141.txt > > > I suggest that we change the title and the content to use "URI" > prior to > publication of the working draft. I suppose I would on balance be > against > changing url to uri in the URI itself: > http://www.w3.org/2001/tag/doc/hash-in-url.html, on the theory that > cool > uri's don't change. If someone wants to go to the trouble of > setting up a > redirect from http://www.w3.org/2001/tag/doc/hash-in-url.html to > http://www.w3.org/2001/tag/doc/hash-in-uri.html and publishing the > document there, I wouldn't be opposed. Probably not worth the > hassle at > this point. > > Noah > > [1] http://www.w3.org/2001/tag/2009/03/04-minutes.html#item02 > [2] http://www.w3.org/2001/tag/doc/hash-in-url.html > > -------------------------------------- > Noah Mendelsohn > IBM Corporation > One Rogers Street > Cambridge, MA 02142 > 1-617-693-4036 > -------------------------------------- > > > > >
Received on Thursday, 2 April 2009 15:33:56 UTC