martin: doc/architecture client_server.sgml, 1.14, 1.15 kde.sgml, 1.6, 1.7

[cvs at intevation.de]

Author: martin

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv14804

Modified Files:
	client_server.sgml kde.sgml 
Log Message:
Martin K.: Minor clarifications


Index: client_server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/client_server.sgml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- client_server.sgml	19 Oct 2004 06:21:34 -0000	1.14
+++ client_server.sgml	20 Oct 2004 05:38:51 -0000	1.15
@@ -293,7 +293,7 @@
 
 <sect1><title>Automatic rules based handling of invitations</title>
 <para>
-The Kolab server implements a mechanism for handling of invitations.
+The Kolab server implements a server side mechanism for handling of invitations.
 Typically this feature is used to handle bookings of resources (e.g. a room,
 car, lcd projector etc.).
 </para>

Index: kde.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/kde.sgml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- kde.sgml	11 Oct 2004 15:38:52 -0000	1.6
+++ kde.sgml	20 Oct 2004 05:38:51 -0000	1.7
@@ -4,23 +4,22 @@
 conducted in the KDE CVS repository and shall be integrated in future releases
 of the existing Free Software projects:</para>
 <itemizedlist>
-<listitem><para> KMail (with Ägypten/SPHINX encryption extensions) </para></listitem>
-<listitem><para> KOrganizer (used as KPart) </para></listitem>
-<listitem><para> KAddressbook </para></listitem>
+<listitem><para> KDE Kontact (used as a container for KParts)</para></listitem>
+<listitem><para> KMail KPart (with Ägypten/SPHINX encryption extensions) </para></listitem>
+<listitem><para> KOrganizer KPart) </para></listitem>
+<listitem><para> KAddressbook KPart </para></listitem>
 <listitem><para> KPilot with Conduits </para></listitem>
 </itemizedlist>
 <para>The following implementation activities have been identified:</para>
 <itemizedlist>
 <listitem><para> Integrate the components with the graphical Kontact shell. Kontact acts as a
-kparts container and run all the KDE componentes for the PIM solution as an embedded kparts. </para></listitem>
+kparts container and runs all the KDE componentes for the PIM solution as embedded kparts. </para></listitem>
 <listitem><para> Add proper offline support to the IMAP kioslave called disconnected IMAP (dIMAP)</para></listitem>
 <listitem><para> Extend the GUI to support further functionality </para></listitem>
-<listitem><para> implement the new Kolab XML storage format 
-in addition to the existing iCalendar format 
-in order to become fully interoperable with clients that are not based on
-KOrganizer (e.g. Outlook based clients).
+<listitem><para> implement the new Kolab XML storage format in addition to the existing iCalendar format
+in order to become fully interoperable with clients that are not based on KOrganizer (e.g. Outlook based clients).
 </para></listitem>
-<listitem><para> implement logic for groupware functionality </para></listitem>
+<listitem><para> implement logic for complex groupware functionality </para></listitem>
 <listitem><para> implement further features as given in the previous chapters </para></listitem>
 <listitem><para> keep iCalendar format for everything sent over SMTP while use the new XML storage format and
 the new IMAP features like annotations to make the clients better interoperate with each other.
@@ -28,21 +27,23 @@
 <listitem><para> development of migration tools to convert mailboxes between usage with the KDE
 client and Outlook/Toltec </para></listitem>
 </itemizedlist>
-<para>A more detailed description is out of the focus of this document.</para> 
+<para>A more detailed description is out of the focus of this document.</para>
 
 <sect1><title>Language dependencies</title>
 <para>
-In order to stay comptible to Microsoft Outlook clients 
-in Kolab 1 it was required that the KDE client 
+In order to stay comptible to Microsoft Outlook clients
+in Kolab 1 it was required that the KDE client
 determined the language used to access folders on the Kolab server.
-With Kolab 2 this is much more cleanly and more robustly solved 
-using IMAP annotations. 
+With Kolab 2 this is much more cleanly and more robustly solved
+using IMAP annotations.
 IMAP annotation allows us to add small annotations to an IMAP folder describing
-its use. Currently annoations are used to define the default calendar, tasks
-etc. and also for marking calendars as relevant for the creation of freebuys
+its use. Currently annotations are used to define calendar, task and contact folders.
+One of each categorie of groupware folders is defined as the default folder for its type.
+E.g. there is always a default calendar which is used for mergeing incoming event requests
+etc. In addition IMAP folder annotations are used for marking calendars as relevant for the creation of freebuys
 information.
 Basically this means that the Kolab 2 clients will be interoperable with each
-other independent of the localizations used.
+other independent of the localizations and languages used.
 </para>
 </sect1>
 </chapter>