- From: Mark Nottingham <mnot@yahoo-inc.com>
- Date: Thu, 22 Jun 2006 14:59:02 -0700
- To: "T.V Raman" <raman@google.com>
- Cc: www-tag@w3.org
The "default" HTTP way to solve the problem posed in section 2.1 would be server-driven conneg; i.e., sending the correct representation in response to the request for http://example.com/ ubiquity/resource, along with the appropriate Vary header and a Content-Location header that can be used to determine where that specific representation can be found again. If you're suggesting that redirection is better, it would be good to say why. Cheers, On 2006/06/22, at 6:07 AM, T.V Raman wrote: > > I've updated the document at > http://www.w3.org/2001/tag/doc/alternatives-discovery.html > Comments welcome. > > ToDos: > > I'd still like to draw a nice generic schematic diagram in the > final section showing how a canonical URI can have various pieces > of context bound into it to create a multiplicity of URIs. > > -- > -- T. V. Raman > > -- Mark Nottingham mnot@yahoo-inc.com
Received on Thursday, 22 June 2006 21:59:40 UTC