W3C home > Mailing lists > Public > public-lod@w3.org > June 2009

Re: .htaccess a major bottleneck to Semantic Web adoption / Was: Re: RDFa vs RDF/XML and content negotiation

From: Pat Hayes <phayes@ihmc.us>
Date: Fri, 26 Jun 2009 08:42:27 -0500
Cc: Tom Heath <tom.heath@talis.com>, martin.hepp@ebusiness-unibw.org, Danny Ayers <danny.ayers@gmail.com>, bill.roberts@planet.nl, public-lod@w3.org, semantic-web at W3C <semantic-web@w3c.org>
Message-Id: <79CF139E-5BCB-47FD-8CDF-CE1880484A7B@ihmc.us>
To: Toby A Inkster <tai@g5n.co.uk>

On Jun 26, 2009, at 3:03 AM, Toby A Inkster wrote:

> On 25 Jun 2009, at 21:18, Pat Hayes wrote:
>
>> If [RDF] requires people to tinker with files with names starting  
>> with a dot [...] then the entire SWeb architecture is fundamentally  
>> broken.
>
> RDF doesn't. Apache does.

I should have said, if the process of getting RDF published requires  
people...

Pat

>
> Many hosts do have front ends for configuring Apache, allowing  
> redirects to be set up and content-types configured by filling in  
> simple web forms. But there are such a variety of these tools with  
> different capabilities and different interfaces that it would be  
> difficult to produce advice suitable for them all, so instead  
> ".htaccess" recipes are provided instead.
>
> That said, there are a couple of steps that Martin could remove from  
> his recipe and still be promoting reasonably good practice:
>
> Step 5a - this rewrites <http://example.org/semanticweb> to <http://example.org/semanticweb.rdf 
> >. Other than aesthetics, there's no real reason to do this. Yes,  
> I've read timbl's old Cool URIs document, and understand about not  
> wanting to include hints of file format in a URI. But realistically,  
> this file is going to always include some RDF - perhaps in a non-RDF/ 
> XML serialisation, but I don't see anything inappropriate about  
> serving other RDF serialisations using a ".rdf" URL, provided the  
> correct MIME type is used.
>
> Step 5b - the default Apache mime.types file knows about application/ 
> rdf+xml, so this should be unnecessary. Perhaps instead have a  
> GoodRelations "validator" which checks that the content type is  
> correct, and only suggests this when it is found to be otherwise.
>
> Steps 3 and 4 could be amalgamated into a single "validate your RDF  
> file" step using the aforementioned validator. The validator would  
> be written so that, upon a successful validation, it offers single- 
> click options to ping semweb search engines, and Yahoo (via a RDF/ 
> XML->DataRSS converter).
>
> With those adjustments, the recipe would just be:
>
> 	1. Upload your RDF file.
> 	2. Add a rel="meta" link to it.
> 	3. Validate using our helpful tool.
>
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
>
>
>
>
>

------------------------------------------------------------
IHMC                                     (850)434 8903 or (650)494 3973
40 South Alcaniz St.           (850)202 4416   office
Pensacola                            (850)202 4440   fax
FL 32502                              (850)291 0667   mobile
phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes
Received on Friday, 26 June 2009 13:43:55 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:21 UTC