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

[Georg C. F. Greve]

On Wednesday 17 November 2010 17.26:31 Sérgio Martins wrote:
> This is good, we can finally change one single occurrence without having
> to  send two iTip messages to attendees ( one adding a new incidence, and
> another changing the exception list of the original incidence ).
> One invitation e-mail will be enough.

Yes, this is one of the reasons why this was proposed.


> I would suggest to use the "recurrence-id" terminology to identify such 
> exceptions.
> "recurrence-id" is the name of this feature in the ical and iTip
> standards,  and it's equal to the occurrence's dtstart.

That is an interesting idea.

I wonder whether we need to make this its own tag, or whether we should simply 
define that the 'exclusion' date is the recurrence-id, because that way we 
retain backwards compatibility and get the benefits of the concept.

Best regards,
Georg


-- 
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/20101117/4311d4a5/attachment.sig>