[gcs-pcs-list] on using URIs

[Young,Jeff (OR)]

Here is a current unAPI request:

identifier= info%3Adoi%2F10.1126%2Fscience.275.5304.1320

Here is the equivalent request in OpenURL:

url_ver=Z39.88-2004&rft_id=info%3Adoi%2F10.1126%2Fscience.275.5304.1320

If an existing unAPI resolver ignored the url_ver and used "rft_id" in
place of "identifier", it would instantly be OpenURL 1.0 compliant.

Jeff

> -----Original Message-----
> From: Raymond Yee [mailto:yee at berkeley.edu]
> Sent: Wednesday, March 01, 2006 11:02 AM
> To: Young,Jeff (OR)
> Cc: Robert Sanderson; gcs-pcs-list at cipolo.med.yale.edu
> Subject: Re: [gcs-pcs-list] on using URIs
> 
> Hi Jeff,
> 
> Having to implement an OpenURL resolver, even a simple one, just
sounds
> lot of work to me, even if it isn't.    What's the minimum requirement
> to be an OpenURL resolver?  Is there code in various languages that
> shows such a minimum implementation?
> 
> -Raymond
> 
> Young,Jeff (OR) wrote:
> > I don't think my suggestion that unAPI could be implemented with
COinS
> > and an OpenURL resolver implies an unreasonably high barrier for
> > implementers. The resolver wouldn't have to implement the complete
> > protocol, only enough to handle the COinS the server generates for
> > itself. These can be as simple or complex as the situation calls
for.
> >
> > Jeff
> >