16:28:10 <RRSAgent> RRSAgent has joined #apa2
16:28:10 <RRSAgent> logging to http://www.w3.org/2017/10/11-apa2-irc
16:28:15 <MichaelC> rrsagent, make log world
16:28:40 <MichaelC> meeting: APA Push/Notifications coord
16:28:46 <MichaelC> chair: Janina
16:37:22 <MichaelC> agenda+ Topic Overview & Brief Participant Intros
16:37:22 <MichaelC> agenda+	Push/Notification RFE Discussion
16:37:22 <MichaelC> agenda+ Next Steps
16:37:29 <MichaelC> scribeOptions: -final
16:39:50 <MichaelC> agenda: https://lists.w3.org/Archives/Public/public-apa/2017Oct/0017.html
16:54:18 <janina> janina has joined #apa2
16:54:28 <beverloo> beverloo has joined #apa2
16:56:09 <tink> tink has joined #APA2
16:57:00 <MichaelC> present+
16:57:05 <MichaelC> present+ Anne
16:57:10 <MichaelC> present+ Janina
16:57:25 <annevk> annevk has joined #apa2
16:59:42 <tink> tink has joined #apa2
17:00:31 <MichaelC> present+ Peter_Beverloo
17:00:44 <tink> present+
17:01:35 <chaals> chaals has joined #apa2
17:01:37 <tink> scribe: tink
17:02:21 <annevk> chaals: https://lists.w3.org/Archives/Public/public-apa/2017Oct/0017.html
17:03:14 <janina> zakim, next item
17:03:14 <Zakim> agendum 1. "Topic Overview & Brief Participant Intros" taken up [from MichaelC]
17:04:46 <tink> present- tink
17:04:49 <tink> present+ Léonie
17:04:55 <tink> rrsagent, make minutes
17:04:55 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/11-apa2-minutes.html tink
17:05:09 <janina> zakim, next item
17:05:09 <Zakim> agendum 2. "Push/Notification RFE Discussion" taken up [from MichaelC]
17:05:34 <tink> JS: A requested enhancement, originally filed against Push API.
17:05:49 <tink> ... Then at the suggestion of the editors and WebPlat chairs was filed against Notifications API.
17:05:53 <MichaelC> -> https://github.com/w3c/push-api/issues/259 Comment filed on Push API
17:06:03 <MichaelC> -> https://github.com/whatwg/notifications/issues/107 Comment filed on Web Notifications
17:06:24 <tink> ... Web Payments IG is also interested in the enhancement request.
17:08:03 <tink> ... The ability to put notifications into "Do Not Disturb (DND(" mode.
17:08:33 <tink> ... to temporarily put a hold on notifications, so they don't interupt an ongoing/current activity like completing a payment.
17:08:51 <tink> ... or to stop notifications for accessibility reasons.
17:09:31 <tink> AVK: This clarifies a lot for me.
17:09:48 <tink> ... I tend to think of APIs as a backend/development thing.
17:09:58 <tink> .. Rather than in terms of the UA/AT.
17:10:38 <tink> ... The thing to note in the spec is an accessibility consideration.
17:11:08 <janina> q?
17:11:21 <tink> LW: Are you thinking this is for the Notifications spec or the Push spec now?
17:11:39 <tink> AVK: The Push spec is not about displaying anything to the user.
17:11:44 <tink> PB: Agree.
17:11:52 <tink> ... This is better suited to the Notifications spec.
17:12:04 <tink> AVK: We can have language there around UA/AT.
17:12:18 <chaals> q+
17:12:25 <tink> ... To provide guidance based on the use cases provided.
17:12:28 <beverloo> q+
17:12:39 <janina> ack c
17:13:07 <tink> CMN: Firefox and Yandex both have mechanisms for turning off notifications for specified periods of time.
17:13:29 <janina> ack b
17:13:40 <tink> ... Providing spec guidance to recommend this sort of behaviour seems achievable.
17:13:53 <tink> PB: It would be easy for us to implement something like this in Chrome too.
17:13:53 <chaals> q+
17:14:46 <tink> ... But the browser doesn't always have control over all notifications.
17:15:24 <tink> LW: Yes, for complete DND it would need to be handled at the OS level.
17:15:29 <tink> CMN: It depends.
17:15:41 <tink> ... The browser is often the key UA.
17:16:09 <tink> ... So being able to set this in the browser isn't the complete solution, but it will cover many scenarios.
17:16:40 <janina> q?
17:16:48 <beverloo> q+
17:16:51 <janina> ack c
17:16:56 <janina> ack b
17:17:13 <tink> PB: Do you have an idea of notifications shown on any platform that come from the browser as opposed to other UA?
17:17:19 <janina> q?
17:17:25 <tink> CMN: Too many variables to know.
17:17:43 <tink> ... In my world it's a high proportion of webapps because I kill off other things fairly ruthlessly.
17:18:40 <tink> AVK: Think it would be useful to note something in the spec.
17:19:27 <janina> q?
17:19:53 <janina> zakim, next item
17:19:53 <Zakim> agendum 3. "Next Steps" taken up [from MichaelC]
17:21:00 <chaals> [In fullscreen is another time when notifications *may* not be welcome.]
17:21:28 <tink> LW: Something like the security/privacy considerations we typically include.
17:22:16 <tink> PB: As it's own section?
17:22:36 <tink> LW: Yes, but in the same place in the spec where we include other considerations like sec/priv.
17:22:58 <tink> CMN: Agree with Léonie.
17:23:14 <tink> ... It's editorial though.
17:23:21 <tink> rrsagent, make minutes
17:23:21 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/11-apa2-minutes.html tink
17:26:02 <tink> present+ Anne VK
17:26:12 <tink> rrsagent, make minutes
17:26:12 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/11-apa2-minutes.html tink
17:26:33 <tink> present+ Chaals
17:27:03 <tink> present- AnneVK
17:27:07 <tink> rrsagent, make minutes
17:27:07 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/11-apa2-minutes.html tink
17:27:29 <tink> present- VK
17:27:34 <tink> present+ Chaals
17:27:49 <tink> rrsagent, make minutes
17:27:49 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/11-apa2-minutes.html tink
17:30:50 <tink> tink has left #apa2
19:10:33 <MichaelC> zakim, bye
19:10:33 <Zakim> leaving.  As of this point the attendees have been MichaelC, Anne, Janina, Peter_Beverloo, tink, Léonie, VK, Chaals
19:10:33 <Zakim> Zakim has left #apa2
19:10:34 <MichaelC> rrsagent, bye
19:10:34 <RRSAgent> I see no action items