Hello Jonathan,

Thanks much for your comments. They are very relevant.

In fact, we (more specifically, Roger Hyam) thought about having the proxy respond with 303 codes just like you recommended. We just decided to leave it out of the HTTP proxy recommendation (on that wiki page) so that we could keep the document simple and reach more people.

We also left the 303 response recommendations out of our LSID Applicability Statement (the doc that specifies how our community should use LSIDS) for the sake of clarity and simplicity. Our current thought is to pack all requirements for LSID HTTP proxies (and their users) in a separate document.

But in short, we have been thinking about adding those recommendations to the proxy server. We'll do that soon.

As the English say: Intelligent minds think alike, but fools seldom differ ;)

Cheers,

Ricardo

Jonathan Rees wrote:

Not that *your* RDF is a dogpile.... it's quite lovely.

May I suggest you put the http/urn owl:sameAs assertion directly into the RDF served from the proxy/lsid server?

Of course, in cases where you want the LSID to denote a document (presumably the one whose content is returned by an LSID getData request), you can sameAs to a 200-responding network resource. This would provide the data, not its metadata. An LSID denotes either its data (getData) or something that's not data, and the so-called "metadata" (really a description, since it's not necessarily about data) is a description of either the data (getData) or of something else.

Jonathan

On Oct 14, 2007, at 6:01 PM, Jonathan Rees wrote:

...

Comment added to http://wiki.tdwg.org/twiki/bin/view/GUID/LsidHttpProxyUsageRecommendation : (hope that's OK)

If you are going to do this, I recommend that the http://lsid.tdwg.org/... URIs result in 303 responses from the server. You want the LSIDs to denote domain objects, and you want the proxy HTTP URIs to denote the same things (that's what owl:sameAs means). But according to current semantic web practice, a 200-responding URI necessarily denotes the document (actually the "network resource"), so your current server behavior is saying something nonsensical, that a dog is a document. If you do a 303 See Other to a second URI that identifies the document carrying the RDF, then you'll be following W3C TAG recommendation httpRange-14 (see http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.html) and your service will make semantic web tools and pedants happier, and no one will confuse a dog with a dogpile of RDF. -- Main.JonathanRees - 14 Oct 2007

---

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