![](images/wiki.gif) | CalDAV |
WebHome | UnixGeekTools | Geekfarm | About This Site
Pointers
My notes from ApacheCon 2005
- presentation by Lisa Dusseault, OSAF
- Open Source, Standards-based Calendar Sharing
Cosmo
- OSAF's Calendaring and Sharing Server
- Support Chandler and others
- Calendaring and Sharing
- Easy to install, administer, for just a workgroup
- Free
CMP?
Architecture
Jackrabbit and JCR
- incubator project
- Reference implementation of the JCR - Java Content Repository API
- alternative to database storage
- less structured, more flexibility, easier to extend
Chandler
- OSAF's Rich Personal Information Management Application
- manage email, events, and tasks in an integrated extensible
framework
- Python, wsWidgets, pyLucene
- about to release 0.6 - experimental calendar app at this point
Scooby
- Calendar WebUI front-end for Cosmo
- Using AJAX
- Using CalDAV as if it were a client
- online alternative calendar access
OSAF goal
- easy to share personal information
- Especially calendars, personal or shared
- email and tasks too - mixed or separate
- Hand control over to users
- easy to set up
- standards complaint data import/export
- user interface - rich clients, easy features
- availability - web app and sync
- .mac - similar goal (plus backup)
WebDAV
- distributed authoring and versioning
- used for file sharing, content managment, source control (subversion)
- internet-scale heirarchical storage
- rich meta-data for any content type
other specialized services
- images - e.g. flikr
- bookmarks - e.g. delicious
- access for rich apps, thin (web) apps, and hip
calendaring
- CAP - "calendar access protocol" like IMAP
- stalled after 7 years
- start over again with new ideas
- start with HTTP - crucial for good Web app architecture
layers
- http - resources, addresses, download, upload, sync
- webDav - collection model, move, copy, permissions: ACL
- use iCalendar for data format
- top with:
- calendar collection type
- query - this week
- query - when is joe busy
CalDAV
- open and interoperable protocol for calendar access and sharing
- IETF submission
- open mailing list
Calendar Consortium
CalDAV implementations
- clients: chandler, sunbird, evolution
- servers: oracle, hula, RPI, cosmo/scooby
protocol architecture
- top - icalender resources
- middle level
- http methods, headers
- WebDAV methods, headers, properties
- CalDAV methods, reports
- bottom - http request model
CalDAV data model
- collection
- resources - individually addressible http urls
special calendar features
- REPORT free-busy time (permissions)
- REPORT events in a time range
- filter by properties as well as time
- required to browse instead of download
- handles recurrences
challenges
- recurrence patterns
- with exceptions
- timezones
- permissions
- sharing - cross site authentication
next steps
- Release Chandler, Cosmo, and Scooby
- help welcome
- finish CalDAV - submit to IETF
- revise WebDAV - more solid spec
- HTTP authentication
- Revise iCalendar in CALSIFY WG
- Components for WebApp/JCR integration
Updated Sun Jul 23, 2006 12:10 PM