16:58:39 RRSAgent has joined #digitaloffers 16:58:39 logging to http://www.w3.org/2017/02/13-digitaloffers-irc 17:00:30 ltoth has joined #digitaloffers 17:00:55 adamlake has joined #digitaloffers 17:01:30 Adam Lake + present 17:03:14 present+ AdamLake 17:03:17 present+ Itoth 17:03:22 present+ Ian 17:03:44 Meeting: Digital Offers Community Group 17:03:47 Chair: ltoth 17:03:49 Scribe: Ian 17:03:50 Agenda: https://lists.w3.org/Archives/Public/public-digitaloffers/2017Feb/0006.html 17:04:04 Ian has changed the topic to: 13Feb agenda => https://lists.w3.org/Archives/Public/public-digitaloffers/2017Feb/0006.html 17:04:05 dezell has joined #digitaloffers 17:05:02 Present+ dezell 17:05:20 zakim, who's here? 17:05:20 Present: AdamLake, Itoth, Ian, dezell 17:05:22 On IRC I see dezell, adamlake, ltoth, RRSAgent, Zakim, dlongley, manu, adam, ShaneM, Ian 17:06:26 present+ aylver 17:06:32 andrelyver_ has joined #digitaloffers 17:06:41 present+ alyver 17:06:53 Topic: Use cases 17:07:28 Changes from Kylie: 17:07:29 https://www.w3.org/community/digitaloffers/wiki/index.php?title=Discussion_Topics&diff=89&oldid=86 17:20:23 kylie_davies has joined #digitaloffers 17:21:35 q+ 17:21:52 q+ 17:21:56 ack dez 17:22:23 IJ: One thought I have on redemption control; I wonder whether we should be thinking about a capability where the merchant sends info back through the browser that is given to the payment app, to enable the payment to update coupon state. 17:22:40 I think rejection of a coupon getting sent back to the user's payment app is a good idea. 17:23:34 present+ Kylie 17:23:44 q? 17:23:49 ack lt 17:26:26 q+ 17:27:25 ack adam 17:27:26 q? 17:27:49 adamlake: +1 to a common theme of merchant-provided information that can help the payment app notify the user and keep a healthy view of offers 17:28:02 Topic: Based on customer segment/expired coupon 17:30:34 ltoth: Merchant doesn't get reimbursed, right? 17:30:35 q? 17:30:39 q 17:30:41 kylie_davies: correct 17:30:44 q+ 17:31:13 ack d 17:32:59 q? 17:33:05 q+ 17:33:10 q+ 17:33:33 ack de 17:33:42 IJ: Not sure what this use case is adding. If this is just a business decision, may be out of scope 17:33:51 ...also, what information in the protocol is needed for this? 17:35:27 q+ 17:36:22 ack lt 17:36:29 IJ: I don't think validation in scope. Merchants can do lots of things; I think we should focus on how people get data not what they do with it 17:36:46 ltoth: Maybe this is part of settlement - if merchant overrides then merchant is on the hook 17:36:54 q? 17:36:56 ack de 17:37:01 ...could talk about this there and label it as out of scope 17:38:44 ltoth: I think validation is important and should be in scope 17:39:36 topic: Individualized Coupon Issuance 17:42:20 IJ: Very hard when we do strong identity. (e.g., real human being v. device? one per family?) 17:42:43 adamlake: Agree with the concern 17:42:47 IJ: Any work going on in that space? 17:45:04 q+ 17:45:41 ack adam 17:46:02 adamlake: I think having a coupon being able to be reduced once by anyone and once by a particular person are very different (the former is easier) 17:47:29 q? 17:47:42 topic: Outreach 17:48:14 dezell: Participation has gone down a bit; what is status of our outreach to people? 17:48:28 ...we also need to figure out our FTF meeting agenda 17:49:04 ltoth: Let's discuss offline 17:53:43 {We continue to walk through the use cases} 17:56:14 Topic: Merchant coupon reimbursement in sale 17:57:19 IJ: I continue to think that settlement is far away from what we should do. 17:57:44 Topic: next meeting 17:57:49 27 February 17:58:02 I have made the request to generate http://www.w3.org/2017/02/13-digitaloffers-minutes.html Ian 18:05:23 reagent, set logs public 18:05:30 RRSAGENT, set logs public 19:59:08 Zakim has left #digitaloffers