Skip to main content
Jump to: navigation, search

Data Sharing With Alice And Bob

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

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.

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.

Introduction

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.

Initial Condition

Alice has:

  • A Higgins-based active client
  • A PDS that supports "sharable" contexts (e.g. exposing them via XDI)
  • A gmail account wherein at least her friend Bob is listed.
  • A PDS provisioned with a Google Contacts Context Provider (CP). This CP syncs with the Google Contacts API and exposes a Higgins PDM 2.0 compatible context.

Bob has:

  • No active client
  • No PDS
  • No gmail account

Alice Opens Her Google Contacts

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.[1]

Alice-bob-1a.png

A note about the images in this document. The round cornered boxes are Higgins Contexts. The dotted lines are foaf:knows attributes. The solid lines are h:correlation links--which roughly means "this is another facet of me."

Merge into Meta

Since no h:correlation 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 itself as well as walking the graph from the root in the Google Contacts context 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 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.

Alice-bob-1b.png

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 this node 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 needs to make sure that any and all nodes to be shared are contained within their own separate shareable contexts--that is that the context is an instance of I-Card (and preferably with so-called relationship qualities).

The active client notices that Bob node is not 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 I-Card context called r-card1. The result is shown in below:

Alice-bob-1c.png

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:

Subject: Stay in sync?
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 Click here to accept my offer. 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.

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.

Alice-bob-1d.png

Bob processes the i-link

Bob extracts the UDI of Alice's Bob entity on r-card2 as well as the UDI of Alice's Alice entity on r-card1.

Approach #1

Bob a foaf:knows link to Bob's MetaMe node to the r-card1's Alice node.  Bob adds a h:correlation link from Bob's MetaMe entity to Alice's Bob entity in Alice's r-card2 context. The result is shown below:

Alice-bob-1e-2.0.1.05.png

Approach #2

An alternative (and more satisfyingly symmetric) approach would be that Alice not only delegates control over her representation of Bob to Bob but also thedata management of this representation.

The result would be:

Alice-bob-2e-1.0.105.png

Note: If Bob also had a gmail (or interestingly any other kind of context!) account of his own that contained nodes for himself and/or Alice he could later open this context and push a "Correlate" button on the PDS Client to compare graphs and infer/suggest new h:correlation links.
Cite error: <ref> tags exist, but no <references/> tag was found

Back to the top