arnaudq's blog
Calconnect discussion: use of VALARM in clients: dismiss versus snooze (continued)
More on alarms (see previous post):
Snoozing an alarm - non recurring event:
It first striked me
that snoozing an alarm was a pure client issue. I "snooze" a lot but in general,
it is to be pinged again 1 minute before the beginning of a meeting. Apparently,
other people are snoozing for much longer periods of time (e.g. one day). And
indeed some popular calendar clients offer options to snooze for up to several
weeks. So maybe in this type of scenario the information should be propagated to the server after all.
My preference would be to use extra VALARM to convey the snooze information as it should work today across clients.
Out of the 3 solutions presented above for non recurring events, only the second and third make sense in the context of recurring events as the first solution (change the TRIGGER) would translate to changing the TRIGGER value for all the upcoming instances of the event. Creating an exception every time the user wants to snooze would not be acceptable either.
One thing to note about the 2 other solutions is that if multiple instances get snoozed, there is no link between the instance that triggered the original alarm and whatever information we add (SNOOZEUNTIL property or VALARM) to indicate that the alarm was snoozed. For example, if I have a recurring weekly meeting, I snooze the alarm on the first instance for 5 more weeks, then one week later, I snooze the alarm of the second instance for 1 more week. I will end up with 2 SNOOZEUNTIL properties or 2 VALARM components but I have no way of knowing which instance triggered them to be added. But do we really care ?...
Posted at 02:43AM Sep 25, 2007 by arnaudq in CalDAV | Comments[1]
It seems to me that it would be fairly simple to link particular snooze-times to certain instances of a recurring event/todo by simply appending a parameter with the recurrence-id to the snooze-time property. Something like
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:19970317T133000Z
X-MOZ-SNOOZE-TIME;X-MOZ-OCCURRENCE=19970318T133000Z:19970318T143000Z
ACTION:DISPLAY
END:VALARM
(apologies for any syntax errors in that hand-crafted ICS, but you get the idea)
Posted by jminta on September 28, 2007 at 10:28 PM CEST #