Web Payments Working Group Teleconference -- 12 Nov 2015

<trackbot> Date: 12 November 2015

<manu> Telecon dial-in: +1-617-324-0000 US Toll Number

<AdrianHB> WebEx: https://mit.webex.com/mit/j.php?MTID=m7fdd2026b815736c50eb6592744f3e6e

<scribe> scribe: Ian

<scribe> Agenda: https://github.com/w3c/webpayments/wiki/Agenda---12th-November-2015-at-17:00-UTC

Introductions

Welcome new participants from: Deque Systems, HM Government, Inswave Systems, Qihoo 360

scribe: will set aside time at the end of the call to introduce themselves, or people can send to the mailing list as well

Technical Work

<AdrianHB> https://github.com/w3c/webpayments/wiki/RegistrationTypes

<Zakim> manu, you wanted to add something to the Agenda - logistics around presenting "new material" - at operations/tech work?

Manu: People are missing work; need to figure out operations

(IJ thinks that falls into Nick's action)

Manu: I don't think what we proposed at the FTF was thought-out

AdrianHB: Can you provide color as to what was done that slipped by the group.

Manu: Where does discussion happen?

AdrianHB: People can put comments in the wiki about their edits, but I suggest that when someone has an action, they post a mail to the mailing list saying that they have.
... and also that people go to the github page for the group and set up notification settings
... note that wiki is github-repo backed

<zkoch> For those that don’t know, the standard way of getting notifications is to “watch” the repo

MattS: +1 to that proposal...I didn't know this was there so want to review it.

<Zakim> manu, you wanted to forsee chaos.

Manu: Typically W3C groups use the mailing list to sync up
... we are proposing multiple mechanisms to sync up (mail + wiki + tracker + github repo)
... I think that it will be complex to keep people subscribed to multiple sources

shepazu: We are getting used to github as the place for doing specs.
... it's becoming more common and also we are getting a lot of issues that way
... the way we've dealt with it is to have the issue reflected on the mailing list
... I'll make sure that's done over the next few days

<manu> +1 to getting everything reflected to the mailing lists.

shepazu: I'd be reluctant to set up a policy or a non-automatic convention for how we are reflecting these things

(No notification list)

(Please just use our list)

<manu> Ian: Nick still has an action to see how we should operate - send suggestions to the mailing list.

<manu> Ian: Let's do technical work on this call.

<manu> Ian: Clearly, this is pressing.

AdrianHB: I wanted to suggest that we have a notification list...Ian shot me down

<nicktr> is in a very noisy environment - but this is useful feedback

AdrianHB: the reason I suggested that is that I think we are seeking a balance between spam on the list and filtering out things we need to look at.
... AdrianB pointed out that if we are notifying everything from github, this needs to be a separate list.
... I leave this as a suggestion for Nick's consideraiton

<Zakim> AdrianHB, you wanted to propose a notifications list

<zkoch> Put me in the bucket of “forgot to watch repo so missed adrian’s update”. Oops…

shepazu: We can simply have github issues reflected on mailing list (not all github events)
... I think we should just go ahead and get issues reflected to the mailing list.
... if we find that this is unworkable, we can revisit the decision

AdrianHB: +1
... Back to Adrian's registration notes

Manu: I think we are doing a bit too much handwaving for the registration mechanism. We need to determine whether something is in scope for our work.
... I would argue that registration becomes problematic if you register all your payment instruments with one brand of browser and you can't take them with you to another browser.
... If the API call is successful, where is the data stored? Or how does data get moved from one browser to another?

AdrianHB: I'm hearing there is more conversation needed beyond enumerating registration types. Is this a correct first step?

Manu: Yes, but we need to add to the wiki.
... A concern section would be helpful - is the group going to look at portability of registration data

dlongley: We need to separate interests (1) what does the UA need? (2) How do we make it available to the UA?
... if we break it down that way, that will facilitate our discussion

<zkoch> +1 to what dlongley said

AdrianHB: My suggestion is that we have some good input. How to capture in the wiki?

<manu> +1 to capturing it in the wiki and expanding on it, and moving on to next agenda item.

AdrianHB: Wiki page; open for people to make changes

Flows

AdrianHB: MattS has agreed to write up legacy flows and lead discussion. How goes it?

MattS: Regarding Action-3

https://www.w3.org/Payments/WG/track/actions/3

scribe: I have done 2 of 3...also existing paypal flows

MattS: I've also received some comments I'll need to respond to

Regarding Action-4

https://www.w3.org/Payments/WG/track/actions/4

<AdrianHB> https://github.com/w3c/webpayments/wiki/Flows

MattS: I've not yet been able to engage with other people who expressed interest in flows during TPAC.
... some have not been able to join the WG yet.
... so no progress on Action 4 but I will chase up people tomorrow.

(Manu has some comments on how the flows are built)

<ShaneM> Looking forward to it!

Manu: Hope is to be able to pull flows into documentation
... using respec
... I think we've made good progress on integration in a way that works for people.
... there's a desire by at least one spec editor to try to work it flows into the document, with annotations

<manu> I've added "Concerns" to wiki page - https://github.com/w3c/webpayments/wiki/RegistrationTypes#concerns

Manu: will use work Matt did at TPAC as basis.

MattS: I have a question...Where should flows be mastered and where should comments be sent?

AdrianHB: I have a few quick points to make before I have to run
... I will help document one of the flows (as listed in the wiki)
... Manu, can you add details to the flows page about how to generate SVG from source?

<manu> ACTION: Manu to add details to flows wiki page on generating SVG from PlantUML source. [recorded in http://www.w3.org/2015/11/12-wpwg-minutes.html#action01]

<trackbot> Created ACTION-6 - Add details to flows wiki page on generating svg from plantuml source. [on Manu Sporny - due 2015-11-19].

<ShaneM> I will put the info into the flows wiki if Manu doesn't have time.

AdrianHB: There is a question about how these flows map to the proposals. I propose we don't do that until we have confirmation from Zach and Manu that changes from TPAC discussion have been incorporated

MattS: Ok, happy to hold off

Mountie: Can we add flows (e.g., Samsung pay)?

AdrianHB: Please do. Add your name and which flow(s) to the wiki.

https://github.com/w3c/webpayments/wiki/Flows#flows-to-be-analysed-with-assignee

MattS: Please also let me know you've signed up to do flow(s)

Operations

AdrianHB: Pressing, so I will follow up with Nick

Next call(s)

AdrianHB: Mountie is here...we want an Asia call but to date there is only Mountie and me. Until we get 5 people interested I think we will not have a call in a favorable time zone to Asia.

<ijmad> thinking there are some other flows not on that list that might be useful such as Direct Debits (UK/EU) through a provider like GoCardless or ACH (US) through providers

<manu> Ian: Is the WG call weekly?

IJ: Note US thanksgiving 26 Nov.

<scribe> ACTION: AdrianHB to work with NickTR on potential agenda for 19 November and possibly set up a call [recorded in http://www.w3.org/2015/11/12-wpwg-minutes.html#action02]

<trackbot> Error finding 'AdrianHB'. You can review and register nicknames at <http://www.w3.org/Payments/WG/track/users>.

RESOLUTION: No WG call on 26 November

<Zakim> manu, you wanted to suggest flows are mastered in github repo for WPWG and questions are raised via issues (which will be mirrored to the mailing list)

Manu: I think flow masters are in github repo and issues on github issue tracker. And ensure those issues are mirrored to the mailing list.
... if we use that mechanism, that aligns with proposal from earlier on the call
... regarding this call, I think we need to talk about other things this group will need to do (e.g., messages spec)
... can we add an agenda item for that?

AdrianHB: I think if there is stuff we need to discuss that's not on the agenda, let's put on the agenda before the call.
... I suggest Manu's topic be on a next agenda, with context created either via wiki or issues
... that's also perhaps enough to schedule a 19 Nov call

RESOLUTION: Next call is 19 November.

<zkoch> +1

- DRAFT -

Web Payments Working Group Teleconference

12 Nov 2015

Attendees

Contents

Introductions

Technical Work

Flows

Operations

Next call(s)

Summary of Action Items

Scribe.perl diagnostic output