Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11)

@sideshowbarker wrote:
> It’s more just about a URLs (and all their baggage) vs just a simple string in some form.

I don't see it that way at all. Why does it have to be an either/or? We can have both (as proposed by option 1a and 1b). The only argument that I heard against having both is that "people mess it up", but again - I'd like to see data on why and how people mess it up (other than "they screw up equivalence testing").

> So the question to ask is more about how many parts of the Web platform have recently picked simple strings in similar cases rather than URLs. And the answer is, many.

Like? Which cases are similar to the one that we're discussing? Links to specs and deployment experience would be helpful.

---
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/11#issuecomment-216004454