W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > July to September 2006

RE: fragment identifiers and media types (was RE: XPointer considered incomprehensible)

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Tue, 5 Sep 2006 12:37:53 -0400
Message-ID: <EBBD956B8A9002479B0C9CE9FE14A6C201143C17@tayexc19.americas.cpqcorp.net>
To: <simonstl@simonstl.com>
Cc: <noah_mendelsohn@us.ibm.com>, "Bjoern Hoehrmann" <derhoermi@gmx.net>, <www-tag@w3.org>, <www-xml-linking-comments@w3.org>, "Jonathan Marsh" <jmarsh@microsoft.com>

> From: Simon St.Laurent
> 
> . . .  For a URI reference like:
> 
> http://simonstl.com/#news
> 
> The interpretation of the fragment identifier depends on the 
> media type returned.  URI philosophers will likely wave their 
> hands and say this isn't a problem. 

As a side comment, this is precisely why, in my opinion, hash URIs are
unsuitable as *general purpose* identifiers: the meaning of the URI is
tied to the media type that is returned when the racine is dereferenced.
(The racine is the part before the hash.)  I.e., the meaning of this
URI:
	http://simonstl.com/#news
depends on the media type that is returned when this other, related URI:
	http://simonstl.com/
is dereferenced.  This may be fine if one is willing to limit one's self
to certain media types, but it is not very general purpose.

Slash URIs using 303-redirects do not have this limitation.  For
example, if
	http://simonstl.com/news
does a 303 "See Other" redirect to
	http://simonstl.com/
then
	http://simonstl.com/news
could identify any resource, independent of the media type returned when
	http://simonstl.com/
is dereferenced.


David Booth, Ph.D.
HP Software
dbooth@hp.com
Phone: +1 617 629 8881
Received on Tuesday, 5 September 2006 16:54:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:46 GMT