[General] Chandler interoperability documentation

[Mikeal Rogers]

> I am probably going to do some tables that show the following:
>
> * which servers Chandler Desktop can subscribe to Calendars from  -  
> i think this is Chandler Server at the moment -- have we tested any  
> others?

Any webcal (might want to mention Google Calendar).
For CalDAV we've tested quite a bit against Apple, Oracle and  
Bedework. I don't know if Oracle has released the CalDAV server we're  
been testing against yet.

Bedework -- http://www.bedework.org/bedework/
Apple Calendar Server -- http://trac.macosforge.org/projects/ 
calendarserver

> * which servers Chandler Desktop can publish to - same as above

Again; Oracle, Apple and Bedework.

>
> * which clients can subscribe to Calendars from Chandler Server -  
> Chandler Desktop, Sunbird, Lightning, iCal

And Evolution http://chandlerproject.org/Projects/CosmoWithEvolution .

That's pretty much it. I know bcm has been working through some  
issues with Google to get them digesting our webcal feeds properly  
but I don't know what the status of that is.

> * which clients can publish calendars to Chandler Server - Chandler  
> Desktop, Sunbird, Lightning, iCal

Sunbird and Lightning publish to cosmo is not without bugs. I believe  
the current release is the one discussed in the page that bcm wrote  
up that you're already linking to, but the next next release will see  
huge changes in that code base. Until the next interop i won't be  
sure how far along they've come. One problem we seem to run in to is  
that client implementations of CalDAV are jumping in to scheduling  
right away and make a lot of assumptions when doing publishing that  
isn't true of CalDAV implementations without scheduling -- i know we  
ran in to some problems with this in the last interop.

iCal 2.x publishing is just the old style webcal publish over WebDAV.  
I would be careful about promoting this because I've seen nothing but  
confusion from everyone I've seen use it.

>
> If people have additional ideas on what would be useful, I'd love  
> to hear them.   My goal is to make a lot of progress on this by the  
> end of the day on Friday.

I would stay away from using one large table for all clients and/or  
servers and break it up in to a few. Like one for webcal, one for  
CalDAV.

You may want to highlight very clearly that we don't support  
scheduling. Especially for anyone who is running pre-release version  
of iCal 3.

-Mikeal