martin: doc/architecture concept.sgml, 1.15, 1.16 overview.sgml, 1.7, 1.8

cvs at intevation.de cvs at intevation.de
Mon Oct 18 07:56:40 CEST 2004


Author: martin

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

Modified Files:
	concept.sgml overview.sgml 
Log Message:
Martin K.: Update with regards to Kolab 2 functionality


Index: concept.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/concept.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- concept.sgml	11 Oct 2004 15:52:29 -0000	1.15
+++ concept.sgml	18 Oct 2004 05:56:38 -0000	1.16
@@ -12,8 +12,8 @@
 <book>
 
 <bookinfo>
-<title>Kolab Free Software Groupware Project</title>
-<subtitle>Architecture Paper Version 1.9.x (CVS Draft)</subtitle>
+<title>Kolab 2 - Free Software Groupware Project</title>
+<subtitle>Architecture Paper Version 1.9.9 (CVS Draft)</subtitle>
 <authorgroup>
 <corpauthor><inlinegraphic entityref="erfrakon" fileref="erfrakon"></inlinegraphic> </corpauthor>
 <othercredit>
@@ -26,7 +26,7 @@
 <othername> email: info at erfrakon.de </othername>
 </othercredit>
 </authorgroup>
-<pubdate>October 11th, 2004</pubdate>
+<pubdate>October 18th, 2004</pubdate>
 <legalnotice>
 <para> This documentation was written in SGML using the DocBook DTD. HTML
 and Postscript output is generated automatically and depends on the
@@ -37,8 +37,6 @@
 <trademark class='registered'>Microsoft Exchange</trademark> and
 <trademark class='registered'>Microsoft Outlook</trademark>
 are registered trademarks of Microsoft Corporation Inc.
-<trademark class='registered'>Insight Connector</trademark>
-is a registered trademark of Bynari Inc.
 <trademark>Toltec Connector</trademark>
 is a trademark of Radley Network Technologies CC.
 <trademark class='registered'>HotSync</trademark>
@@ -109,7 +107,12 @@
 <revremark>
 Kolab 2 XML Storage format.
 </revremark>
+
+</revision><revision>
+<revnumber>1.9.9</revnumber>
+<date>2004/10/13</date>
 </revision>
+
 
 </revhistory>
 </bookinfo>

Index: overview.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/overview.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- overview.sgml	17 Mar 2004 17:56:42 -0000	1.7
+++ overview.sgml	18 Oct 2004 05:56:38 -0000	1.8
@@ -1,20 +1,26 @@
-<chapter><title>  Kolab Free Software Groupware Overview </title>
+<chapter><title>Kolab 2 Free Software Groupware Overview </title>
 
-<para>This highly scalable and secure solution is strictly based on a 
-client/server architecture.The server part of the groupware solution, herein 
+<para>The Kolab Groupware is a highly scalable and secure solution and strictly based on a 
+client/server architecture. The server part of the groupware solution, herein 
 referred to as "Kolab Server" runs on GNU/Linux, namely on a current 
-distribution out of Debian, Red Hat or SuSE in addition to FreeBSD.
-We minimized the usage of Linux 
-distribution dependencies in order to gain maximal portability. In order to be 
+distribution out of Debian, Red Hat or SUSE in addition to FreeBSD. Most
+testing was done on Debian and SUSE.
+</para>
+<para>
+We minimized the usage of Linux distribution dependencies in order to gain maximal portability. In order to be 
 able to apply readily available security updates in a timely manner employment of 
 a well-maintained GNU/Linux distribution like the above mentioned seems 
 desirable. The goal is that standard security updates as provided by 
 thesevendors can be installed without affecting the Kolab server 
 functionality.</para>
 <para>
-I is not the scope of this architecuture to integrate with the underlaying
+The Kolab server is distributed as OpenPKG packages which allows for a single
+source for our many target platforms.
+</para>
+<para>
+It is not the scope of this architecuture to integrate with the underlaying
 operating system in such a way that the administration of the operating system 
