RE: Recurring Anniversary Instances?

["Dan Hickman" <dhickman@xxxxxxxxxxxxxxxxxx>]

Frank,

 

I don't think your short-hand suggestion would be the right way to interpret it.  Either it is an error case or you can indeed have DATE occurrences in a DATE-TIME event (and vice-versa).

 

We do need a concensus on this.  I have already added the capability to my app and I know others have it as well (MS Outlook 97 does).  If it is an error state, I will remove it, but we need to decide.

 

I agree that this would be a wierd type of event, but the spec doesn't specifically disallow it and I don't think we should eliminate the option to provide that functionality.

 

-Dan

> Frank wrote: 
> >No, this is an error UNLESS the 
>     semantics are that when this occurs, it is a short-hand for >"take 
>     the time portion of the date/time" from the original DTSTART and DTEND. 
>     This makes >sense to me. For example, define a -T080000Z to -T090000Z 
>     meeting (a soiree for us >US-Eastern time zone folks ;-) ) event that is 
>     augmented with a RDATE property that >specifies 5 other dates. The 
>     interpretation is that these 5 other occurrences are at the >same 
>     start/end as the first occurrence. 
> > 
> >Other wise, there appears to be a value type 
>     mismatching here also introduces this hybrid >event that is both a 
>     traditional appointment and a day-long event. Too weird.