13:24:49 RRSAgent has joined #wpay 13:24:49 logging to http://www.w3.org/2015/04/10-wpay-irc 13:25:01 rrsagent, make logs member 13:25:43 dsr has joined #wpay 13:26:12 padler has joined #wpay 13:26:54 manu /invite RRSAgent 13:27:01 invite RRSAgent 13:27:14 Zakim, this will be wpay 13:27:14 wpay matches both T&S_WEBPYMT(WPAY_USE)10:00AM and T&S_WEBPYMT(WPAY_AGENT)9:30AM 13:27:34 rrsagent, make logs public 13:27:48 rrsagent make minutes 13:28:07 zakim, who is on the call? 13:28:07 sorry, padler, I don't know what conference this is 13:28:09 On IRC I see padler, dsr, RRSAgent, dezell, chaals, Karen, ShaneM_, Zakim, halmas, dlongley, manu, wseltzer, trackbot, Ian 13:28:29 invite Zakim 13:28:39 zakim, this will be wpay 13:28:39 wpay matches both T&S_WEBPYMT(WPAY_USE)10:00AM and T&S_WEBPYMT(WPAY_AGENT)9:30AM 13:28:54 zakim, who is on the call? 13:28:54 sorry, padler, I don't know what conference this is 13:28:56 On IRC I see padler, dsr, RRSAgent, dezell, chaals, Karen, ShaneM_, Zakim, halmas, dlongley, manu, wseltzer, trackbot, Ian 13:29:14 zakim, room for 15 for 90 minutes 13:29:14 I don't understand 'room for 15 for 90 minutes', padler 13:29:25 zakim, room for 15 for 90 minutes? 13:29:27 sorry, padler; could not schedule an adhoc conference; passcode overlap; if you do not have a fixed code you may try again 13:30:32 zakim, meeting? 13:30:32 I don't understand your question, dezell. 13:30:39 jheuer has joined #wpay 13:30:47 zakim, what meeting is this? 13:30:47 I don't understand your question, dezell. 13:31:10 hmmm... 13:31:34 zakim, who is on the call? 13:31:34 has not yet started, padler 13:31:36 On IRC I see jheuer, padler, dsr, RRSAgent, dezell, chaals, Karen, ShaneM_, Zakim, halmas, dlongley, manu, wseltzer, trackbot, Ian 13:31:36 pbazin has joined #wpay 13:31:48 zakim, this will be 9729 13:31:48 ok, dsr; I see T&S_WEBPYMT(WPAY_AGENT)9:30AM scheduled to start now 13:31:57 zakim, call dsr-office 13:31:57 ok, dsr; the call is being made 13:32:44 zakim, who is on the call? 13:32:44 T&S_WEBPYMT(WPAY_AGENT)9:30AM has not yet started, padler 13:32:46 On IRC I see pbazin, jheuer, padler, dsr, RRSAgent, dezell, chaals, Karen, ShaneM_, Zakim, halmas, dlongley, manu, wseltzer, trackbot, Ian 13:34:13 zakim, who is on the phone? 13:34:13 T&S_WEBPYMT(WPAY_AGENT)9:30AM has not yet started, dezell 13:34:15 On IRC I see pbazin, jheuer, padler, dsr, RRSAgent, dezell, chaals, Karen, ShaneM_, Zakim, halmas, dlongley, manu, wseltzer, trackbot, Ian 13:34:54 zakim, this is T&S. 13:34:54 T&S matches both T&S_WEBPYMT(WPAY_USE)10:00AM and T&S_WEBPYMT(WPAY_AGENT)9:30AM, dezell 13:35:12 zakim, this is 9:30AM. 13:35:12 ok, dezell; that matches T&S_WEBPYMT(WPAY_AGENT)9:30AM 13:35:32 zakim, who is on the phone. 13:35:32 I don't understand 'who is on the phone', dezell 13:35:37 zakim, who is on the phone? 13:35:37 On the phone I see padler, +33.1.55.01.aaaa, +49.303.3.aabb, Dsr, dezell 13:36:19 zakim, 49 is jheuer. 13:36:19 sorry, dezell, I do not recognize a party named '49' 13:36:29 Topic: Agenda 13:36:31 https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0059.html 13:36:33 zakim, aabb is jheuer 13:36:33 +jheuer; got it 13:36:49 zakim, aaaa is pbazin. 13:36:49 +pbazin; got it 13:37:18 zakim, who is on the call? 13:37:18 On the phone I see padler, pbazin, jheuer, Dsr, dezell 13:37:35 Agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0059.html 13:37:42 scribenick: dezell 13:37:54 Meeting: Web Payments Payment Agent TF 13:38:08 rrsagent, make minutes. 13:38:08 I'm logging. I don't understand 'make minutes.', dezell. Try /msg RRSAgent help 13:38:16 rrsagent, make minutes 13:38:16 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell 13:39:24 +Erik 13:39:48 DE: I think this call is the place where Erik's missive needs to be addressed. 13:45:26 ShaneM has joined #wpay 13:45:28 padler has joined #wpay 13:45:35 chaals1 has joined #wpay 13:45:36 Karen_ has joined #wpay 13:45:39 zakim, who is on the call? 13:45:40 On the phone I see padler, pbazin, jheuer, Dsr, dezell, Erik 13:45:48 dlongley has joined #wpay 13:45:52 Erik has joined #WPAY 13:46:04 dezell2 has joined #wpay 13:46:08 dsr_ has joined #wpay 13:46:12 zakim, who is on the call? 13:46:12 On the phone I see padler, pbazin, jheuer, Dsr, dezell, Erik 13:46:20 David: I think the existing short list is good – X9.68, X9.73, X9.119pt2 is a good starting list. Add ISO12812 and ISO20022. 13:46:20 Erik: so this looks OK. 13:46:33 scribenick: dezell2 13:46:56 pbazin has joined #wpay 13:47:19 https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html 13:47:28 +1 to W3C playing an important role in a global payment standard 13:48:25 Topic: Discuss updates related to alignment 13:49:29 David: I think the existing short list is good – X9.68, X9.73, X9.119pt2 is a good starting list. Add ISO12812 and ISO20022. 13:49:29 Erik: so this looks OK. 13:49:46 https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html as well as any proposed updates 13:49:57 what can you do when you just see the HTML in order to get to the document? 13:50:49 pat: we've broken into 4 sections. 13:51:00 to see html: get the raw content and copy it into a local html file, then display it with your browser 13:51:26 really?! 13:51:38 s/4/several/ 13:52:35 pat: 4 sections - introduction, detailed reqs and use case illustration, references, acknowledgements. 13:52:49 s/ and/,/ 13:52:59 1.1 The Challenge with Payments on the Web 1.2 Key Principles and Goals 1.3 Elements of a Unified Web Payments Architecture 1.4 Deployment Contexts 1.5 Functional Contexts (Role) 1.6 Putting things together 13:53:16 http://htmlpreview.github.io/ 13:56:15 http://htmlpreview.github.io/?https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html 13:56:47 works for me 13:57:04 works for me 13:58:08 pat: we need to review the introduction. There are three major sections, similar to how we broke down use cases into "phases", we've taken a similar approach. 13:58:37 pat: section 1.3 describes "what we want the payment architecture to be able to do." 13:58:49 pat: section 1.4 describes "who." 13:59:36 q? 14:01:08 http://htmlpreview.github.io/?https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html 14:02:54 pat: I think the functional units 1.3.3 etc. describe the functional areas. 14:02:57 q+ 14:03:30 q+ 14:04:44 Erik: there is an interoperability risk for tokens (for example). 14:05:32 q? 14:05:40 Pat: so each functional area may need more explanation. 14:06:43 q? 14:06:48 ack dez 14:07:12 dezell: I suggest drop API from the description and replace components with "functionalities" 14:07:33 joerg: one thing that has made it possible to make progress is to use APIs. 14:08:23 q+ 14:08:27 joerg: can we describe a transaction in a way that makes use of the APIs. 14:08:36 q+ 14:08:43 ack jheuer 14:09:42 joerg: be cautious about thinking "API" or "functionality" - we need abstractions. 14:10:24 pat: so I hear "what are the core logical services that can be assembled into a payment transaction." 14:11:39 pat: Section 1.3 is the functional "whats". 14:11:43 q? 14:11:47 ack Erik 14:12:43 Erik: I think we need not to give too much wiggle room in the APIs. There shouldn't be a difference between a payment and a coupon. 14:12:53 +1 to encapsulating on an abstract level 14:13:26 pat: yes, interoperability requires very specific definitions. 14:13:40 pat: that will be addressed later in the document. 14:14:23 don't think we could understand how coupons, loyalty, etc. work - we can only try to channelize where they pass through 14:14:49 ... and how they are represented and handled by e.g. user agents 14:14:58 q? 14:18:26 +1 to aligning with use case 'phasing' 14:19:25 q? 14:19:29 ack dez 14:21:08 https://dvcs.w3.org/hg/webpayments/raw-file/default/WD/use-cases/2015-04-16/index.html 14:22:22 dezell: Ithink we need to approach both sides of ISO20022 - dictionary/message and business process definition. 14:23:10 pat: working from flows in 6.1. It's important to break these flows out, and describe where these functions might be running. 14:23:58 q? 14:24:00 q? 14:25:27 q+ 14:26:08 q? 14:26:15 ack jheuer 14:26:38 joerg: I'm starting to wonder how my initial contribution maps to what we have here. 14:26:45 zakim, mute Erik. 14:26:45 Erik should now be muted 14:27:17 joerg: my warning - given the genericness, I'm worried about boiling things down to technology. 14:27:36 joerg: I'd like to try to map what I had previously to what we have here. 14:28:00 joerg: my thinking was horizontal payment agent, but this model is very vertical. 14:28:31 joerg: should W3C actually try to solve all these problems? 14:28:36 q+ 14:28:54 joerg: I feel pressure in the payment industry to solve lots of these problems. 14:29:15 joerg: but I don't see a clear mapping. 14:30:13 pat: I can see that there might be maps to the functional goals in 1.3, informed by prototypes. 14:30:41 I'm happy to provide such input, pat 14:30:56 pat: but I'm not sure how the previous work actually solves the problems. 14:31:09 rrsagent, make minutes 14:31:09 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell2 14:31:31 chair: Patrik Adler 14:32:24 q? 14:32:31 q? 14:32:45 I dont think that we should have different flows based on the capabilities of a different device. I believe that regulatory constraints, say a transactional value of < $300 doesnt need a biometrics as part of the transaction. I believe that regulatory support should be brought in such that if a transaction is of a high value then biometrics is required 14:32:58 q+ 14:33:43 q+ 14:35:27 ack dezell 14:35:31 ack Erik 14:36:18 Erik: TecSec said don't limit payment capabilities based on the device. 14:37:07 Erik: as mobile devices get better, validation capabilities will get better. 14:37:47 q? 14:38:08 ack joerg 14:38:18 ack jo 14:38:24 ack jh 14:38:48 joerg: we have gone from an area where I could solve problems, and now we're in an area where I can't. 14:39:11 Thats why we are a group jheuer! 14:39:19 joerg: I will do my best to bring this all together. 14:39:34 zakim, close the queue 14:39:34 ok, dezell2, the speaker queue is closed 14:40:17 pat: we are calling this document "Payment Agent" but we are really describing a "Payment Architecture for the Web". 14:40:47 I'm a decomposer by heart! Hope that helps... 14:41:24 q? 14:41:39 rrsagent, make minutes 14:41:39 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell2 14:42:48 pat: big topic - more and more interest. We need to start framing this document as a unified architecture. 14:42:56 +1 to "unified architecture" 14:43:51 rrsagent, make minutes 14:43:51 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell2 14:44:34 -Erik 14:44:35 -padler 14:44:37 -dezell 14:44:37 -jheuer 14:44:40 -pbazin 14:44:58 -Dsr 14:44:59 T&S_WEBPYMT(WPAY_AGENT)9:30AM has ended 14:44:59 Attendees were padler, +33.1.55.01.aaaa, +49.303.3.aabb, Dsr, dezell, jheuer, pbazin, Erik 14:48:01 Present: pbazin,jheruer, dezell, padler, eanderson, draggett 14:48:06 rrsagent, make minutes 14:48:06 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell2 14:51:50 s/unified architecture/calling this "unified web payment architecture"/ 14:51:58 rrsagent, make minutes 14:51:58 I have made the request to generate http://www.w3.org/2015/04/10-wpay-minutes.html dezell2