PURL and 303's

• From: John McClure <jmcclure@hypergrove.com>
• Date: Wed, 7 Sep 2005 16:57:46 -0700
• To: "Booth, David \(HP Software - Boston\)" <dbooth@hp.com>
• Cc: <public-swbp-wg@w3.org>
• Message-ID: <MGEEIEEKKOMOLNHJAHMKCELODOAA.jmcclure@hypergrove.com>

I don't recall seeing a note about the relationship of the
"thing-described-by.org approach" with the PURL service provided by the OCLC
(see http://purl.oclc.org/).... Is there a need for both? Or is the PURL service
ultimately intended to be passe?

Their site says
	"Functionally, a PURL is a URL. However, instead of pointing directly to
	the location of an Internet resource, a PURL points to an intermediate
	resolution service. The PURL resolution service associates the PURL
	with the actual URL and returns that URL to the client. The client can
	then complete the URL transaction in the normal fashion.

	In Web parlance, this is a standard HTTP "redirect".

They also state that the 'future' solution is to use URNs for (library)
resources, so I'd also appreciate hearing about the relationship of URNs to the
"thing-described-by.org approach".

Thanks
John McClure

Received on Wednesday, 7 September 2005 23:56:27 UTC