[Kolab-devel] Kolab XML specification

[Till Adam]

On Wednesday 20 April 2005 21:03, Joon Radley wrote:

> > running Kolab 2 Beta 3 I have messages for events in my
> > resource account which have:
> >
> >   Subject: libkcal-357617956.864
> >   <uid>kolab-71cbdf53d0ecc61bf4ea77158e238817</uid>
> >   <scheduling-id>libkcal-357617956.864</scheduling-id>
> >
> > So the <uid> doesn't correspond to the subject while the
> > <scheduling-id> does. I've searched the format specification
> > PDF for scheduling-id and couldn't find it in that document.
> > Who can give further details?
>
> The subject must contain the <uid>. Anything else is a bug. BTW what is
> <scheduling-id>? Any unknown tag sould start with x-.

The scheduling-id was introduced to the format (if it's missing in the spec 
then Bo forgot about that, I'm pretty sure it was discussed on the format 
list, at the time) to solve a problem with the same incidence being in 
several folders at the same time, all of them visible to the same user. To 
avoid confusion with the incidence being there twice, with the same uid, 
which violates the global assumption that each event has a unique id, the 
concept of separating the uid, which is globally unique, even for identical 
copies of the same incidence in different folders, from the scheduling id, 
which is the uid to be used when scheduling this event (the uid of the 
"original" instance of the event). That means that clients should use the 
scheduling uid for all scheduling actions on the incidence as soon as it is 
present, and use the uid as normal otherwise. The details of how this came 
about and the different strategies discussed to resolve the issue are to be 
found in the archives, I believe. 

Till
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20050420/7633e458/attachment.sig>