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

@ianbjacobs I think this issue is worth keeping open to get clarity discuss the different requirements of __owning__ a PMI for the sake of dereferencing vs matching.

By that I mean, for the URL http://example.com we can assume the __owner__ of the URL is the owner of the domain example.com but that doesn't mean they also __own__ all of the payment method specs that use that URL as a PMI. 

If that sounds wrong, then @maoyanhua 's assertion about industry associations is a great use case to illustrate.

Let's assume that the owner of example.com is a company called Example Corp. Let's assume Example Corp is part of an industry association called The Payment Processors Association and the association has defined a payment method supported by their members and published a payment method spec at http://payproc.org/payment-methods/paynice_spec.html. That payment method spec lists the following PMIs as being related to this payment method:

* http://payproc.org/payment-methods/paynice
* http://example.com/payment-methods/paynice
* http://otherco.com/payment-methods/paynice
* http://3pay.io/payment-methods/paynice

__Ownership__ of those URL's is only important if they are going to be dereferenced because the owner of the URL controls what resource sits at http://example.com/payment-methods/paynice.

So if Example Corp wants to host a resource at http://example.com/payment-methods/paynice they can do that. Right now we are not proposing to set any expectations for what that resource might be or if it needs to even exist.

For the purposes of matching the browser (payment mediator) doesn't really care who owns the URL because it doesn't dereference it as part of the matching process. All the mediator cares about is if that URL _matches_ (and I use the term loosely because we are still defining the algorithm) another PMI which would help it determine if a payment app can process a given payment request.

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