Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200)

@adrianhopebailie, 

I do not understand from what you wrote why we need to keep the issue open. I agree with the following statements:

* A payment method (note "method" not "method specification" here)  may be identified by more than one PMI.
* A payment method specification may be referenced by entities who do not control that specification. 
* The matching algorithms we have been discussing do not involve dereferencing URLs.

@maoyanhua wrote:

> in 30, we talked about subclassing/hierarchy, which to me implies a tree structure.

I don't believe that #30 assumes a tree. In fact, I've been in discussion with @mattsaxon and @adrianhopebailie about writing up a proposal for using query parameters as a way to represent a graph of information.

Ian (still thinking we can close this issue)

---
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/200#issuecomment-220432071