martin: doc/architecture kde.sgml,1.4,1.5

[cvs at intevation.de]

Author: martin

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

Modified Files:
	kde.sgml 
Log Message:
Martin K.: Updated the description about interoperability (IMAP annotations, XML format)


Index: kde.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/kde.sgml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- kde.sgml	20 Feb 2003 15:15:18 -0000	1.4
+++ kde.sgml	5 Oct 2004 05:42:14 -0000	1.5
@@ -1,35 +1,38 @@
 <chapter><title> The KDE Client </title>
 <para>The KDE client is implemented using these existing Free Software KDE
-projects and their technologies. It is intended to feed back this development
-into the existing Free Software projects:</para>
+projects and their technologies. This development development effort is directly
+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> Kitchensync with Conduits </para></listitem>
+<listitem><para> KPilot with Conduits </para></listitem>
 </itemizedlist>
 <para>The following implementation activities have been identified:</para>
 <itemizedlist>
-<listitem><para> Couple KOrganizer with Kmail. Kmail must act as
-a kparts container and run the KOrganizer as an embedded kpart. </para></listitem>
-<listitem><para> Add offline support to the IMAP kioslave </para></listitem>
+<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>
+<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> simplify and standardize the VCAL parser implementation throughout KDE </para></listitem>
+<listitem><para> implement the new Kolab XML storage format in addition to the exisiting iCal format 
+in order to become fully interoperable with Outlook based clients</para></listitem>
 <listitem><para> implement logic for groupware functionality </para></listitem>
 <listitem><para> implement further features as given in the previous chapters </para></listitem>
-<listitem><para> make KMail and KOrganizer partly TNEF-aware (Outlook/Bynari stores all information using the
-Microsoft proprietary TNEF format) </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.
+</para></listitem>
 <listitem><para> development of migration tools to convert mailboxes between usage with the KDE
-client and Outlook/Bynari </para></listitem>
+client and Outlook/Toltec </para></listitem>
 </itemizedlist>
 <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 it is required that the KDE client determines the language used to access folders on the Kolab server. The KDE client shall be able to use a different language for storing than for its own user interface. Basically this means that a single binary of the KDE client will be interoperable to any localized version of MS Outlook.
-</para>
-<para>
-The language used for an account is set either with the first use of Outlook with the corresponding language or set by the administrator in advance in case the KDE client will be used before Outlook. The administrator hints the KDE client by creating the required folders in the corresponding language. The KDE client creates an unique hash over the folder names and therfor can savly determine the correct mapping of the folder names to its internal data structures.
+In order to stay comptible to Microsoft Outlook clients it was required that the KDE client determines 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. 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 information.
+Basically this means that the Kolab 2 clients will be interoperable with eacht other independent of the localizations used.
 </para>
 </sect1>
 </chapter>