As usual, I like your explanation very much. It borders on sophistry,
but that doesn't bother me much, or won't until my next conversation
with someone who's upset about the use of http: URIs to refer to
things that aren't network resources.
I've copied your email to the wiki page, reformatted
On Oct 11, 2007, at 4:19 PM, Pat Hayes wrote:
URI1 the first URI
endpthe http endpoint identified by URI1
URI2 the URI to which endp redirects URI1
redir the http endpoint identified by URI2
potato the potato which (we all know) URI refers to
Then the following should hold, accordin
I think we are in agreement here, but let me blab on to make sure.
On 10/12/07, Xiaoshu Wang <[EMAIL PROTECTED]> wrote:
> Jonathan,
> > The httpRange-14 resolution [1] is about identification (of a thing
> > by/to an http server), not reference.
> "httpRange-14" is an *engineer* but not a *philos
From: Adrian Walker <[EMAIL PROTECTED]>
Date: Oct 11, 2007 9:21 PM
Subject: Re: [ANN] LENA: Lens-based RDF Browser
Hi Chris --
Would the approach in
www.reengineeringllc.com/demo_agents/RDFQueryLangComparison1.agent
be a candidate? It looks as though the rules could serve as general
purpose
Jonathan,
The httpRange-14 resolution [1] is about identification (of a thing
by/to an http server), not reference.
"httpRange-14" is an *engineer* but not a *philosophical/ontological*
solution because a server response code such as 200/303/404 etc. do not
tell you more about what you alread
