- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sat, 11 Nov 2017 03:48:05 -0500
- To: public-payments-wg@w3.org
On 11/08/2017 12:18 PM, Ian Jacobs wrote: > For Payment Request API specifically, the group set a strong > expectation at the March face-to-face meeting that CR exit would > depend on native browser implementation on both native and mobile. > The group can revisit that question if they wish. To clarify our request - Digital Bazaar doesn't think a polyfill implementation is sufficient to exit CR. We're not asking for the WG to reconsider this. We do need two native interoperable browser implementations. What we are requesting is to be included in the implementation report to demonstrate broader implementation than just the native browser implementations. The logic being that implementation is a sort of wider review of the technical nature of the specification and thus the more diverse implementations that there are, the wider the review. So, we'd like to be included in the implementation report ONLY to demonstrate wider review, NOT to be counted towards the exit criteria. It's up to the TAG and transition team to determine the exit criteria implication and that can happen in parallel without being a blocker for CR (as I expect we'll have at least two native implementations of PR and PH). -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Rebalancing How the Web is Built http://manu.sporny.org/2016/rebalancing/
Received on Saturday, 11 November 2017 08:48:31 UTC