- From: Jörn Hees <j_hees@cs.uni-kl.de>
- Date: Fri, 5 Nov 2010 15:41:23 +0100
- To: public-lod@w3.org
Ah, it's magic in the header: curl -i http://iandavis.com/2010/303/toucan HTTP/1.1 200 OK Date: Fri, 05 Nov 2010 14:22:40 GMT Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.10 with Suhosin-Patch mod_wsgi/1.3 Python/2.5.2 Content-Location: toucan.rdf Vary: negotiate TCN: choice Last-Modified: Fri, 05 Nov 2010 09:24:27 GMT ETag: "264186-403-4944ad745a8c0;4944ad754eb00" Accept-Ranges: bytes Content-Length: 1027 Content-Type: application/rdf+xml; qs=0.9 Notice the Content-Location field. curl -i http://iandavis.com/2010/303/toucan.rdf HTTP/1.1 200 OK Date: Fri, 05 Nov 2010 14:22:53 GMT Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.10 with Suhosin-Patch mod_wsgi/1.3 Python/2.5.2 Last-Modified: Fri, 05 Nov 2010 09:24:27 GMT ETag: "264186-403-4944ad745a8c0" Accept-Ranges: bytes Content-Length: 1027 Content-Type: application/rdf+xml; qs=0.9 Well, I'd be ok with this, as it lowers the roundtrip problems of 303. But might take a long time till all tools support it and don't get confused. A bit offtopic: I'd rather see people putting information about a responsible sparql endpoint into the play. If you have that you can do a lot more / wiser things than crawling data which is incomplete anyhow (if you dereference a URI you can't expect to get all triples back, which are relevant for you, try http://dbpedia.org/resource/United_States (not the HTML page, but rdf+xml content negotiation and see that you don't even get a label but only incoming links)). Jörn
Received on Friday, 5 November 2010 14:41:59 UTC