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

RE: PROPFIND allprop with more properties (was AW: Resource class )

From: Julian F. Reschke <julian.reschke@greenbytes.de>
Date: Mon, 28 May 2001 09:50:04 +0200
To: "Clemm, Geoff" <gclemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCAEHGCFAA.julian.reschke@greenbytes.de>
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
> Sent: Saturday, May 26, 2001 5:27 PM
> To: ietf-dav-versioning@w3.org
> Subject: RE: PROPFIND allprop with more properties (was AW: Resource
> class )
> I agree with Lisa's criticism of my counter-proposal,
> i.e. that it prevented DAV:all-dead-prop from being
> used as a property name.
> To avoid the introduction of the DAV:include element,
> and to reflect that fact that we are "adding stuff to what
> DAV:allprop returns", another minor variant we could consider
> would be:
> <propfind xmlns="DAV:">
>   <allprop>
>     <checked-in/><checked-out/><version-name/>
>   </allprop>
> </propfind>

This one won't interoperate with old servers, because <allprop> is defined
to be EMPTY (in RFC2518).

So if you hit an old server, you'll have to two two additional requests
(<allprop> and <prop> with the three named properties), while with
<include>, it will be just one additional request (using <prop> to get the
three additional properties).

BTW: chapter 23.3.2 of RFC2518 gives a very similar example for legally
extending PROPFIND.
Received on Monday, 28 May 2001 03:50:37 UTC

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