PROPPATCH precondition CALDAV:valid-free-busy-set
bernard.desruisseaux at oracle.com
Mon Jan 7 08:18:56 PST 2008
The text currently specify when the precondition identifier is returned in
the response of a failed PROPPATCH request. We should rephrase this to
specify what is the actual requirement instead.
Thanks for pointing this out.
Gren Elliot wrote:
> draft-desruisseaux-caldav-sched-04 Section 5.3.2 Additional
> Precondition for PROPPATCH
> says the precondition is :
> (CALDAV:valid-free-busy-set): One or more resources referenced in
> a CALDAV:calendar-free-busy-set property being stored on a
> scheduling Inbox collection is invalid.
> Should the "invalid" read "valid"? I can understand that some of the
> resources might be invalid due to calendar deletions or future additions
> but requiring one to be invalid seems wrong.
> Ietf-caldav mailing list -- Ietf-caldav at osafoundation.org
> See http://ietf.webdav.org/caldav/ for more CalDAV resources
More information about the Ietf-caldav