[Design] Options for Invitation workflow in 0.7

[Mimi Yin]

Could we implement subsequent Update/Notifications of an event item  
simply as email text? (ie. what happens today if you stamp an event  
as an email and hit Send). That way, we get a "complete" workflow,  
even if the entire workflow isn't interoperable. Here's the scenario:

+ A (Chandler user) sends invitations to B (Chandler user) and C  
(Outlook user) [iMIP request]
+ B edits and updates the event and sends it out as an email to A and C

+ A and C have to go manually update their invitations with B's  
updates OR
+ A and B are sharing the event through a shared calendar, therefore  
A doesn't have to manually update their invitation

Mimi

On Jan 24, 2006, at 6:33 PM, Lisa Dusseault wrote:
> Note that I'm consciously proposing a system and a workflow that is  
> not "complete".  It would provide the ability for an organizer to  
> send an invitation that would be reasonably well received by any  
> email client, not just Chandler.  It would provide the ability for  
> an attendee to indicate their attendance, yes/no.  But I suspect we  
> won't quickly get to the point of successfully handling other steps  
> -- perhaps reschedules are a little fuzzy, the ability of a  
> recipient to do a major update and automatically Notify others (see  
> Mimi's concept of an explicit conscious Notification) would be  
> interop-impaired, if even possible...   Anyway, I'm proposing some  
> first steps and not addressing all steps.