Features of Bedework
- Java : Written completely in Java, Bedework is system independent. Currently it will compile and run in Java 1.6.
- Standards based and interoperable :Interoperability with other calendar systems and clients by way of standards compliance is a fundamental design goal of the Bedework system. The following standards are supported:
- iCalendar support (rfc2445)
- iTIP (rfc2446)
- CalDAV (rfc4791)CalDAV scheduling (draft)
- CardDAV v.4
- VVenue (draft)
- CalDAV server : a full CalDAV server is a core feature of Bedework. It can be used with any CalDAV capable client and has been shown to work with Mozilla Lightning, Apple's iCal, Evolution, and others.
- CardDAV server : Bedework 3.7 provides a CardDAV server providing personal and public contact stores for use in the personal client. A stand-alone javascript JavaScript address book application is included with the personal web client suitable for deployment in other web applications such as email web clients.
- Web clients :The Bedework web clients provide access to public events in guest mode and to public and personal events in authenticated mode. All web clients are easily skinned allowing a high degree of customization.
- Public calendar suites : Public events are displayed using "calendar suites" allowing multiple organizations to maintain their own public views of events with whatever degree of visibility is appropriate. A Bedework public calendaring installation may have one or many calendar suites. A calendar suite provides a customized view of events, custom theming, and control over how events are tagged by event administrators.
- Public calendar feeds and embeddable JavaScript widgets, supporting ical, json, and XML.
- Personal calendars : Bedework provides a web client for personal and group calendaring including scheduling. Using CalDAV desktop clients, users can see a fully synchronized view of their personal and subscribed events between their desktop client and the web client.
- Administrative client for public events : Public event entry and maintenance is carried out through the administrative web client. The system supports three roles: Super Users control global system settings including user and calendar maintenance and the setup of calendar suites. Calendar Suite Owners can modify the settings of their calendar suite, and Event Administrators can add and edit events for the administrative groups to which they belong.
- Public event community submission : Bedework provides a web client for submitting events to a public queue allowing members of your community who are not event administrators to suggest public events.
- Highly customizable look and feel and standards based : The web clients are themed using CSS and a theme settings file, or by deeper maniuplation of XSLT. Designers can theme Bedework for multiple clients and uses, without involving your programming staff. Bedework comes with skins for producing the web clients, data feeds, and displays suitable for handheld devices. Bedework provides a widget builder that makes it easy to embed dynamic event listings on static web sites.
...
- Tagging & Filtering : Events and folders can be tagged by any number of categories and event views, feeds, and feeds widgets can be filtered by these.
- Internationalization : Internationalization is carried out by creating a new skin. The skin selected is based upon skin name and locale allowing a significant degree of multilanguage support in the client. Work is currently taking place to strengthen support for internationalization independent of Bedework skins Bedework supports full internationalization, including multilingual content (though multilingual content creation is not yet exposed in the web UI).
- Data feeds: RSS, Javascript (e.g. json), iCalendar, and XML feeds are natively available, and custom feeds can be developed by writing an XSL skin. Feeds can be filtered by category or creator, and a feed and widget builder is available to help end users and developers design public feeds and embeddable event widgets.
...
- Timezone support : Full timezone support is implemented. There is a set of system defined timezones based upon externally available sets of timezone definitions. In addition users are able to store their own timezone definitions.
- Recurring events : Extensive recurring event support is available via CalDAV and the web clients.
...