W3C home > Mailing lists > Public > public-lod@w3.org > February 2013

Re: Content negotiation for Turtle files

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Wed, 06 Feb 2013 09:23:29 +0000
Message-ID: <51122111.60903@epimorphics.com>
To: public-lod@w3.org
I use the follow .htaccess file:

AddType  text/turtle             .ttl

AddType  application/rdf+xml     .rdf
AddType  application/ld+json     .jsonld
AddType  application/n-triples   .nt
AddType  application/owl+xml     .owl

AddType  text/trig               .trig
AddType  application/n-quads     .nq

	Andy

On 05/02/13 23:49, Bernard Vatant wrote:
> Hello all
>
> Back in 2006, I thought had understood with the help of folks around
> here, how to configure my server for content negotiation at lingvoj.org
> <http://lingvoj.org>.
> Both vocabulary and instances were published in RDF/XML.
>
> I updated the ontology last week, and since after years of happy living
> with RDF/XML people eventually convinced that it was a bad, prehistoric
> and ugly syntax, I decided to be trendy and published the new version in
> Turtle at http://www.lingvoj.org/ontology_v2.0.ttl
>
> The vocabulary URI is still the same : http://www.lingvoj.org/ontology,
> and the namespace http://www.lingvoj.org/ontology# (cool URI don't change)
>
> Then I turned to Vapour to test this new publication, and found out that
> to be happy with the vocabulary URI it has to find some answer when
> requesting application/rdf+xml. But since I have no more RDF/XML file
> for this version, what should I do?
> I turned to best practices document at
> http://www.w3.org/TR/swbp-vocab-pub, but it does not provide examples
> with Turtle, only RDF/XML.
>
> So I blindly put the following in the .htaccess : AddType
> application/rdf+xml .ttl
> I found it a completely stupid and dirty trick ... but amazigly it makes
> Vapour happy.
>
> But now Firefox chokes on http://www.lingvoj.org/ontology_v2.0.ttl
> because it seems to expect a XML file. Chrome has not this issue.
> The LOV-Bot says there is a content negotiation issue and can't get the
> file. So does Parrot.
>
> I feel dumb, but I'm certainly not the only one, I've stumbled upon a
> certain number of vocabularies published in Turtle for which the conneg
> does not seem to be perfectly clear either.
>
> What do I miss, folks? Should I forget about it, and switch back to good
> ol' RDF/XML?
>
> Bernard
>
> --
> *Bernard Vatant
> *
> Vocabularies & Data Engineering
> Tel : + 33 (0)9 71 48 84 59
> Skype : bernard.vatant
> Blog : the wheel and the hub <http://blog.hubjects.com/>
> --------------------------------------------------------
> *Mondeca*****
> 3 cité Nollez 75018 Paris, France
> www.mondeca.com <http://www.mondeca.com/>
> Follow us on Twitter : @mondecanews <http://twitter.com/#%21/mondecanews>
> ----------------------------------------------------------
>
> Meet us at Documation <http://www.documation.fr/> in Paris, March 20-21
>
Received on Wednesday, 6 February 2013 09:24:01 UTC

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