Restart DTSTART for recurrence instances thread

[email protected]
Newsgroups gmane.ietf.calendar
Message-ID <OF7E10A896.6BA89EB0-ON85256DF8.0064FB78-85256DF8.00652584@egenconsulting.com>
If we have a good line of conversation going, I agree, let's keep it 
rolling.  Anyone else want to reply?  If we keep the number of notes to a 
minimum it may give people bandwidth to be able to reply.  Also, try to 
change the subject line if you are stating something different.  In trying 
to go back and build and issues list, i am missing things because they are 
in notes that have different subject lines.  Thanks for helping on that.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652



"Michael Fair" <[email protected]> 
Sent by: [email protected]
12/09/2003 19:09

To
[email protected]
cc

Subject
Re: DTSTART for recurrence instances







I think someone should pick up this thread with Doug.
This is the most productive line of conversation yet to
create clarity around this.  Some time ago Doug Royer
started ignoring me.  Will someone please reply to my post
or Doug's directly to persue this?


>     BEGIN:VEVENT
>     UID:XXX
>     SEQUENCE:1
>     ...
>     METHOD:REQUEST
>     DTSTART:2-dec-2003 at 2pm
>     DTEND:2-dec-2003 at 3:30pm
>     RECURRENCE-ID:2-dec-2003 at noon
>     ..
>     END:VEVENT
>
> Do you agree that is how to move a single instance?

Yes I agree that would be the iTIP to send to move the
2nd instance from noon to 2pm.

Now I believe the next step is to move it from 2pm to 4pm.
(I moved the RECURRENCE-ID property to place it with the identifiers.)

     BEGIN:VEVENT
     METHOD:REQUEST
     UID:XXX
     RECURRENCE-ID:2-dec-2003 at noon
     SEQUENCE:2
     ...
     DTSTART:2-dec-2003 at 4pm
     DTEND:2-dec-2003 at 5:30pm
     ..
     END:VEVENT

The key being that Recurrence-id is "at noon" and not "at 2pm".
Do you agree that is how to move a single instance a second time?

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