Re: [w3c/browser-payment-api] Identifiers or Locators (#150)

My understanding of where we are today on this is:

* There will be a registry
* It will be owned by the WG (or some other group at W3C)
* It will list identifiers under the control of the group that owns the registry (i.e. If they are URLs they will start with https://w3.org)
* These identifiers will be linked to payment method specifications published by the W3C as WG notes or in future perhaps IG notes or perhaps delegated to some other group.
* The purpose of this set of registered specifications is to bootstrap the process of developing an ecosystem of payment methods so that the API is useful from day 1 and is not dependent on third parties developing these payment method specs
* The vision is for anyone to be able to develop new payment methods (as long as they can persuade payers (read, payment app publishers) and payees (read, online merchants or their PSPs) to support them. (i.e. The bitcoin community could come together over a Bitcoin payment method, spec this out and publish the spec anywhere they choose. They would also define the identifier(s) for that payment method)
* The payment method identifiers for those independent payment methods will not be in the W3C registry and the payment method specs will not be hosted by W3C.
* If a group at W3C (such as this WG or the Payments IG) considers it useful in the future (perhaps to consolidate some very similar specs) they will attempt to standardize a third party payment method by publishing a payment method spec for that payment method in W3C space.
* It will be entirely up to payment apps and payee systems to decide which specs they want to implement (W3C or otherwise) and will simply advertise that through the identifiers they list as supported.

---
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/150#issuecomment-214411622