[gcs-pcs-list] on using URIs

Young,Jeff (OR) jyoung at oclc.org
Wed Mar 1 16:24:32 EST 2006


Uncle.

> -----Original Message-----
> From: gcs-pcs-list-bounces at cipolo.med.yale.edu [mailto:gcs-pcs-list-
> bounces at cipolo.med.yale.edu] On Behalf Of Alf Eaton
> Sent: Wednesday, March 01, 2006 4:17 PM
> To: GCS-PCS list
> Subject: Re: [gcs-pcs-list] on using URIs
> 
> On 01 Mar 2006, at 13:31, Young,Jeff (OR) wrote:
> 
> > I'm not saying unAPI isn't worthwhile. I'm saying that unAPI should
be
> > implemented as a profile of OpenURL. Everyone is so convinced
> > OpenURL is
> > incomprehensible that their brains shut down immediately. I'm
claiming
> > that converting the existing unAPI protocol to be OpenURL 1.0
> > compliant
> > is utterly trivial. Here's what it would take:
> >
> > 1) Add "url_ver= Z39.88-2004" in the "microformat" span
> 
> Which just made it about 10x harder to implement.
> 
> > 2) rename "uri" to "rft_id" in the span
> 
> Ditto.
> 
> > 3) Change the resolver so it doesn't blow up when it
> > sees the url_ver
> > parameter
> 
> Surely an OpenURL resolver shouldn't ignore the parameter passed to
> it that tells it what kind of OpenURL it has to handle?
> 
> > 4) Change the resolver to look for "rft_id" in place of "uri"
> >
> > You are now 100% OpenURL 1.0 compliant.
> 
> Great - what do I win?
> 
> alf (sarcastically, but only because I think the chances of
> persuading everyone to do this are much higher if it looks as much
> like a simple microformat as possible).
> _______________________________________________
> gcs-pcs-list mailing list
> gcs-pcs-list at cipolo.med.yale.edu
> http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list


More information about the gcs-pcs-list mailing list