[Ietf-calsify] Section 4.8.7.2 Date/Time Stamp: Purpose of DTSTAMP in the context of calendaring

[Cyrus Daboo]

Hi Bernard,

--On July 5, 2007 12:59:59 AM -0400 Bernard Desruisseaux 
<bernard.desruisseaux at oracle.com> wrote:

> New text:
>
>  > Purpose:  In the case of an iCalendar object that specifies a
>  >    "METHOD" property, this property specifies the date and time that
>  >    the instance of the iCalendar object was created.  In the case of
>  >    an iCalendar object that doesn't specify a "METHOD" property, this
>  >    property specifies the date and time that the information
>  >    associated with the calendar component was last revised in the
>  >    calendar store.

Well "calendar store" is not defined anywhere. Plus if I happen to use 
iCalendar format as the native format in my calendar store this would not 
hold true - i.e. DTSTAMP would not change when the calendar data changed.

I am also a little unsure of what "created" means in the METHOD case. For 
instance, in at least one implementation I have done I create the iTIP 
message for an event by copying that event. Are you saying that when that 
happens a new DTSTAMP must be used? If so, I think the term "generated" 
might be better than "created". Or we should be much more explicit. In fact 
perhaps iTIP should state that every new iTIP message, be it a PUBLISH, 
REQUEST, REPLY etc MUST have a new DTSTAMP generated for it. If we go down 
that route then maybe 2445 needs to say nothing about DTSTAMP + METHOD.

-- 
Cyrus Daboo