PDS Use Cases
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.
- She navigates in web client to a place where a gallery of available templates is displayed
- She clicks on the "Google Ads" card-shaped template
- She sees a new Google Ads card in her list of cards
- Alice is already logged in to her PDS web client
- The PDS includes a card gallery
- PDS gallery is pre-configured with a set of template contexts and one of these is the Google Ads template.
- 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
- She navigates to a place that shows her list of cards
- She clicks on a card (e.g. Google Ads") to select it
- The card displays a set of attributes including age-range widget
- Alice edits the value of the age-range widget
- Alice logs into web client