Lists Home |
Date Index |
In a message dated 26/01/2003 01:28:39 GMT Standard Time,
> Maybe, but is that "something" a Resource in the RFC 2396 sense?
Absolutely, beyond any shadow of doubt. 2396 says a resource is
anything that has identity.
Actually RFC doesn't say it quite as clearly as that.
The definition of a "resource" in RFC 2396 is as follows, "A resource can be
anything that has identity." So a resource **can be** anything that has
The presence of "can be" intimates, to me at least, a "delightful"
uncertainty. Which criteria determine whether or not something that has
"identity" is or is not a "resource"? Those criteria, if they are clearly
understood, are not part of the definition.
More fundamentally, what is "identity" in this context?
It seems to me, with my highly limited understanding on this topic, that the
definition of a resource in RFC2396 is seriously inadequate.
A resource might be _anything_. There are resources with identity and those
without. In this context, a resource with 'identity' is a resource which is
_identified_ by a URI. A resource 'without identity', in this context, is a
resource which is not _directly_ identified by a URI.
For example, suppose 2 resources: *you* and *your mailbox*
"mailto:AndrewWatt2000@aol.com" identifies *your mailbox*.
the person who owns the mailbox mailto:AndrewWatt2000@aol.com identifies
*you* but indirectly.