 |
 |
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of > Jonathan Rochkind > Sent: Wednesday, April 01, 2009 1:23 PM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolution and identification > > Houghton,Andrew wrote: > > > > Organizations need to have a clear understanding of what they are > minting > > URIs for. > > > > Precisely. And in the real world... they don't always have that. Then one could contend that they should not be minting URIs, this is why they get into trouble. No clear policy on what a URI identifies, when is it appropriate to create aliases and when URI aliases are created making sure you use appropriate HTTP mechanisms to redirect them or indicate that they are URI alias. They also need to understand the difference between URIs for Real World Objects, Generic Documents and Web Documents. Failure to understand these issues and you will create a mess. > ONE of the benefits of info is that the registry process forces minters > to develop that clear understanding (to some extent), and documents it > for later users. There are also other pros and cons. Right, but your argument seems to be that you have all these HTTP URIs so rather than sort it out, using appropriate standards based mechanisms, lets create yet another URI to add to all the other URI aliases? Andy.