PURLs

[Marc Salomon]

--Thom (from oclc) wrote:

|I thought that was what I said. Each network would have it's on holding
|library. For example at www.indiana.edu the holding library would be the
|IU library. The _persistence_ needs to be distributed and not just at
|OCLC or LC.

persistence is but one slice of the larger (largest?) problem. replication is
equally as important for certain documents.  one problem i have w/purls was
that it was a one-to-one mapping of purl->url, and for many applications this
hinders scalability. why can't a purl server respond with multiple uri: fields
pointing to replicated documents and the client can decide which to retrieve?

can a client/proxy cache the location: <url> as a substitute for the original
one or will you use the moved temporarily http response code, and if the latter
doesn't this present scaling problems as you double the number of transactions
required to fetch each request?

but i do think that this is a good first step towards experimenting with a
level of indirection in web document access.

-- 
--/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
// Marc Salomon - Software Engineer - Innovative Software Systems Group     \\ 
\\ Library and Center for Knowledge Management - UC, San Francisco          // 
// phone :  415.476.9541 - e-mail : marc at ckm.ucsf.edu - fax: 415.476.4653   \\
\\/\/\/\/\/\/\/\/\/\/\<URL:http://www.ckm.ucsf.edu/marc/>/\/\/\/\/\/\/\/\/\///