Re: Analysis of W3C Web Payments Specifications (2017)

One of the Web Payments WG implementers noted that the following two
statements were misleading, and given that we want to be fair, even
handed, and constructive in our analysis, we've updated the language in
the blog post:

> The great news here is that this solution works right now in roughly 
> 3.3 billion browsers, which is around 85% of the people using the
> Web today.

Changed to:

The great news here is that this solution is compatible with roughly 3.3
billion browsers today, which is around 85% of the people using the Web.
In order to take advantage of this opportunity, just like the native
implementations, the polyfill has to be deployed by merchants and
payment app providers on their websites.

> Like the Web Payments polyfill, this solution works right now in 
> roughly 3.3 billion browsers, which is around 85% of the people
> using the Web today.

Changed to:

Like the Web Payments polyfill, this solution is compatible with roughly
3.3 billion existing browsers, which is around 85% of the people using
the Web today. Again, this doesn’t mean that 3.3 billion people are
using it today, the polyfill still has to be deployed on issuer,
verifier, and digital wallet websites to make that a reality.

If anyone else feels that any other parts of the post are misleading or
not constructive, please let us know so we can make the appropriate changes.

-- 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 Wednesday, 1 November 2017 14:21:44 UTC