Re: [w3c/browser-payment-api] Currency Types and Rendering (#185)

@adamroach,

> Sure, but it eliminates the chance of collisions.

Anyone who wants to avoid those collisions can do so by using URLs.

Summary: I think requiring all unknowns to be represented by URLs would be premature at this point. By saying "undefined" now we can do two things:
 - let people use URLs who want to
 - the ability to change the spec in the future to require all unknowns to be expressed as URLs if that turns out to be useful. That is: saying "undefined" today allows us to say more in the future.

Ian

---
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/185#issuecomment-220432589