   From: Clemm, Geoff <gclemm@rational.com> Date: Tue, 29 May
2001 15:23:24 -0400 Message-ID:
<3906C56A7BD1F54593344C05BD1374B1018E2419@SUS-MA1IT01> To: ietf-
dav-versioning@w3.org (Warning: detailed multi-spec language
lawyering to follow :-)     From: Julian F. Reschke
[mailto:julian.reschke@greenbytes.de]     > From:  Clemm, Geoff
> ... you could nest the    > DAV:include node inside the
DAV:allprop, rather than inside the    > DAV:propfind, i.e.    >
<propfind xmlns="DAV:">    >   <allprop>    >    <include>    >
<checked-in/><checked-out/><version-name/>    >    </include>
>   </allprop>    >  </propfind>     Well, that would be invalid
for the same reason (I think).  Now that's an interesting
question.  According to section 14 of RFC 2518, a server that
didn't understand the DAV:include element must ignore it (and
its children).  So the question then is, what does "ignore"
mean?  In particular, does the result of "ignoring" the include
element in:  <allprop> <include>...</include> </allprop> h