Re: eimml and expanding recurring events

Moving to list:

I don't want to have one format for modifications and one
for  
occurrences. In my mind there's no real difference -
occurrences are  
just modifications without modifications.

Who says that a regular instance doesn't have a
recurrenceId? The way  
I read the spec (rfc2445 section 4.8.4.4) is that recurrence
Id's  
identify instances (what we call occurrences.) It reads:

	The "RECURRENCE-ID   property allows the reference to
an individual  
instance within the recurrence set."

By definition recurrenceId == startDate for non-exceptional 

occurrences, so it may seem like I am being pedantic. But
there is a  
real reason I would like it to be the same as modifications
and that  
is because for modifications we decided that the UID fields
contains  
the dtStart converted to UTC, but for occurrences it has a
DtStart  
which is not converted (i.e. it remains in its original
timezone.)  
That seems to me inconsistent and an unnecessary burden on
consumer  
of EIM to decide when to make that conversion.

>
> On May 18, 2007, at 10:39 AM, Brian Moseley wrote:
>
>> On 5/18/07, Bobby Rullo <brosafoundation.org> wrote:
>>> To be pedantic, in the uuid, it's really not
"dtStart" but
>>> recurrenceId, right?
>>
>> no, because a regular recurrence instance doesn't
have a
>> recurrence-id. only exceptions do. recurrence-id is
only necessary
>> when the dtstart of the instance could be different
from the dtstart
>> as defined by the recurrence rule. this isn't
possible with a regular
>> recurrence instance because its dtstart *is*
defined by the  
>> recurrence
>> rule.
>

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev