Next message: by way of : "RE: draft-ietf-deltav-versioning-08 now available"
To: ietf-dav-versioning@w3.org
Message-ID: <OF46176324.A143B9C1-ON8525695A.004F67E0@ott.oti.com>
From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>
Date: Thu, 14 Sep 2000 10:43:48 -0400
Subject: Re: Naive question
PROPFIND doesn't
return live properties of the version when accessed through the
version selector.
That's correct, you'd have to ask for the live properties of
the version if they wanted the live properties of the version.
<jra>
But this doesn't seem right. If you get the contents and dead properties
through the version selector, then why not the version's live properties?
Why are we requiring clients to get the version URL for this special case?
</jra>
<bb>
For clients, this is not a very special case. In particular, when
displaying a tree of versioned resources in a GUI, I am interested in
getting the value of the selected versions' DAV:version-name property
using PROPFIND Depth: infinity. If the live properties of versions were
not visible through a version selector, I would have to issue one
additional request per resource to get the version name. The same may
apply to other live properties of versions, such as DAV:checkin-date.
BTW, I don't think that a GUI can use the version URL (DAV:target) for
displaying version identification.
</bb>