W3C home > Mailing lists > Public > public-payments-wg@w3.org > June 2016

Re: New Web Payments Architecture document proposal

From: Rouslan Solomakhin <rouslan@google.com>
Date: Sat, 18 Jun 2016 17:32:55 +0000
Message-ID: <CAMMzaWHqkG4e_-RMTO=T9CwvCk3bBNoHpfNcqW_-jAXL+QM2yg@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments WG <public-payments-wg@w3.org>
Cc: Web Payments IG <public-webpayments-ig@w3.org>
Great document. Everything seems right, but I cannot comment on the "Payer
Registers Payment App" section, because that's not implemented anywhere
yet, AFAIK.

On Fri, Jun 17, 2016 at 12:19 PM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> Hi all,
>
> Now that the Browser API has settled down a bit and we've had some time
> to establish a rhythm for the group, it might be good to (very briefly)
> revisit the architecture document to make sure we're all still reading
> off of the same page. I have to do this anyway for the HTTP API, so
> decided to do the architecture document at the same time.
>
> What follows is a high-level, very terse outline of the architecture as
> it stands right now:
>
> https://w3c.github.io/webpayments/proposals/wparch/
>
> This need also came up recently during an internal company meeting as
> well - we have a few new hires that would like to get involved in the
> Web Payments work, but when they asked for a high-level overview of the
> architecture we couldn't point them to a simple, up-to-date document.
>
> While we're aware of AdrianHB's good work in this area (the wiki page),
> we wanted something a tad less involved, less text, more images, more up
> to date, and something that was a lead into our other specs.
>
> In doing so, I strived to:
>
> * Not put anything controversial in there
> * Be terse and to the point, the document should be a 10 minute read
>   tops.
> * Be more abstract than concrete - thus, the document really does talk
>   about architecture and message flow, not implementation details
>   or specifics. It's an approximation and is not specific in certain
>   areas on purpose.
> * Provide it as a jumping off point into all of our specs (which
>   happens toward the bottom of the spec).
>
> Please review and provide your thoughts.
>
> I'd like to get this into the group as an ED soon and publish it as a
> FPWD in July/Aug (possibly making a decision to do so at the F2F).
>
> This is a request to spend 5 minutes on it during the next telecon.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: The Web Browser API Incubation Anti-Pattern
> http://manu.sporny.org/2016/browser-api-incubation-antipattern/
>
>
Received on Saturday, 18 June 2016 17:33:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:17 UTC