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

[w3c/webpayments] PROPOSAL: A new document structure for this API (#134)

From: Adrian Hope-Bailie <notifications@github.com>
Date: Tue, 31 May 2016 01:26:09 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/134@github.com>
Migrated from https://github.com/w3c/browser-payment-api/issues/138

There are a number of issues raised and comments made about the need to explicitly define the role of payment mediator and user agent. I propose that we separate the current API spec into a spec defining the conformance criteria for a payment mediator and a spec defining conformance criteria for a user agent in it's role as a payment mediator but also in its role as data collection service to optimize the checkout flow.

## Proposal

 1. Create a new payment mediator specification that defines the conformance criteria for any mediator (not just a user agent in this role).
 1. Migrate the appropriate elements of the API specification into this new specification.
 1. Make the new specification a normative dependency of the API specification.
 1. Update the API specification so that it describes the conformance criteria of a user agent in assuming two roles:
    1. Payment mediator (as defined in the payment mediator spec)
    1. Data collection mediator for collection of data to optimize the checkout flow.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Tuesday, 31 May 2016 08:27:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 May 2016 08:27:09 UTC