Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138)

@msporny,

> @dlongley and I have read over your first three bullet points multiple times and agree with them. So, I think we're agreed on those 3 bullet points (did you think we didn't agree on those bullet points?).

I am glad to hear there is agreement. My thoughts are still evolving, but glad to hear there's a chance for us to move in the same direction.

> [Regarding the payment method identifier spec] I assume you mean that there will be a fairly substantial rework/modification of the content of this spec (to the point that it's a new spec). The current PMI spec is only about the identifiers. 

> Add content to the spec that provides details on how to define a payment method and the minimum requirements for a new payment method specific spec

I agree we "want" both things: payment method identifiers and instructions for how to write a payment method identifier spec. 

It is not clear to me (yet) that both of those belong in the same spec because the audiences are different:

* The primary consumers of the payment method identifier spec will be Web app developers, payment app developers, and those writing implementations of the APIs.
* The primary consumers of the "how to write a payment method spec" will be people who design payment methods. 

So while the topics are indeed related (and we see them come together in each "payment method spec"), the audiences may be different enough to split the material into two resources.

Furthermore, I think we may have several resources that are not really normative (for implementations) but rather good practices, and those resources should be able to evolve on an ongoing basis (e.g., in the group's github repo). These include:

* How to write a payment app (showing some examples of how to use different payment methods)
* How to write a Web app to use the paymentRequest API
* How to write a payment method specification

Ian


---
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/browser-payment-api/issues/138#issuecomment-210156025