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)

> Hopefully we don't get the other extreme of a chaotic proliferation of different URLs all essentially meaning "pay with bitcoin".

+1 - one way to avoid this is to get the Bitcoin community engaged in the WG and to produce a Bitcoin Payment Method spec (along the lines of the Basic Card Payment spec) that is endorsed by the WG. It would be published as a W3C WG Note and we can use a w3.org URL as the base for the payment method identifier.

It was proposed in our call yesterday (https://www.w3.org/2016/03/31-wpwg-minutes.html#item05) that we produce payment method specs for as many of the flows we have documented as we can. This will depend entirely on resources available to write the specs and interest from the group in reviewing them and publishing them.



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