KEP 3: Introduction of 'subevent' sub-tag for 'exclusion' from 'recurrence'

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at kolabsys.com
Wed Nov 17 16:00:45 CET 2010


On Wednesday, November 17, 2010 11:50:07 am Georg C. F. Greve wrote:
> Hi all,
> 
> Another decision that has been in the pipeline since 2007 was the question
> of handling exceptions from recurrence in ways that do not break the
> logical link between recurring events and their exceptions.
> 
> The initial proposal for how to resolve this was still made by Martin
> Konold, and I think it makes sense, so I wrote it up for a KEP.
> 

Do we want the subevent element to be a child of the exclusion for recurrence, 
or do we want to consider these are not exclusions to the event perse, but 
instead exceptions?

Either way the difference would be semantical, I suppose.

I would like to have documented which elements must or may be stored in within 
subevent elements though;

- start date (obviously),
- duration or end-date (this may be a validly altering aspect of a recurrent 
event as well),
- location,
- attendees,
- ...?

Thoughts?

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/format/attachments/20101117/0df6d2c2/attachment.html>


More information about the format mailing list