[Cosmo-dev] sharing update 12/20
jeffrey at osafoundation.org
Thu Dec 21 10:10:16 PST 2006
> * cosmo only supports event rdates and exdates that specify lists
> of icalendar dates. icalendar also allows rdates and exdates to
> specify lists of periods. is it okay for event:rdate and event:exdate
> to have values containing either dates or periods? if either, that
> implies we need to include the icalendar VALUE parameter in the field
> value as well.
In my humble opinion RDATEs with periods are nuts. I've never actually
seen one in the wild, and it would be interesting to see which, if any,
major iCalendar clients will even import them successfully. We should
lobby for rfc2445bis to remove them (/me goes off and composes a message
to calsify about that)...
I don't even understand what an EXDATE for a period of time is supposed
> * similarly, cosmo only supports icalendar datetimes for event
> dtstart, dtend, and recurrenceid. do we need to support icalendar
> dates as well? these icalendar properties all have a VALUE parameter
Dates (as opposed to datetimes) are heavily used by existing clients, so
I'd say yes, you do need this here.
More information about the cosmo-dev