Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98)

I disagree with the "A Payment App is an origin" definition that you are arguing above. I really liked the "A Payment App is a Web App that can do payments" definition that I thought we had some consensus on. I think most people's idea of the concept "Web App", is that it is the collection of web pages that are related to a particular Web App Manifest. I think most people think of a "Web App" as the thing you can install to the home screen of your phone if you're on a page that links to such a manifest. I think most people do *not* think that a "Web App" is an origin.

I know the permissions model works on origins but that, I believe, is unrelated to the concept of a "Web App" and to the concept of a "Payment App".

@ianbjacobs 
> We have also discussed this question: "If we refer to a payment app by origin, how can someone
get from origin information to the code of a Web-based payment app?" One tentative answer
has been: use script_url in Web App Manifest.

1. How do you plan to get from the origin information to the Web App Manifest? Bear in mind my earlier examples that show that there can be multiple Web App Manifests within a single origin.
2. How does the `script_url` relate to a Payment App?

@ianbjacobs 
> there is not currently a need for a special "payment app identifier."

I agree with this. But in my opinion, the above statement is not compatible with your earlier statement: "We are currently planning to identify payment apps by their origin".

Any disagreements we have here are likely to be caused by us having differing definitions of the term "Payment App" or of the term "Web App". If I seem to be spouting complete gibberish, please take a moment to consider your definitions, and whether or not they match mine, which I have laid out in the initial paragraph of this comment.

-- 
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-payment-apps-api/issues/98#issuecomment-280478570