<br><div><span class="gmail_quote">On 11/19/06, <b class="gmail_sendername">Herbert Van de Sompel</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(2) A facet of the problem domain that unAPI covers has been explored in<br>other contexts. A generic formulation of that problem could be (if I<br>dare) "How to obtain (in an interoperable manner) a manifest of all
<br>available Representations of a Resource" (to use W3C Web architecture<br>language). </blockquote><div><br>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.
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The parties that I know have explored this problem area (see<br>below) have all used different ways to frame the problem, different
<br>operating contexts to explore it, and different approaches to tackle it.<br> This problem, as well as all the existing ideas regarding ways to<br>approach it will almost certainly be on the ORE discussion table. And,
<br>obviously I hope that the ORE group can propose an informed and inspired<br>resolution.<br><br>A few pointers to explorations of this problem domain in our community:<br><br>(*) unAPI: <<a href="http://unapi.info/">
http://unapi.info/</a>><br><br>(*) DLF-Aquifer Asset Actions Experiment:<br><<a href="http://dx.doi.org/10.1045/october2006-cole">http://dx.doi.org/10.1045/october2006-cole</a>><br><br>(*) the Pathways Obtain service hinted at in our recent D-Lib paper
<br><<a href="http://www.dlib.org/dlib/october06/vandesompel/10vandesompel.html">http://www.dlib.org/dlib/october06/vandesompel/10vandesompel.html</a>><br><br>(*) The "obtain" service environment described in Jeroen Bekaert's Phd
<br>thesis <<a href="http://hdl.handle.net/1854/4833">http://hdl.handle.net/1854/4833</a>>.<br><br>But see also the recent<br><<a href="http://www.w3.org/QA/2006/10/missing_http_feature.html">http://www.w3.org/QA/2006/10/missing_http_feature.html
</a>> as an<br>illustration that this issue is not only on the minds of our community.<br><br></blockquote></div>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 aggregators.
<br><br>did i miss something?<br>regards,<br>robert<br>