Handling of DUE; VALUE=DATE [Issue 10: Re: [Ietf-calsify] All Day Events and DTEND]

[Bruce Kahn]

ietf-calsify-bounces at osafoundation.org wrote on 02/19/2007 11:39:23 AM:
> The same way that the DTEND property specifies the non-inclusive end
> of events, the DUE property should be handled the same way for to-dos.

+1

> The implication here is that any application that presents a DUE 
property
> of DATE value type as a "Due date" needs to substract one day to its 
value
> since for an end user if some to-do is due on Feburary 14, 2007 he has
> until the end of the day to complete the to-do (i.e., until 23:59:59 on
> February 14, 2007). I've been told that some applications are presenting
> this value as "Due by" to avoid this ambiguity.

  There are be different ways to express the same intent.  If something 
has a due date of today then it I have until the end of the day to get it 
done.  The same situation can also be described by saying that whatever it 
is must be done by midnight tomorrow.  Users do not care how you write it 
as long as you can clearly and consistently express the correct intent. We 
need to clearly define the meaning in iCalendar so that UI's are free to 
express it accurately but in their own way to the user.

  I find that a "due by" meaning is much less ambiguous then a "due date" 
one but perhaps that's just me.

Bruce
=========
==================================================================
Bruce Kahn                                INet: 
Bruce_Kahn at notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Once you make something idiot-proof, they build a better idiot.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20070223/cdd3d47f/attachment.htm