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

On 2016-04-26 23:54, kirkalx wrote:
> @dret <https://github.com/dret> I don't think a meta-registry would
> cover it, unless that meta-registry was itself decentralized. I'm still
> thinking about what would satisfy some of the more extreme/purist parts
> of the cryptocurrency communities in this matter. What Adrian describes
> above in #150 (comment)
> <https://github.com/w3c/browser-payment-api/issues/150#issuecomment-214411622>
> is probably good enough for the first version of the spec, the concern
> for the bitcoin community in particular is that while getting them to
> agree on something is not that hard if the benefits are clear,
> perceptions of ownership/control are highly controversial.

thanks for the clarification. a registry is a pattern for managing an 
evolving set of identifiers in a centralized place, most often intended 
for design-time lookup purposes. that is not always what is 
needed/wanted when it comes to designing an API that uses identifiers.

my main concern was to point out that there is a huge body of experience 
with that pattern outside of W3C, so if that pattern is what the final 
API wants to use, then tapping into that experience might be a good idea.


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