RFC: KEP3: Introduction of 'subevent' sub-tag for 'exclusion' from 'recurrence' (revision #10661)

Georg C. F. Greve greve at kolabsys.com
Fri Dec 10 15:13:24 CET 2010

Hi Alain,

On Monday 06 December 2010 21.36:54 Alain Abbas wrote:
> but it s more simple to process all at the same level for alghorithm as
> subevent Poom model in active sync is like that and the object model in
> outlook i think too if the deletion is in the same tag you have just a loop
> and a test . if there are at different level you must have 2 loops with the
> risk of error if a date is in the exclusion and in the subevent too

I must say this defeats my expectation of how this would work practically.

Normally I'd parse XML through one of the parsers, which would give me a tree 
structure in memory. From that came the expectation that a check

	if ( exception.subevent != null) { // treat as deletion

would be as simple as

	if ( exception.delete == 1) { // treat as deletion

Help, anyone? How do others see this?

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20101210/f75677de/attachment.sig>

More information about the format mailing list