Jonathan, Don't confuse the SAP community for OpenURL in general. It is the community profiles and their implied consensus that are the limiting factors in this case.
In contrast, I can imagine other OpenURL profiles that are open-ended and dynamic, although I would agree this is somewhat problematic given the current community profile schema. Jeff > -----Original Message----- > From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > Jonathan Rochkind > Sent: Wednesday, January 07, 2009 12:40 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] audio/video citations in an OpenURL > > Would it be a legal OpenURL to use any of those in an OpenURL? They > aren't approved for OpenURL use, right? > > But if I have to do something non-standard with OpenURL, might as well > use a non-OpenURL standard, sure. > > In general, the lack of easy extensibility of OpenURL is a flaw that > hopefully we will learn from in subsequent standards. > > Jonathan > > Ross Singer wrote: > > On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind <rochk...@jhu.edu> > wrote: > > > > > >> Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there > >> is no format for an XML DC? Kind of odd), and use the "type" element. > >> > > > > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc > > > > Other possibilities here would be: > > > > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:MARC21 > > > > and > > > > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:mods > > > > The latter is in trial use, but it would be odd for it not to be > > approved at some point in the not too distant future. > > > > -Ross. > > > > > > -- > Jonathan Rochkind > Digital Services Software Engineer > The Sheridan Libraries > Johns Hopkins University > 410.516.8886 > rochkind (at) jhu.edu
