- From: Booth, David (HP Software - Boston) <dbooth@hp.com>
- Date: Tue, 4 Sep 2007 13:53:11 -0400
- To: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>, <www-tag@w3.org>
> From: Williams, Stuart (HP Labs, Bristol) > > [33]HttpRedirections-57 and Semantic Web Architecture (ISSUE-57) > [ . . . ] > * Review of Draft finding: > [ . . . ] > + Hash URIs Problematic ([38]David Booth) > o any approach based on hash URIs is architecturally > flawed Update: I had complained that hash URIs limit the media type that can be used to serve the associated URI declaration, because the meaning of the fragment identifier depends on the media type returned by the racine, and therefore if one were using a hash URI to identify a person, for example, then one could not serve HTML from the racine, because the HTML media type says that the fragment identifies an element within the returned document. However, Leo, Richard and Max's "Cool URIs" document http://www.dfki.uni-kl.de/~sauermann/2006/11/cooluris/ has suggested a hash/303 hybrid approach that avoids this limitation by having the racine 303-redirect to the URI declaration, which can then be served using any media type. Therefore, my complaint about that limitation of hash URIs should be withdrawn. This media type dependency is not an *inherent* limitation of hash URIs. Rather, it is a limitation of hash URIs only when the racine directly serves information. > [38] http://lists.w3.org/Archives/Public/www-tag/2007Aug/0054 David Booth, Ph.D. HP Software +1 617 629 8881 office | dbooth@hp.com http://www.hp.com/go/software Opinions expressed herein are those of the author and do not represent the official views of HP unless explicitly stated otherwise.
Received on Tuesday, 4 September 2007 17:55:18 UTC