[gcs-pcs-list] on using URIs

[Mike Rylander]

On 3/1/06, Young,Jeff (OR) <jyoung at oclc.org> wrote:
> > Yes... cool... I get it.  unAPI can be implemented as a profile of
> > OpenURL, and in your opinion, it should be.  And unAPI conventions
> > can be converted trivially to OpenURL.  Right.  No arguments here.
> >
> > But:  are you saying we should change unAPI-the-specification to make
> > it an OpenURL profile?  Your words don't say that explicitly, but
> > your tone implies it, and regrettably, we're not at the same table at
> > the bar anymore, so I can't guess whether this is really what you
> > mean or not. :(
>
> If you change the unAPI specification to include a url_ver parameter and
> use rft_id in place of url, I think you're 99% of the way there. If
> implementers obey these rules, OpenURL 1.0 compliance comes for free.
> Your spec could link to the OpenURL 1.0 spec and unAPI Community Profile
> as footnotes.

Or, you can just follow 'net convention and be "liberal on read,
strict on write", and implement the unAPI spec on top of your existing
OpenURL server.  I, however, have no plans to build my own OpenURL
resolver any time soon.  That implies far to much functionality, and
I'd rather not get blasted for having a crappy OpenURL server instead
of a great unAPI server.

Just my $.02 ... :)

>
> BTW, Community Profile means something specific in OpenURL terms and
> refers to an entry in the OpenURL Registry. For example, here is a
> "Dublin Core" profile:
>
> http://www.openurl.info/registry/docs/pro/info:ofi/pro:dccp-2004
>
> The profile for unAPI would be much simpler and I would be happy to mock
> one up for you.
>
> Jeff
>
> _______________________________________________
> gcs-pcs-list mailing list
> gcs-pcs-list at cipolo.med.yale.edu
> http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list
>


--
Mike Rylander
mrylander at gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org