1.1 --- a/docs/wiki/UseCases Mon Oct 26 13:49:51 2015 +0100
1.2 +++ b/docs/wiki/UseCases Mon Oct 26 14:05:25 2015 +0100
1.3 @@ -1,13 +1,20 @@
1.4 = Use Cases =
1.5
1.6 -Some situations where the imip-agent framework can provide automation opportunities.
1.7 +Some situations where the imip-agent framework can provide automation
1.8 +opportunities.
1.9
1.10 == Room and Resource Booking ==
1.11
1.12 * Enforce booking privileges
1.13 - * Enforce booking "budgets" to prevent people booking too many things or booking things simultaneously that they will attend
1.14 - * Support pools of resources where one address may be responsible for multiple units that are not individually identified at the time of booking
1.15 - * Support duration limits and start/end time granularity, using `COUNTER` to suggest acceptable periods
1.16 +
1.17 + * Enforce booking "budgets" to prevent people booking too many things or
1.18 + booking things simultaneously that they will attend
1.19 +
1.20 + * Support pools of resources where one address may be responsible for
1.21 + multiple units that are not individually identified at the time of booking
1.22 +
1.23 + * Support duration limits and start/end time granularity, using `COUNTER` to
1.24 + suggest acceptable periods
1.25
1.26 == Appointment Booking ==
1.27
1.28 @@ -20,11 +27,19 @@
1.29
1.30 == Event Polls ==
1.31
1.32 -Event voting is effectively the gathering of free/busy information from participants followed by the selection of a specific period by an organiser.
1.33 +Event voting is effectively the gathering of free/busy information from
1.34 +participants followed by the selection of a specific period by an organiser.
1.35 +
1.36 + 1. Free/busy information is solicited from potential recipients by the
1.37 + organiser.
1.38
1.39 - 1. Free/busy information is solicited from potential recipients by the organiser.
1.40 - 1. Recipients respond with details of their availability (typically emphasising when they are free for the event, busy otherwise).
1.41 - 1. The organiser then decides on a free period and notifies all free participants as normal.
1.42 + 1. Recipients respond with details of their availability (typically
1.43 + emphasising when they are free for the event, busy otherwise).
1.44 +
1.45 + 1. The organiser then decides on a free period and notifies all free
1.46 + participants as normal.
1.47 +
1.48 1. Recipients respond as normal to the event invitation.
1.49
1.50 -A Web interface would merely provide a direct means of indicating event-specific free/busy information.
1.51 +A Web interface would merely provide a direct means of indicating
1.52 +event-specific free/busy information.