[gcs-pcs-list] on using URIs

[Daniel Chudnov]

Young,Jeff (OR) wrote, on Wed, Mar 01, 2006 at 02:06:12PM -0500:
> > 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.
...
> 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:

I think it's a good idea to create an OpenURL Community Profile for
unAPI-like services.  Other members of this list have exchanged messages
with me off-list suggesting something similar, so you'd probably have
willing and knowledgeable collaborators.  Plus, if unAPI fails, then we
could all just use the OpenURL profile. :)

The unAPI specification is not OpenURL, and it isn't intended to be,
so direct compliance doesn't seem to me to offer anything.  Basing the
spec on simple HTTP rather than OpenURL (or any other existing spec)
makes it palpably easier to understand and gives it a chance at succeeding
across communities and across existing protocols on its own merits.

  -Dan


-- 
Daniel Chudnov
Yale Center for Medical Informatics
(203) 737-5789