<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>The main use of the LSID http proxy would be when you have an RDF document or a triple store full of data that has BOTH the LSID and the http version (as described on the wiki page <A href="http://wiki.tdwg.org/twiki/bin/view/GUID/LsidHttpProxyUsageRecommendation">http://wiki.tdwg.org/twiki/bin/view/GUID/LsidHttpProxyUsageRecommendation</A>).</DIV>
<DIV> </DIV>
<DIV>If ALL you had was the LSID "URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18" and no other data at all, and you want to resolve it using the http proxy, then yes you are a bit stuck (as far as I know). Unless we set up an LSID http proxy repository that can be queried and returns the http proxy url for an LSID? Or you could just use the "hard coded" http proxy resolver at <A href="http://.tdwg.org">http:/lsid.tdwg.org</A>/[lsid].</DIV>
<DIV> </DIV>
<DIV>Kevin<BR><BR>>>> "Gregor Hagedorn" <G.Hagedorn@BBA.DE> 12/06/2007 7:17:35 p.m. >>><BR></DIV>
<DIV style="COLOR: #000000">> For those wanting another LSID http proxy example, I have changed our<BR>> LSID resolver here at Landcare to serve up the proxy compliant RDF.<BR>><BR>> Eg<BR>> <A href="http://lsid.landcareresearch.co.nz/lsid/URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18">http://lsid.landcareresearch.co.nz/lsid/URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18</A><BR>><BR>> returns the metadata for the lsid<BR>> URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18<BR>><BR>> I took me about an hour to change the RDF generator and setup a<BR>> redirection web directory on our web server (Microsoft IIS).<BR><BR>I have an object with<BR><BR>URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18<BR><BR>I think the problem is that, without me telling my software something I have<BR>gathered from this email, my software has no means to know about what you<BR>describe as easy.<BR><BR>Unless it has an LSID resolver, in which case it would not need the http<BR>method.<BR><BR>This is what the proposal to always use alternating http and LSID guids in any<BR>object we communicate about is saying. Whenever you publish<BR>URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18 you<BR>also have to provide the http version of it.<BR><BR>Gregor----------------------------------------------------------<BR>Gregor Hagedorn (G.Hagedorn@bba.de)<BR>Institute for Plant Virology, Microbiology, and Biosafety<BR>Federal Research Center for Agriculture and Forestry (BBA)<BR>Königin-Luise-Str. 19 Tel: +49-30-8304-2220<BR>14195 Berlin, Germany Fax: +49-30-8304-2203<BR><BR>_______________________________________________<BR>tdwg-guid mailing list<BR>tdwg-guid@lists.tdwg.org<BR><A href="http://lists.tdwg.org/mailman/listinfo/tdwg-guid">http://lists.tdwg.org/mailman/listinfo/tdwg-guid</A><BR></DIV>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
WARNING: This email and any attachments may be confidential and/or<BR>
privileged. They are intended for the addressee only and are not to be read,<BR>
used, copied or disseminated by anyone receiving them in error. If you are<BR>
not the intended recipient, please notify the sender by return email and<BR>
delete this message and any attachments.<BR>
<BR>
The views expressed in this email are those of the sender and do not<BR>
necessarily reflect the official views of Landcare Research. <BR>
<BR>
Landcare Research<BR>
http://www.landcareresearch.co.nz<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
<BR>
</BODY></HTML>