- From: Jonathan Rees <jar@creativecommons.org>
- Date: Wed, 4 Feb 2009 11:50:11 -0500
- To: David Booth <dbooth@hp.com>
- Cc: public-awwsw@w3.org
You can put the same fftr:IR (i.e., identical representation portfolio, with identical time variation) at distinct URIs, with very different results. Consider the case where an HTML representation contains a form with a relative URIref as the action. The action is therefore a function of the URI. Posting to the two action URIs do radically different things (one could cost you money, the other could pay you money). You could argue that they're the same resource, darnit, or you could redefine fftr:IR to be sensitive to the request-URI, but neither fix would cause "resource" to match user expectations around bookmarking (the use case the Tim always brings up).
Received on Wednesday, 4 February 2009 16:50:51 UTC