Re: [w3ctag/design-reviews] Proliferation of manifests at W3C (#423)

Restating my comment from https://github.com/w3c/payment-method-manifest/issues/27

> Merging the [Web App and Payment Method] manifests doesn't make sense because they are for very different things.

> A Web App is a user application whereas a payment method is a sub-protocol (or specifically a request/response format) of the Payment Request API. The designer of a payment method may wish to provide meta-data about the method to browsers to:

>  1. limit the origins that are permitted to handle payments using this method
>  2. indicate which web apps (and also non-Web apps) are preferred for processing payments using this method (to facilitate Just In Time installation for example)

Said differently, and in a similar vein to @llemeurfr 's comment above about the relationship between an App and Publication:

 1. A payment method is NOT a payment app (where a payment app is a web app that uses the payment handler API). 
 2. Many payment apps (at different origins) might support payments using the same payment method
 3. A single payment app can support multiple payment methods (described by manifests at various origins)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/423#issuecomment-542254817