- From: <Joerg.Heuer@telekom.de>
- Date: Mon, 17 Nov 2014 16:47:24 +0100
- To: <boyera@w3.org>
- CC: <public-webpayments-ig@w3.org>
Hello Stephane, In my view your plan is okay - and partially already on track. I will provide some more input from our work in different categories: - current best practice (from what we developed - and learned from others) - legacy support (we had the pleasure to learn a lot about payments and other things of various sorts) - support of existing innovative solutions Especially for the latter two, support from the IG members would be needed. I'd volunteer to take on the editor role for the UPA part. Cheers, Jörg -----Original Message----- From: Stephane Boyera [mailto:boyera@w3.org] Sent: Sonntag, 16. November 2014 20:08 To: public-webpayments-ig@w3.org Subject: action-16 IG deliverable and timeline Dear colleagues, As discussed during the call last friday, I'm launching the discussion related to IG deliverables and timeline. First of all, in order to attract attention, it is esential that the group publish regularly deliverables that summarize its work. The charter contains a series a deliverables. see http://www.w3.org/2014/04/payments/webpayments_charter.html#deliverables This list points as the first deliverable a "Web Payments Roadmap" I think it is the most important one that will highlight the gaps in the technology stack, as well as clearly identify the areas where the group is planning to make a significant contribution. I believe that if we want to use the current momentum, and use the activity in the domain to be visible, we should aim at publishing a first version of this deliverable sometime in Q1 2015. I suggest we put a data, like 1st March and do our best to deliver at this date. What we need for a deliverable is 2 things: *an individual or a set of editors for the document *content What is imho more important for now is the second part, the content. My feeling was that the 2 task forces we have on use-cases and payment-agent are working on two sides of the problem: the bottom-up approach defining a set of scenario we want to cover, and a top-down approach defining a framework with various modules. My view after the face-to-face was that the roadmap deliverable will be the results of the encounter of the work of the two task forces: an overall architecture with relatively high level modules that are addressing a series of use-cases. A first draft could stay at a high-level identifying the modules, and perhaps the set of actors that are essential for their implementation as well as the other standards that are in the scope of the module. Such a deliverable should allow us to identify working groups (existing or new ones) to handle some of the modules. Therefore, per my action, I wanted to write down my view on this, and see what people think about this approach, the proposed timeline etc. cheers steph -- Stephane Boyera stephane@w3.org W3C +33 (0) 6 73 84 87 27 BP 93 F-06902 Sophia Antipolis Cedex, France
Received on Monday, 17 November 2014 15:47:57 UTC