david: doc/kolab-formats commonfields.sgml,1.20,1.21

[cvs at intevation.de]

Author: david

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

Modified Files:
	commonfields.sgml 
Log Message:
Mention scheduling-id


Index: commonfields.sgml
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/commonfields.sgml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- commonfields.sgml	11 Mar 2005 11:37:07 -0000	1.20
+++ commonfields.sgml	3 May 2005 10:53:31 -0000	1.21
@@ -53,6 +53,7 @@
 <para><programlisting><![CDATA[
         <summary>(string, default empty)</summary>
         <location>(string, default empty)</location>
+        <scheduling-id>(string, default not present)</scheduling-id>
         <creator>
           <display-name>(string, default empty)</display-name>
           <smtp-address>(string, default empty)</smtp-address>
@@ -79,6 +80,15 @@
           <role>(string, default required)</role>
         </attendee>}
 ]]></programlisting></para>
+
+<para>The scheduling ID is usually not set (meaning that it's identical to the UID).
+The only case where it's set, is when the event comes from accepting an incidence.
+In that case, the scheduling ID is the same as the UID of the initial invitation,
+and this incidence has a different UID. The scheduling ID is used for all
+scheduling purposes, in particular for matching replies with invitations.
+The reason for not using the same UID in both incidences is that they would
+conflict if they are stored in different calendar folders.</para>
+<!-- http://www.kolab.org/pipermail/kolab-format/2004-October/000471.html -->
 
 <para>The start-date is optional for tasks. For events, it is required. If
 they are there, they can either have a date or a datetime as the