atom feed151 messages in org.w3.public-lodRe: Is 303 really necessary? (dealing...
FromSent OnAttachments
67 earlier messages
Leigh DoddsNov 5, 2010 2:28 am 
Michael HausenblasNov 5, 2010 2:29 am 
Leigh DoddsNov 5, 2010 2:34 am 
Leigh DoddsNov 5, 2010 2:36 am 
Leigh DoddsNov 5, 2010 2:41 am 
William WaitesNov 5, 2010 2:53 am 
Ian DavisNov 5, 2010 2:57 am 
NathanNov 5, 2010 3:05 am 
NathanNov 5, 2010 3:12 am 
Ian DavisNov 5, 2010 3:16 am 
Ian DavisNov 5, 2010 3:24 am 
NathanNov 5, 2010 3:33 am 
Ian DavisNov 5, 2010 3:40 am 
NathanNov 5, 2010 3:56 am 
Ian DavisNov 5, 2010 3:59 am 
Ian DavisNov 5, 2010 4:01 am 
NathanNov 5, 2010 4:14 am 
Mischa TuffieldNov 5, 2010 4:47 am 
Norman GrayNov 5, 2010 5:11 am 
Dave ReynoldsNov 5, 2010 5:38 am 
NathanNov 5, 2010 5:52 am 
NathanNov 5, 2010 5:56 am 
Vasiliy FaronovNov 5, 2010 6:00 am 
Vasiliy FaronovNov 5, 2010 6:33 am 
NathanNov 5, 2010 7:17 am 
David WoodNov 5, 2010 7:18 am 
Pat HayesNov 5, 2010 7:27 am 
Ian DavisNov 5, 2010 8:12 am 
Kingsley IdehenNov 5, 2010 8:18 am 
NathanNov 5, 2010 8:39 am 
Kingsley IdehenNov 5, 2010 9:35 am 
Pat HayesNov 5, 2010 10:29 am 
Kingsley IdehenNov 5, 2010 10:30 am 
NathanNov 5, 2010 10:37 am 
Hugh GlaserNov 5, 2010 10:50 am 
David BoothNov 6, 2010 1:41 pm 
Norman GrayNov 6, 2010 3:45 pm 
Kingsley IdehenNov 6, 2010 4:07 pm 
David BoothNov 7, 2010 10:27 pm 
David BoothNov 7, 2010 10:27 pm 
Tore ErikssonNov 7, 2010 11:17 pm 
Toby InksterNov 8, 2010 12:36 am 
Toby InksterNov 8, 2010 2:10 am 
David BoothNov 8, 2010 6:39 am 
David BoothNov 8, 2010 6:42 am 
Norman GrayNov 8, 2010 7:51 am 
Toby InksterNov 8, 2010 8:03 am 
David BoothNov 8, 2010 12:33 pm 
Lars HeuerNov 8, 2010 1:16 pm 
David BoothNov 8, 2010 1:35 pm 
Dave ReynoldsNov 8, 2010 1:50 pm 
David BoothNov 8, 2010 3:34 pm 
Tore ErikssonNov 8, 2010 5:51 pm 
Dave ReynoldsNov 9, 2010 6:36 am 
Lars HeuerNov 9, 2010 8:00 am 
Kjetil KjernsmoNov 10, 2010 7:13 am 
Jason BorroNov 11, 2010 11:47 am 
David BoothNov 18, 2010 2:09 pm 
Kingsley IdehenNov 19, 2010 4:25 am 
David BoothNov 19, 2010 1:55 pm 
Kingsley IdehenNov 19, 2010 2:07 pm 
NathanNov 19, 2010 2:57 pm 
Kingsley IdehenNov 19, 2010 5:55 pm 
Bob FerrisNov 26, 2010 6:15 am 
NathanNov 26, 2010 6:29 am 
David BoothNov 26, 2010 9:32 am 
David BoothNov 26, 2010 9:48 am 
Kingsley IdehenNov 26, 2010 12:36 pm 
William WaitesNov 26, 2010 1:47 pm 
Kingsley IdehenNov 26, 2010 6:05 pm 
Richard LightNov 27, 2010 4:47 am 
Tim Berners-LeeNov 27, 2010 12:24 pm 
William WaitesNov 28, 2010 5:47 am 
Giovanni TummarelloNov 28, 2010 5:51 am 
Jiří ProcházkaNov 28, 2010 6:46 am 
Tim Berners-LeeNov 28, 2010 7:07 am 
Kingsley IdehenNov 28, 2010 9:45 am 
Jiří ProcházkaNov 28, 2010 12:51 pm 
Toby InksterNov 28, 2010 3:27 pm 
Kingsley IdehenNov 28, 2010 3:47 pm 
Jiří ProcházkaNov 28, 2010 4:51 pm 
Kingsley IdehenNov 28, 2010 5:15 pm 
James LeighNov 29, 2010 5:54 am 
Bob FerrisDec 14, 2010 2:54 pm 
Subject:Re: Is 303 really necessary? (dealing with ambiguity)
From:David Booth (dav@dbooth.org)
Date:Nov 8, 2010 1:35:24 pm
List:org.w3.public-lod

On Mon, 2010-11-08 at 16:18 +0900, Tore Eriksson wrote:

Hi David,

David Booth wrote:

[ . . . ]

And others may well make statements about that web page. For example, someone crawling the web may make a statement saying that <http://iandavis.com/2010/303/toucan> returned 1027 bytes in response to a GET request. They may not say it in RDF -- they might say it in XML or any other language.

As long as they they are aware that they are talking about a specific representation of this resource I can't see any problem with this. If they think they are stating something about the resource itself, well they would be wrong even if the current URI was an "information resource". They apparently need to learn more about web technology - representations, caching, con-neg, &c.

How about:

"Ian Davis owns web page <http://iandavis.com/2010/303/toucan>."

"The content at <http://iandavis.com/2010/303/toucan> was last updated 7-Nov-2010."

"<http://iandavis.com/2010/303/toucan> has a page rank of 123,456,789."

Those statements are not talking about any specific representations, nor are they talking about the toucan. All are completely reasonable statements for someone knowing nothing about RDF to make.

So I don't think it is reasonable or realistic to think that we can *avoid* creating an ambiguity by returning additional RDF statements with the 200 response. Rather, the heuristic that you propose is a way for applications to *deal* with that ambiguity by tracking the provenance of the information: if one set of assertions was derived from an HTTP 200 response code, and another set of assertions was derived from an RDF document that you trust, then ignore the assertions that were derived from the HTTP 200 response code.

By not drawing ill-founded conclusions about the nature of the resource through the response code, ambiguity could have been avoided in the first place.

Apparently you and I disagree about what it means to be a web page. I personally know of no better qualification criterion for something being a web page than if that thing returns a 200 status code in response to a GET request. Perhaps one would characterize this as duck typing: http://en.wikipedia.org/wiki/Duck_typing What other criteria would you use?

Opinions expressed herein are those of the author and do not necessarily reflect those of Cleveland Clinic.