W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1998

RE: Clarification of URI vs. resource

From: Larry Masinter <masinter@parc.xerox.com>
Date: Thu, 5 Nov 1998 09:40:26 PST
To: "Yaron Goland" <yarong@microsoft.com>
Cc: "Webdav" <w3c-dist-auth@w3.org>
Message-ID: <001801be08e3$5f5a3ba0$d111020d@copper.parc.xerox.com>

> Internal members are defined in the context of the request URI used to
> reference the collection.


> > An internal member URI MUST be
> > immediately relative to the base URI of the collection.  That is, the
> > internal member URI is equal to the containing collection's URI plus an
> > additional segment for non-collection resources, or additional segment
> > trailing slash "/" for collection resources, where segment is defined in
> > section 3.3 of [RFC2396].

I can see what you mean, but it isn't what the spec says. The spec
says it's a constraint between "collection" and "internal member".

But you're saying that a "collection" as a resource will have different
"internal member"s (as URIs) depending on the URI with which the collection
is referenced.

Frankly, you'd probably be better off if you defined "internal member"
as a resource, not as a URI, and then note that the internal member
must be accessible using a URL that is a direct relative URL of whatever
resource used to access the collection.

You'd also be better of saying that an 'internal member' can only
occur twice, that is, if http://host/coll/ is the collection and
http://host/coll/mem and http://host/coll/MEM are both URIs of the
same resource, that the resource is a member only once.

Received on Thursday, 5 November 1998 12:40:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:15 UTC