[Ietf-calsify] DTEND for day events

[Jeffrey Harris]

> Then please see the following mail by Frank Dawson, who is one of the original 
> authors of rfc 2445:
> http://www.imc.org/ietf-calendar/archive1/msg03648.html
> 
> In particular:
> 'We explicitly got feedback to add the "non-inclusive" term. It means up to 
> "T235959".'

Wow.  You're right, it looks like their intention was for non-inclusive
to mean not including the last minute of but including the rest of the
day.  That's sure not the way I read that language, so lets come up with
better language for 2445bis as Lisa suggests.

> So, the question is now what to do about this. Shall we stick to the 
> interpretation that "non-inclusive" means that DTEND needs to be first date 
> after the item? Or shall we use the correct interpretation from now on? 
> 
> The reason I'm asking is that we are releasing KDE 3.5 shortly, and currently 
> I fixed it to use Frank's interpretation. 

It seems to me that there's lots of iCal data out there with the
"doesn't include the whole day" interpretation, I suspect Outlook does
the same thing.  So I'd suggest we change the language in 2445bis to say
something like:

"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."

It's too bad there's data in the wild that means this, I really think
dates for dtends would adhere to common usage better if they were
inclusive, but ce la vies.

Sincerely,
Jeffrey Harris