[OAI-implementers] repository auto-discovery
robert at livingreviews.org
Sun Nov 19 05:16:46 EST 2006
just one more pointer to the use of autodiscovery in related contexts:
and like opensearch auto-discovery helps browser extensions, oai pmh should
help browser based applications like zotero.
On 11/19/06, Robert Forkel <robert at livingreviews.org> wrote:
> On 11/19/06, Herbert Van de Sompel <herbertv at lanl.gov> wrote:
> > (2) A facet of the problem domain that unAPI covers has been explored in
> > other contexts. A generic formulation of that problem could be (if I
> > dare) "How to obtain (in an interoperable manner) a manifest of all
> > available Representations of a Resource" (to use W3C Web architecture
> > language).
> well, i'm aiming at something much lower: namely, how to get the baseUrl
> of an OAI PMH data provider? and it seems particularly embarassing, that i
> have no standard way to advertise my own service to people (including
> robots) surfing my own pages.
> > The parties that I know have explored this problem area (see
> > below) have all used different ways to frame the problem, different
> > operating contexts to explore it, and different approaches to tackle it.
> > This problem, as well as all the existing ideas regarding ways to
> > approach it will almost certainly be on the ORE discussion table. And,
> > obviously I hope that the ORE group can propose an informed and inspired
> > resolution.
> > A few pointers to explorations of this problem domain in our community:
> > (*) unAPI: < http://unapi.info/>
> > (*) DLF-Aquifer Asset Actions Experiment:
> > <http://dx.doi.org/10.1045/october2006-cole>
> > (*) the Pathways Obtain service hinted at in our recent D-Lib paper
> > <http://www.dlib.org/dlib/october06/vandesompel/10vandesompel.html>
> > (*) The "obtain" service environment described in Jeroen Bekaert's Phd
> > thesis <http://hdl.handle.net/1854/4833>.
> > But see also the recent
> > <http://www.w3.org/QA/2006/10/missing_http_feature.html > as an
> > illustration that this issue is not only on the minds of our community.
> > looking at these resources, they seem to also focus on the problem you
> stated, but less so on my much smaller one. bekaert says something about the
> repository index in lanl's adore architecture. while this is closest to the
> problem i'd like to solve, as far as i can see, all attempts for global oai
> repository indexes have failed. at least there seems to be no service which
> can resolve oai identifiers to repository baseUrls. so i'd be hoping for the
> rss way. feed auto-discovery definitely helped a lot to establish feed
> did i miss something?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OAI-implementers