@ianbjacobs The problem with not having a definition for "Web application", is that we then have no proper definition of what a "Payment App" is. I think that figuring out things like the relationship to service workers, and what a good identifier might be, is almost impossible without some kind of a definition. It wouldn't have to be an official definition, and I wouldn't expect it to go into the actual specification, but working out some kind of loose definition of what a "Web application" is, and keeping it in wiki, would be very useful for further discussions. >From today's meeting minutes, I see some arguments for focusing less on payment apps, and more on the features needed to implement them. I think that is reasonable, and I am positive to renaming the specification. In particular, I like Adrian's statement: @adrianhopebailie >e.g., the spec could be named after the feature name >... so it's less about payment apps and more about features that we are defining to let someone build a payment app -- 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/105#issuecomment-281472200
Received on Tuesday, 21 February 2017 20:38:08 UTC