For those wanting another LSID http proxy example, I have changed our LSID resolver here at Landcare to serve up the proxy compliant RDF.
Eg http://lsid.landcareresearch.co.nz/lsid/URN:LSID:landcareresearch.co.nz:Name...
returns the metadata for the lsid URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18
I took me about an hour to change the RDF generator and setup a redirection web directory on our web server (Microsoft IIS).
I have an object with
URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18
I think the problem is that, without me telling my software something I have gathered from this email, my software has no means to know about what you describe as easy.
Unless it has an LSID resolver, in which case it would not need the http method.
This is what the proposal to always use alternating http and LSID guids in any object we communicate about is saying. Whenever you publish URN:LSID:landcareresearch.co.nz:Names:0F9D60F1-59C7-495D-A37E-09C23770DD18 you also have to provide the http version of it.
Gregor---------------------------------------------------------- Gregor Hagedorn (G.Hagedorn@bba.de) Institute for Plant Virology, Microbiology, and Biosafety Federal Research Center for Agriculture and Forestry (BBA) Königin-Luise-Str. 19 Tel: +49-30-8304-2220 14195 Berlin, Germany Fax: +49-30-8304-2203