1.1 --- a/docs/wiki/FrontPage Tue Oct 27 18:56:08 2015 +0100
1.2 +++ b/docs/wiki/FrontPage Tue Oct 27 19:06:56 2015 +0100
1.3 @@ -4,47 +4,47 @@
1.4 Postfix) providing extra support for calendaring and scheduling.
1.5
1.6 * It uses the [[https://tools.ietf.org/html/rfc5545|iCalendar]],
1.7 - [[https://tools.ietf.org/html/rfc5546|iTIP]] and
1.8 - [[https://tools.ietf.org/html/rfc6047|iMIP]] Internet standards.
1.9 + [[https://tools.ietf.org/html/rfc5546|iTIP]] and
1.10 + [[https://tools.ietf.org/html/rfc6047|iMIP]] Internet standards.
1.11
1.12 * It can inspect messages containing calendar objects and extract
1.13 - availability information for sharing and publication. You and your users
1.14 - decide exactly which kind of messages it will inspect, whose messages it
1.15 - will inspect, and for whom no inspection or sharing will occur at all.
1.16 + availability information for sharing and publication. You and your users
1.17 + decide exactly which kind of messages it will inspect, whose messages it will
1.18 + inspect, and for whom no inspection or sharing will occur at all.
1.19
1.20 * It can provide a Web-based interface to calendar information for users who
1.21 - cannot or choose not to use mail software with calendaring support. This is
1.22 - optional and your users can choose to adjust, ignore or disable this
1.23 - functionality.
1.24 + cannot or choose not to use mail software with calendaring support. This is
1.25 + optional and your users can choose to adjust, ignore or disable this
1.26 + functionality.
1.27
1.28 * It supports autonomous entities such as meeting rooms and resources,
1.29 - automatically accepting or declining invitations according to their
1.30 - schedules. You can adjust this behaviour to implement your own policies.
1.31 + automatically accepting or declining invitations according to their
1.32 + schedules. You can adjust this behaviour to implement your own policies.
1.33
1.34 * It is licensed as Free Software, giving you the freedom to see what the
1.35 - software does, as well as the freedom to modify and share the software with
1.36 - others.
1.37 + software does, as well as the freedom to modify and share the software with
1.38 + others.
1.39
1.40 Unlike some monolithic groupware solutions...
1.41
1.42 * It does not require you to change your mail delivery software or your mail
1.43 - storage software (subject to existing support provided by imip-agent;
1.44 - support for other software can always be added).
1.45 + storage software (subject to existing support provided by imip-agent; support
1.46 + for other software can always be added).
1.47
1.48 * It does not require your users to change their mail client software.
1.49
1.50 * It does not insist that everybody must store their schedules on a single
1.51 - server in order to collaboratively schedule events.
1.52 + server in order to collaboratively schedule events.
1.53
1.54 * Instead, imip-agent takes advantage of the decentralized nature of the
1.55 - [[http://tools.ietf.org/html/rfc5545|iCalendar]] and
1.56 - [[http://tools.ietf.org/html/rfc5546|iMIP]] Internet standards.
1.57 + [[http://tools.ietf.org/html/rfc5545|iCalendar]] and
1.58 + [[http://tools.ietf.org/html/rfc5546|iMIP]] Internet standards.
1.59
1.60 * It allows people in your organisation to collaborate with people outside
1.61 - your organisation without insisting that they join your infrastructure or
1.62 - that everybody join some cloud service that keeps everyone's information
1.63 - within a single, typically proprietary, remote service (that may also be
1.64 - potentially vulnerable to intrusion and surveillance).
1.65 + your organisation without insisting that they join your infrastructure or
1.66 + that everybody join some cloud service that keeps everyone's information
1.67 + within a single, typically proprietary, remote service (that may also be
1.68 + potentially vulnerable to intrusion and surveillance).
1.69
1.70 The role of imip-agent is to bridge the gap between plain e-mail and
1.71 "full-stack" groupware solutions, thus allowing organisations and individuals
2.1 --- a/docs/wiki/UseCases Tue Oct 27 18:56:08 2015 +0100
2.2 +++ b/docs/wiki/UseCases Tue Oct 27 19:06:56 2015 +0100
2.3 @@ -8,13 +8,13 @@
2.4 * Enforce booking privileges
2.5
2.6 * Enforce booking "budgets" to prevent people booking too many things or
2.7 - booking things simultaneously that they will attend
2.8 + booking things simultaneously that they will attend
2.9
2.10 * Support pools of resources where one address may be responsible for
2.11 multiple units that are not individually identified at the time of booking
2.12
2.13 * Support duration limits and start/end time granularity, using `COUNTER` to
2.14 - suggest acceptable periods
2.15 + suggest acceptable periods
2.16
2.17 == Appointment Booking ==
2.18
2.19 @@ -31,13 +31,13 @@
2.20 participants followed by the selection of a specific period by an organiser.
2.21
2.22 1. Free/busy information is solicited from potential recipients by the
2.23 - organiser.
2.24 + organiser.
2.25
2.26 1. Recipients respond with details of their availability (typically
2.27 - emphasising when they are free for the event, busy otherwise).
2.28 + emphasising when they are free for the event, busy otherwise).
2.29
2.30 1. The organiser then decides on a free period and notifies all free
2.31 - participants as normal.
2.32 + participants as normal.
2.33
2.34 1. Recipients respond as normal to the event invitation.
2.35