Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

PDS Use Cases

Revision as of 07:51, 25 August 2011 by (Talk | contribs) (Design)


Get card from gallery

A card is a metaphor representing a bi-directional data channel that connects a site (e.g. a merchant) to a site-specific subset of the user's overall set of attributes.


  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


  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.


Data model:

  • Template vocabulary shows an example template--this example is the Google Ads template
  • Design issues
    • 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?


Edit simple attribute of a card


  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


  1. Alice logs into web client


Back to the top