event XML 1.1 (fix recurrances)

Joon Radley joon at radleys.co.za
Thu Jan 18 10:00:36 CET 2007

Hi Ger,

> If a client sees a tag it does not understand, this tag must 
> be preserved and saved back to the file.

The problem with this is that in Outlook when you create a change in
attachments it creates a second object, even if the GUI only shows one
series. Toltec will preserver the unknown tag. But how does Kontact or Horde
know what object to ignore on the server?

The attachment exception is now contained in both the original object and in
the second object. Combining the two objects in Outlook is a very big
problem as the linking between them have change over many versions and was
not even supported in Outlook 2000. Until Microsoft publishes what they have
done here it is a total mine field.

Best Regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
Web: www.toltec.co.za 

> -----Original Message-----
> From: kolab-format-bounces at kolab.org 
> [mailto:kolab-format-bounces at kolab.org] On Behalf Of Gerd v. Egidy
> Sent: Wednesday, January 17, 2007 4:00 PM
> To: kolab-format at kolab.org
> Cc: Martin Konold
> Subject: Re: event XML 1.1 (fix recurrances)
> Hi,
> one thing just came to my mind:
> > - The concluding list of allowed tags below <subevent> is:
> making the list of tags allowed within <subevent> concluding 
> is different than the policy used within the rest of the 
> kolab xml format:
> >From http://www.kolab.org/doc/kolabformat-2.0rc5-html/x89.html:
> If a client sees a tag it does not understand, this tag must 
> be preserved and saved back to the file.
> If we tell clients that there can be unknown tags within 
> <subevent> and they have to preserve them as done everywhere 
> else, we could improve the <subevent> format later on without 
> unpleasant surprises. Clients just knowing the old format use 
> a best-effort strategy.
> So I'd not call the tags within subevent concluding to leave 
> space for future enhancements.
> Kind regards,
> Gerd
> _______________________________________________
> Kolab-format mailing list
> Kolab-format at kolab.org
> https://kolab.org/mailman/listinfo/kolab-format

More information about the format mailing list