[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RECURRENCE-ID discussion
While not in direct reply to this response, at the
end of at least two messages, Bruce has asked a
specific and direct question of you Doug.
Does each instance of a recurring event have its own
SEQEUNCE or is there one SEQUENCE value for the entire
recurring series which they all share?
In case the question isn't clear:
If I have a new recurring event and the only
I change I make is to update one instance in
which I use SEQUENCE:1, and then I go to
update a totally different instance, is the
SEQUENCE value for the second instance 1 or 2?
-- Michael --
"Doug Royer" <Doug@xxxxxxxxx> wrote in message
> Bruce_Kahn@xxxxxxxxxxxxxxxx wrote:
> > Doug replied on 08/08/2003 03:37:26 PM:
> > > I do not follow how or why you think his point has anything to do
> > with storage
> > > format. Are you saying because your storage format does not allow for
> > > it to change that you want other vendors to change?
> > Tim cited the example of infinite recurrence as a factor in his decision
> > for how he interpreted the RFCs. I was responding to this by pointing
> > out that the internal storage format of any CUA or CS is NOT covered by
> > iCalendar or iTIP. iCalendar is an interoperability format for on the
> > wire and iTIP is the semantics for understanding the data it represents.
> > Are you now saying that all iTIP implementations MUST use a storage
> > format thats basically native iCalendar?
> Doug Royer | http://INET-Consulting.com
> Doug@xxxxxxxxx | Office: (208)612-INET
> http://Royer.com/People/Doug | Fax: (866)594-8574
> | Cell: (208)520-4044
> We Do Standards - You Need Standards