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

Georg C. F. Greve greve at kolabsys.com
Tue May 31 19:01:47 CEST 2011


On Wednesday 25 May 2011 11.54:34 Bernhard Reiter wrote:
> Isn't the example is missing the required fields? E.g creation-date.

Good catch, added.


> We could consider referring to the updated rfcs for iTIP and iCalender
> 5545 and 5546 instead of the older ones.

Ack. Added.


> If we were looking into b) from above, by reference, this would be
> something a little bit like the RELATED-TO of iCalender. It would be
> useful for other purposes as well, so it can be introduced later as an
> alternative to the more complex cases. For simple cases the current KEP3
> draft seems okay to me.

Ok. So let's go forward with this now so we can resolve the issue, and then 
think about more complex scenarios when they come up.

Will send out a new version in a moment.

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/20110531/840bb515/attachment.sig>


More information about the format mailing list