CAP, the Calendar Access Protocol currently under discussion by the IETF calendaring and scheduling working group, is an emerging standard. Although still in the draft phases, it will most likely become the new standard protocol for calendar servers and clients to talk to one another.
In order for the Reefknot project to determine module architecture, it will help greatly for us to understand what CAP provides. We may implement CAP first, or we may implement a lighter-weight CAP alternative while we wait for the CAP spec to stabilize. This document is an overview of the current state of CAP as of CAP draft 4, which expires in September 2001. This is intended to be a gentle introduction to the basic concepts of CAP; the goal is that once you've read this, the CAP draft won't be quite so intimidating.
This document assumes that the reader has at least passing familiarity with iCalendar (RFC2445), iTIP (RFC2446), and iMIP (RFC2447). If you're not clear about what these RFCs specify, you might check out the Reefknot Bootstrap Guide.
If you have comments or corrections about this document, please mail them to the Reefknot developers' mailing list at reefknot-devel@sourceforge.net.
| Next | ||
| Basic Concepts |