Difference between revisions of "Data Sharing With Alice And Bob"

Latest revision as of 21:09, 15 May 2011

Alice opens her sharable context in her PDS, call it context-A1.
Alice clicks the "share via email" button, and enter's Bob's email address.
The PDS system does the following:
- Generates a GUID for this invitation, call it GUID-1
- Makes the following entries in the sharing_inbox context:
  - GUID-1, invited_to, context-A1
  - GUID-1, invited_timestamp, {timestamp}
  - GUID-1, invited_method, email
  - GUID-1, identified_by, bob@bob.com
- Sends an email message to Bob that contains an invitation message, and a link back to the PDS that embeds these pieces of data:
  - Alice's user ID
  - The URI to the context that Alice shared
  - The URI to the template for the context that Alice shared
  - The invitation GUID-1

Bob Clicks the Link

Bob retrieves the email message
Bob clicks the link
The link opens the PDS to a page that offers Login or Create Account, and saves the GUID-1 in a session variable.
Bob creates an account.
Bob sees some UI that asks if he want to accept sharing of Alice's context, and in turn, share his equivalent context.
The PDS creates a context for Bob using the template URI from the link, call it Context-B1.
The PDS grants read-access to Alice to Context-B1 (since it knows her root ID).
Creates a pointer form Context-B1 to Context-A1.
Bob's PDS creates a GUID-2 for the reciprocal invitation to Alice, and creates the following statements in Alice's sharing_inbox context:
- GUID-1, accepted_by, bob
- GUID-1, accepted_timestamp, {timestamp}
- GUID-2, invited_to, Context-B1
- GUID-2, invited_timestamp, {timestamp}
- GUID-2, invited_method, internal
- GUID-2, identified_by, alice
Bob's PDS creates the following statements in Bob's sharing_inbox context:
- GUID-2, invited_to, Context-B1
- GUID-2, invited_timestamp, {timestamp}
- GUID-2, invited_method, internal
- GUID-2, identified_by, alice

Alice finalizes the sharing

Alice's PDS reads Alice's sharing_inbox and does the following:

