W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2002

RE: Marshalling DAV:xxx-collection-set as a live property, and no t an OPTIONS request.

From: Sohn, Matthias <matthias.sohn@sap.com>
Date: Mon, 8 Jul 2002 07:49:07 +0200
Message-ID: <333D9700B499084C9DF804896DDA71787E03AC@dewdfx14>
To: "'Clemm, Geoff'" <gclemm@rational.com>, "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>


I vote for (c)

I am not sure on which resources these live properties 
specifying server wide properties (which in general are not a property of 
a specific resource) should be exposed, I would appreciate some standardized
way to define these server wide features.

In addition I would like to see that the same mechanism can be used to
server specific extension features preventing name clashes by the namespace 
of the respective live property


-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@rational.com]
Sent: Sonntag, 7. Juli 2002 14:59
To: DeltaV (E-mail)
Subject: Marshalling DAV:xxx-collection-set as a live property, and not
an OPTIONS request.

Since I was not able to convince the ACL working group to marshall
this kind of information as an OPTIONS request, we should probably
consider changing the versioning protocol to also marshall this
kind of information (i.e. DAV:workspace-collection-set,
DAV:activity-collection-set, and DAV:version-history-collection-set)
as live properties, and not as OPTIONS requests.

So I'd like to poll the mailing list (especially DeltaV client and/or
server implementors:

Do you prefer to:
(a) leave xxx-collection-set as it is (marshalled only as OPTIONS)
(b) support marshalling both as OPTIONS and as live properties
(c) marshal only as live properties and deprecate the OPTIONS marshalling

I vote for (c), as it simplifies the spec, and makes it consistent
with the ACL protocol.

Received on Monday, 8 July 2002 01:49:42 UTC

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