A long time ago I gave a tutorial on the calendar standards that then
existed, to allow people to send around invitations, respond. The
notes are still up on our wiki of course:
<http://wiki.osafoundation.org/bin/view/Journal/LisaDusseault20041005>
What that doesn't provide is a technical understanding of how we'd
combine that with sharing but let's see if I can make some quick
sense of that.
- The meeting organizer can send out an iMIP invitation (with an
iTIP REQUEST method) in email
- the email can have a URL to a CalDAV/WebDAV representation of the
event -- there's a well understood field for that in iCalendar
- Any other structured information that we want to add to iCalendar,
we can (X-OSAF-CUSTOMPROPERTY)
- People who receive the invitation:
- can almost always reply (accept, counter) because this is a
normal part of the standard workflow and relies only on email
functionality
- can *also* go to the shared version of the event, if they have
access to the sharing server, and if they have read access
- can even collaborate on the shared version of the event, if they
have write access too.
How we coordinate replies together with collaborative changes, is
going to be somewhat of a challenge -- we haven't even fully
implemented handling conflicts for regular sharing scenarios, let
alone scenarios where some of the changes go to the organizer via
email instead of directly to the server.
Lisa
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
