W3C home > Mailing lists > Public > www-tag@w3.org > February 2008

Re: [httpRedirections-57] Resource-Decription Header: a possible proposal to consider.

From: Ed Davies <edavies@nildram.co.uk>
Date: Thu, 07 Feb 2008 10:40:52 +0000
Message-ID: <47AAE034.6010800@nildram.co.uk>
To: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>
CC: Richard Cyganiak <richard@cyganiak.de>, "www-tag@w3.org" <www-tag@w3.org>, Graham Klyne <GK@ninebynine.org>, Jonathan Borden <jonathan@openhealth.org>

Richard Cyganiak:
>> Your argument seems to be that 303 redirects are too weak;
>> that the redirect doesn't imply anything more than
>> "try-over-there".

Stuart Williams:
> There are some who make that complaint about 303. They 
> want to be able to make stronger assertions at least about 
> what is at the end of the redirect chain - in particular 
> they like to be able to assert that some (architectural) 
> conformance requirement has been violated *if* following 
> the chain does not yield a description of (amongst other 
> things) ?u. IMO 303 does not and cannot give such an 
> assurance.

Richard Cyganiak:
>> I would like to know why more than this
>> weak implication is necessary on the transport layer.

Stuart Williams:
> Others will have to speak up on that... but roughly 
> AFAIUI its about what it would mean to conform and 
> detecting when a source has failed to conform.

Give or take a few quibbles, 303 and rdfs:seeAlso are
pretty much equivalent.  If such "conformance" is really
required then wouldn't there also be a need for a
strong version of rdfs:seeAlso with similar guarantees?
If such a property hasn't been missed for a while then
surely that's an indication that this conformance
rule is not required.

Ed Davies.
Received on Thursday, 7 February 2008 10:41:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:52 GMT