Creates an ACL entry in Context-A1 granting read-access to {bob's user ID}
Creates a pointer from Context-A1 to Context-B1
Write the following entries into Bob's sharing_inbox context:
- GUID-2, accepted_by, alice
- GUID-2, accepted_timestamp, {timestamp}

@@ Line 1: / Line 1: @@
 {{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
+=== Introduction ===
 This document describes a use case wherein Alice offers to enter into a data sharing relationship with Bob.
-A cursory knowledge of the concept of a [[Personal Data Store 2.0]] and of the [[Persona Data Model 2.0]] (PDM 2.0) is assumed. Although not mentioned explicitly the graph of objects being shared are described in the PDM 2.0 model.
+A cursory knowledge of the concept of a [[Attribute Data Service 2.0]] and of the [[Persona Data Model 2.0]] (PDM 2.0) is assumed. Although not mentioned explicitly the graph of objects being shared are described in the PDM 2.0 model.
-This use case assumes that there is an active client providing a little bit of UI and the ability to kick off sending an email to Bob. But the reality is that 95% of the implementation of this use case is done by the [[PDS Client 2.0]], so a webapp (built on the PDS client library/service) could just as easily have provided the UI instead of an active client with its so-called dashboard UI. Best of all if both kinds of clients existed they would of course interoperate seamlessly.
+=== Overview  ===
-=== Introduction  ===
+Alice wishes to grant access to one of her contexts to her friend Bob. In accepting this invite, Bob will grant access to Alice to an equivalent context owned by Bob.
-Alice wishes to delegate to her friend Bob authority over the record in Alice's Google Contacts (think gmail) account that is about him, to him. In inviting Bob to do this she simultaneously offers him read-only access to the record about herself.
-The social protocol is that Alice sends an offer to "stay in sync" to Bob. The offer contains two gifts: (i) a link to the record about Alice so Bob can always have her latest information and (ii) a link to Bob's record so that anytime Bob's information changes Alice gains a copy.
-== Approach #1 ==
-Volunteered r-card approach.
 === Initial Condition  ===
-* Alice has a Higgins-based active client
+Alice has:
-* Alice has a gmail account wherein at least her friend Bob is listed.
+* An account on a Higgins-based ADS
-* Bob has no active client installed
+* A Higgins-based PDS
-* Bob has no gmail account
+* A share-able context, call it context-A1
+* A sharing_inbox contex, which is read/writeable by Alice, and appendable by all.
-=== Open Google Contacts  ===
+* Bob's email address
-As shown below, Alice opens a Google Contacts context, providing her gmail username/password credentials. If Alice does not have an entry for herself in Google, then an empty one is created. If Alice does have an entry for herself this is somehow found,<ref>I don't know enough about Google Contacts to know if this can be done automatically or if the active client's UI (the so-called dashboard) must display a list of Alice's contacts and ask her to select the one that is her. We could allow her to specify multiple entries and tag them as personas too in the future.</ref>
-[[Image:R-card data sharing 1.png|center]]
-A note about the images in this document. The round cornered boxes are Higgins Contexts. The dotted lines are <code>foaf:knows&gt;</code> attributes. The solid lines are <code>h:correlation</code> links--which roughly means "this is another facet of me."
-=== Merge into Meta  ===
-Since no <code>h:correlation</code> link exists between Alice's root entity in the meta context and the root node in the Google Contacts (GC) context, then this correlation needs to established.
-This involves creating the h:correlation link as well as walking the entire graph from the root in the GC context down and merging it into either a new or an existing persona branch under the root (aka MetaMe) node in Alice's meta context.
-The result of this generalization process is shown in figure 2 below. As you can see not only is the node representing Alice merged into the meta context but all of the other contacts that Alice has (including Bob) are merged in too. The dotted lines are foaf:knows links.
-For clarity all of Alice's contacts (other than herself and Bob) have been omitted for simplicity in Figure 2 below.
-[[Image:R-card data sharing 2.png|center]]
-=== Share Alice's (Alice and Bob) with Bob  ===
-In the UI of the active client Alice selects the Bob persona node in her meta context. One of the operations she can perform on it is to share it with someone. She chooses to share this Persona node with Bob. And by Bob we mean here Bob's email address (which is an attribute of the Bob node). For social protocol reasons Alice will simultaneously offer to share her own contact info with Bob. (See the "Stay in Sync?" email below).
-After she clicks "Share" on the Bob node in the Meta context the active client notices that the Bob Persona node is contained within its own context, and since the minimum unit for sharing (and access control) is an entire context, it must create a new context and move the Bob node into it.
-Moving the Bob node involves rewriting the link from Alice to Bob so that it points to the moved Bob. The moved Bob node will now have a new entityid because it whereas before it had a relative UDI within the meta context, it now it must be addressed from the meta context using an absolute UDI.
-The new context, named ''r-card2'', is an instance of P-Card, a sub-class of the Context class. As with all contexts the r-card2 context ends up (after synchronization) physically stored on both the PDS Client and the PDS. This same process is repeated for the Alice node, and results in the new context called r-card1. The result is shown in below:
-[[Image:Alice-bob-f3.png|center]]
-With the nodes and links in place the [[PDS Client 2.0]] needs to add Bob to the access control list for the new contexts. Since at this point we only know Bob as his email address, so that must (for now) be his identifier. The access control list is maintained by the PDS, so Alice's PDS Client must communicate with the PDS to add Bob to the "allow access" list of r-card1 and r-card2. We add "Bob has full read/write access to r-card2" to the r-card2 ACL. And we add "Bob has read-only access to r-card1" to the r-card1 ACL.
-The last step is for the active client to arrange that an email be sent to Bob. The email contains what we call an ''i-link''.
-The i-link (URI) encodes (a) a link to an active client download site (b) the UDI of the Bob entity on r-card2 (c) the UDI of the Alice entity on r-card1
-The text of the email says something like:
-<blockquote>
-'''Subject: Stay in sync?'''
-</blockquote>
-<blockquote>I'd like to stay in sync with you. By clicking on the link below please accept my offer to always having my latest contact/profile information. You have the option of <u>Click here to accept my offer</u>. Note: If you don't already have a Higgins active client, clicking here will bring you to a download page where you can get one. I've started using Higgins to stay in sync with co-workers, friends and family. With Higgins everything stays up-to-date because everyone who uses Higgins '''''only has to update their own contact info'''''--and all the changes are automatically reflected it everyone else's address book.</blockquote>
-=== Bob clicks on the i-link  ===
-Since Bob's browser doesn't have the Higgins BX installed when he clicks on the i-link it just takes him to the Higgins download site. Bob downloads and installs an active client. Now Bob has a meta context as shown in Figure 4 below. Note that Bob is not expected to have a gmail account.
-[[Image:Alice-bob-f4.png|center]]
-=== Bob processes the i-link ===
-Higgins active client extracts the UDI of Alice's Bob entity on the r-card she created.
-Since the i-link ''tells'' Bob about a particular Alice identity, Bob's PDS Client can add a <code>foaf:knows</code> link Bob's MetaMe entity and his friend Alice. Secondly, since the i-link also tells Bob about Alice's representation of Bob (r-card2), Bob's PDS Client can add a <code>h:correlation</code> link from Bob's MetaMe entity to Alice's representation of Bob in Alice's gmail context. The result is shown in figure 5 below:
-[[Image:Alice-bob-f5v2.png|center]]
-=== Bob processes the i-link (alternative implementation) ===
-Shown below is an alternative implementation.
-[[Image:2alice-bob-f2.png|center]]
-== Scenario #2 ==
-=== Initial Condition  ===
-* Alice has a Higgins-based active client
+Bob has:
-* Alice has a gmail account wherein at least her friend Bob is listed.
-* Bob has no active client installed
-* Bob '''does have''' a gmail account
-===Initial State===
+* No ADS account
+* No PDS
+* An email address
-[[Image:2alice-bob-f1.png|center]]
+=== Alice Initiates Sharing  ===
-Final state:
+* Alice opens her sharable context in her PDS, call it context-A1.
+* Alice clicks the "share via email" button, and enter's Bob's email address.
+* The PDS system does the following:
+** Generates a GUID for this invitation, call it GUID-1
+** Makes the following entries in the sharing_inbox context:
+*** GUID-1, invited_to, context-A1
+*** GUID-1, invited_timestamp, {timestamp}
+*** GUID-1, invited_method, email
+*** GUID-1, identified_by, bob@bob.com
+** Sends an email  message to Bob that contains an invitation message, and a link back to the PDS that embeds these pieces of data:
+*** Alice's user ID
+*** The URI to the context that Alice shared
+*** The URI to the template for the context that Alice shared
+*** The invitation GUID-1
+=== Bob Clicks the Link ===
+* Bob retrieves the email message
+* Bob clicks the link
+* The link opens the PDS to a page that offers Login or Create Account, and saves the GUID-1 in a session variable.
+* Bob creates an account.
+* Bob sees some UI that asks if he want to accept sharing of Alice's context, and in turn, share his equivalent context.
+* The PDS creates a context for Bob using the template URI from the link, call it Context-B1.
+* The PDS grants read-access to Alice to Context-B1 (since it knows her root ID).
+* Creates a pointer form Context-B1 to Context-A1.
+* Bob's PDS creates a GUID-2 for the reciprocal invitation to Alice, and creates the following statements in Alice's sharing_inbox context:
+** GUID-1, accepted_by, bob
+** GUID-1, accepted_timestamp, {timestamp}
+** GUID-2, invited_to, Context-B1
+** GUID-2, invited_timestamp, {timestamp}
+** GUID-2, invited_method, internal
+** GUID-2, identified_by, alice
+* Bob's PDS creates the following statements in Bob's sharing_inbox context:
+** GUID-2, invited_to, Context-B1
+** GUID-2, invited_timestamp, {timestamp}
+** GUID-2, invited_method, internal
+** GUID-2, identified_by, alice
-[[Image:2alice-bob-f2.png|center]]
-=== References  ===
+=== Alice finalizes the sharing ===
+Alice's PDS reads Alice's sharing_inbox and does the following:
+* Creates an ACL entry in Context-A1 granting read-access to {bob's user ID}
+* Creates a pointer from Context-A1 to Context-B1
+* Write the following entries into Bob's sharing_inbox context:
+** GUID-2, accepted_by, alice
+** GUID-2, accepted_timestamp, {timestamp}
-<references />
+[[Category:Higgins 2]]

Breadcrumbs

Difference between revisions of "Data Sharing With Alice And Bob"

Latest revision as of 21:09, 15 May 2011

Contents

Introduction

Overview

Initial Condition

Alice Initiates Sharing

Bob Clicks the Link

Alice finalizes the sharing