See also: IRC log
https://github.com/w3c/webpayments/wiki/Agenda-20170119
next call is 26 Jan
Please register for the FTF => https://www.w3.org/2002/09/wbs/83744/wpwg-201703/
Do we want to plan for an additional FTF in 2017 before TPAC?
(TPAC is 6-10 Nov in California)
July FTF?
scribe: e.g, in Asia or
Europe
... any host volunteers?
<zkoch> Alibaba hosting in China? :)
AdamR: 17-21 July is IETF in Prague
https://www.ietf.org/meeting/99/index.html
https://github.com/w3c/webpayments/wiki#experimentation-and-implementation
"
Experimentation and Implementation"
IJ: Please update or send info to
me.
... Anybody here have stuff to link to?
https://github.com/w3c/webpayments/wiki/Networks-List
Q. Should we move this to w3.org with more limited editing?
<zkoch> +1 to w3.org
scribe: if so, I propose this URL https://www.w3.org/Payments/card-network-ids
<zkoch> LGTM
Q Has W3C management committed to long-term maintenance?
A: Yes
Q Is there any issue with strings that may be trademarked names?
IJ; Awaiting feedback from Amex
zkoch: Please create that URL and let's update the spec to reflect that.
IJ: Support for that?
<rouslan> +1
zkoch: This is implemented in Chrome and Edge
adamR: +1
<scribe> ACTION: Ian to create w3.org/Payments/card-network-ids [recorded in http://www.w3.org/2017/01/19-wpwg-minutes.html#action01]
<trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., ijacobs, ijmad).
IJ: Any other expectations to set about how the list will change?
IJ: Any issues need priority attention from the WPWG?
zkoch: We are running through
issues; we have closed some recently. I don't think there are
any main ones for discussion right now
... some things are small or updates to the spec text (e.g.,
from Boris feedback)
... nothing controversial right now
IJ: Please tee up tough questions for FTF meeting
zkoch: Ok; by then we should have a smaller list
IJ: Will the manifest spec change between now and the FTF meeting?
https://w3c.github.io/webpayments/proposals/Payment-Manifest-Proposal.html
IJ: Any update on HTTP Link
header experimentation?
... I see payment method manifest as tools or proprietary
payment method owners to say things about their method and app
support.
{IJ discusses state of payment app discussions}
IJ: We don't have concept of payment app manifest file right now; just data from the payment app for the user agent.
zkoch: What is the identifier for payment apps?
IJ: I am distinguishing (as usual) payment methods and payment apps.
<zkoch> gahhh
<zkoch> i don’t think so
<zkoch> i shall rejoin
<zkoch> sigghh
<zkoch> well, carry on, ill work on this
zkoch: I am asking a simpler question - for web-based payment apps, is there a need still for the payment app manifest file?
max: I want to say that the manifest file should support both native and web-based
Ian: +1
... the quesiton is how
Max: Maybe we reuse Web manifest file
IJ: Maybe origin information suffices; those are open conversations
<zkoch> thanks! bye!