Skip to main content
Jump to: navigation, search

Difference between revisions of "PDS Use Cases"

(Connect to a site)
(Design)
Line 19: Line 19:
 
Data model:
 
Data model:
 
* [[Template vocabulary]] shows an example template--this example is the Google Ads template
 
* [[Template vocabulary]] shows an example template--this example is the Google Ads template
* Design issues
+
Issues:
** Q: How does the PDS code know by inspection of the card gallery whether the PDS user is the definer/creator of the template? In other words how does it know which role (definer vs. participant) it should play?
+
* Q: How does the PDS code know by inspection of the card gallery whether the PDS user is the definer/creator of the template? In other words how does it know which role (definer vs. participant) it should play?
*** A: If the card is in the gallery at all, we will assume it was defined by an external (non-user) definer. We'll put user-defined templates somewhere else.
+
** A: If the card is in the gallery at all, we will assume it was defined by an external (non-user) definer. We'll put user-defined templates somewhere else.
** Q: how is the connectionType for the Proxy determined from the template?
+
* Q: how is the connectionType for the Proxy determined from the template?
Code:
+
** A: See [[Template vocabulary#UML_Overview]]--the tempalte has a proxy:connectiontype attribute whose value should be copied to the Proxy.
 +
 
 +
Logic:
 +
# Flow stars in the cline (aka portal). User opens the card gallery. User selects card to add.
 +
# Client instantiates the participant context based on the Participant prototype in the template
 +
# Client instantiates the definer context based on the Definer prototype in the template. It also adds an h:correlation link from the newly minted p:Person in the Definer context to the p:Person in the Participant context
 +
# Client adds the reciprocal h:correlation link
  
 
==Edit simple attribute of a card==
 
==Edit simple attribute of a card==

Revision as of 14:09, 27 August 2011

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

Add card from gallery

Note: Cards represent a relationship between the user and an external site or business. The relationship includes a bi-directional data channel that shares and synchronizes a site-specific set of attributes between the site and the user's PDS. This set is a subset of the user's overall set of attributes.

Story

  1. She navigates in web client to a place where a gallery of available templates is displayed
  2. She clicks on the "Google Ads" card-shaped template
  3. She sees a new Google Ads card in her list of cards

Assumptions

  1. Alice is already logged in to her PDS web client
  2. The PDS includes a card gallery
  3. PDS gallery is pre-configured with a set of template contexts and one of these is the Google Ads template.

Design

Data model:

Issues:

  • Q: How does the PDS code know by inspection of the card gallery whether the PDS user is the definer/creator of the template? In other words how does it know which role (definer vs. participant) it should play?
    • A: If the card is in the gallery at all, we will assume it was defined by an external (non-user) definer. We'll put user-defined templates somewhere else.
  • Q: how is the connectionType for the Proxy determined from the template?

Logic:

  1. Flow stars in the cline (aka portal). User opens the card gallery. User selects card to add.
  2. Client instantiates the participant context based on the Participant prototype in the template
  3. Client instantiates the definer context based on the Definer prototype in the template. It also adds an h:correlation link from the newly minted p:Person in the Definer context to the p:Person in the Participant context
  4. Client adds the reciprocal h:correlation link

Edit simple attribute of a card

Story

  1. She navigates to a place that shows her list of cards
  2. She clicks on a card (e.g. Google Ads") to select it
  3. The card displays a set of attributes including age-range widget
  4. Alice edits the value of the age-range widget

Assumptions

  1. Alice logs into web client

Design

Create a connection with a site

User goes to a site that allows a PDS-to-site connection. (We're being vague here about the protocol because we assume it can entirely be done using the hot-off-the-presses OpenID Connect protocol, but we're not yet sure).

Back to the top