-is done with it.
+is accomplished with it.
 </para>
 <para> The free software groupware client application is developed 
 as a native KDE 3 application. Microsoft Windows XP based clients access the 
@@ -22,8 +28,7 @@
 Plugin installed (reference platform). A high-level description of 
 the complete free software groupware solution seen from the user spoint of view 
 follows. The list was created with existing proprietary groupware products in 
-mind, namely Microsoft Exchange Server with Outlook 2002 
-clients on Windows NT.</para>
+mind, namely Microsoft Exchange Server with Outlook 2002 clients on Windows NT.</para>
 
 <sect1><title>Email Functionality </title>
 <para>The common 
@@ -31,86 +36,94 @@
 <itemizedlist>
 <listitem><para> sending 
 email via SMTP over TLS and receive it via IMAP over TLS (preferably) or plain 
-SMTP andIMAP (alternatively for backward compatibility 
-reasons)</para></listitem>
-<listitem><para> support for strong cryptography for 
-email bodies and attachments in addition to the securityfeatures provided by the 
-transmission protocol  (as can be found in the former project 
-"Ägypten")</para></listitem>
-<listitem><para> optional support of message receive 
-confirmations (the user gets prompted for an 
-acknowledgment)</para></listitem>
-<listitem><para> adding priorities to emails 
-(importance header)</para></listitem>
-<listitem><para> vacation message 
-functionality (via web interface)</para>
-</listitem><listitem><para> receiving 
-and sending business cards along with 
-email</para></listitem>
+SMTP and IMAP (alternatively for backward compatibility reasons)</para></listitem>
+<listitem><para> support for strong cryptography for email bodies and attachments in addition to the securityfeatures provided by the transmission protocol  (as can be found in the former project "Ägypten")</para></listitem>
+<listitem><para> optional support of message receive confirmations (the user gets prompted for an acknowledgment)</para></listitem>
+<listitem><para> adding priorities to emails (importance header)</para></listitem>
+<listitem><para> vacation message functionality</para>
+<listitem><para> email forwarding functionality</para>
+</listitem><listitem><para> receiving and sending business cards along with email</para></listitem>
 </itemizedlist>
-<para>Every standard-conformant mail user 
-agent (MUA) and web browser can be used to access the Kolab server for this 
+<para>Every standard-conforming mail user agent (MUA) and web browser can be used to access the Kolab server for this 
 functionality.</para>
 </sect1>
 
