Re: Alarms/SEQUENCE (was Re: Status of the CALSCH working group)

Nathaniel Borenstein wrote:
> 
> On Friday, November 7, 2003, at 04:14 PM, Doug Royer wrote:
> 
>           Alarms/SEQUENCE -- I remain confused: Can there be two identical objects in the same calendar? If not, we should clearly say so.
> 
>      You can and iCAL has no such restriction on any component including VALARMs.
>      Currently all components have a unique identifier within their context of usage.
>      Some want no unique identifier, and their stated reasons specifically ignores the
>      identical components issue.
> 
> But what does this mean? If you store two identical items in your database
> without any unique identifiers, how can a client ever choose one over
> the other? I'm having a hard time seeing how this is a good idea. -- Nathaniel

On my PDA the default entry is audio alarm. I have often accidentally
created two audio alarms when I really wanted one audio and one pager
(email) alarm. Then had to go back and fix them later when the
two alarms go off which when I notice that I made the mistake.

If CAP did not allow me to fixed them I have to throw away
the entire VEVENT and start over? I hope not.

VALARMS need a unique identifier. Think about it, the topic is
why would you need to uniquely identify a VALARM in a MODIFY command.
One answer is to fix a problem.