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

RE: semantics of external members

From: Yaron Goland <yarong@microsoft.com>
Date: Sun, 18 Jan 1998 16:42:51 -0800
Message-ID: <3FF8121C9B6DD111812100805F31FC0D0113C647@red-msg-59.dns.microsoft.com>
To: "'Jim Davis'" <jdavis@parc.xerox.com>, w3c-dist-auth@w3.org
I think I finally understand the source of your confusion. Does the
existence in the next draft of an optionally read-only required property
called externalmembers answer your questions?


> -----Original Message-----
> From:	Jim Davis [SMTP:jdavis@parc.xerox.com]
> Sent:	Saturday, January 17, 1998 5:05 PM
> To:	Yaron Goland; w3c-dist-auth@w3.org
> Subject:	RE: semantics of external members
> At 03:25 PM 1/17/98 PST, Yaron Goland wrote:
> >The purpose of the external member mechanism is to provide a place to
> record
> >a set of URIs that are associated with a collection, that is it.
> That's fine, very sensible decision, but could you or some other author
> answer the questions?  I simply can't tell from reading the spec what the
> semantics *are*.  The spec should be clear on the issues, otherwise people
> will simply guess, and likely guess inconsistently.  If possible the spec
> should say clearly what happens, if the matter is server-specific or
> undefined, it should say that too.
> To restate them, briefly:
> 1) can I do a PROPFIND on an external URI? (*)  Do the results depend in
> any way on the collection that contains the external URI?
> 2) can I do a PROPPATCH?
> 3) Can I do a LOCK?
> 4) What are the semantics of GET or PUT on an external URI.
> * by "do a PROPFIND" I mean if I do one, will I get back some useful
> values, not just a 404 error.
> Yours in confusion
> Jim
Received on Sunday, 18 January 1998 19:43:24 UTC

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