2.2. Scheduling Inbox Collection

A scheduling Inbox collection contains copies of incoming scheduling messages. These can be requests sent by an "Organizer", or replies sent by an "Attendee" in response to a request. The scheduling Inbox collection is also used to manage scheduling privileges.

A scheduling Inbox collection MUST report the DAV:collection and CALDAV:schedule-inbox XML elements in the value of the DAV: resourcetype property. The element type declaration for CALDAV: schedule-inbox is

Example

  
 
 
  
Scheduling Inbox collections MUST only contain calendar object
resources that obey the restrictions specified in iTIP [RFC5546].
Consequently, scheduling Inbox collections MUST NOT contain any types
of collection resources.  Restrictions defined in Section 4.1 of
CalDAV "calendar-access" [RFC4791] on calendar object resources
contained in calendar collections (e.g., Unique Identifier ("UID")
uniqueness) do not apply to calendar object resources contained in a
scheduling Inbox collection.  Thus, multiple calendar object
resources contained in a scheduling Inbox collection can have the
same "UID" property value (i.e., multiple scheduling messages for the
same calendar component).

A scheduling Inbox collection MUST NOT be a child (at any depth) of a calendar collection resource.

The following WebDAV properties specified in CalDAV "calendar-access" [RFC4791] MAY also be defined on scheduling Inbox collections and apply to scheduling messages delivered to the collection:

o CALDAV

supported-calendar-component-set

o CALDAV

supported-calendar-data

o CALDAV

max-resource-size

o CALDAV

min-date-time

o CALDAV

max-date-time

o CALDAV

max-instances

o CALDAV

max-attendees-per-instance

o CALDAV

calendar-timezone

The following WebDAV property is defined on principal resources and used to locate the corresponding Inbox collection for the associated principal.