Re: [ietf-calsify] Clarification on DUE in TODO's in rfc2445bis

"Must not be earlier in time" is in line with RFC 2445, which says

The value MUST be a date/time equal to or after the DTSTART value, if 
specified.

and the RFC 2445bis says

the value of this property MUST be later in time than the value of the "DTSTART" property.

This seems like a gratuitous departure from the old standard. Even 
though this is a small matter, it is important  to get the words right.

Tim Hare wrote:
> A TODO could start at 00:00 and be due by 23:59 on the same date, which
> satisfies the requirements as written.
>
> I don't know the status of the RCF vis-a-vis changes as I write this, but
> proposed alternate text if we need it:
>
>   
>> This property defines the date and time before which a
>>      to-do is expected to be completed.  For cases where this property
>>      is specified in a "VTODO" calendar component that also specifies a
>>      "DTSTART" property, the value type of this property MUST be the
>>      same as the "DTSTART" property, and the value of this property
>>      MUST NOT be earlier in time than the value of the "DTSTART" property.
>>      Furthermore, this property MUST be specified as a date with local
>>      time if and only if the "DTSTART" property is also specified as a
>>      date with local time
>>     
>
> I changed "MUST be later in time" to "MUST NOT be earlier in time" to allow
> the DTSTART and DUE to be equal, although for most use cases that seems
> illogical, and I don't necessarily agree with it.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> From: Nigel Swinson [mailto:Nigel.Swinson@mailsite.com] 
> Sent: Monday, September 07, 2009 4:41 AM
> To: Tim Hare; 'Satya Vempati'
> Cc: ietf-calsify@osafoundation.org
> Subject: Re: [ietf-calsify] Clarification on DUE in TODO's in rfc2445bis
>
> Sounds like another use case for saying something starts at 11am "ish! and
> is due by 6pm "ish".  Switching from date to date-time implies a degree of
> precision that might not be appropriate.  I'd very much like there to be
> better options for saying "I've arranged to have dinner with a friend on
> Tuesday evening", when the start/end time of that event have yet to be
> firmed up.
>
> ----- Original Message -----
> From: "Tim Hare" <TimHare@comcast.net>
> To: "'Satya Vempati'" <Satyanarayana.Vempati@Sun.COM>;
> <ietf-calsify@osafoundation.org>
> Sent: Saturday, September 05, 2009 3:13 AM
> Subject: Re: [ietf-calsify] Clarification on DUE in TODO's in rfc2445bis
>
>
>   
>> It is possible, but in my opinion, that's a case where date AND time 
>> should be used, making it easy to have the DUE value be later than the 
>> DTSTART value.
>>
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>> -----Original Message-----
>> From: ietf-calsify-bounces@osafoundation.org
>> [mailto:ietf-calsify-bounces@osafoundation.org] On Behalf Of Satya 
>> Vempati
>> Sent: Friday, September 04, 2009 7:08 PM
>> To: ietf-calsify@osafoundation.org
>> Subject: [ietf-calsify] Clarification on DUE in TODO's in rfc2445bis
>>
>> According to the text in
>> http://tools.ietf.org/html/draft-ietf-calsify-rfc2445bis-10#section-3.
>> 8.2.3
>>
>> This property defines the date and time before which a
>>      to-do is expected to be completed.  For cases where this property
>>      is specified in a "VTODO" calendar component that also specifies a
>>      "DTSTART" property, the value type of this property MUST be the
>>      same as the "DTSTART" property, and the value of this property
>>      MUST be later in time than the value of the "DTSTART" property.
>>      Furthermore, this property MUST be specified as a date with local
>>      time if and only if the "DTSTART" property is also specified as a
>>      date with local time.
>>
>> Does this mean that even when the DTSTART property type is DATE, DUE 
>> has to be greater than DTSTART? Why can't they be equal? Isn't it 
>> possible to have to-do's that start and are due on the same day?
>>
>>
>>     
>
> _______________________________________________
> ietf-calsify mailing list
> ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>   