[Ietf-caldav] non-calendar resources in calendar collections
bernard.desruisseaux at oracle.com
Thu Mar 16 07:08:55 PST 2006
Servers may allow clients to create regular collections in calendar
collections for this purpose. Clients can store any kind of resources
in those regular sub-collection including calendar resources that don't
obey the restrictions of calendar collection. Sub-collections and their
content is simply ignored by the calendaring reports.
Servers may provide support for calendar resources of different media
type (e.g., text/calendar for iCalendar, text/x-vCalendar for vCalendar).
So, a resource might be considered as a non-calendar resource by one
CalDAV server and as a calendar resource by another CalDAV server.
If you could store a calendar resource in a media type not supported
by the CalDAV server in a calendar collection (i.e., a non-calendar
resource as far as this server can tell), you'll be stuck with an ugly
problem the day the CalDAV server will be upgraded to support calendar
resource of this media type. After the upgrade either some calendar
resources that never appeared in your calendar will now show up or
some calendar resources in your calendar collections will be considered
invalid as they won't obey the restriction of calendar collections.
Brian Moseley 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?
> 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