> From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > Mike Taylor > Sent: Thursday, April 02, 2009 8:41 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] resolution and identification (was Re: > [CODE4LIB] registering info: uris?) > > I have to say I am suspicious of schemes like PURL, which for all > their good points introduce a single point of failure into, well, > everything that uses them. That can't be good. Especially as it's > run by the same compary that also runs the often-unavailable OpenURL > registry.
What you are saying is that you are suspicious of the HTTP protocol. All the PURL server does is use mechanisms specified by the HTTP protocol. Any HTTP server is capable of implementing those same mechanisms. The actual PURL server is a community based service that allows people to create HTTP URIs that redirect to other URIs without having to run an actual HTTP server. If you don't like its single point of failure, then create your own in-house service using your existing HTTP server. I believe the source code for the entire PURL service is freely available and other people have taken the opportunity to run their own in-house or community based service. Andy.