-<sect1><title>  Contacts </title>
-<para>The client 
-application maintains a private address book ("Contacts", German: 
+<sect1><title>Contacts</title>
+<para>The client application maintains a private address book ("Contacts", German: 
 "Kontakte"). Note that this is very different from a global address book. A users 
-private address book is stored on the Kolab server. A bidirectional vCard 
+private address book is stored on the Kolab server in IMAP folders. A bidirectional vCard 
 interface is provided. In consequence, vCards received as email attachments can 
-be easily added to a users contacts.</para></sect1>
+be easily added to a users contacts.</para>
+<para>In Kolab 2 the newly introduced cross-platform XML-storage format is
+introduced which allows for a server side personal addressbook which is
+interchangeable between Kolab clients including Microsoft Outlook with the
+Toltec Connector.
+<para>In Kolab 2 a user may have multiple contact folders. One is marked as
+the default contact folder though. Last but not least contact folders can be
+directly shared between users using IMAP.
+</para>
+
+</sect1>
 <sect1><title> Address Book 
 </title><para>A global shared address book is available independently from the 
 above mentioned contacts. Address book entries are maintained inside a LDAP 
-directory on the Kolab server and can be exported to iCalendar format. 
-The necessary conversion is done by the groupware client application.</para>
-<para> A user can 
-change his personal contact information on the Kolab server by using a web 
-interface.</para>
+directory on the Kolab server and can be exported to vCard and XML format. 
+The necessary conversion is done by the Kolab client application.</para>
+<para> A Kolab user or Kolab maintainer can change the LDAP based personal contact information by using the Kolab web administration interface.</para>
 </sect1>
 
-<sect1><title> Calendar Entries </title>
+<sect1><title>Calendar Entries</title>
 <para>A user can have private calendar events. Although these events are visible 
-for other users,the exact event information is hidden from them. They only see 
+for other users using published free-busy lists ,the exact event information is hidden from them. They only see 
 that a given private event of another user exists. 
-Private events are saved on 
-the Kolab server.Users can schedule group events and invite other users. An 
+Private events are saved on the Kolab server in an IMAP folder. Users can schedule group events and invite other users. An 
 existing group event can be modifiedby the user who originally created it. 
 Examples for group events are:<itemizedlist>
-<listitem><para> Group meetings </para></listitem>
-<listitem><para> Conferences</para></listitem>
+<listitem><para>Group meetings</para></listitem>
+<listitem><para>Conferences</para></listitem>
 </itemizedlist>
 Group events are saved like private calendar entries on the Kolab server and 
-differ onlyby their attributes and access permissions.
+differ only by their attributes and access permissions.
 When creating a new group event, one can check the availability of the desired 
 attendees.We refer to this later as "publishing and checking free-busy 
-lists".</para></sect1>
+lists".</para>
+<para>In addition Kolab 2 allows for multiple calendar folders for every Kolab
+user and knows about group calendars shared directly via IMAP. There is always
+one default calendar folder for every Kolab account.
+</para>
+</sect1>
 
 <sect1><title>  Notes </title>
 <para> A user may take private notes which are then stored on the Kolab server. 
-Notes can easily bemailed to other users and therewith shared with them, as 
-copies.</para></sect1>
+Notes can easily be mailed to other users and there with shared with them, as 
+copies in addition to sharing them via IMAP.</para></sect1>
 
 <sect1><title> Task Lists </title>
 <para>Users can maintain task lists with priorities. Task lists are saved on the 
-Kolab server.Items on the task list can be assigned to different users and are 
-added to their task listsas well, as they receive and accept them. Task lists 
-are private if no items are assigned to other users.</para></sect1>
+Kolab server. Items on the task list can be assigned to different users and are 
+added to their task lists as well, as they receive and accept them. Task lists 
+are private if no items are assigned to other users.</para>
+<para>Task list may be shared using IMAP folders</para>
+</sect1>
 
 <sect1><title> Shared Resources </title>
-<para>Shared resources (e. g. meeting rooms or pool cars) can be managed with 
-the solutionin the same way as regular group calendar events.</para>
+<para>Shared resources (e. g. meeting rooms or pool cars) can be managed in the same way as regular group calendar events.</para>
+<para>Basically this means that shared resources are invited to events like
+any Kolab user.</para>
+<para>In addition Kolab 2 implements automatic handling of shared resources
+with resource dependent configurable policies.
+</para>
+
 </sect1>
 
 <sect1><title> Print Services </title>
-<para>Emails, calendar events, task lists, and notes are easily printable by the 
+<para>Emails, calendar events, task lists, contacts and notes are easily printable by the 
 client application.</para></sect1>
 
 <sect1><title> Palm PDA Synchronization </title>
 <para>The contacts, calendar events, notes, and task lists can be synchronized 
-with a personaldigital assistant (PDA) bidirectionally. The HotSync protocol is 
-used and guaranteescompatibility to a wide range of PDA devices. The reference 
+with a personal digital assistant (PDA) bidirectionally. The HotSync protocol is 
+used and guarantees compatibility to a wide range of PDA devices. The reference 
 platform is a 3Com Palm V running Palm OS v3.1.</para></sect1>
 
 </chapter>





More information about the commits mailing list