[Design] Item Sharing Proposal for Preview

[Mimi Yin]

http://wiki.osafoundation.org/bin/view/Journal/ 
PreviewItemSharingProposal

Sheila, Morgan, bkirsch and I have been making the rounds on the  
whole idea of item sharing for Preview. Below is a proposal for a  
limited approach to item sharing, something we think might be doable  
in the Preview timeframe. Further below is a more full-blown model  
for item-sharing.

For Preview, we are proposing the following:
+ Chandler users with Cosmo accounts can share items.
+ However, Chandler users will not be subscribing to items in  
Chandler. Instead Chandler users will continue to 'share' with each  
other via the email edit/update workflows described in the Stamping  
Spec.
+ Item sharing in Preview will be primarily focused on providing a  
way for non-Chandler desktop users to participate in collaboration  
workflows with Chandler users via Cosmo.

Limitations of the proposal: To simplify the UI for sharing items  
from Chandler desktop, we have imposed the following limitations on  
functionality:
+ Chandler items can only be shared by Chandler users with Cosmo  
accounts
+ Chandler items can only be shared read-write. _Reason: We do not  
want to build UI to allow users to choose between read-only and read- 
write sharing. We also do not want to get into reconciling Chandler- 
to-Chandler sharing via email (which is always read-write) with an  
item sharing model that allows read-only._
+ Chandler items can only be shared read-write with all recipients.  
_Reason: We do not want to build UI that allows users to assign  
different privileges to different recipients._

Design proposal:
Add option to make single items available on Cosmo in the detail  
view, either under the Addressing fields or under the Notes field,  
above the Appears in/Label field.

[x] Make this item available on Cosmo.

Users who do not have Cosmo accounts will be prompted to create one  
if they check this option.

What happens under the hood when the sharer hits Send:
+ Item is uploaded to the sharer's Cosmo account
+ A read-write URL is issued for the item
+ The read-write URL is added to the message body of the email
+ The sharers sees the read-write URL in the Notes field after  
Sending the item
+ Anyone else sharing the item via collection will also see the read- 
write URL in the Notes field

===

This is the short-term plan, in the long-term, We will need a clearer  
story for item-sharing, which involves:
+ Allow sharer to distinguish between read-only and read-write item  
sharing.
+ Differentiate between personal annotations and shared edit/updates  
to an item.

+ De-couple whether an item is read-only versus read-write from  
whether it is actually shared on Cosmo.

In this future world Chandler users will be able to subscribe to  
individual items that are shared, and...

If the item is read-only and shared,
+ Chandler recipients receive the item and are asked if they want to  
subscribe to the item or just view a static copy of it.
+ If they choose to subscribe, Chandler recipients can see edits as  
they happen.
+ Regardless of whether they choose to subscribe or view a static  
copy, Chandler recipients receive Updates to the item in both their  
email clients and in Chandler.

+ Non-Chandler recipients receive an email in their email client with  
a read-only URL to view the item in Cosmo
+ Non-Chandler recipients can see edits as they happen in Cosmo
+ Non-Chandler  recipients receive Updates to the item in their email  
clients and in Cosmo

+ Recipients can add personal annotations to the item in Chandler and  
Cosmo, but cannot send Updates to other sharees.

If the item is read-only and not-shared,
+ Chandler recipients receive a static copy of the item in their  
Chandlers (with the same UUID as the original item in the sender's  
repository).
+ Chandler recipients cannot see edits as they happen in Chandler
+ Chandler recipients receive Updates in their email clients and in  
Chandler

+ Non-Chandler recipients receive an email in their email clients and  
NO url
+ Non-Chandler recipients receive Updates in their email clients

+ Recipients can add personal annotations to the item in Chandler and  
Cosmo, but cannot send Updates to other sharees.

If the item is read-write and shared,
+ Chandler recipients receive the item and are asked if they want to  
subscribe to the item or just view a static copy of it.
+ If they choose to subscribe, Chandler recipients can see edits as  
they happen.
+ Regardless of whether they choose to subscribe or view a static  
copy, Chandler recipients receive Updates to the item in both their  
email clients and in Chandler.

+ Non-Chandler recipients receive an email in their email client with  
a read-only URL to view the item in Cosmo
+ Non-Chandler recipients can see edits as they happen in Cosmo
+ Non-Chandler  recipients receive Updates to the item in their email  
clients and in Cosmo

+ Recipients can add personal annotations to the item in Chandler and  
Cosmo
+ Recipients can edit and update the item in Chandler and Cosmo

If the item is read-write and not-shared,
+ Chandler recipients receive a static copy of the item in their  
Chandlers (with the same UUID as the original item in the sender's  
repository).
+ Chandler recipients cannot see edits as they happen in Chandler
+ Chandler recipients receive Updates in their email clients and in  
Chandler

+ Non-Chandler recipients receive an email in their email clients and  
NO url
+ Non-Chandler recipients receive Updates in their email clients

+ Recipients can add personal annotations to the item in Chandler and  
Cosmo
+ Chandler recipients can edit and send Updates to other sharees;
+ Non-Chandler recipients cannot

Mimi



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20061004/5cc8f960/attachment.html