W3C home > Mailing lists > Public > uri@w3.org > May 2004

RE: removing constraints on 'resource' [024-identity]

From: Larry Masinter <LMM@acm.org>
Date: Tue, 25 May 2004 01:31:47 -0700
To: "'Roy T. Fielding'" <fielding@gbiv.com>, uri@w3.org
Message-id: <0HY900I46H14YP@mailsj-v1.corp.adobe.com>

Personally, I think the attempt by the Semantic Web to make URIs do
the semantic lifting of denotational terms in representation systems
is flawed, and that RFC2396bis cannot 'fix' it and shouldn't try.
The best way out of the mess is to be explicit that RFC2396bis
doesn't circumscribe 'resource', but leaves it up to the URI scheme
to define how the scheme binds URIs to resources:


OLD
    Resource
       Anything that has been named or described can be a resource.      ^
       Familiar examples include an electronic document, an image, a
       service (e.g., "today's weather report for Los Angeles"), and a
       collection of other resources. A resource is not necessarily
       accessible via the Internet; e.g., human beings, corporations, and
       bound books in a library can also be resources. Likewise, abstract
       concepts can be resources, such as the operators and operands of a
       mathematical equation, the types of a relationship (e.g., "parent"
       or "employee"), or numeric values (e.g., zero, one, and infinity).
       These things are called resources because they each can be
       considered a source of supply or support, or an available means,
       for some system, where such systems may be as diverse as the World
       Wide Web, a filesystem, an ontological graph, a theorem prover, or
       some other form of system for the direct or indirect observation
       and/or manipulation of resources. Note that "supply" is not
       necessary for a thing to be considered a resource: the ability to
       simply refer to that thing is often sufficient to support the
       operation of a given system.

NEW
   Resource
       This document doesn't limit the scope of what might be a
       'resource'; rather, the term 'resource' is used for whatever it
       is that a Uniform Resource Identifier identifies; each URI scheme
       defines the range of things that are identified by
       URIs using that scheme. Commonly, URIs are used to identify
       Internet accessible objects or services; for example, an electronic
       document, an image, a service (e.g., "today's weather report for
       Los Angeles"), a collection of other resources. However,
       a resource need not be accessible via the Internet; URIs might
       be used to identify human beings, corporations, bound books in a
library,
       and even abstract concepts.


I'll give you the same challenge: is there any system or specification
that would break with this definition?

When in doubt, duck.

Larry
-- 
http://larry.masinter.net
Received on Tuesday, 25 May 2004 04:33:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:51 UTC