r2 - 07 Jul 2005 - 17:44:06 - LisaDusseaultYou are here: OSAF >  Projects Web  >  ProductManagement > CanogaSharingDesign20040419 > DotFourSharingUseCases

0.4 Sharing Use Case Candidates

Goals:

  • Enumerate the list of possible sharing use cases we can reasonably look to implement in 0.4. Intent is start with too much and whittle down to a do-able set.
  • Purpose of these use cases is to provide scoping and prioritization directions for both design and engineering

The Use Cases:

Calendar View Sharing:

At the minimum, we should provide sharing capabilities roughly at the 0.1 release functionality
  • Mitch shares his calendar in a read-only fashion
  • Calendar view is either public or private, there are no individual permissions
  • Users are invited to view Mitch's calendar through email if available or in an out-of-band fashion through the view URL [OI]
  • Support for both remote browsing(?) and view replication
  • When Mitch adds, changes or deletes a calendar item, the change is reflected to all sharees
  • Sharer and sharee recovers gracefully when connection is severed unexpectedly

Additionally, we can add the following features (in suggested order) :

  • Sharees can modify (write privilegse) remote calendar
  • Access control lists and individual permission levels (e.g. Esther has read/write, while Freada has read permission)
  • Sharee gets to move remote calendar event to local calendar layer (item replication)
  • Authentication of each user (either as per CanogaSharingInitiation or Dartmouth PKI proposal)
  • Notify users of available share and subsequent changes to remote share
  • Support for sharing to groups as well as individuals
  • Support for ItemConversations?

Explicitly, NO:

  • Republishing/chain-sharing
  • Firewall sharing
  • non-Chandler users or iTip/iMip support
  • Calendar invitation workflow nor free/busy information
  • Annotations ( & sharing of annotations)

Content Item Sharing

Content item sharing probably requires basic Email or IM functionality. In 0.4, should we try to kludge a workflow without eMail? Or should we provide really skeletal eMail just to support sharing? other ideas?

Use Case Questions

  • What is acceptable performance?
    • When receiving the first remote calendar view?
    • When receiving an update?
  • What is the limit on the number of users for 0.4 to behave "reasonably"?

-- ChaoLam - 18 Feb 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.