1 Event Invitations and Attendance
2 --------------------------------
3
4 iTIP invitations (RFC 5546) could be supported. REQUEST method payloads are
5 effectively equivalent to plain iCalendar payloads; ADD method payloads are
6 similar to plain iCalendar payloads but augment previously received data,
7 whereas CANCEL method payloads remove or retract previously received data;
8 REFRESH method payloads are minimal requests for complete iCalendar payloads
9 to be sent in response. Other methods (REPLY, COUNTER, DECLINECOUNTER) update
10 the state of events according to attendance notifications.
11
12 For iTIP exchanges to work effectively, a mapping of the UID of each event to
13 the received information needs to be maintained. (An awareness of each
14 RECURRENCE-ID in an event is also useful where recurring events are being
15 handled.) Here, a form of index needs to be supported for efficient access via
16 event UIDs to event data. Other indexes might be supported for efficient
17 free/busy resource generation.
18
19 The actual sending and receiving of iTIP messages needs to be supported by
20 other components such as MoinMessage. It might be interesting to support iTIP
21 notifications if events are changed directly on a wiki.
22
23 Navigation Controls
24 -------------------
25
26 The "New event" link should probably not be present when only remote events
27 are being aggregated by a calendar.
28
29 Improve the accessibility of controls by providing links with titles and
30 offering links as alternatives to pop-up elements.
31
32 Points in Time
33 --------------
34
35 Consider making dates convertible to timespans of the form (start of day,
36 start of next day).
37
38 Localised Keywords
39 ------------------
40
41 It should be possible to define events using localised equivalents of "start",
42 "end", "summary" and so on. To achieve this, the page language would be found
43 and regular expressions built to use the localised keywords, falling back on
44 the English keywords, would then search for event details.
45
46 Recurring Events
47 ----------------
48
49 Recurring event information from iCalendar sources should be considered in
50 order to avoid showing incomplete or incorrect event datetimes. Ultimately,
51 such information may need to be parsed and incorporated into the general event
52 recurrence processing.
53
54 Having events recur at certain intervals would potentially involve the
55 expansion of events to produce multiple instances within a specified period of
56 interest, and such expansion could occur after an event's details have been
57 read. Care would need to be taken in cases where no limits are placed on a
58 calendar: the expanded instances should not be allowed to recede into the past
59 and future indefinitely; where no other events exist to provide implicit
60 limits, some other default limits might be required to let the expansion
61 occur.
62
63 The description of recurring events could be based on the iCalendar
64 specification, although simpler schemes could be preferable. Recurring event
65 descriptions might start with "every" and then provide a time period ("day",
66 "week", "month", "year") for offsets from a specified date or time, perhaps
67 using qualifiers ("first", "second", "other", and so on), or instead provide a
68 more complete description using additional qualifiers that may override any
69 specified date or time for instances other than the primary occurrence. For
70 example, "every second Wednesday of every other month".
71
72 The resolution of each successive <recurrence> would need to be lower than
73 those it follows. Thus, "every second day of every second week..." would be
74 valid whereas "every second week of every second day..." would not.
75
76 Map Views
77 ---------
78
79 Other projections might be supported. This would be necessary for various
80 retrieved map images.
81
82 Dynamic images obtained from other sites or generated locally might provide some
83 enhancements to the map view. For example, a weather/radar image might show the
84 cloud or rain forecast either for the current situation or, if forecasts are
85 available, for the times of events shown.
86
87 Consider having day numbers down the side of a map view with highlighted days
88 indicating days having events, and with pop-up elements shown upon hovering over
89 each highlighted day.
90
91 To Do Items
92 -----------
93
94 Consider adding support for "to do" items. These might have time-related details
95 such as deadlines, but are more likely to have relationships with other items,
96 potentially forming a hierarchy of items.
97
98 Event Section Parser
99 --------------------
100
101 Events in page sections/regions could be presented using more sophisticated
102 methods and potentially be editable. To support direct editing, the parser
103 would provide a hidden form field indicating the location of the section in
104 the Wiki text, and the new event action would be enhanced to read existing
105 events from the indicated page region, populating the form fields with the
106 data found in the page.
107
108 UID Properties
109 --------------
110
111 Especially in the case of aggregation from multiple sources, the only reliable
112 way of avoiding repetition of the same events described in different places is
113 for authors to include a UID property identifying each event, using the same
114 value regardless of where the event is being published.
115
116 Formatting in iCalendar Output
117 ------------------------------
118
119 If there is a reasonably standard way of incorporating Wiki text in iCalendar
120 output alongside plain text, this would enable events aggregated from Wiki
121 sources to use Wiki text to describe things like the location and topics of an
122 event with links and other formatting that could then be reproduced in the
123 aggregating Wiki.
124
125 Remote Source Timeouts
126 ----------------------
127
128 Sometimes, network problems can cause delays in accessing remote sources. The
129 library should support either a timeout mechanism or asynchronous retrieval of
130 remote source data.