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:

> 4: We did not opt for a delta RECURRENCE-ID model so its not useful in 
> trying to do any shift calculations.  This coupled the above means you 
> are inventing mechanisms or behavior that is just not there or that is 
> incorrect.


The discussion was how to expand RECURRENCE-ID's in the result set.
So, what you are talking about has (again) nothing to do with the
topic of if (or not) the RECURRENCE-ID changes on old 'set's.

As has been pointed out by several on this mailing list, including
Robert-(what-ever-his-name-is) from Lotus AND YOU that the RECRRENCE-ID
is not fixed to the value it was in SEQUENCE:0. Everyone seems to agree
to that including your peers and Frank and Derik. If it was you can never
invite a new attendee or delegate to someone that never got the sequence:0
object. -You- also seem to have declared that it is per 'set' 
(uid/sequence/...).

So, given an object you were first invited to is (or your 'booked' 
object is):

    SEQUENCE:100
    UID: uid-1
    DTSTART: monday 10am
    DTEND: monday 11am
    RRULE ... daily for 5 days...

Are you trying to tell me that only a CS that have the sequence:0
object can ever return an expanded object? No. there has never been any 
one that
proposed that RECURRENCE-IDs only relate to only old objects. If your
BOOKED object is SEQUENCE:X, then the -ONLY-  RECURRENCE-ID's
that you  will ever be able to calculate is the set that contains 
SEQUENCE:X .

No amount of claming 'this' means 'that' or quoting for the nTh time 
that someone
said whatever, will ever make such objets be able to create the SEQUENCE: <X
RECURRENCE-ID values when the booked object is > X.

If you expand an object, that is exactly what it means, the named object is
expanded. It can not mean that some previous incarnation of the object is
to be expanded. It means the object you have is expanded.

So, no, the RECURRENCE-ID's are NOT the same as in the previous
topic, they must be from the BOOKED (or unscheduled) objects you have.

Think of it this way, you have X new unscheduled objects in your CS.
The CU wishes to determine IF they will respond YES I  WILL ATTEND.
The CU will need to know the dates IN THAT OBJECT in order to decide
if THOSE dates are acceptable.

The CS MUST expand those object "as is", else no matter how many times
the CUA asks, it will only get the dates for the OLDER object? No, that
would be busted.

-- 

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.