1.1 --- a/TO_DO.txt Sun Mar 23 01:33:55 2014 +0100
1.2 +++ b/TO_DO.txt Sat Mar 29 15:10:15 2014 +0100
1.3 @@ -1,3 +1,25 @@
1.4 +Event Invitations and Attendance
1.5 +--------------------------------
1.6 +
1.7 +iTIP invitations (RFC 5546) could be supported. REQUEST method payloads are
1.8 +effectively equivalent to plain iCalendar payloads; ADD method payloads are
1.9 +similar to plain iCalendar payloads but augment previously received data,
1.10 +whereas CANCEL method payloads remove or retract previously received data;
1.11 +REFRESH method payloads are minimal requests for complete iCalendar payloads
1.12 +to be sent in response. Other methods (REPLY, COUNTER, DECLINECOUNTER) update
1.13 +the state of events according to attendance notifications.
1.14 +
1.15 +For iTIP exchanges to work effectively, a mapping of the UID of each event to
1.16 +the received information needs to be maintained. (An awareness of each
1.17 +RECURRENCE-ID in an event is also useful where recurring events are being
1.18 +handled.) Here, a form of index needs to be supported for efficient access via
1.19 +event UIDs to event data. Other indexes might be supported for efficient
1.20 +free/busy resource generation.
1.21 +
1.22 +The actual sending and receiving of iTIP messages needs to be supported by
1.23 +other components such as MoinMessage. It might be interesting to support iTIP
1.24 +notifications if events are changed directly on a wiki.
1.25 +
1.26 Navigation Controls
1.27 -------------------
1.28