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

Re: [w3c/webpayments] New Architecture Proposal (#125)

From: Adrian Hope-Bailie <notifications@github.com>
Date: Thu, 21 Apr 2016 13:27:17 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/pull/125/c213100952@github.com>
@ianbjacobs said:

> I support an "overview" document that provides:

This is not intended to be an "overview" document. It is a technical document that defines the primary roles in the architecture (mediator and app) and the key concept of a payment method.

This is intended to be a REC track document (not a note). There should be separate documents that specify how to implement these roles in specific deployment scenarios and this should be a normative dependency of those.

The If you feel we still need an "overview" document then that should be a separate WG note titled something like "Overview" and include content such as:

> * Information about what the user experience will be
> * An explanation of the set of specs that define the space.

With regard to:

> Specific instructions (especially if related to conformance) belong in a different document.

I disagree. We need to record somewhere the specifics of how a conformant payment app and a conformant payment mediator must behave. We can repeat this for every implementation specific spec or have this in a single place and refer to it from those implementation specific specs.

---
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/pull/125#issuecomment-213100952
Received on Thursday, 21 April 2016 20:29:42 UTC

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