> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of > Mike Taylor > Sent: Thursday, April 02, 2009 10:07 AM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolution and identification (was Re: > [CODE4LIB] registering info: uris?) > > Houghton,Andrew writes: > > > 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. > > That is NOT what I am saying. > > I am saying I am suspicious of a single point of failure. Especially > since the entire architecture of the Internet was (rightly IMHO) > designed with the goal of avoid SPOFs. OK, good, then if you are concerned about the PURL services SPOF, take the freely available PURL software and created a distributed PURL based system and put it up for the community. I think several people have looked at this, but I have not heard of any progress or implementations. Andy.