[Ietf-caldav] non-calendar resources in calendar collections

[Cyrus Daboo]

Hi Brian,

--On March 15, 2006 8:47:52 PM -0800 Brian Moseley <bcm at osafoundation.org> 
wrote:

> i'd like to re-examine the decision to blanket disallow non-calendar
> resources within calendar collections.
>
> i recognize that for some servers it may not be possible to allow
> anything other than an event or task to be put into a calendar
> collection, but surely some would like to be able to support this
> without contradicting the spec
>
> why not state that servers MAY allow non-calendar resources in
> calendar collections, and that PUTs containing resources that are not
> supported will return 415 responses?

Note that the current spec does allow regular collections inside of a 
calendar collection (c.f. Section 4.2). So there is nothing to stop a 
client creating its own private collection inside a calendar and storing 
whatever it wants in there. Yes that does mean non-calendar resources at 
Depth:1 in a calendar collection are disallowed, but you can have that at 
'lower' depths than that if needs be. The benefit of keeping non-calendar 
resources out of the top-level of the calendar is that clients and servers 
can easily ignore such data by simply doing Depth:1 PROPFINDs etc. Thus 
clients that don't use the extra 'meta' data resources don't pay the 
penalty of 'seeing' them in PROPFINDs. Yes they will see the regular 
collections - but hopefully those will be fewer than the resources they 
might contain.

-- 
Cyrus Daboo