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

Re: New Web Payments Architecture document proposal

From: Ian Jacobs <ij@w3.org>
Date: Tue, 21 Jun 2016 22:31:51 -0500
Cc: Web Payments Working Group <public-payments-wg@w3.org>
Message-Id: <07C38A70-E933-4274-9CC6-93380F2DB6A8@w3.org>
To: Manu Sporny <msporny@digitalbazaar.com>

> On Jun 21, 2016, at 9:06 PM, Manu Sporny <msporny@digitalbazaar.com> wrote:
> 
[snip]

> This document is an attempt to summarize the architecture that we have
> as we go (not create a software architecture document).

[snip]

> 
>> * Payment Instruction
>> 
>> Not sure where this term comes from?
> 
>> From Kris and Vincent's suggestions... it's ISO20022 terminology and
> feels like it gives future WGs more breathing room than just PaymentRequest.

I agree the document can usefully summarize what “we have” (as you said
above). It undercuts that purpose to add bits that we don’t have.

[snip]

> We should trying to make sure we have a bit of leeway for other types of
> requests in the future, especially use cases like SubscriptionRequests
> (which are in our use cases for v1, btw):

We don’t have those things yet, and therefore the document should not
speak to them (yet).

> 
> https://www.w3.org/TR/web-payments-use-cases/#uc-subscription
> 
>> If your intent is to change from payment request to payment
>> instruction then I think that warrants some discussion before we
>> adopt the change.
> 
> Agreed, this is a way of raising that question.

Now we’ve changed topics. (I suggest a GitHub issue.)

Ian

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447




Received on Wednesday, 22 June 2016 03:32:01 UTC

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