Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: icalendar parser ?

From: jason:cunliffe:verizon at: 13-May-2004 19:31

Hi Gregg
> Thanks for posting all the info! I agree that this looks like a great > opportunity and, while I can't promise any real commitment, I'm going > to put it on my (ever growing :) "to do" stack.
As I understand it iCalendar derived from vCalendar, a spec developed by Microsoft who was working with w3C and IETF to extend from their own Exhange/Outlook csheduling tools. Apple changed the game in 2002 [?] when they seized the initiative again in OSX with their own clean little iCal application set. A Zope developer friend tells me many businesses he knows are now pissed off with Microsoft's Exchange scheduling system are looking for alternatives and interoperable options. Some Plone/CMF iCalendar work has already been being done. Lotus have done a lot of work on this of course, and Chandler selected iCalendar I think. I forgot to include these link which introduce the set of protocols around iCalendar. It's part of the 'Reefknot' project and is a little out of date [2001]. Reefknot [project seems to have been suspended end of 2001, but some good whitepapers] Project goals - Build a Perl toolkit for iCalendar/RFC2445 compliant calendaring - Use the toolkit to build one or more example implementations of calendar servers and clients iCalendar Bootstrap Guide iCalendar iTIP defines what the the grammar book of scheduling. It allows you to talk with others about your calendar data CAP is a calendaring and scheduling protocol for operating on iCalendar (RFC 2445) data. It is designed to allow calendar stores (CSs) and calendar clients (CUAs, Calendar User Agents) to interact with one another over an open connection. It is a client-server protocol not unlike the IMAP protocol for communicating with a mail storage server. Some interesting user requirements reading [spring 2000] you'd expect tantalizing scope for Jabber and iCalendar. Relevant to any Rebol implementations for sure. [Design] Jabber handling of iCal [discussion posting] GwClientUseCases [Jabber] Here's a juicy excerpt... Imagine this use case: I get email from a friend that she wants to meet with me. I notice in my jabber client that she's present. I open my CUA [Calendar User Agent] to next week, and somehow select" the whole week's free-busy information. I drag the selection to my jabber client, and hit send. The info is packaged up as iTIP info, wrapped in an iCal "envelope" and sent to my friend. On her side, she can look at the events as text, or she can drag them to her CUA and see them on top of her calendar (temporarily). She creates a proposed time, drags it to her jabber client, and I recieve the invitation. I accept, adding the invitation to my CUA, which saves it back to my calendar store. Details may change based on whether or not the jabber client and the CUA are the same app, etc., but perhaps this paints an interesting picture... " Please keep me posted if you have time/mind to dig into any of this. -- Jason