[Ietf-calsify] DTEND for day events
daboo at isamet.com
Fri Sep 2 08:49:38 PDT 2005
--On September 2, 2005 8:11:27 AM -0700 Jeffrey Harris
<jeffrey at skyhouseconsulting.com> wrote:
> If we followed what I believe iCal is doing (and what I have done in
> Chandler, following iCal, but Chandler's not shipping so it can change
> however we want), there would be no semantic difference between the
> three examples above.
> I'll freely admit I have lots of special casing in Chandler to deal with
> this oddity, I'd be delighted to get rid of it. Unfortunately, I think
> given how widespread the above (admittedly not the intended by the
> authors) interpretation is in actual use, we need to work with it for
> VERSION:2.0 iCalendar.
> We should probably find out what different implementations are doing
> what with VALUE=DATE events at the upcoming CalConnect... Perhaps if
> it's just iCal, we could special case anything old iCal data, but that
> sounds like a nightmare to me.
I treat DTEND as always being exclusive in iCalendar data - even for
date-only values. However, when a user edits or creates an 'all-day' event,
the displayed end time is actually the inclusive end. So I basically map
between inclusive/exclusive values for display purposes because I found
inclusive end to be more intuitive for users. i.e it makes more sense that
a two day event starts on Monday and ends on Tuesday, than it does to start
on Monday and end on Wednesday (the exclusive option).
More information about the Ietf-calsify