1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
= Use Cases =
Some situations where the imip-agent framework can provide automation
opportunities.
== Room and Resource Booking ==
* Enforce booking privileges
* Enforce booking "budgets" to prevent people booking too many things or
booking things simultaneously that they will attend
* Support pools of resources where one address may be responsible for
multiple units that are not individually identified at the time of booking
* Support duration limits and start/end time granularity, using `COUNTER` to
suggest acceptable periods
== Appointment Booking ==
* Support checks to verify the right to request an appointment
* Allow both requester-initiated and requester-contacted transactions
== Assistant and Secretarial ==
* Handle certain kinds of events whilst leaving others to the recipient
== Event Polls ==
Event voting is effectively the gathering of free/busy information from
participants followed by the selection of a specific period by an organiser.
1. Free/busy information is solicited from potential recipients by the
organiser.
1. Recipients respond with details of their availability (typically
emphasising when they are free for the event, busy otherwise).
1. The organiser then decides on a free period and notifies all free
participants as normal.
1. Recipients respond as normal to the event invitation.
A Web interface would merely provide a direct means of indicating
event-specific free/busy information.
|
