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

@ianbjacobs wrote:
> Here's a text description of the relationships as I conceive of them

@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?).

Only one minor nit on your conclusion (agree w/ the other bullet points not mentioned):

> All the specs will depend on 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. I suggest (integrating some of @adrianhopebailie's ideas):

* Renaming the spec to "Payment Methods"
* 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'll note that we keep deviating from hard lessons learned in ISO20022 and IETF. Transactional systems  (like payment systems) are typically best modeled as messages + protocols (many systems fit well into that model). A Payment Method is just another type of message in the system that expands on the core payment request / response.

---
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-210131663