Re: WebIDs and Content-Location

right, content negotiation looks correctly implemented:

http://validator.linkeddata.org/vapour?vocabUri=http%3A%2F%2Fvmuss13.deri.ie%2Ffoafprofiles%2Fhada%23me&classUri=http%3A%2F%2F&propertyUri=http%3A%2F%2F&instanceUri=http%3A%2F%2F&validateRDF=1&defaultResponse=dontmind&userAgent=vapour.sourceforge.net

so it might be a bug on the toolkit used...

On 16 April 2012 00:52, Dave Beckett <dave@dajobe.org> wrote:
> On 4/15/12 2:41 PM, Toby Inkster wrote:
>> On Sun, 15 Apr 2012 21:48:09 +0100
>> Norman Gray <norman@astro.gla.ac.uk> wrote:
>>
>>> tl;dr: content-location trumps request-uri.
>>
>> As per RFC 2616, true.
>>
>> But in practice, most browsers have never implemented this. Some HTTP
>> libraries do though. (libwww-perl does.) There are Internet drafts
>> planned to obsolete RFC 2616, and these change Content-Location's de
>> jure behaviour to match that of browsers.
>>
>> See http://trac.tools.ietf.org/wg/httpbis/trac/ticket/154
>>
>
> For your information I ddid consider this a bug in raptor since it handled
> the Content-Location: header but not a relative URI in C-L.  This is fixed
> in GIT (will be 2.0.8)
>
> Dave
>
>



-- 
Sergio Fernández
CTIC - Technological Center
Parque Científico y Tecnológico de Gijón
C/ Ada Byron, 39 Edificio Centros Tecnológicos
33203 Gijón - Asturias - Spain
Tel.: +34 984 29 12 12
Fax: +34 984 39 06 12
E-mail: sergio.fernandez@fundacionctic.org
http://www.fundacionctic.org
Privacy Policy: http://www.fundacionctic.org/privacidad

Received on Monday, 16 April 2012 07:14:22 UTC