- From: Miles, AJ \(Alistair\) <A.J.Miles@rl.ac.uk>
- Date: Thu, 10 Mar 2005 18:40:15 -0000
- To: <public-esw-thes@w3.org>
Originally, if you did an HTTP GET from a web browser against ... http://www.w3.org/2004/02/skos/core ... you got a representation of the SKOS Core Vocabulary with MIME type 'application/rdf+xml'. What actually happened was that the Apache server served the file 'core.rdf' from the 2004/02/skos/ directory, which it did automatically (I don't understand precisely how it works, but it has its own system for choosing a best thing to serve). A few months ago I created the directory 2004/02/skos/core/ which had the effect that subsequently an HTTP GET against http://www.w3.org/2004/02/skos/core got redirected to http://www.w3.org/2004/02/skos/core/ . To put things back the way they were I've added a few lines to the .htaccess file in the 2004/02/skos/ directory. Specifically that file now has the following directives ... RewriteEngine On RewriteRule ^core$ core.rdf <Files ~ "core.rdf"> ForceType "application/rdf+xml" </Files> If anyone thinks this isn't the way to go (and I know best practice here is still fuzzy) then let me know. Also, I think I know enough about Apache HTTP server content negotiation to implement some simple content negotiation functionality for the resource http://www.w3.org/2004/02/skos/core (I'd do it via a directive in .htaccess that rewrote the URL such that a .var file got invoked, which then supplied representations according to the requested content-type) - but should content-types other than application/rdf+xml be available, and if so which? Cheers, Al. --- Alistair Miles Research Associate CCLRC - Rutherford Appleton Laboratory Building R1 Room 1.60 Fermi Avenue Chilton Didcot Oxfordshire OX11 0QX United Kingdom Email: a.j.miles@rl.ac.uk Tel: +44 (0)1235 445440
Received on Thursday, 10 March 2005 18:40:47 UTC