- From: Manu Sporny <notifications@github.com>
- Date: Tue, 31 May 2016 17:24:51 -0700
- To: w3c/webpayments <webpayments@noreply.github.com>
- Cc:
- Message-ID: <w3c/webpayments/issues/134/222860000@github.com>
@adrianhopebailie wrote: > Proposal: > Create a new payment mediator specification that defines the conformance criteria for any mediator (not just a user agent in this role). +0.4 - it would help to know what the conformance criteria for a mediator would be - do you have a short list? > Migrate the appropriate elements of the API specification into this new specification. +0 - unsure about this bit if it means taking the WebIDL and placing it into a mediator spec that the HTTP API spec can't build on top of. > Make the new specification a normative dependency of the API specification. +1, the PaymentRequest API currently feels like it's conflating two concepts (which you go into below): > Update the API specification so that it describes the conformance criteria of a user agent in assuming two roles: > * Payment mediator (as defined in the payment mediator spec) > * Data collection mediator for collection of data to optimize the checkout flow. +0.8 --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/134#issuecomment-222860000
Received on Wednesday, 1 June 2016 00:25:23 UTC