Re: [w3c/webpayments-method-identifiers] Why URLs? (#9)

@tabatkins said:

> Within this, tho, I recommend the spec require that the URL be normalized (using terms from the URL standard) to be just origin + path (and dictate whether there's a trailing slash or not). That way there's no confusion about query parameters or fragments.

This is complicated by the fact that there is a desire for this document to potentially contain an embedded object which is necessarily represented by a different URL (it is an identifier for a payment app, not a payment method). The only way to do this would be to have a fragment that points to the embedded object and therefor the URLs only differ based on that fragment.

See: https://github.com/w3c/webpayments-payment-apps-api/issues/35


-- 
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/webpayments-method-identifiers/issues/9#issuecomment-246465907