If GPO had a system where I could resolve Sudoc identifiers, then this
whole problem would be solved right there, I wouldn't need to go any
further, I'd just use the http URI's associated with that system as
identifiers! This whole problem statement is because GPO does not
provide any persistent URIs for sudoc's in the first place, right?
Houghton,Andrew wrote:
From: Code for Libraries [mailto:[email protected]] On Behalf Of
Jonathan Rochkind
Sent: Friday, March 27, 2009 5:28 PM
To: [email protected]
Subject: Re: [CODE4LIB] registering info: uris?
Another good idea, true. There are indeed lots of ways to do this.
But wait, you don't need a unique hostname for a tag uri, a unique uri
(hostname+path) will do? purl.org will only give me the latter, not the
former, right?
Tag URIs require that the authorizing "agency" own the domain name and they
cannot specify a date that is before their domain registration or in the
future. So nobody could mint Tag URIs with purl.org as the domain name.
PURLs might be an interesting solution for you if GAO has a system where
you can resolve SUDOC identifiers. Then you could create a PURL and point
it to their system. Now you get to use your PURL for your project and as
a side benefit get lookup capabilities from GAO! Otherwise you could just
send them to a relevant page on GAO site.
Andy.
