RE: A (controversial) proposal for what should be in/out of scope

There are quite a few requirements put up in the charter, which seem good reasons to do that work from my point of view. Whether you read them as features or as deficiencies of what we have today is up to all, but I doubt that form-filling will meet those requirements.

Jörg

From: Evan Schwartz [mailto:evan@ripple.com]
Sent: Mittwoch, 17. Juni 2015 20:48
To: David Singer
Cc: Web Payments IG
Subject: Re: A (controversial) proposal for what should be in/out of scope

You're right that we're interested in enabling merchants to collect payments from users on the web, but they already do that today.

We need to get more specific about what problem we're trying to solve. One of the browser vendor reps made a good point yesterday that most web payments today are made by filling out forms. If we're talking about improving this, we're talking about replacing filling out forms with something else. If we're proposing a replacement for something, we need very compelling reasons for people to switch.

On Wed, Jun 17, 2015 at 2:35 PM, David Singer <singer@apple.com<mailto:singer@apple.com>> wrote:
Thanks Evan,

> On Jun 17, 2015, at 10:45 , Evan Schwartz <evan@ripple.com<mailto:evan@ripple.com>> wrote:
>
> Arguably, the W3C should only focus on standards that increase interoperability between systems that need to communicate.

I think it’s great (and important) to understand the landscape, but I agree, focusing on (a) the interfaces (b) that are important and (c) related to the world-wide web (and hence this consortium), is important.

Isn’t the “high nail” here enabling a merchant to collect an e-payment from a consumer? What is the simplest set of markup, APIs, protocols etc. needed to make that happen?

David Singer
Manager, Software Standards, Apple Inc.




--
Evan Schwartz | Software Architect | Ripple Labs
[http://upload.wikimedia.org/wikipedia/commons/e/eb/Ripple-Logo.png]<http://ripple.com>