On 07/07/15 17:46, Milan Crha wrote: > On Tue, 2015-07-07 at 08:50 +0200, Daniel Pocock wrote: >> If the CalDAV and iCalendar standards don't specify a way to do this, > > Hi, > to be honest, I'm just not aware of anything for it. I do not have the > RFCs that well studied (and remembered), thus it's possible there is a > way to store such things on a CalDAV calendar, in an iCalendar > structure. > >> then would the Evolution developers consider submitting an IETF draft >> proposing a solution? > > I wouldn't be surprised if there is one already. I wouldn't do it > myself right now, it requires some time to get with something sane.
Looking at this more closely, it appears that Mozilla Lightning stores the alarm snooze and dismiss status in the CalDAV server using custom fields X-MOZ-LASTACK and X-MOZ-SNOOZE-TIME Mozilla is also looking at storing local state for alarms from read-only calendars: https://bugzilla.mozilla.org/show_bug.cgi?id=861594 Some other vendors, including Google Calendar, appear to support the X-MOZ-* extensions: https://bugzilla.mozilla.org/show_bug.cgi?id=451821 A search engine finds other examples. There appears to be work in progress on an RFC, it is currently known as draft-daboo-valarm-extensions https://tools.ietf.org/html/draft-daboo-valarm-extensions-04 It could be interesting for the GNOME Evolution community to give feedback on the draft. I created enhancement requests in Bugzilla for each of these possible solutions: https://bugzilla.gnome.org/show_bug.cgi?id=777274 https://bugzilla.gnome.org/show_bug.cgi?id=777275 Regards, Daniel _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
