ACTION-94: Try and map minimal v1 features to use cases.

Try and map minimal v1 features to use cases.

State:
closed
Person:
Manu Sporny
Due on:
April 30, 2015
Created on:
April 23, 2015
Associated Product:
Payment Agent
Related emails:
  1. Re: [payment agent] Payment architecture feature priorities (from msporny@digitalbazaar.com on 2015-05-01)
  2. Re: [payment agent] Payment architecture feature priorities (from ij@w3.org on 2015-04-27)
  3. Re: [payment agent] Payment architecture feature priorities (from eanders@pobox.com on 2015-04-27)
  4. Re: [payment agent] Payment architecture feature priorities (from dlongley@digitalbazaar.com on 2015-04-24)
  5. [payment agent] Payment architecture feature priorities (from msporny@digitalbazaar.com on 2015-04-24)

Related notes:

Created wiki to map payment architecture features to use cases and attempt to prioritize.

Manu Sporny, 24 Apr 2015, 04:42:35

Wiki can be found here:

https://www.w3.org/Payments/IG/wiki/Payment_Architecture_Feature_Priorities

Manu Sporny, 24 Apr 2015, 04:42:51

Display change log.

David Ezell <david_e3@verifone.com>, Dapeng Liu <max.ldp@alibaba-inc.com>, Kenneth Mealey <kenneth.mealey@aexp.com>, Chairs, Ian Jacobs <ij@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 94.html,v 1.1 2017/09/15 15:02:29 ted Exp $