martin: doc/kolab-formats kolab-file-format.lyx,1.4,1.5
cvs at intevation.de
cvs at intevation.de
Thu Apr 1 20:14:35 CEST 2004
Author: martin
Update of /kolabrepository/doc/kolab-formats
In directory doto:/tmp/cvs-serv26906
Modified Files:
kolab-file-format.lyx
Log Message:
Martin K.: Newest additions
Index: kolab-file-format.lyx
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/kolab-file-format.lyx,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- kolab-file-format.lyx 31 Mar 2004 00:41:44 -0000 1.4
+++ kolab-file-format.lyx 1 Apr 2004 18:14:32 -0000 1.5
@@ -26,14 +26,10 @@
\layout Title
-Kolab Storage Format
+Kolab Storage Format 2.0
\layout Date
-29
-\begin_inset Formula $^{\textrm{th}}$
-\end_inset
-
- March 2004
+31 March 2004
\layout Author
Martin Konold
@@ -48,10 +44,10 @@
2026.
Different approaches to solve the issue have been proposed.
Sofar no final solution has been proposed.
- This document provides an alternative approach to the problem using a redundant
- data technique circumventing the need for a common data format and the
- corresponding need to adapt either the KDE Kolab client, the Outlook Kolab
- Plugin tor both to the ability to write foreign formats.
+ This document provides an alternative solution to the problem using a redundant
+ data technique which circumvents the need for a common data format and
+ the corresponding need to adapt either the KDE Kolab client, the Outlook
+ Kolab Plugin or both to the ability to write foreign formats.
\layout Standard
Copyright (c) 2004 Martin Konold.
@@ -63,6 +59,16 @@
on License".
\layout Section
+Goal
+\layout Standard
+
+The goal is to have a Kolab storage format which allows different Kolab
+ clients either KDE or Microsoft Outlook based to access the same data simultane
+ously in a robust and reliable fashion without loosing any data or functionality.
+ This is a hard requirement for full shared calendar and shared folder support
+ in Kolab 2.0.
+\layout Section
+
Kolab Storage Format dilemma
\layout Standard
@@ -614,7 +620,7 @@
FAQ
\layout Subsection
-Why a redundant and asymmetric format
+Why a redundant and asymmetric format?
\layout Standard
The Kolab 2.0 format as described in Chapter
@@ -682,7 +688,7 @@
in Outlook as observed by users of early versions of the Bynari Plugin.
\layout Subsection
-Why TNEF in the Kolab 2.0 format
+Why TNEF in the Kolab 2.0 format?
\layout Standard
TNEF is actually not the real issue with the legacy Kolab 1.0 formated MAPI
@@ -717,7 +723,7 @@
\layout Standard
The MS Exchange client is the predecessor of MS Outlook.
- Please also note that MS Outlook and MS Outlook express are two distinct
+ Please also note that MS Outlook and MS Outlook Express are two distinct
code bases.
\end_inset
More information about the commits
mailing list