- From: Erik Anderson <eanders@pobox.com>
- Date: Mon, 27 Apr 2015 09:32:56 -0400
- To: Web Payments IG <public-webpayments-ig@w3.org>
On 2015-04-24 00:55, Manu Sporny wrote:
> I took an action today to try and attempt to figure out how to
> prioritize payment architecture features and map them to use cases:
>
> https://www.w3.org/Payments/IG/track/actions/94
Isnt this a case of cart before the horse? As discussed, next step is
Payment Agent Summary Requirements.
1) Usecases
2) Payment Agent Summary Requirements
- Mapping those to Use Cases
3) Proposal for new W3C Working Groups (Likely this will happen at the
F2F)
4) Payment Agent Detailed Requirements
- Bi-directional mapping between Use Cases and Summary Requirements
5) Final proposal of new W3C Working Groups and work delegation to
existing W3C groups.
The payment agent features and requirements are kind-of interchangeable
but the approaches are very different when talking features vs
requirements. Of course, diagrams are always used to tell the story at
any phase.
Erik
Received on Monday, 27 April 2015 14:09:31 UTC