Re: yet another sidetrack on what a URI identifies

> Unfortunately, your model doesn't work for me, in trying to to
> effectively use URIs in knowledge representation languages (like RDF).

Why?  Every statement to that effect has so far been disproven, not
by me but by members of the RDF interest group.  What exactly is it
that breaks in the REST model?

I know why your model breaks.  Try describing caching.  For real,
not in your imagination, but on paper and with appropriate definitions
for the metadata that is included in HTTP responses so that the
client has an interoperable clue as to what you are talking about.
Then try describing hierarchical proxies, gateways, etc.  And if you
are willing to continue work on that model, use it to describe the
semantics of a Web to GSM SMS gateway using POST.  I already did that
stuff seven years ago, so I expect a little more than talk at this
point from the W3C.

....Roy