13:58:57 RRSAgent has joined #wpay 13:58:57 logging to http://www.w3.org/2015/10/08-wpay-irc 13:59:02 rrsagent, make logs public 13:59:09 Meeting: Web Payments IG Work Session 13:59:18 rrsagent, draft minutes 13:59:18 I have made the request to generate http://www.w3.org/2015/10/08-wpay-minutes.html manu 13:59:57 AdrianHB has joined #wpay 14:00:58 VincentK has joined #wpay 14:01:31 Laurent_ has joined #wpay 14:01:54 CyrilV has joined #wpay 14:02:19 Present+ CyrilV 14:03:39 Present+ ShaneM 14:04:04 Present+ Manu 14:04:22 Present+ Laurent_ 14:04:50 Present+ Vincent Kuntz 14:04:54 DJackson has joined #wpay 14:04:54 Present+ AdrianHB 14:05:00 present+ DJackson 14:05:23 chaals has joined #wpay 14:06:04 present+ Stephanie 14:07:01 scribe: AdrianHB 14:07:07 Agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Oct/0030.html 14:07:37 manu: majority of agenda is review of WG charter to review changes based on feedback from AC 14:07:51 steph_fetzer has joined #wpay 14:08:06 ... followed by tpac agenda discussion 14:08:12 Topic: Review Web Payments WG Charter changes 14:08:15 ... any other items? 14:08:22 Latest charter is here: http://w3c.github.io/webpayments-ig/latest/charters/payments-wg-charter.html 14:08:44 All changes since IG signed off on the charter for vote: http://manu.sporny.org/tmp/payments-wg-charter-diff.html 14:09:02 Here are all of the changes that we'll be reviewing today: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Oct/0032.html 14:09:50 manu: plan is to go through changes top to bottom. On Monday the group must decide if it supports the revised charter. 14:09:56 .. any q? 14:10:35 Starting from the top: http://manu.sporny.org/tmp/payments-wg-charter-diff.html 14:11:23 Meeting number = 647 262 873 14:12:02 manu: goals have been simplified a lot to make the document easier to digest 14:12:08 kketels has joined #wpay 14:12:30 ... if you look at diff marked version you'll see all the areas highlighted in pink have been removed 14:13:54 ... focus is on new types of payment instruments rather than customer satisfaction (hard to gauge) 14:14:19 ... also changed language from "standard" to "recommendation" 14:14:27 ... all happy with the changes? 14:14:42 +1 on those changes 14:14:50 manu: 3 major changes in scope section 14:15:21 ... simplified to say the WG will work on messages, message flows and an API 14:15:23 q+ to ask about the scope of the API work 14:15:31 q+ 14:15:40 ack ShaneM 14:15:40 ShaneM, you wanted to ask about the scope of the API work 14:16:04 shanem: it's not clear what the scope of the API work is? 14:16:23 manu: In section 3.2 the API is outlined more specifically 14:16:56 q+ 14:17:02 ... in the scope section we say that the WG will work on APIs as opposed to UIs and then defers to later section for specifics 14:17:03 ack kketels 14:18:08 kketels: seems to me this is like the orchestration of a payment interaction as opposed to an api. Seems to describe the behaviour of both ends of the API. A transaction flow. 14:18:25 manu: it is orchestrating the flow on the front-end 14:18:45 ... the flow is defined but also the API 14:19:35 ... section 3.2 says there may be many delivery mechanisms but one that will be specifically addressed is the browser 14:20:30 ... we may do server to server flows but limited to initiation through the web and if the instrument supports it notification of the payment 14:20:43 .. did that address the q? 14:21:19 kketels: agree there is a need to describe all of these things I am just not sure that I agree with the terminology 14:22:20 manu: this is sometimes confusing to people unfamiliar with W3C work. We are talking about 2 types of API. Browser based and a REST API. We're not talking about native APIs 14:22:53 ack Laurent_ 14:22:54 kketels: happy to take offline to clarify terminology 14:23:42 laurent_: there is still a use of the word "standardise" in the scope 14:23:57 manu: will change 14:24:16 ... any other comments? 14:24:20 * CyrilV has to leave the Telcon- sorry 14:25:16 manu: section 2 has new language "mediating" when referring to the user agent. is everyone happy with that language? 14:25:43 ... also that user agent is not limited only to a browser 14:25:55 laurent_: is a mobile OS a valid UA? 14:26:12 manu: I think so. It's not supposed to be limiting 14:27:12 ... big change to digital wallet definition. 14:27:35 ... (reads new definition) 14:27:45 ... any concerns over that definition? 14:28:06 q+ 14:28:21 ... section 2.2 - required capabilities has 4 major changes 14:28:32 ... first is a simplification of intro text 14:30:02 ack Laurent_ 14:30:10 padler has joined #wpay 14:30:12 ... second is related to registration. Concern that the registration is done "with" the user agent as opposed to "through" 14:31:21 laurent_: do we need to reference the @@ from the IG work as they are not referred to in the charter 14:31:30 IanJacobs has joined #wpay 14:31:42 ... we should link to the IG use cases doc or remove 14:31:45 +1 about "through" the user agent. That makes more sense to me. 14:31:46 q+ 14:31:53 ack AdrianHB 14:32:13 AdrianHB: I want to agree with Shane, we shouldn't say "with the user agent" - we should say "through the user agent" 14:32:22 +1 14:32:31 +1 14:32:55 manu: any objections to changing to through the user agent? 14:33:05 ... (notes no objections) 14:34:02 ... lots of simplification in this section (2.2) 14:34:08 .. (reads flow) 14:34:12 q+ 14:34:18 ack AdrianHB 14:34:42 q+ 14:35:07 AdrianHB: There was a bit of discussion around the flow - mentioned on the mailing list - catching up after being away for 2 weeks - that section it seems like we've narrowed ourselves down to a flow where the payee can initiate a push payment immediately as soon as they get a request from the payer. If the payer has a push payment, the payer may just make the payment. 14:36:07 AdrianHB: If the payer wants to defer the payment - the payer doesn't execute the payment - they return a response to say they want to use the 'push payment method' - that was the major change. Previous flow was always a response back first - we had language around payment completion - notifying the payer - a lot of people didn't like we didn't like the word "completion" - payment execution happening in what we were describing. 14:36:41 AdrianHB: There was a flow that was the same whether push vs. pull - now we have a flow that can change slightly - we have a good compromise here - accomodating of UX concerns from folks like browser vendors - a lot of back and forth could be bad for user experience. 14:36:47 ack VincentK 14:37:28 vincentK: in ISO20022 model the starting point is an obligation and the flow follows from that 14:37:42 ... the neg of terms is linked to this too 14:37:59 ... so there are elements that are still missing in the charter 14:39:06 ... compared to ISO20022 the whole flow is not defined 14:40:05 manu: yes, this is by design. You should still be able to execute the whole flow but only the elements of the flow that we can define technical standards for are in scope. i.e. the flow we define is a subset of the complete flow 14:40:50 ... there is a new section on deferred payment execution which allows some flexibility on the flow 14:41:23 do you (vincentk) feel that we are not going to be able to implement the ISO20022 flows? 14:42:04 vincent: there are some links that are missing between the elements? 14:42:17 manu: do you have some suggested changes that would correct this? 14:42:58 kkettels: perhaps it is unclear what the purpose of the charter is in relation to what the WG will do? 14:43:57 manu: the charter is not intended to explain the WG work in detail. the WG will look at these and make decisions about how to acheive the capabilities in the charter. W3C charters are seldom prescriptive but rather set boundaries 14:44:20 ... if the WG wants to map the flow to ISO20022 then that will be done within the group 14:44:43 q+ 14:45:01 ack shepazu 14:45:02 vincent: suppose the charter does not mention a capability and we decide that there is one required what happens? 14:45:36 shepazu: the charter is there to set the scope. to both define what the WG should and shouldn't work on. 14:46:27 ... there is a some wiggle room if the WG agrees that to achieve one of their goals some new scope is required 14:46:43 ... if the WG doesn't agree then you need to recharter 14:47:12 manu: item 10 on the list. deferred payment execution 14:47:32 ... any concerns? 14:47:46 ... next is digital wallets 14:47:58 ... definition has been shortened 14:48:07 ... (reads definition) 14:48:49 q+ 14:49:01 ack shepazu 14:49:12 ... other change is that the WG may define an API that may be used outside a user agent 14:49:39 shepazu: all the things mentioned are user agents so perhaps this langauge needs to change 14:50:21 manu: agree, will raise the change 14:51:08 ... we have been clear about what is out of scope wrt wallets 14:51:13 ... any concerns? 14:51:24 ... moving on to security and privacy 14:51:32 dezell has joined #wpay 14:51:37 ... (section 2.4) 14:51:50 Present+ dezell (briefly) 14:51:51 ... minor changes 14:52:19 I have made the request to generate http://www.w3.org/2015/10/08-wpay-minutes.html dezell 14:52:49 .. into section 3.1. minor changes. have explicitly called out that the messages we are standardising could be used in server to server comms 14:52:57 ... concerns? 14:53:08 q+ 14:53:21 ... 3.2 is a lot of simplification but again nothing controversial 14:53:49 ack ShaneM 14:54:42 shanem: (reads back end of section 3.2) suggest that this should refer to "user agents" (plural) 14:54:50 manu: will add to changes 14:56:04 ... deliverables, stating that we would like to see specs that have already had some form of review as a starting point. Usually this means going through the community groups 14:56:34 ... also changes for interoperability success criteria. sets a high bar 14:57:06 ... a number of things must be achieved to consider the work a success 14:57:43 q+ to ask about native implementation 14:57:55 ... (reads through reqs) 14:58:11 ack ShaneM 14:58:11 ShaneM, you wanted to ask about native implementation 14:58:38 q+ 14:58:47 ack ShaneM 14:58:54 ack shepazu 14:59:04 shanem: when you say native do you mean native code on the device or must it be build into the platform from the platform vendor 14:59:49 shepazu: by native, we mean something other than interpreted javascript within the browser 15:00:26 manu: the language is getting around this being acheived only through polyfills. 15:00:37 ... thats the top of the hour 15:00:49 q+ 15:01:27 ack dezell 15:01:27 shepazu: we could consider any number of apps as native. the credibility of the app is also considered. The deployment numbers of the implementation is important 15:01:49 dezell: do we need to continue this discussion on Monday 15:02:12 manu: 1 item left, will take a few minutes 15:02:53 dezell: do we need time for agenda development for the IG on Monday 15:03:16 shepazu: yes lets set some time aside 15:04:04 manu: please all note that the licensing has changed in section 9. we are using the very permissive W3C licensing. Be aware that the WG deliverables will be under a very permissive license 15:04:06 its very similar to the X Window System license. 15:04:24 ... any strong objections to the changes covered today? 15:05:38 PROPOSAL: Suggest that the new Web Payments WG Charter with the changes discussed today be sent to the Web Payments IG for approval. 15:06:03 +1 15:06:04 +1 15:06:05 +1 15:06:05 +1 15:06:10 +1 15:06:49 RESOLVED: Suggest that the new Web Payments WG Charter with the changes discussed today be sent to the Web Payments IG for approval. 15:06:50 +1 15:07:17 rrsagent, draft minutes 15:07:17 I have made the request to generate http://www.w3.org/2015/10/08-wpay-minutes.html manu 15:07:54 Changes suggested by the group: 15:07:57 1. Remove last 'standardize' 15:07:57 2. Link payment phases to IG use cases document for context 15:07:57 3.Change "with the user agent" to "through the user agent" 15:07:57 4. Make disctinction between a user agent and a service - Relation to  Digital Wallets 15:07:58 5. "mobile device's user agent." -> "user agents" 15:08:01 rrsagent, draft minutes 15:08:01 I have made the request to generate http://www.w3.org/2015/10/08-wpay-minutes.html manu 15:42:15 github-bot has joined #wpay 15:42:15 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06master: 02https://github.com/w3c/webpayments-ig/commit/f7efa83895b95fc162e59eef009d12178761b955 15:42:15 13webpayments-ig/06master 14f7efa83 15Ian Jacobs: Edit based on Mozilla review... 15:42:16 github-bot has left #wpay 15:42:50 github-bot has joined #wpay 15:42:50 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06gh-pages: 02https://github.com/w3c/webpayments-ig/commit/ef11a444f29b886d78e98c88b5a5fea32ffd97d7 15:42:50 13webpayments-ig/06gh-pages 14ef11a44 15Ian Jacobs: Merge branch 'master' into gh-pages 15:42:51 github-bot has left #wpay 15:43:10 dezell has left #wpay 16:04:16 github-bot has joined #wpay 16:04:16 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06master: 02https://github.com/w3c/webpayments-ig/commit/044280085865a2503d01ddab2c7847ab00cebf9e 16:04:16 13webpayments-ig/06master 140442800 15Ian Jacobs: Some changes based on IG review on 2015-10-08... 16:04:17 github-bot has left #wpay 16:04:52 AdrianHB has joined #wpay 16:06:51 shepazu_ has joined #wpay 16:07:20 github-bot has joined #wpay 16:07:20 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06gh-pages: 02https://github.com/w3c/webpayments-ig/commit/8fbfae6f06684ada95ea9bbd6564a18d28f1193e 16:07:20 13webpayments-ig/06gh-pages 148fbfae6 15Ian Jacobs: Merge branch 'master' into gh-pages 16:07:21 github-bot has left #wpay 16:08:08 shepazu__ has joined #wpay 16:44:15 dbaron has joined #wpay 17:03:10 Zakim has left #wpay 17:45:32 github-bot has joined #wpay 17:45:32 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06master: 02https://github.com/w3c/webpayments-ig/commit/590f08bb929fbc2d6d69097de44f735a5d683a2b 17:45:32 13webpayments-ig/06master 14590f08b 15Ian Jacobs: Other edits based on IG review... 17:45:33 github-bot has left #wpay 17:46:28 github-bot has joined #wpay 17:46:28 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06gh-pages: 02https://github.com/w3c/webpayments-ig/commit/9670ab19b5ade1cc1a08747da80ec84b51a34079 17:46:28 13webpayments-ig/06gh-pages 149670ab1 15Ian Jacobs: Merge branch 'master' into gh-pages 17:46:29 github-bot has left #wpay 17:50:16 github-bot has joined #wpay 17:50:16 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06master: 02https://github.com/w3c/webpayments-ig/commit/ba5f11ab80bd2702663e3d1986757fbc9491b326 17:50:16 13webpayments-ig/06master 14ba5f11a 15Ian Jacobs: Tweak language 17:50:17 github-bot has left #wpay 17:50:37 github-bot has joined #wpay 17:50:37 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06gh-pages: 02https://github.com/w3c/webpayments-ig/commit/7dada1a7108ee59bdfaddafc4ff7f9f8dff95a4a 17:50:37 13webpayments-ig/06gh-pages 147dada1a 15Ian Jacobs: Merge branch 'master' into gh-pages 17:50:38 github-bot has left #wpay 18:40:49 github-bot has joined #wpay 18:40:49 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06master: 02https://github.com/w3c/webpayments-ig/commit/5fc866cfc6f4167c0329008f550c34456db575ab 18:40:49 13webpayments-ig/06master 145fc866c 15Ian Jacobs: Editorial fix 18:40:50 github-bot has left #wpay 18:41:12 github-bot has joined #wpay 18:41:12 [13webpayments-ig] 15ianbjacobs pushed 1 new commit to 06gh-pages: 02https://github.com/w3c/webpayments-ig/commit/10b2697102ee2f67d028093ffbdbc3e8e45c6934 18:41:12 13webpayments-ig/06gh-pages 1410b2697 15Ian Jacobs: Merge branch 'master' into gh-pages 18:41:13 github-bot has left #wpay 19:02:06 yaso has joined #wpay 19:16:43 AdrianHB has joined #wpay 20:34:51 Karen has joined #wpay 20:36:56 AdrianHB has joined #wpay 20:39:07 Karen has joined #wpay 21:11:59 yaso has joined #wpay 21:21:01 dbaron has joined #wpay 21:48:43 yaso has joined #wpay 22:22:45 chaals has joined #wpay 22:32:51 yaso has joined #wpay 23:02:56 AdrianHB has joined #wpay 23:04:20 Karen has joined #wpay