OPENCAP
The goal of the Open CAP project is to provide an Open Source server for Internet Calendaring by following the specifications of the Internet Engineering Task Force (IETF).
OpenCAP is available under Apache License, Version 2.0 at .
Why another calendaring project ?
Ideally, Internet Calendaring should allow every Internet user to schedule meeting with each-other like they send mails. Unfortunately, Internet Calendaring suffers from a lack of interoperability. That's why it's so important to follow such standards.
Project status
OpenCAP is under development, not usable yet.
(12/12/2005) - The core server features are implemented :
- Client communication (BEEP, TLS)
- Modular authentication (SASL/Plain, JAAS)
- Query analysis (Cap4j, iCal4j)
- Create, Modify, Delete calendar objects (Cap4j, iCal4j)
- Add, delete, modify, search on calendar content (events, todo..) (Cap4j, iCal4j)
- Data storage (filesystem storage only for now)
We're working on Access Control Lists (to be able to share calendar content) with JAAS.
Project history
This project was started in 
in October 2004 by:
- Alexandre PAUZIES - Project founder, leader, core developer
- Alexandre SANHAJI - Core developer
- Dan GALULA - Member
- Vincent TOUITOU - Member
- Yohann ZERBIB - Member
- Livio JEANGOUDOUX - Member
under the direction of Flav ASTRAUD and Jerome LANDRIEU.
EPITECH is computer science school in Paris - FRANCE
Downloads
Actually you could download only the Cap4j library.
Cap4j is an implementation of Cap protocol from RFC 4324 written by Doug Royer based on iCal4j wroten by Ben Fortuna which is an implementation of iCalendar (RFC2445).
See Available files on .
You could also get it from the CVS repository.
Documentation
-
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
-
iCalendar Transport-Independent Interoperability Protocol (iTIP)
This document describes the messages used to schedule calendar events.
-
Calendar Access Protocol (CAP) is now RFC
This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them.
This document describes the data format for representing calendar information, to be used and exchanged by other protocols.
This document describes the Calendar Access Protocol (CAP), an Internet protocol that permits a Calendar User to utilize a Calendar User Agent to access an iCAL based Calendar Store.
This document describes a generic application protocol kernel for connection-oriented, asynchronous interactions called the BEEP (Blocks Extensible Exchange Protocol) core. BEEP permits simultaneous and independent exchanges within the context of a single application user-identity, supporting both textual and binary messages.
Developers
- Alexandre PAUZIES <apauzies@opencap.net> - Founder, Developer
- Alexandre SANHAJI <asanhaji@opencap.net> - Cap4j author, Developer
Schema Architecture
Dependencies
- JAVA JRE >= 1.4.2
- Ant >= 1.6.5
- Beepcore-java >= 0.9.08
- iCal4j Latest CVS Version
- ...
Contact
-
Mailing list opencap-devel on
.
Links
-
ietf-calendar - The vehicle for the IETF Calendaring and Scheduling (calsch) Working Group.
-
iCal4j - iCal4j is a Java library used to read and write iCalendar data streams
-
The Sunbird Project - The Sunbird Project is a redesign of the Mozilla Calendar component.
-
KOrganizer - KOrganizer is the calendar and scheduling program for the K Desktop Environment (KDE).
-
Evolution - Evolution provides integrated mail, addressbook and calendaring functionality to users of the GNOME desktop.
-
iCal - The commercial Calendar User Agent of Apple.