martin: doc/kolab-formats commonfields.sgml, 1.22, 1.23 contacts.sgml, 1.15, 1.16 kolabformat.sgml, 1.17, 1.18 mail.sgml, 1.1, 1.2
cvs at kolab.org
cvs at kolab.org
Thu Nov 16 23:34:57 CET 2006
Author: martin
Update of /kolabrepository/doc/kolab-formats
In directory doto:/tmp/cvs-serv22293
Modified Files:
commonfields.sgml contacts.sgml kolabformat.sgml mail.sgml
Log Message:
Martin Konold: new version 2.0rc5
Index: commonfields.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/commonfields.sgml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- commonfields.sgml 12 May 2005 13:48:16 -0000 1.22
+++ commonfields.sgml 16 Nov 2006 22:34:55 -0000 1.23
@@ -1,28 +1,28 @@
<chapter><title>Common Fields</title>
-<sect1 id="common-in-all-types"><title>Common In All Types</title>
+<sect1 id="common-in-all-types"><title>Common Fields In All Types</title>
-<para>There are a number of fields that are present in all non-mail
+<para>There are a number of fields that MAY be present in all non-mail
folder types. These are:</para>
<itemizedlist>
-<listitem><para>uid (string, no default)</para></listitem>
+<listitem><para>uid (string, mandatory)</para></listitem>
-<listitem><para>body (string, default empty)</para></listitem>
+<listitem><para>body (string, default "")</para></listitem>
-<listitem><para>categories (string, default empty)</para></listitem>
+<listitem><para>categories (string, default "")</para></listitem>
-<listitem><para>creation-date (datetime, no default)</para></listitem>
+<listitem><para>creation-date (datetime, mandatory)</para></listitem>
-<listitem><para>last-modification-date (datetime, no default)
+<listitem><para>last-modification-date (datetime, mandatory)
</para></listitem>
-<listitem><para>sensitivity (string, default public)</para></listitem>
+<listitem><para>sensitivity (string, default "public")</para></listitem>
<listitem><para>inline-attachment (string, no default)</para></listitem>
<listitem><para>link-attachment (string, no default)</para></listitem>
-<listitem><para>product-id (string, default empty)</para></listitem>
+<listitem><para>product-id (string, default "")</para></listitem>
</itemizedlist>
@@ -32,10 +32,16 @@
<para>The sensitivity possibilites are private, confidential and
public.</para>
+<para>
+private data SHALL not be disclosed to other users except if explicitly allowed by the user.
+Normal IMAP ACLs granting reading permissions on a folder don't mean that other users MAY read
+private data.
+</para>
+
<para>There can be any number of attachments. "inline-attachment" references the
filename of attachments in the mail where this is stored. Attachments
not referenced from the XML should simply not be displayed to the user.
-This allows to attach application-specific attachments (like TNEF for Outlook)
+This allows to attach application-specific attachments (like TNEF for Outlook clients)
that remain hidden to the user.</para>
<para>"link-attachment" means the attachment is external; the contents of the tag is the URL.</para>
@@ -51,15 +57,15 @@
base class can be called incidence.</para>
<para><programlisting><![CDATA[
- <summary>(string, default empty)</summary>
- <location>(string, default empty)</location>
+ <summary>(string, default "")</summary>
+ <location>(string, default "")</location>
<creator>
- <display-name>(string, default empty)</display-name>
- <smtp-address>(string, default empty)</smtp-address>
+ <display-name>(string, default "")</display-name>
+ <smtp-address>(string, default "")</smtp-address>
</creator>
<organizer>
- <display-name>(string, default empty)</display-name>
- <smtp-address>(string, default empty)</smtp-address>
+ <display-name>(string, default "")</display-name>
+ <smtp-address>(string, default "")</smtp-address>
</organizer>
<start-date>(date or datetime, default not present)</start-date>
<alarm>(number, no default)</alarm>
@@ -72,11 +78,11 @@
{<exclusion>(date, no default)</exclusion>}
</recurrence>
{<attendee>
- <display-name>(string, default empty)</display-name>
- <smtp-address>(string, default empty)</smtp-address>
+ <display-name>(string, default "")</display-name>
+ <smtp-address>(string, default "")</smtp-address>
<status>(string, default none)</status>
<request-response>(bool, default true)</request-response>
- <role>(string, default required)</role>
+ <role>(string, default "required")</role>
</attendee>}
]]></programlisting></para>
@@ -84,9 +90,9 @@
they are there, they can either have a date or a datetime as the
type. Parsing this is just a matter of looking at the length of the
date string. In the case of an all day event (floating event) the end-date
-must also be in date only format</para>
+MUST be in date only format</para>
-<para>The alarm specifies number of minutes before the incidence that
+<para>The alarm specifies the number of minutes before the incidence when
the alarm should fire. In case of incidences with only a start date
but no specific time, this means minutes before 0:00 on that
day.</para>
Index: contacts.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/contacts.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- contacts.sgml 11 Mar 2005 11:37:07 -0000 1.15
+++ contacts.sgml 16 Nov 2006 22:34:55 -0000 1.16
@@ -29,7 +29,7 @@
</name>
<free-busy-url>(string, default empty)</free-busy-url>
<organization>(string, default empty)</organization>
- <web-page>(string, default empty)</webpage>
+ <web-page>(string, default empty)</web-page>
<im-address>(string, default empty)</im-address>
<department>(string, default empty)</department>
<office-location>(string, default empty)</office-location>
Index: kolabformat.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/kolabformat.sgml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- kolabformat.sgml 27 Jul 2005 22:46:44 -0000 1.17
+++ kolabformat.sgml 16 Nov 2006 22:34:55 -0000 1.18
@@ -15,7 +15,7 @@
<bookinfo>
<title>The Kolab Storage Format</title>
-<subtitle>2.0rc3</subtitle>
+<subtitle>2.0rc5</subtitle>
<!--<subtitle>Draft CVS</subtitle>-->
<authorgroup>
<othercredit>
@@ -27,7 +27,7 @@
<othername> Stuart Binge, s.binge at codefusion.co.za </othername>
</othercredit>
</authorgroup>
-<pubdate>June 3rd, 2005</pubdate>
+<pubdate>November 16th, 2006</pubdate>
<!--<pubdate>CVS $Date$ $Revision$</pubdate>-->
<legalnotice>
<para> This documentation was written in SGML using the DocBook DTD. HTML
@@ -38,10 +38,9 @@
<trademark class='registered'>Microsoft Outlook</trademark>
are registered trademarks of Microsoft Corporation Inc.
</para>
-<para> <trademark>Toltec Connector</trademark> is a trademark of Radley Network Technologies CC, South Africa.</para>
+<para> <trademark>K Desktop Environment</trademark> and <trademark>KDE</trademark> are registered trademarks of the KDE e.V. </para>
<para> <trademark>KONSEC Konnektor</trademark> is a trademark of KONSEC GmbH, Germany.</para>
-
-<para> <trademark>K Desktop Environment</trademark> and <trademark>KDE</trademark> are trademarks of the KDE e.V. </para>
+<para> <trademark>Toltec Connector</trademark> is a trademark of Radley Network Technologies CC, South Africa.</para>
<para> All other herein mentioned trademarks belong
to their respective owners. Use of a term in this document should not be regarded as
@@ -133,6 +132,14 @@
<date>July 26th, 2005</date>
<revremark>
Clarifications about keywords and folder annotations.
+</revremark>
+</revision>
+
+<revision>
+<revnumber>2.0rc5</revnumber>
+<date>November 16th, 2006</date>
+<revremark>
+Clarifications about empty strings and changed </webpage> to </web-page>.
</revremark>
</revision>
Index: mail.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/mail.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- mail.sgml 10 Jun 2004 15:15:52 -0000 1.1
+++ mail.sgml 16 Nov 2006 22:34:55 -0000 1.2
@@ -2,4 +2,6 @@
<para>Mail folders hold mails in the format as described in RFC 822.</para>
+<para>All other details about mail folders are already defined in the previous chapter</para>
+
</chapter>
More information about the commits
mailing list