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

RE: Meaning of precondition DAV:supported-live-property

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 11 Apr 2002 23:21:16 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B106819088@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
Stefan is correct.  These conditions ensure that you will see
those properties on a (3253 compliant) resource if and only if
they have the 3253 defined semantics.

Cheers,
Geoff

-----Original Message-----
From: Stefan Eissing [mailto:stefan.eissing@greenbytes.de]

As I understand it, the precondition will prevent that a resource
can have dead properties of the same name as a deltav live property.

So, on a deltav compliant server, you cannot retrieve or set the
property DAV:version-history on a non-VCR resource (e.g. plain,
unversioned resource of RFC 2518 style).

A server, just followin 2518, would allow the setting of such
a property. It would be a dead properties without any meaning,
but returned on a PROPFIND nevertheless.


Am Donnerstag den, 11. April 2002, um 14:38, schrieb Nevermann, 
Dr., Peter:

> In our group we are discussing about the exact meaning of the 
> additional
> precondition(s) DAV:supported-live-property for PROPFIND and 
> PROPPATCH (3.11
> and 3.12 in RFC 3253). In particular, the meaning of "the 
> semantics of a
> property being supported by the server".
>
> Is the following an example?
> A PROPPATCH request intends to modify the value of a "checkout-fork"
> property of a checked-out VCR to something different than 
> DAV:forbidden or
> DAV:discouraged, say, to an empty value. Then the
> DAV:supported-live-property precondition is violated.
>
> Another interpretation is, that it has to do with properties which 
> are not
> REQUIRED (...but there are not such properties as fas as I can see!).
>
> Thanks,
> Peter
>
Received on Thursday, 11 April 2002 23:21:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT