No, unfortunately not. There are so many other things at the moment.
as much as I personally like the davx5 client functionality/stability, it seems like this may not be the solution that fits for broader use here.
»When a calendar component is created, its sequence number is 0. It is monotonically incremented by the “Organizer’s” CUA each time the “Organizer” makes a significant revision to the
The “Organizer” includes this property in an iCalendar object that it sends to an “Attendee” to specify the current version of the calendar component.
The “Attendee” includes this property in an iCalendar object that it sends to the “Organizer” to specify the version of the calendar component to which the “Attendee” is referring.
A change to the sequence number is not the mechanism that an “Organizer” uses to request a response from the “Attendees”. The “RSVP” parameter on the “ATTENDEE” property is used by the “Organizer” to indicate that a response from the “Attendees” is requested.
Recurrence instances of a recurring component MAY have different sequence numbers.«
So this means that we have to