Good Example of Calendaring Interoperability

I was working with my email the other day, using my favorite email and calendar product, and I received an email invitation to a meeting. When I opened the email, my application "recognized" it as a calendar invite, and gave me the opportunity to accept, decline, delegate or recommend another date.  Sounds simple, right?

Except for the fact that the invite came from a web-based Meeting service. When I spoke to the person who had "invited" me to this meeting, I found out they, in turn, had used a completely different email and calendar package than mine.  It's pleasing to realize that this represents real interoperability. The calendar event used all three calendar specifications--iCalendar to describe the calendar objects, iMIP to send me the invitation by email, and iTIP to give me the opportunity to accept and decline the event. Three different vendors touched this calendar object and it still managed to arrive in my inbox in a proper format so that my calendar application readily accepted and understood the object.

To me, someone who has been waiting for just this sort of a interoperability since 1989, it was an exciting day. Hopefully it bodes well for the future interoperability.

... Pat Egen

One Comment

  1. Stuart J. McRae
    Posted September 3, 2005 at 2:05 AM | Permalink

    Hi Pat!

    Yes, it is good to see that we are finally getting there after all our efforts.

    Around 6 months ago the EEMA office started sending calendar invitations from their Outlook/Exchange system for our committee meetings and I was relieved to see that the standards and development effort had paid off and I can received the meeting invitations without problem in Lotus Notes/Domino.

    Now we just need to start training the users to actually use meeting invitations to external parties!


Post a comment

You must be logged in to post a comment. To comment, first join our community.