Menu

Projects:

  Higgins

  Identity Gang  

  Identity Schemas

SocialPhysics.org

SP Blog

Paul's Blog 

Context Instances

Shown below are a set of context instances living within the Context Provider implementation that creates and manages them. the information in red contexts is never shared with anyone (other than the user). Yellow context contain non-identifying information that the user allows to be shared with relying websites. The green contexts contain identifying information that if explicitly allowed by the user is shared with a relying website.

Middle tier contexts 

Below the root context are middle tier contexts. These represents reusable sets of information that may be used singly or in combination when the user visits a particular relying party website. One ore more yellow contexts can be marked as "default". The profile in the "Customer" (as in "customer shopping and surfing the web anonymously") context has no identifying information. The profile in the "Personal" context has identifying attributes such as "firstName" and "lastName".

Schemas 

Note: The spreadsheet referred to below is here.

1. Personal context schema: see spreadsheet's "Personal" tab
2. Customer context schema: see spreadsheet's "Customer" tab
3. Identity Mashup context schema: union of the spreadsheet's "Conference" tab and the spreadsheet's "Personal" tab
4. Best Buy context schema: same as spreadsheet's "Customer" tab plus: FirstName, LastName, Email, Password fields
   

Instantiation

Dynamic: Identity Mashup and Best Buy should be dynamically created when the user first lands on any one of the websites in each of these two respective site groups. Every "landing" page of each site in these two site groups must include the RSS-P object tag and associated parameters.

On startup: The Root, Personal, Customer, and Identity Mashup and Social Commerce contexts should be created when the users PIP account is created.

Property initialization

1. Personal context: properties have no value (i.e. they are displayed as blank fields)
2. Customer context: properties have no value
3. Identity Mashup context: For all properties that are the same as those in Personal context, the values are copied, the rest (all very Berkman conference specific) have no value
4. Best Buy context: all properties values copied from "Customer" context

Relying Website RSS-P coding (see also HBX RSS-P Protocol Support (v0.5.1+))

"Landing" pages in the Identity Mashup site group should all contain the following (where "receive-bestbuy-rss.jsp" is replaced appropriately):

<form name="rss-p-test" method="post" action="receive-bestbuy-rss.jsp" id="rss-p-id">
  <object type="application/rss-p" name="RSS-P">
    <param name="schema" value="mashup.owl"/>
  </object>
</form> 

"Landing" pages in the Best Buy site group should all contain the following (where "receive-bestbuy-rss.jsp" is replaced appropriately):

<form name="rss-p-test" method="post" action="receive-bestbuy-rss.jsp" id="rss-p-id">
  <object type="application/rss-p" name="RSS-P">
    <param name="schema" value="bestbuy.owl"/>
  </object>
</form>

Edit History

v26: changes in green: added 4 missing fields to Best Buy context 

v25: made "Identity Mashup" context pre-created (not dynamic) 

v24: removed social commerce card 

v23: removed the "conference" middle tier context, added "Relying WEbsite RSS-P coding" section. rewrote latter half of the text to be clearer.