[Ietf-calsify] DTEND for day events

Jeffrey Harris jeffrey at skyhouseconsulting.com
Fri Sep 2 08:11:27 PDT 2005


Hi Folks,

>>>"When a DATE value is used for DTEND no time during the given day is
>>>included in the component, so
>>>
>>>DTSTART;VALUE=DATE:20050101
>>>DTEND;VALUE=DATE:20050102
>>>
>>>represents a 24 hour period."
> 
> 
> The problem then is that DTEND and DURATION are not required. If you have only 
> a DTSTART, e.g. 
> 
> DTSTART;VALUE=DATE:20050101
> 
> the above quote says that this is equivalent to
> 
> DTSTART;VALUE=DATE:20050101
> DTEND;VALUE=DATE:20050101
> 
> How would you have to understand this? And what would be the difference to
> 
> 
> DTSTART;VALUE=DATE:20050101
> DTEND;VALUE=DATE:20050102

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.

Sincerely,
Jeffrey



More information about the Ietf-calsify mailing list