[JDEV] iCalendar project?

[Peter Millard]

Being quite familar w/ Jabber, but not at with CAP, I check it out at ietf.org,
and I have to agree with Kellan. It looks like CAP provides a standard for
storing and dealing w/ Calendar related data, but you'd still need the store
(CS) and some kind of CUA (this _could_ be implemented into an existing Jabber
client I suppose).

You'd probably want to use some kind of existing CS if one already exists and
just create another transport for it. This would make stuff go from CAP -> XML.
But again, you'd still not a bulk of stuff on either end of the Jabber
implementation. You can easily pass stuff back and forth using either IQs or <x>
tags though.

-Peter

----- Original Message -----
From: "Sandpiper" <kceF95 at hampshire.edu>
To: <jdev at jabber.org>
Sent: Wednesday, March 29, 2000 4:29 PM
Subject: Re: [JDEV] iCalendar project?


> I agree, the speed (or lack there of) of the iCal project over the last
> several years has certainly been frustrating, though I've high hope for
> CAP.
>
> How would you use jabber and iCal together?  The most obvious way would be
> as a transport layer, i.e. create a jabber implementation of iTip. This
> would be relatively simple once you had an iCal parser, and an agreed upon
> method of representing iCal in XML.  And there is the rub.  vCard has an
> XML DTD, and while it has been suggested that iCal move to XML this
> suggestion has been met with strong resistance.
>
> Similarly, the problem of providing access to a calendar store via jabber
> would not be all that difficult(ala CAP) but this still leaves you with
> the bulk of work to be done implementing the CS and CUA.
>
> Not to be discouraging, I just don't think the communication layer is the
> hard part with scheduling.(or I could simply be being too short-sighted)
>
> Kellan