- From: Telford-Reed, Nick <Nick.Telford-Reed@worldpay.com>
- Date: Thu, 31 Mar 2016 13:02:55 +0000
- To: 'Adrian Hope-Bailie' <adrian@hopebailie.com>, Manu Sporny <msporny@digitalbazaar.com>
- CC: Web Payments IG <public-webpayments-ig@w3.org>, Web Payments Working Group <public-payments-wg@w3.org>
- Message-ID: <F83606EEAA40AC4EA2919143B15B74C189F3C7BC@UKDC2-PC-MBX03.worldpay.local>
Manu I’d echo Adrian’s thanks for sharing. I am on record<https://www.w3.org/2016/03/22-ac-minutes.html#item05> at the last Advisory Council meeting in Boston as saying that taking in two ‘competing’ specs turned out to be a bad idea. The question now is how do we rebuild trust and cooperation so that the outcomes are as good as we _collectively_ can make them. I think the two key areas for the WG over the coming months are in security/privacy, and the payment application registration/integration/communication architecture. In both cases I think both the CG and the broader payments community have a huge role to play and so your blog is helpful in trying to frame some of the challenges in getting this large, disparate group to work more effectively. Thanks Nick -- Nick Telford-Reed e: nick.telford-reed@worldpay.com<mailto:nick.telford-reed@worldpay.com> | m: +447799473854 | t: +44 203 664 5069 From: Adrian Hope-Bailie [mailto:adrian@hopebailie.com] Sent: 31 March 2016 11:27 To: Manu Sporny Cc: Web Payments IG; Web Payments Working Group Subject: Re: The Web Browser API Incubation Anti-Pattern Manu, thank you for sharing this openly. As a co-chair of the WG I don't believe it would be appropriate to take a public position on what you have said. We have had some private discussion and I am always eager to learn from experienced W3C members like yourself, how we might improve the way we are operating. My only comment would be to encourage the Web Payment CG to continue engaging in the process. 1. We have early drafts of a number of specifications but nothing proposed for some of the most important deliverables such as the HTTP API and extensibility guidelines. I am hopeful that you and the CG will put forward proposals on how we will address these requirements. 2. The browser API specification is still very immature. There are a great number of unanswered questions and issues that still need to be resolved. The final browser API specifications need to reflect the consensus of the WG of which you, and a number of other CG participants, are members so I encourage you to continue submitting PR's against the existing documents where you believe your proposals have technical merit. 3. A particularly urgent need is for the WG to get detailed proposals on how the registration and integration of Payment Apps will work and how we can guarantee that there is a level playing field for Payment App publishers. I'd encourage the CG to use the work it has already done on this and make a concrete proposal. Adrian On 31 March 2016 at 03:34, Manu Sporny <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>> wrote: I've just published a blog post regarding the first four months of the Web Payments Working Groups somewhat rough operation. It tries to analyze what went right and what went wrong with the way we approached the creation of the first set of specifications around payments at W3C. http://manu.sporny.org/2016/browser-api-incubation-antipattern/ We should keep these lessons in mind before we try to launch any more Working Groups via the Web Payments Interest Group. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Web Payments: The Architect, the Sage, and the Moral Voice https://manu.sporny.org/2015/payments-collaboration/ This e-mail and any attachments are confidential, intended only for the addressee and may be privileged. If you have received this e-mail in error, please notify the sender immediately and delete it. Any content that does not relate to the business of Worldpay is personal to the sender and not authorised or endorsed by Worldpay. Worldpay does not accept responsibility for viruses or any loss or damage arising from transmission or access. Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct Authority No: 504504), Worldpay AP Limited (Company No: 05593466 / Financial Conduct Authority No: 502597). Registered Office: The Walbrook Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial Conduct Authority under the Payment Service Regulations 2009 for the provision of payment services. Worldpay (UK) Limited is authorised and regulated by the Financial Conduct Authority for consumer credit activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam, the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence from and is included in the register kept by De Nederlandsche Bank, which registration can be consulted through www.dnb.nl. Worldpay, the logo and any associated brand names are trade marks of the Worldpay group.
Received on Thursday, 31 March 2016 13:03:25 UTC