W3C home > Mailing lists > Public > semantic-web@w3.org > December 2019

Re: HTML entry point for the RDF Namespace?

From: Ivan Herman <ivan@w3.org>
Date: Thu, 19 Dec 2019 17:18:11 +0100
Cc: semantic-web@w3.org, Kian Schmalenbach <kian.schmalenbach@fau.de>
Message-Id: <BB42EE54-509A-4061-838C-E27F34A9375B@w3.org>
To: Andreas Harth <andreas@harth.org>

> On 19 Dec 2019, at 17:15, Andreas Harth <andreas@harth.org> wrote:
> Hi Ivan,
> On 12/17/19 7:06 AM, Ivan Herman wrote:
>> The question is: are there applications that (would) have problems, with these settings, when referring to the PROV vocabulary? Or would have problems with the RDF core vocabulary if experienced the same returned values?
> the issue seems to be with correctly implementing content negotiation.
> The content negotiation on the PROV vocabulary seems to ignore complex Accept headers, e.g., "Accept: application/ld+json,application/n-quads,application/n-triples,application/rdf+xml,application/trig,text/turtle;q=0.95,text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8".
> Also, Apache (2.4.38) also seems to have problems to correctly handle complex Accept headers (check with a foo.html and a foo.ttl file and GET foo with Accept headers of increasing complexity).

Our server runs Apache. The conneg is done via pure apache tools, namely using xxxx.var files to describe the alternatives. Ie, if apache has a problem, then prov has a problem:-(

I must admit what this all tells me that maybe it is more cautious not to install the HTML fileā€¦


> DBpedia, on the other hand, works nicely.
> Cheers,
> Andreas.

Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704
Received on Thursday, 19 December 2019 16:18:20 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:46:02 UTC