bo: doc/kolab-formats folders.sgml,1.1,1.2 overview.sgml,1.1,1.2

[cvs at intevation.de]

Author: bo

Update of /kolabrepository/doc/kolab-formats
In directory doto:/tmp/cvs-serv2002

Modified Files:
	folders.sgml overview.sgml 
Log Message:
Fixing some of the bad descriptions

Index: folders.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/folders.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- folders.sgml	10 Jun 2004 15:15:52 -0000	1.1
+++ folders.sgml	15 Jun 2004 09:15:29 -0000	1.2
@@ -49,13 +49,23 @@
 
 <sect1><title>Mail contents</title>
 
-<para>The mail we store in will have the some so far undefined text as
-the body, and any number of attachments. One of these attachments will
-be the XML file containing the entry. The mimetype will be
+<para>The IMAP folder contents will of course normally be email. But
+in the special folders containing notes, events, tasks and so on, the
+following rule applies.</para>
+
+<para>We store on note/event/task/... in each mail on the IMAP server.
+The mail we store in will have the some so far undefined text as the
+body (could for example be a link to www.kolab.org and say why you can
+not view this as a normally mail), and any number of attachments. One
+of these attachments will be the XML file containing the actual entry
+(the note/event/task/...). The mimetype of this attachment will be
 "application/kolab.<type>" where type is the content type of the
 file. Some of these attachments can be referenced in the file, and
-these are "owned" by the XML file.  Those that are not referenced must
-be preserved when the mail is saved again.</para>
+these are "owned" by the XML file, meaning if the client application
+deletes the attachment reference, the attachment should also be
+deleted.  Those attachments that are not referenced must be preserved
+when the mail is saved again.</para>
+
 </sect1>
 
 </chapter>

Index: overview.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/overview.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- overview.sgml	10 Jun 2004 15:15:52 -0000	1.1
+++ overview.sgml	15 Jun 2004 09:15:29 -0000	1.2
@@ -1,5 +1,8 @@
 <chapter><title>Kolab Storage Format Overview</title>
 
+<para>This document describes what a Kolab client can store in the
+IMAP folders on a Kolab server.</para>
+
 <para>The Kolab storage format is designed to provide a unified
 storage format for several Kolab client implementations.</para>
 
@@ -42,6 +45,10 @@
           Entry fields go here
         </Type>
 ]]></programlisting></para>
+
+<para>where <Type> can be Note, Event, Task, Journal, or
+Contact. If a client has a new type, it is allowed to implement this,
+but then other clients will not be able to handle the folder entry.</para>
 
 <para>All node names are case insensitive.</para>