 |
 |
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of > Ray Denenberg, Library of Congress > Sent: Wednesday, April 01, 2009 1:59 PM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolution and identification (was Re: > [CODE4LIB] registering info: uris?) > > We do just fine minting our URIs at LC, Andy. But we do appreciate your > concern. Sorry Ray, that statement wasn't directed at LC in particular, but was a general statement. OCLC doesn’t do any better in this area, especially with WorldCat where there are the same issues I pointed out with your examples and additional issues to boot. The point I was trying to make was *all* organizations need to have clear policies on creating, maintaining, persistence, etc. Failure to do so creates a big mess that takes time to fix, often creating headaches for those using an organizations URIs. Take for example when NISO redesigned their site and broke all the URIs to their standards. Tim Berners-Lee addresses this in his Cool URIs Don't Break article. > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of > Ross Singer > Sent: Wednesday, April 01, 2009 2:07 PM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolution and identification (was Re: > [CODE4LIB] registering info: uris?) > > Ray, you are absolutely right. These would be bad identifiers. But > let's say they're all identical (which I think is what you're saying, > right?), then this just strengthens the case for indirection through a > service like purl.org. Then it doesn't *matter* that all of these are > different locations, there is one URI that represent the concept of > what is being kept at these locations. At the end of the redirect can > be some sort of 300 response that lets the client pick which endpoint > is right for them -or arbitrarily chooses one for them. Exactly, but purl.org is just using standard HTTP protocol mechanisms which could be easily done by LC's site given Ray's examples. What is at issue is the identification of a Real World Object URI for MODS v3.3. Whether I get back an XML schema, a RelaxNG schema, etc. are just Web Documents or representations of that abstract Real World Object. What Ross did was make the PURL the Real World Object URI for MODS v3.3 and used it to redirect to the geographically distributed Web Documents, e.g., representations. LC could have just as well minted one under its own domain. Andy.