Re: httpRange-14 Two Years On

On 4 Dec 2007, at 17:15, Sean B. Palmer wrote:
> You can do an HTTP GET on
> http://example.org/amaya and if it returns a 200 then it must be an
> information resource, so it can't be a tool but it could be
> documentation. And if you get a 303 then... well it could be either.
>
> But then... that doesn't really resolve *anything* does it? If it
> returns a 200 then it could be documentation about Amaya or it could
> be Moby Dick, and if it returns a 303 then it could be Amaya, or
> documentation about Amaya, or Moby Dick, or the moon, or a unicorn, or
> anything.

Post-httpRange-14, if it returns a 200, and opening it in a web  
browser says “Amaya homepage”, then it's a document about Amaya, and  
it is not the tool.

Pre-httpRange-14, it was anyone's guess if it was the documentation or  
the tool. Essentially it was impossible to use web page URIs in RDF  
statements, because you were never sure how others would interpret  
them. You might not remember, but that uncertainty was a major pain.

Richard


>
>
> In other words, httpRange-14 doesn't help out in this case at all. As
> I just wrote to David Booth, I don't understand what intrinsic
> beneficial properties InformationResource has in the wider case
> either—intrinsic properties that are beneficial enough to offset make
> publishing stuff on the Semantic Web such a pain. I know there's a lot
> of noise about this right now... but perhaps there's due cause.
>
> Somebody help me out here?
>
> -- 
> Sean B. Palmer, http://inamidst.com/sbp/

Received on Tuesday, 4 December 2007 17:50:16 UTC