Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDS Use Cases"

(Edit simple attribute of a card)
(Connect to a site)
Line 40: Line 40:
 
* [[Context Editor Design Notes]]
 
* [[Context Editor Design Notes]]
  
==Connect to a site==
+
==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).
 
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).
  
 
* [[Person-Site Relationship Management]]
 
* [[Person-Site Relationship Management]]

Revision as of 13:55, 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:

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

Code:

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).

Copyright © Eclipse Foundation, Inc. All Rights Reserved.