W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

RE: Option abuse

From: Clemm, Geoff <gclemm@rational.com>
Date: Sat, 10 Feb 2001 00:11:48 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B101FC0672@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
The DAV:workspace-collection set is usually the same for a
whole server, so just like the DAV header, there is no need
to query it for more than one resource on a given server.

In contrast, the supported methods and live properties vary
from resource to resource, and therefore are more appropriately
marshalled as a property so that it can easily be retrieved
in a depth fashion with the other information about that resource.


-----Original Message-----
From: James J. Hunt [mailto:jjh@allerton.de]
Sent: Monday, February 05, 2001 1:15 PM
To: Geoffrey M. Clemm
Cc: ietf-dav-versioning@w3.org
Subject: Re: Option abuse

"Geoffrey M. Clemm" wrote:

> It really doesn't matter whether we marshall this as an OPTIONS call
> or as a PROPFIND for a property.  This used to be marshalled as a
> property but a reviewer pointed out that this information seemed more
> like an option than a property.
> Can you give some motivation for switching this back to being a property?
> Cheers,
> Geoff

Dear Geoff,

My understanding of an option is "does the server support x".  Properties
associate values to keys for a given resource.  Let us take
DAV:workspace-collection-set.  Especially when you say that the http
can be spread over several servers, the question I ask with this tag is not
you support workspaces, rather for a given versionable workspace, where can
create a workspace for it?  In other words, I am asking what is the
area associated with this resource.  That seems to me to be a property of
resource, because every resource could answer it differently.

Received on Saturday, 10 February 2001 00:03:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC