Re: DTSTART for recurrence instances

Doug Royer <[email protected]>
Newsgroups gmane.ietf.calendar
Organization http://INET-Consulting.com
Message-ID <[email protected]>

[email protected] wrote:

>
> Doug wrote on 12/04/2003 04:10:11 PM:
> > > Section 4.8.4.4 Recurrence ID
> > > . . .
> > >    The date/time value (RECURRENCE-ID) is set to the time when the
> > > original recurrence
> > >    instance would occur; meaning that if the intent is to change a
> > >    Friday meeting to Thursday, the date/time (RECURRENCE-ID) is still
> > > set to the
> > >    original Friday meeting.
> >
> > Meaning in the object being sent in the reschedule. In order to say X
> > moves to Y,
> > you need to properties to hold X and Y. So the above paragraph means 
> send a
> > new object with the new Y in RECURRENCE-ID and the old X in DTSTART.
>
> Lets not start this again shall we?  The original authors have even 
> responded to this and they have clearly said that RECURRENCE-ID does 
> not change on an instance reschedule.  The DTSTART for the instance 
> can change on each instance reschedule but the the RECURRENCE-ID does 
> not.   


NO ONE SAID THAT IS THE TOPIC.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
[email protected]                 | Office: (208)520-4044
http://Royer.com/People/Doug   |    Fax: (866)594-8574
                               |   Cell: (208)520-4044

               We Do Standards - You Need Standards
smime.p7s (application/x-pkcs7-signature, 4.6 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.