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

Re: Updates to "Payment Request API Architecture"

From: Shane McCarron <shane@halindrome.com>
Date: Fri, 11 Mar 2016 19:27:24 -0600
Message-ID: <CAJdbnOBK4jeqAGvv+rZNyo6-57BBbnEkzxxjUG6e4kiR7JKB1g@mail.gmail.com>
To: Ian Jacobs <ij@w3.org>
Cc: Web Payments Working Group <public-payments-wg@w3.org>
Thank you for doing this, Ian.  I will dig through it over the weekend.  I
like the name change especially.

On Fri, Mar 11, 2016 at 12:48 PM, Ian Jacobs <ij@w3.org> wrote:

> Hi all,
>
> At yesterday’s meeting [1] i volunteered to reread the Architecture wiki
> [2] and the draft
> architecture spec [3]. I have a goal of getting the architecture spec into
> shape so that
> we can publish it as a FPWD the first week of April.
>
> To that end, I edited it to make it align more with what is in the wiki. I
> welcome feedback on the
> updated draft [3].
>
> The three main parts of the document are now:
>
>  * An overview of the anticipated user experience. Some of this is covered
> in the wiki, but in more
>    detail than I think we need in the spec.
>  * The “components” that emerge from the user experience.
>  * The organization of the specifications that together (will) describe
> interactions among these
>    components.
>
> I also made it clearer in this draft that the “payment request
> architecture” is not the only thing
> that the WG is developing. To that end, I have also updated the title, now
> "Payment Request API
> Architecture”. The purpose of the spec, therefore, is  narrowly to explain
> how the associated specifications
> (for payment method identifiers, payment request API, etc.) fit together.
> It is not a description of
> a complete or comprehensive payment architecture for the Web.
>
> The spec still needs work, but I wanted to share this direction with
> people to see if there is
> support.
>
> If we decide to publish this as a FPWD, I would like to then update the
> Wiki to prune away
> some material (and refer instead to the spec).
>
> After this exercise I am more confident that the two resources are in
> alignment, and that
> we can reduce redundancy by editing the wiki as the next step.
>
> Ian
>
> [1] https://www.w3.org/2016/03/10-wpwg-minutes#item01
> [2]
> https://github.com/w3c/webpayments/wiki/A-Payments-Initiation-Architecture-for-the-Web
> [3] https://w3c.github.io/browser-payment-api/specs/architecture.html
>
> —
> Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
> Tel:                       +1 718 260 9447
>
>
>
>


-- 
-Shane
Received on Saturday, 12 March 2016 01:27:54 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 12 March 2016 01:27:55 UTC