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

> from where i come from, having a registry that only one party can write to is a bit of an edge case for what i'd call an actual registry. after all, mostly registries are created to keep track of an evolving ecosystem of identifiers, and usually there is some process for how it can be updated by anybody, and not just one party.

You are right but that is why I think our use case is unique. The W3C registry has 2 functions and the latter may never materialize:

 1. Bootstrap the ecosystem by providing the necessary pieces (identifiers and specs) for common payment methods
 1. Standardize payment methods where communities have produced a variety of specs that are good candidates for standardization and do this by publishing a W3C note that is a consolidated standardized payment method spec.

As such there is no need for anyone but the W3C to contribute to the "registry".

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