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

> Some of the problems are the same as XML Namespaces. Some points described here are relevant.

We are talking about identifiers not namespaces so I think a lot of the reasons in that reference are irrelevant.

At this stage we're not expecting developers to have to namespace the data in their payment requests or responses so there's no risk that these URLs become anything more than identifiers.

A payment method identifier needs to be globally unique and it should be possible for anyone to mint one easily. 

Also, as @ianbjacobs says end user's will never see these so how pretty or easy to remember they are is irrelevant to my mind.

We should provide guidance up front around conventions such as http vs https and the presence or not of trailing slashes to help with consistency.

> I personally like short identifiers that map to URLs. And of course some sort of registry for same ;-)

Why add the overhead of a registry if it's not actually required?

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