- From: Prescod <prescod@gmail.com>
- Date: Mon, 28 Jul 2008 08:53:12 -0700
- To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
- Cc: "Tim Berners-Lee" <timbl@w3.org>, "Mark Baker" <distobj@acm.org>, "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>, "David Orchard" <orchard@pacificspirit.com>, "Henry S. Thompson" <ht@inf.ed.ac.uk>, "www-tag@w3.org" <www-tag@w3.org>
On Mon, Jul 28, 2008 at 7:39 AM, Booth, David (HP Software - Boston) <dbooth@hp.com> wrote: >> From: Paul Prescod >> [ . . . ] >> Is it the position of Tim, Mark and David Orchard that it would be >> wrong? Dangerous? to define a mechanism for embedding hints for >> alternate resolution protocols inside of HTTP URIs? > > No, it is not wrong. It is fine to embed hints of any kind in HTTP URIs. (I realize you didn't ask me, though.) Can you be more specific about "hints of any kinds?" Do you believe as I do that that there must be an orderly mechanism for recognizing and processing those hints? e.g. a browser vendor could not declare that any URI that embeds the path /netscape/ should be resolved at netscape.com rather than on the host specified in the URI. I believe that the three current proposals are: * use the most specific bit of the domain name as a way of triggering hinting * use the least specific bits of the domain name * invent a new convention in paths like /foo:/ which would allow the hint to be orthogonal to the HTTP domain Paul Prescod
Received on Monday, 28 July 2008 15:53:52 UTC