See also: IRC log
<scribe> scribe: Ian
Next call: 23 Nov
IJ: regrets?
Ian incorporated changes based on 2 November discussion:
Updated text:
https://w3c.github.io/webpayments-payment-apps-api/#selectable-app-information-display
IJ: Anybody look at those?
https://lists.w3.org/Archives/Public/public-payments-wg/2016Nov/0031.html
Conor: We met Monday - Conor
Hackett, Rouslan Solomakhin, Tommy Thorsen, Dongwoo Im
... chatted about what's available in browsers to integrate
to
Rouslan: We are developing support for payment apps; not done yet
IJ: Android only?
Rouslan: Both
Conor: Basically next steps will
be to develop a payment app using Chrome experimental build +
web apps using service workers
... we discussed how we would work as a subgroup
... we'll work on the WG's public list
[Ian: +1]
Conor: Also, for Chrome to release info in a public build, they want to link to public information
IJ: any other thoughts from people on the call?
<conorhwp> +q
IJ: What spec issues are coming up from implementation attempts?
Conor: I think Rouslan covered a lot in the integration of android apps.
Rouslan: In the beginning of the
development of web-based payment apps, the Samsung devs were
contributing to Chromium; I am doing code reviews.
... I noticed that "icon" is a string. What is it meant to
represent?
... we will coming back to the spec on what "icon" is and how
that string should be intepreted?
https://github.com/w3c/webpayments-payment-apps-api/issues/69
IJ: For new issues, use GitHub or send them to public-webpayments-wg@w3.org
Rouslan: I think some of the issues that Samsung raised were about native apps; ok to use W3C GitHub?
IJ: +1
https://w3c.github.io/webpayments-payment-apps-api/
IJ: Any updates on UX issues for web-based payment apps?
Rouslan: We still have questions and will do research; we will contribute ideas back to the payment apps api
TommyT: One small issue came up
on Monday
... I'll add to GitHub
... it's about payment app identifiers
... if we want to do merchant-recommended payment apps, we need
for merchants to recommend apps
... the spec says 'use payment app identifiers'
... but issue 35 says "scope" url should be payment app
identifier
https://w3c.github.io/webpayments-payment-apps-api/#set-manifest
IJ: What are the big challenges ahead that people see, so that we can prioritize issues for this call?
Rouslan: The whole project is challenging. :)
https://w3c.github.io/webpayments-methods-card/#request
[Ian does a quick summary]
Alan: Are we looking at single functions or multiple?
Ian: Have not discussed yet at that level of detail
Alan: A use case that came to
mind is recurring payments
... e.g., you might not want to take a card that has an
expiration next month
https://github.com/w3c/webpayments-payment-apps-api/issues
IJ: Please put thoughts in GitHub
https://github.com/w3c/webpayments/wiki/PaymentApp_Notes
<rouslan> +1
<jenan> +1
<conorhwp> +1
<alyver> 0
Should we move the call later if we are not having colleagues dial in from Korea and China?
<TommyT> I can probably not make it if the call is later
<scribe> ACTION: Ian to look into modified call time [recorded in http://www.w3.org/2016/11/16-apps-minutes.html#action01]