I wish I had time to contribute to all of this properly - next month after our portal launch I should. My quick take on this is that a proxified LSID is not to be treated as a GUID. A proxy's responsibility should simply be to retrieve the data for an LSID.
I recognise that there are still many concerns (often mutually contradictory) about how this LSID infrastructure can and will actually work out. Right now, however, we have a significant number of projects of different sizes all setting up LSIDs and LSID resolution for their data, mostly in time for the meeting in Bratislava. I believe that we should seek to document all of these experiences to determine the success of the approach. As I suggested before the current proposal to use a proxy in certain contexts is an attempt to address a range of specific concerns about some aspects of the standard, but should also give us the opportunity to switch smoothly to an HTTP URI-based approach if that ultimately does seem more sensible.
I think the critical thing is for us to respond to the call Chuck issued earlier to have some kind of "Bratislava Declaration" that provides a clear and coherent statement of how and when to use LSIDs - I will make it a priority in July to contribute to producing such a statement. Most of the constituent parts already exist, but they clearly need better packaging and some fine tuning.
Thanks,
Donald ------------------------------------------------------------ Donald Hobern (dhobern@gbif.org) Deputy Director for Informatics Global Biodiversity Information Facility Secretariat Universitetsparken 15, DK-2100 Copenhagen, Denmark Tel: +45-35321483 Mobile: +45-28751483 Fax: +45-35321480 ------------------------------------------------------------
On Jun 12, 2007, at 11:02 PM, Bob Morris wrote:
Is the http proxy a GUID?
What vouches for an assertion that a given proxy actually resolves the associated LSID?
On 6/12/07, Kevin Richards RichardsK@landcareresearch.co.nz wrote:
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 http://wiki.tdwg.org/twiki/bin/view/GUID/ LsidHttpProxyUsageRecommendation).
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 http:/lsid.tdwg.org/[lsid].
Kevin
"Gregor Hagedorn" G.Hagedorn@BBA.DE 12/06/2007 7:17:35 p.m. >>>
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:Names:0F9D60F1-59C7-495D- A37E-09C23770DD18
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
tdwg-guid mailing list tdwg-guid@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-guid +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++ WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments.
The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research.
Landcare Research http://www.landcareresearch.co.nz +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++
tdwg-guid mailing list tdwg-guid@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-guid
tdwg-guid mailing list tdwg-guid@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-guid