Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)

> avoid the confusion and cost of relying on dereferencing a URI to establish that identical strings in fact mean different things.

You don't have to dereference the URI. Systems can and do hard-code interpretation based on well-known context URLs and clear update methodologies on those contexts.

If the URL is well known and the data at that URL is only ever added to, hard coding or long-term caching of the context in your application is something that we'd expect people to do.

The key here is that we have some formal definition with provable correctness vs. "just a list of words that a bunch of yahoos in a WG have slapped together and put in a human readable document online". :)

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/35#issuecomment-169726379