Westwood Calendar Requirements

This page is meant to collect requirements for Westwood, feature by feature. In the "recommended release" column is our current thinking about what features might be in Canoga or Westwood. Note: we're probably still being too optimistic about what can make it into Canoga, we haven't done the hard work of bottom up scheduling yet.

OSAF is interested in feedback from CSG folks about what requirements are essential for deployment, what requirements are exciting, interesting or motivating, and what requirements are less important for a first Westwood release.

Release code names for OSAF:

• Canoga => the first release of Chandler (1.0)
• Westwood => a release of Chandler for higher education
• Pasadena => a future release of Chandler (2.0)

Feature priorites for CSG:

• S => Showstopper, couldn't deploy without this feature
• H => High, important but could live without it in the first release
• M => Medium
• L => Low, not especially interesting to us

Individual Calendaring Requirements

Group Calendaring Requirements

Interoperability Requirements

Open Issues

• Delegation/designate: the set of features where an administrator can act-on-behalf-of someone else. IETF specs and Corporate Time call this "designate", Outlook calls this "delegate".
  • Description of how this works in Corporate Time
• Interoperability: Corporate Time, CAP, etc. See notes on scenarios in preparation for the conference call on March 28.
• Web client: Can be skipped if Chandler is a client to an enterprise system, because the system will have it. Otherwise its pretty important, for "nomadic" users. Universities are implementing web "portals" and of course you'll want your calendar data in a portal. Folks might be doing some work to make this happen if we provide the right architecture and APIs.
• PDA interoperability: Synchronization (e.g. Palm conduit) is ok for first release. People will be interested in first class Palm/Pocket PC clients in the long term.

We discussed these and other issues in the conference call on March 28. Notes from the meeting.

Related Requirements, not addressed here

Calendaring poses some special requirements

• Security, authentication, authorization, identity
  • Calendar access rights for shared calendar data, need to share free-busy time at least
  • Delegation features
• Contacts
  • Discovery of other calendar users for calendar scheduling
  • LDAP interoperability
    • Discovery of other calendar users from "enterprise directory"
    • Storage of contact data on enterprise directory
  • Address book migration

-- KatieCappsParlante - 16 Apr 2003