August 2006 - Current status of UW Calendar and this website:

The UW Calendar project has evolved into Bedework. Please see the Bedework website for current code and updates. We will continue to keep this website up as an archive of the status of UW Calendar as of August 2006.

UW Calendar FAQ

This most up-to-date version of this document is available in the docs directory in the CVS repository. Reasonably up-to-date versions are also accessible on the University of Washington and the RPI CCT websites.

Frequently Asked Questions (FAQ)

  1. What is UW Calendar?

    UW Calendar is an open-source calendaring system designed for institutions of higher education. UW Calendar supports personal and public events and will support group events. It uses existing open standards, and supports web-based and other forms of access, including CalDAV and portal integration.

    The mission statement for UW Calendar reads, in part, "UW Calendar will be a total calendaring and events system for institutions of higher learning. UW Calendar will be open source and platform independent. It will use existing open standards where possible, especially the standards of the IETF Calendaring and Scheduling Working Group. It will support integration with other systems and middleware, particularly open systems such as uPortal and Shibboleth. It will be modular, so an institution can deploy only the components it needs, and extensible, so an institution can build any new component it needs."

    return to top

  2. Why the name UW Calendar?

    The open source UW Calendar was originally based on a University of Washington production system, which in turn was based on the WebCal web calendaring program. We don't particularly like the name UW Calendar, but attempts to find a new name that is both clever and not yet claimed by another web application, have so far proved surprisingly difficult.

    return to top

  3. What features are implemented?

    Skinnable public events web client, personal calendar web client, public events admin web client, CalDAV, SyncML, dump/restore utilities, RSS feeds, portlet support. Public/personal calendar integration, including subscribing to public calendars and adding individual public events to a personal calendar.

    return to top

  4. What forms of synchronization are supported?

    Individual events, not entire calendars, can be downloaded, but not synchronized in the current production release.

    We have a pre-production version (which needs to be repackaged for general distribution) of synchronization using SyncML. Currently, it is possible to synch with MS-Outlook with the iCalendar Synch Client. Support for Palm, PocketPCs or PDAs can be added. The implementation consists of a small synchronization framework to connect a calendar server with a synch server.

    return to top

  5. Who's using UW Calendar?

    1. Rensselaer Polytechnic Institute (
    2. University of Washington (
    3. Memorial University of Newfoundland (demo site) (
    4. Cornell University

    return to top

  6. What calendaring standards are supported?

    Our goal is to support RFC 2445. Currently, only a portion of that standard is implemented. We have implemented a subset of the CalDAV standard draft version 5.

    return to top

  7. How are recurring events supported?

    Recurring events are not presently supported. We anticipate supporting recurrence in the near future.

    return to top

  8. What technologies are used and/or required?

    Required: Java 1.4, an application server that understands the standard Java servlet API (2.4), a database with a JDBC driver

    Used: Struts, Synch4j 2.2 (for SyncML support), Jetspeed-2, Ical4j , Java / J2EE, XML, XSLT

    The quickstart version uses Tomcat 5.0.28, Ant 1.6.2, and HSQLDB, but none of these are required.

    return to top

  9. What development environments are supported?

    We currently use Ant. There has been some debate of the use of Maven.
    Memorial University has had some success using Eclipse and has produced a howto document.

    return to top

  10. How do I install the UW Calendar Quickstart version?

    The Quickstart distribution contains an entire runtime environment, including a database and application server, so that you need to download nothing except a Java runtime environment. The Quickstart is intended to be easily installed for demonstration purposes, and serve as a basis for your own customized version.

    Download Quickstart, which includes usage instructions in the README file. Familiarize yourself with Quickstart as distributed before you attempt to customize UW Calendar.

    return to top

  11. How do I install a customized production version of UW Calendar?

    There are authentication, database, presentation (look and feel) issues:

    1. Authentication - the calendar has been used with at least:
      1. Yale CAS filter
      2. PubCookie
      3. Servlet container-based (including LDAP)
    2. Presentation
      There is no presentation logic in the core calendar code. The interfaces are skinnable by changing or adding XSLT files (for each client).
    3. Databases
      Currently, production schemas are available for HSQLDB, MySQL, and Oracle. A Hibernate version is under development which will provide support for many additional databases.

    return to top

  12. Does UW Calendar support JSR 168 or otherwise integrate with portals?

    A proof of concept portlet version has been demonstrated using the JetSpeed2 portal-struts bridge. We are looking at getting the calendar running as a portlet in other portals. Options include writing a native JSR 168 front end, probably a modification of the current front end, or implementing the appropriate interface to get the portal-struts bridge running in the target portal.

    return to top

  13. Is resource scheduling supported?

    UW Calendar does not currently support resource scheduling.

    return to top

  14. Can I share my calendar with other people?

    UW Calendar supports personal calendars, but does not currently support sharing personal calendars

    return to top

  15. What administrative features are available?

    1. Distributed, fine grained administration
    2. Administrative groups
    3. Location and contacts management

    return to top

  16. What enhancements and new features are planned?

    1. A Hibernate backend to the system
    2. Timezones support
    3. Automated installation
    4. Alerts
    5. E-mail subscriptions
    6. Events in multiple categories
    7. Departmental calendars
    8. Recurring events
    9. Clustering
    10. Group calendaring

    return to top

  17. Where can I get more information on UW Calendar?

    1. The UW Calendar website:
    2. A recent presentation on UW Calendar:

    return to top

  18. How can I participate in the development of UW Calendar?

    1. Join the developers' mailing list.
    2. Execute the Contributor License Agreement.
    3. Contribute code and documentation, fix bugs, implement new features

    return to top