r5 - 05 Feb 2007 - 12:01:21 - MimiYinYou are here: OSAF >  Journal Web  >  MimiYin > PreviewSharing

Usage Scenarios

  • Angie the Apex and Eli the Executive Assistant sharing Eli's task list
  • Helen the Hub sharing a team task list
  • Bart the Busy Body / Coordinator sharing an office calendar / collection of resources

  • We're not supporting 'Sharing with Yourself', aka Repository Sync, Back-up, Remote access

Workflows

  • Publish
    • Option to password protect Cosmo share
    • Publish to multiple Cosmo accounts
    • Publish to multiple Cosmo servers
    • Publish to multiple CalDAV and WebDAV servers
  • Subscribe
    • Subscribe from multiple Cosmo accounts
    • Subscribe from multiple Cosmo servers
    • Subscribe from other CalDAV and WebDAV servers
  • Restore published shares and subscriptions

  • We are optimizing sharing scenarios to work for:
    • Publishing to 1 Cosmo account
    • Subscribing from multiple Cosmo accounts
    • Subscribing to .Mac calendars

  • Publish and Subscribe to free-busy calendars
  • Open Issue Make events query-able for free-busy by other servers?

  • Reconciling shared secondary items with themselves if they happen to be re-shared as primary items later on, e.g.
    • Lars shares an event with me that points to a secondary contact item for Joelle
    • Later on, Lars shares Joelle's contact item with me as a primary item
    • In the interest of security, we are NOT providing users with affordances to edit and/or manipulate (e.g. Drag into a collection to add as a primary item) secondary items.
    • For more detailed discussion of security issues, see: SharingDiscussion20060803

  • Reconciling collection-membership if an item belongs to two shared collections
    • Lars shares the Airplanes collection with me, which contains the Note, Boeing 747
    • Later on, Lars shares the Jets collection with me, which also contains the Note, Boeing 747
    • I already have a collection named Jets, so I rename Lar's Jets collection: Lar's Jets
    • THe Note item, Boeing 747 points to Lar's Jets

  • Magic URL to view and subscribe to shares
    • Sharer publishes a share and receives 2 URL tickets to hand out (Read-only and Read-Write)
    • Sharee receives URL and clicks on URL to access share via Cosmo UI
    • Sharee has option to:
      • Interact with share anonymously
      • Subscribe to share with a Cosmo UI account by logging in
      • Subscribe to share with Chandler desktop
      • Subscribe to share with Apple iCal
      • Subscribe to share with CalDAV client: Evolution? Sunbird? Lightening?
      • Subscribe to share as a RSS feed
      • Subscribe to share as an atom feed
      • Download calendar as an .ics file

  • Sharing individual items
    • Sharer stamps an item to Address it and Sends it
    • Sharees receive the item in their email clients and can click on a URL to view and edit the item in the Cosmo UI
    • Sharees can 'Edit and Update' the item via:
      • mailto link workflow described in the 0.3 Scooby spec
      • or some in-band method, still to be worked out (depending on how much time we have) * Sharee has option to:
      • Interact with the shared item anonymously
      • Open Issue Subscribe to the shared item with a Cosmo UI account by logging in
      • Instructions on how to pull the item into Chandler desktop
      • Open Issue Subscribe to the shared item with Apple iCal
      • Open Issue Subscribe to share with CalDAV client: Evolution? Sunbird? Lightening?
      • Subscribe to the shared item as a RSS feed
      • Subscribe to the shared item as an atom feed
      • Download item as an .ics file

  • We're not supporting rationalizing changes to a single item in multiple collections on the server and web UI. Changes to a single item in multiple collections will be rationalized on the desktop client at sync-time.

In the sharing cloud

  • Stamps
  • Addressing fields
  • Communications status
  • Title
  • Location
  • Date/time fields
  • Notes

  • Who edited/updated the item
  • When they edited/updated the item

  • Secondary items (Contacts, Locations)

  • @time-ness
  • Anytime-ness
  • Events with no date/time
  • Gobbledy-gook stored in Addressing fields and Date/time fields

Out of the sharing cloud

  • Read/Unread/Needs reply status
  • Labels
  • Order of an item when collection is sorted by Triage status

Optional sharing cloud

  • Triage status
  • Alarms
  • Event status, including
    • FYI event status

Schema changes and Translation of Chandler Schema to iCalendar

  • Set Event status to FYI for events that are imported / subscribed to as Not-Mine
  • Add Cancelled Event status
  • Translate From:, To:, CC:, BCC:, Sent by: into corresponding iCalendar Organizer, Participant and Proxy attributes

Open Issues

  • Sharing 3rd party parcels?


Security issues

  • Continue support for tickets
  • Option to password protect a collection
  • Disallow users to edit/manipulate items received as 2ndary items

  • Open Issue Time out to safeguard against dictionary attacks on tickets and passwords


Implementation goals

  • Improve performance
    • Implement new Sharing format to get rid of dual format - ICS and XML
    • Fix bugs related to dual-format (ICS and XML)
    • Make it so Cosmo can take the XML and spit out the right format
  • External Information Model
    • Open Issue Implement in Cosmo as well? Used to turn Cosmo into a data hub as well?

  • NOT implementing framework for diffs to support incremetal updates

-- MimiYin - 21 Aug 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < 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.