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