October 28 2008 Conference Call: Difference between revisions

From Project VRM
Jump to navigation Jump to search
(still working...)
 
(3 intermediate revisions by one other user not shown)
Line 18: Line 18:
* There should be two states: one open and one closed
* There should be two states: one open and one closed


Doc:
* We need to reach a temporary agreement has two states or more than two states
* What we don't do: take your money, checkbox, but that's all there is to the relationship ==> don't want this to be replicated on the customer side


Doc
== Decision ==
We need to reach a temporary agreement has two states or more than two states
* There are three states to the r-button: not visible, visible + open, and visible + closed
What we don't do: take your money, checkbox, but that's all there is to the relationship ==> don't want this to be replicated on the customer side
* The r-button is not visible if there are no VRM relationship actions available for the user to take on this screen/page
* The r-button is visible and open if VRM relationship actions are available (with an entity represented on or in the page), but none have been taken by the user
* The r-button is visible and closed if a user has taken a VRM relationship action associated with a represented entity
* An r-button will close when a user has taken a relationship action, regardless if the vendor subscribes to the supporting service, or is even aware of VRM
* An action is a "VRM action" if it is provided by a relationship service that is based on VRM-compliant standards
* A relationship service based on a VRM-compliant standard must allow a vendor to participate (e.g. reciprocate the user intention), thereby making the closing of the r-button meaningful. In other words, a true VRM action must allow the vendor to agree to your terms in a standard way


More discussion on personal data store
== Follow up ==
 
* More discussion on personal data store
ka-chunk / two-sided
* Chris will take to-do to update the state transition diagram on the r-button spec page
 
how can this be bi-lateral
Red/gray

Latest revision as of 17:52, 28 October 2008

Topic: R-button working meeting

Attendees

  • Keith Hopper
  • Iain Henderson
  • Dean Landsman
  • Doc Searls
  • Joe Andrieu
  • Charles Andres
  • Asa Hardcastle
  • Christopher Carfi
  • Drummond Reed

Points

Asa:

  • concerned about the increasing complexity of states. Closing of magnets symbolizing relationship = a relationship action has taken place.
  • There should be two states: one open and one closed

Doc:

  • We need to reach a temporary agreement has two states or more than two states
  • What we don't do: take your money, checkbox, but that's all there is to the relationship ==> don't want this to be replicated on the customer side

Decision

  • There are three states to the r-button: not visible, visible + open, and visible + closed
  • The r-button is not visible if there are no VRM relationship actions available for the user to take on this screen/page
  • The r-button is visible and open if VRM relationship actions are available (with an entity represented on or in the page), but none have been taken by the user
  • The r-button is visible and closed if a user has taken a VRM relationship action associated with a represented entity
  • An r-button will close when a user has taken a relationship action, regardless if the vendor subscribes to the supporting service, or is even aware of VRM
  • An action is a "VRM action" if it is provided by a relationship service that is based on VRM-compliant standards
  • A relationship service based on a VRM-compliant standard must allow a vendor to participate (e.g. reciprocate the user intention), thereby making the closing of the r-button meaningful. In other words, a true VRM action must allow the vendor to agree to your terms in a standard way

Follow up

  • More discussion on personal data store
  • Chris will take to-do to update the state transition diagram on the r-button spec page