- Revision
- 870
- Author
- mimi
- Date
- 2006-07-20 17:16:54 -0700 (Thu, 20 Jul 2006)
Log Message
Rationalizing Spec with updates to StampingStoryboards: http://wiki.osafoundation.org/bin/view/Journal/StampingStoryboards#StampingWorkflow
Modified Paths
Diff
Modified: trunk/docs/specs/rel0_7/Stamping-0.7.html (869 => 870)
--- trunk/docs/specs/rel0_7/Stamping-0.7.html 2006-07-20 23:02:05 UTC (rev 869) +++ trunk/docs/specs/rel0_7/Stamping-0.7.html 2006-07-21 00:16:54 UTC (rev 870) @@ -342,8 +342,9 @@ </li> <li>I suggest an Agenda in the body by adding some notes.<br> </li> - <li>I stamp it as Communication to send it to Carol and Amy for -review. Type in Carol and Amy’s email addresses in the To: field.</li> + <li>I stamp it as Communication to send it to Carol, Amy, Junior +and Lars for +review. I type in their email addresses in the To: field.</li> <li>I select an email account to send the invitation with. (OPTIONAL)<br> </li> @@ -363,7 +364,8 @@ </li> <li>The <b>Who</b> column displays the list of the people to whom the -invitation was sent (TO Amy and Carol). In this case, it’s a simple +invitation was sent (TO Amy, Carol, Junior and Lars). In this case, +it’s a simple invite where the person sending the email is the same as the meeting organizer in the From: field.</li> @@ -379,7 +381,7 @@ <li>Carol received my invitation in her email client as an email from me to her and Amy, with the event attached as an .ics file. <ul> - <li>Carol may or may add the event item to her calendar, + <li>Carol may or may not add the event item to her calendar, depending on whether she uses a digital calendar.</li> </ul> </li> @@ -450,47 +452,30 @@ includes date/time information about when the Update was sent.</li> </ul> </li> - <li>Amy, another Chandler user who is sharing the event with me via a -shared collection makes some changes of her own and updates the + <li>Junior, another Chandler user who is sharing the event with me +via a +shared collection makes some changes of his own and updates the invitation. <ul> - <li>Note: Amy can edit this event Invitation <b>even if she has -read-only privileges</b> via the shared collection, because she is an -explicit recipient on the Item.<br> - </li> - <li>When Amy first saw the shared event/invitation, the <b>Send</b> -button was disabled (because the invitation had already been sent by -me) and the <b>Communication</b> stamp displayed Inbound, Unread -status. If Amy had not been on the recipient list for the invitation, -as in, listed in the To:, CC:, or BCC: fields, she would have seen the -invitation as an Outbound invitation.<br> - </li> - <li>As I made edits to the invitation, Amy saw those edits, -assuming both of us had synced. Amy also received my <b>Update</b> -to the invitation via email in whatever email client she’s using. My <b>Update</b> -also re-centered the invitation item in the NOW section of her -Dashboard. </li> - <li>Once Amy edited the invitation, the <b>Update</b> button -enabled for her, the <b>Communication</b> stamp changed to display <b>Draft-Update</b> -status, and the text under the To: field that formerly said, Updated -by: me, changed to <b>Edited by: Amy</b>.<br> - </li> </ul> </li> - <li>Amy hits <b>Update</b>.<br> + <li>Junior hits <b>Update</b>.<br> <ul> <li>The <b>Communication</b> stamp shows that the item is a <b>Sent-Update</b>. -The From field shows that the item is still From: me, To: Amy and Carol.<br> +The From field shows that the item is still From: me, To: Amy, Carol, +Junior, and Lars.<br> </li> </ul> </li> - <li>Carol and I receive Amy’s <b>Update</b> in our respective email -clients. Amy’s Update also re-centers the invitation Item in the NOW + <li>Carol, Junior, Lars and I receive Junior’s <b>Update</b> in our +respective email +clients. Junior’s Update also re-centers the invitation Item in the NOW section of my Dashboard. The <b>Communication</b> stamp again shows that the invitation item is an <b>Unread-Inbound-Update</b>. The <b>Who</b> -column shows that the invitation has been UP Amy. <br> +column shows that the invitation has been UP Junior. <br> <ul> - <li>I go to Amy’s Update to inspect the Message headers, where I + <li>I go to Junior’s Update to inspect the Message headers, where +I am listed as a recipient of the update email. However, on the invitation item, I am still in the From: field. <br> </li> @@ -501,6 +486,26 @@ Instead, she syncs her changes so that I can see them via the shared collection. <ul> + <li>Note: Amy can edit this event Invitation <b>even if she has +read-only privileges</b> via the shared collection, because she is an +explicit recipient on the Item.<br> + </li> + <li>When Amy first saw the shared event/invitation, the <b>Send</b> +button was disabled (because the invitation had already been sent by +me) and the <b>Communication</b> stamp displayed Inbound, Unread +status. If Amy had not been on the recipient list for the invitation, +as in, listed in the To:, CC:, or BCC: fields, she would have seen the +invitation as an Outbound invitation.<br> + </li> + <li>As I made edits to the invitation, Amy saw those edits, +assuming both of us had synced. Amy also received my <b>Update</b> +to the invitation via email in whatever email client she’s using. My <b>Update</b> +also re-centered the invitation item in the NOW section of her +Dashboard. </li> + <li>Once Amy edited the invitation, the <b>Update</b> button +enabled for her, the <b>Communication</b> stamp changed to display <b>Draft-Update</b> +status, and the text under the To: field that formerly said, Updated +by: me, changed to <b>Edited by: Amy</b>.</li> <li>If Amy had not synced to get my changes before she made her edits, when she synced her edits, the standard merging and conflict rules would apply.</li>
_______________________________________________ Commits mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/commits
