- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 27 Apr 2016 23:02:50 -0400
- To: public-payments-wg@w3.org
A few thoughts on the priorities of the group. WGs rarely work on one priority at a time unless they only have one spec they're working on. I'll note that Web Apps has 33 specs in their charter, many of them are worked on at the same time: https://www.w3.org/2014/06/webapps-charter.html#deliverables Web AppSec has 12 specs, a number of which are moved forward in parallel: https://www.w3.org/2015/03/webappsec-charter-2015.html#deliverables That's not to say we shouldn't have a narrow focus, but there are different views on where the priorities should be in this WG (based on, for example, which industry each of us is coming from). On 04/27/2016 09:12 AM, Telford-Reed, Nick wrote: > o Extensibility (and specifically payment app registration and > architecture for browser-payment-api) I think AdrianHB is focusing on this and making good progress. I hope the WG formally takes on his Architecture proposal next week. > o Moving published working drafts forward and supporting > implementations I think Zach and AdrianB are focusing on this and making progress. > o Widening the scope of our published work (HTTP API, additional > payment methods) Dave Longley and I are volunteering to do the HTTP API and Core Messages. Matt has volunteered to do SEPA and generalize the Payment Method spec writing approach. So, we can (and should) work on things in parallel and not block people that are motivated to work on particular specs. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. JSON-LD Best Practice: Context Caching https://manu.sporny.org/2016/json-ld-context-caching/
Received on Thursday, 28 April 2016 03:03:15 UTC