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