W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2001


From: Lisa Dusseault <lisa@xythos.com>
Date: Wed, 9 May 2001 16:41:35 -0700
To: "Jim Whitehead" <ejw@cse.ucsc.edu>, "WebDAV WG" <w3c-dist-auth@w3.org>
I'm not sure I agree with Judy's original post that "Other live DAV
properties (supportedlock, getetag) should be
copied / moved live if possible, but should not be copied / moved dead."

It seems to me that there are at least two kinds of live properties, the
distinction between which has caused confusion in the past (at least to me).

There are live properties which are typically read-only and calculated (or
only altered indirectly), such as lockdiscovery, supportedlocks, getetag,
creationdate, getlastmodified, resourcetype.  These should usually be
recalculated as the result of a MOVE or COPY so one might as well say they
are not moved or copied.

There can also live properties which are writable and which have an effect
on the server either immediately or at a later date (if they didn't have an
effect, they'd just be dead).  This category includes auto-checkout and
auto-checkin from DeltaV.  If they are writable, they should usually be
"written" when the resource is copied or moved.

There are also dead properties which are not calculated by the server, nor
is their value used by the server.

So the distinction of interest for MOVE/COPY is seemingly whether the
property is in theory writable, not whether it's live/non-live.

Can we get some more context about what the "issue" is?  is it only for
purposes of MOVE/COPY that the spec should distinguish whether between live
and non-live, or are there other reasons to distinguish?  Is the goal to be
able to define a way to identify which properties should be copied or moved?


> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Jim Whitehead
> Sent: Wednesday, May 09, 2001 4:21 PM
> To: WebDAV WG
> Subject: Issue: LIVE_AND_NON_LIVE
> This is a seemingly simple issue:
>  The specification should explicitly state which properties are live, and
> which are non-live.
> It was initially raised by Judy Slein:
> http://lists.w3.org/Archives/Public/w3c-dist-auth/1999JanMar/0025.html
> - Jim
Received on Wednesday, 9 May 2001 19:43:02 UTC

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