1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/wiki/UseCases Mon Oct 26 13:49:51 2015 +0100
1.3 @@ -0,0 +1,30 @@
1.4 += Use Cases =
1.5 +
1.6 +Some situations where the imip-agent framework can provide automation opportunities.
1.7 +
1.8 +== Room and Resource Booking ==
1.9 +
1.10 + * Enforce booking privileges
1.11 + * Enforce booking "budgets" to prevent people booking too many things or booking things simultaneously that they will attend
1.12 + * Support pools of resources where one address may be responsible for multiple units that are not individually identified at the time of booking
1.13 + * Support duration limits and start/end time granularity, using `COUNTER` to suggest acceptable periods
1.14 +
1.15 +== Appointment Booking ==
1.16 +
1.17 + * Support checks to verify the right to request an appointment
1.18 + * Allow both requester-initiated and requester-contacted transactions
1.19 +
1.20 +== Assistant and Secretarial ==
1.21 +
1.22 + * Handle certain kinds of events whilst leaving others to the recipient
1.23 +
1.24 +== Event Polls ==
1.25 +
1.26 +Event voting is effectively the gathering of free/busy information from participants followed by the selection of a specific period by an organiser.
1.27 +
1.28 + 1. Free/busy information is solicited from potential recipients by the organiser.
1.29 + 1. Recipients respond with details of their availability (typically emphasising when they are free for the event, busy otherwise).
1.30 + 1. The organiser then decides on a free period and notifies all free participants as normal.
1.31 + 1. Recipients respond as normal to the event invitation.
1.32 +
1.33 +A Web interface would merely provide a direct means of indicating event-specific free/busy information.