Possible Scenarios

Scenario: Westwood provides a workgroup calendaring solution

We know we would want:

• Chandler users can do group calendaring with their workgroup
  • Chandler users store their individual data in a local repository.
  • Chandler users can look at other users' repositories if they have permission.
  • Chandler users can replicate their data to another repository.
    • To a relay server to make the calendar data always available to the group
    • To another machine of the user, essentially for synchronization.
  • Chandler users can schedule meetings with other Chandler users.
  • Chandler calendar data bears a strong resemblance to iCalendar data, iCalendar data can be imported/exported without loss of calendar information.

We have questions about:

• Chandler may be a client to another CAP server.
  • Possible CAP servers include a UW CAP server, or an industry solution like Corporate Time or Sun One.
  • Chandler is not the primary calendar store, the CAP server is the calendar store.
  • Chandler's relationship to CAP in this case is similar to its relationship to IMAP. Lou's IMAP inter-operability document
• Chandler may interoperate with Corporate Time (and other calendars) using iMIP/iTIP.
  • Chandler is the primary calendar store for Chandler users.
  • Chandler users can invite Corporate Time users to meetings, and vice versa.
  • Chandler users and Corporate Time users cannot see each other's free-busy time, or generally share calendars.
• Chandler may interoperate with Corporate Time (and other calendars) using CAP/iTIP.
  • Chandler is the primary calendar store for Chandler users.
  • Chandler users can invite Corporate Time users to meetings, and vice versa.
  • Chandler users and Corporate Time users can publish calendar information to each other, including free-busy time.
  • Chandler needs to act as both CAP client and CAP server, to send and receive CAP/iTIP scheduling items.
• Chandler may interoperate with Corporate Time, using a Corporate Time APIs.
• Chandler may act as a Corporate Time client, using Corporate Time APIs.

Scenario: Westwood provides an "experimental" central server solution

We know we would want:

• The Chandler server can act as a scalable, available, calendar store for Chandler clients.

We're not sure about:

• The Chandler server may be a CAP server.
  • The Chandler server is the calendar store for Chandler users.
  • Other CAP clients could use Chandler server as a calendar store.
  • Other CAP client/server deployments could interoperate with Chandler via CAP/iTIP.

Questions for CSG folks

• Would CSG folks be interested in deploying a group calendar solution for small groups, departments?
  • Is it interesting for groups of around 100 users?
  • Is it interesting for groups of around 2000 users?
• How prevalent is Corporate Time? We've heard from a few folks that interoperability with Corporate Time is a must have feature. Can we address the interoperability issue with CAP? Would iMIP/iTIP support be enough, or will folks not be happy with the loss of free-busy time visibility?
• How interested are CSG folks in Chandler being a CAP client?
• Would CSG folks be interested in deploying a "test" server (calendaring and other pim data) even if it was not yet scalable/highly stable?
  • How interested are CSG folks in Chandler as a CAP server, in addition to being a general pim data store?
• Feature by feature Higher Ed Calendar Requirements, it would be good to know what features are required for deployment, and what features are particularly helpful or motivating.
• We could use your help brainstorming use cases and requirements for the "delegated authority" features.
• Is there anything else we're missing?

Open Questions for OSAF

• What size workgroup does Chandler need to support for group calendaring? 2,000 users?
• Should the Chandler client be a CAP client for the Westwood release?
• Should OSAF release a Chandler server for Westwood? This server would likely be a "test" or "experimental" server for the Westwood release, with the plan of evolving to scalability and stability.
  • Should the Chandler server be a CAP server?

Architecture

• Strawman Calendar Architecture Diagrams

-- KatieCappsParlante - 01 Apr 2003