Re: [w3c/browser-payment-api] Should a payment app identifier (URL) or a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46)

@kirkalx consider that there may be multiple payment methods for paying via Bitcoin proposed by various people. If the WG takes a position on the "best" way for that to work it could publish a payment method spec at a w3.org owned URL and hope that the Web community favors that one but we can't enforce that any more than we can enforce the card networks to adopt our basic card payment spec.

Put another way, I disagree with this:
> There should be no sense that the URL owner has any additional powers over that payment method than ownership of that particular URL gives them.

If the Bitcoin community doesn't trust the onwers of bitcoin.org then I'd expect them to not use payment methods where the identifier is a bitcoin.org URL but to self-select a better payment method managed by an entity they trust (which could be w3.org).


---
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/46#issuecomment-203875796