13:49:45 RRSAgent has joined #dap 13:49:45 logging to http://www.w3.org/2013/10/03-dap-irc 13:49:47 RRSAgent, make logs world 13:49:47 Zakim has joined #dap 13:49:49 Zakim, this will be DAP 13:49:49 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 11 minutes 13:49:50 Meeting: Device APIs Working Group Teleconference 13:49:50 Date: 03 October 2013 13:50:12 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0009.html 13:50:27 fjh has changed the topic to: dap 3279 ; agenda http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0009.html 13:50:43 Chair: Frederick_Hirsch 13:50:47 Present+ Frederick_Hirsch 13:50:51 Josh_Soref has joined #dap 13:56:35 nwidell has joined #dap 13:58:15 igarashi has joined #dap 13:58:57 Regrets+ Giri_Mandyam 14:00:18 UW_DAP()10:00AM has now started 14:00:26 +??P4 14:01:17 +[IPcaller] 14:01:24 -??P4 14:01:26 zakim, [IPcaller] is me 14:01:26 +fjh; got it 14:01:30 zakim, who is here? 14:01:30 On the phone I see fjh 14:01:32 On IRC I see igarashi, nwidell, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:01:45 +??P12 14:01:50 Zakim, ??P12 is me 14:01:51 +dom; got it 14:02:16 jcdufourd has joined #dap 14:02:21 +??P11 14:02:27 nwidell has left #dap 14:02:51 zakim, who is making noise? 14:02:52 Zakim, ??P11 is igarashi 14:02:53 +igarashi; got it 14:02:55 +Josh_Soref 14:02:57 LisaDeLuca_IBM has joined #dap 14:03:02 fjh, listening for 10 seconds I heard sound from the following: fjh (9%), dom (31%) 14:03:04 Zakim, mute me 14:03:06 Josh_Soref should now be muted 14:03:06 scribe: Josh_Soref 14:03:21 Zakim, who is on the call? 14:03:21 On the phone I see fjh, dom, igarashi, Josh_Soref (muted) 14:03:25 +Tatsuya_igarashi 14:03:33 +??P16 14:03:37 zakim, ??P16 is me 14:03:37 +anssik; got it 14:03:43 + +1.415.787.aaaa 14:03:47 Present+ Lisa_DeLuca 14:03:50 Present+ Anssi_Kostiainen 14:04:01 s/+Tatsuya_igarashi// 14:04:14 Zakim, aaaa is LisaDeLuca_IBM 14:04:15 +LisaDeLuca_IBM; got it 14:04:24 Topic: Welcome, agenda review, scribe selection, announcements 14:04:28 zakim, who is here? 14:04:28 On the phone I see fjh, dom, igarashi, Josh_Soref (muted), anssik, LisaDeLuca_IBM 14:04:30 On IRC I see LisaDeLuca_IBM, jcdufourd, igarashi, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:04:36 Zakim, LisaDeLuca_IBM is LisaDeLuca_(IBM) 14:04:36 +LisaDeLuca_(IBM); got it 14:04:43 +??P25 14:04:45 fjh: welcome everyone 14:04:52 CR drafts of Ambient Light Events and Proximity Events published 1 Oct, http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0001.html 14:05:14 ... thanks to anssik for working on 14:05:20 Zakim, who is making noise? 14:05:29 fjh: i wonder if we should cancel the call the week of TPAC 14:05:30 Josh_Soref, listening for 10 seconds I heard sound from the following: 7 (16%), fjh (63%) 14:05:34 +1 to cancel call during TPAC week 14:05:35 anssik: i think we should cancel 14:05:41 RESOLUTION: Cancel DAP teleconference 14 November 14:05:46 Present+ JeanClaude_Dufourd 14:05:51 (week of TPAC) 14:05:59 zakim, who is here? 14:05:59 On the phone I see fjh, dom, igarashi, Josh_Soref (muted), anssik, LisaDeLuca_(IBM), ??P25 14:06:01 On IRC I see jcdufourd, igarashi, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:06:04 LisaDeLuca_IBM has joined #dap 14:06:17 zakim, P25 is jcdufourd 14:06:17 sorry, jcdufourd, I do not recognize a party named 'P25' 14:06:23 Zakim, ??P25 is jcdufourd 14:06:23 +jcdufourd; got it 14:06:27 s/zakim, P25 is jcdufourd// 14:06:34 topic: Minutes Approval 14:06:37 Approve minutes from 26 September 2013 14:06:38 http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/att-0060/minutes-2013-09-26.html 14:06:46 RESOLUTION: Minutes from 26 September 2013 are approved 14:06:54 topic: Proximity and Light 14:06:57 CR drafts published 1 Oct, 14:06:57 http://www.w3.org/TR/2013/CR-ambient-light-20131001/ 14:06:58 http://www.w3.org/TR/2013/CR-proximity-20131001/ 14:07:07 ISSUE-153? 14:07:07 ISSUE-153 -- Would interface and event name change be possible and clearer -- pending review 14:07:07 http://www.w3.org/2009/dap/track/issues/153 14:07:28 fjh: we got feedback asking about changing the name 14:07:31 q+ 14:07:38 ack anssik 14:07:40 ... but we had feedback from Mozilla that they have shipped it and aren't willing to change 14:07:49 anssik: Mozilla has a point 14:07:57 ... this is about naming (bike-shedding), not functionality 14:08:10 ... I wonder if the person w/ the feedback had a proposal 14:08:16 fjh: i proposed an alternative 14:08:25 ... the feedback was just that the name didn't match functionality 14:08:50 ... but it isn't worth cycling around on this given Mozilla's feedback 14:08:57 anssik: regardless of the name, someone will be unhappy 14:09:04 ... we have Device-prefix and User-prefix 14:09:10 ... we have getUserMedia 14:09:16 ... we have DeviceOrientation 14:09:28 ... i agree they don't clearly match what the api is about but... 14:09:31 fjh: i agree 14:09:40 ... i'd suggest we close the issue out 14:09:42 Josh_Soref: +1 14:09:57 ... i'll send a response 14:10:05 s/.../fjh:/ 14:10:21 ISSUE-153: feedback on list from Mozilla that too late to change naming for implementation, WG agrees to close issue with no change 14:10:21 Notes added to ISSUE-153 Would interface and event name change be possible and clearer. 14:10:26 close ISSUE-153 14:10:26 Closed ISSUE-153. 14:10:57 action: fjh to respond regarding ISSUE-153 that it is closed 14:10:57 Created ACTION-663 - Respond regarding issue-153 that it is closed [on Frederick Hirsch - due 2013-10-10]. 14:11:34 fjh: we need to figure out our next steps for Proximity and Light 14:11:42 ... later in the agenda, we can do test plan 14:11:47 ... anything else to talk about now? 14:11:57 anssik: wrt Tests, iirc i've asked our QA to review them 14:12:05 ... i'll need to refer back to the repo to find out what has been done 14:12:16 dom: there was a review of the existing TCs 14:12:26 ... and i reviewed them before merging 14:12:31 ... the existing TCs match the spec 14:12:35 ... but they don't completely cover it 14:12:43 ... there's very little about semantics of the event 14:12:49 ... that there is/isn't an object 14:12:55 ... that there is/isn't a level of light 14:13:06 ... I understand that you guys were going to look into contributing test cases 14:13:12 ... but i don't know if there are specific plans 14:13:29 anssik: i'm trying to find the initial pull-request where the comments were 14:13:47 fjh: i assume your team knows it's in CR now 14:13:53 ... and i think they should review the plans 14:13:57 -> https://github.com/dontcallmedom/web-platform-tests/pull/2 Pull Request for proximity events 14:13:57 anssik: i think they're informed 14:14:06 ... QA follows the list 14:14:18 -> https://github.com/dontcallmedom/web-platform-tests/pull/1 Pull Request for ambient light events 14:15:05 anssik: those are the changes 14:15:13 ... our QA looked at them 14:15:17 ... to look for gaps 14:15:21 ... i tasked them to fill in the gaps 14:16:13 dom: i can't recall if there was a private thread or a thread on the public test list 14:16:23 anssik: i'll follow 14:16:25 ... up 14:16:33 s/on the public test list/on the main repo issues list/ 14:16:35 ... our QA guy said he'd like to add new tests 14:16:55 ... let's leave this open 14:17:00 ... we'll come back w/ more tests 14:17:05 fjh: any idea when that will happen? 14:17:20 anssik: there's a holiday period this week in China 14:17:28 ... but definitely by the end of the year 14:17:33 ... i'd assume w/in a couple of weeks 14:17:57 ... i'll follow up on the thread 14:18:03 fjh: it'd be helpful if you could share where we're at 14:18:17 topic: Vibration 14:18:23 ISSUE-146? 14:18:23 ISSUE-146 -- Add vibration strength control -- open 14:18:23 http://www.w3.org/2009/dap/track/issues/146 14:18:30 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0019.html 14:18:41 Zakim, who is making noise? 14:18:52 Josh_Soref, listening for 10 seconds I heard sound from the following: fjh (34%) 14:19:02 LisaDeLuca_IBM: There was feedback in cordova that iOS doesn't support vibration strength 14:19:11 fjh: so you support deferring it 14:19:14 LisaDeLuca_IBM: yes 14:19:27 fjh: and anssik, you were the same? 14:19:43 Josh_Soref: i also support deferring 14:20:03 fjh: and anssik was asking for other feedback 14:20:19 proposed RESOLUTION: defer strength until future version 14:20:30 Josh_Soref: +1 14:20:38 RESOLUTION: defer strength until future version 14:20:50 ISSUE-149? 14:20:50 ISSUE-149 -- handling of long vibration list - truncate or no vibration at all -- open 14:20:50 http://www.w3.org/2009/dap/track/issues/149 14:21:06 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0012.html 14:21:15 fjh: i think we should put this in the spec 14:21:50 LisaDeLuca_IBM_ has joined #dap 14:21:57 defer until next week, but proposal is to adopt resolution provided by anssi 14:22:06 Josh_Soref: i wonder if someone does something like: [1, 2, 3, 4, 1000, 2, 1000] 14:22:21 ... if all you get is 1,2,3,4 then you might totally miss the goal of the thing 14:22:31 ISSUE-150? 14:22:31 ISSUE-150 -- Should vibration be additive when multiple instances, e.g. iframes -- open 14:22:31 http://www.w3.org/2009/dap/track/issues/150 14:23:02 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0003.html 14:23:12 anssik: back to Josh_Soref 's question 14:23:25 ISSUE-150: proposal related to ACTION-652 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0003.html 14:23:25 Notes added to ISSUE-150 Should vibration be additive when multiple instances, e.g. iframes. 14:23:26 ... i don't have a position 14:24:01 Josh_Soref: on additive 14:24:18 anssik: i was still thinking about 149 14:24:26 fjh: let's move on to 150 14:24:47 Josh_Soref: on additive ... my concern is that the timing is fairly random 14:25:23 this one makes sense to me, please review ,we will decide next week for ISSUE-150 14:25:24 Josh_Soref: so yes, i think i support anssik 's proposal 14:25:38 anssik: iOS is probably the most limited 14:25:52 Josh_Soref: i don't think the underlying system matters so much 14:25:58 Zakim, unmute me 14:25:58 Josh_Soref should no longer be muted 14:26:27 ... as long as the underlying system has a stop and insert replacement 14:26:31 ... you can always emulate this 14:26:44 ... but the timing of the overlapping things will be fairly inconsistent 14:26:51 ... and impossible for a user to recognize 14:27:18 fjh: where you layer it might have an effect 14:27:29 ... os/browser-engine/browser 14:27:44 fjh: i think the proposal is good 14:27:47 Josh_Soref: me too 14:27:48 ISSUE-152? 14:27:48 ISSUE-152 -- Vibration API events start/pause/resume/cancel and status listener start/pause/resume/cancel/finish -- pending review 14:27:48 http://www.w3.org/2009/dap/track/issues/152 14:28:12 fjh: i think i can just close this 14:28:13 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0004.html 14:29:19 Josh_Soref: would it tell the app when it's not-currently-vibrating-but-will-shortly 14:29:26 fjh: it isn't speced out 14:29:32 http://lists.w3.org/Archives/Public/public-device-apis/2012Nov/0015.html 14:29:34 +Cathy 14:29:52 earlier similar feedback: http://lists.w3.org/Archives/Public/public-device-apis/2012Nov/0015.html 14:29:55 ... i think we could ask for a more detailed proposal 14:30:23 Josh_Soref: i think we'd need UCs 14:30:32 fjh: do we have accurate enough timings to be able to do anything? 14:30:37 Josh_Soref: i doubt we could 14:30:48 ... my guess is that you won't be able to respond fast enough to do something useful 14:30:49 +1 for deferring to v2 14:30:57 Josh_Soref: +1 for deferring 14:31:07 fjh: it seems the UC would have to be specifically spelled out 14:31:21 ... proposing a change could result in more complexity without solving the problem 14:31:28 +LisaDeLuca_(IBM).a 14:31:54 RESOLUTION: Defer ISSUE-152 14:32:51 ACTION: fjh to respond indicating ISSUE-152 deferred, suggesting more detailed use case/requriements for v.next 14:32:52 Created ACTION-664 - Respond indicating issue-152 deferred, suggesting more detailed use case/requriements for v.next [on Frederick Hirsch - due 2013-10-10]. 14:33:08 topic: Network Service Discovery 14:33:28 zakim, who is here? 14:33:28 On the phone I see fjh, dom, igarashi, Josh_Soref, anssik, LisaDeLuca_(IBM), jcdufourd, Cathy, LisaDeLuca_(IBM).a 14:33:30 On IRC I see LisaDeLuca_IBM_, jcdufourd, igarashi, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:33:32 fjh: Cathy is here, richt is not 14:33:41 ISSUE-154? 14:33:41 ISSUE-154 -- Security approach -- open 14:33:41 http://www.w3.org/2009/dap/track/issues/154 14:33:43 ... i added a new issue 14:33:52 ... i'm trying to capture what we've raised and what we've resolved 14:34:04 RRSAgent, draft minutes 14:34:04 I have made the request to generate http://www.w3.org/2013/10/03-dap-minutes.html Josh_Soref 14:34:19 fjh: it starts w/ a good message by Youenn Fablet 14:34:23 Cathy has joined #dap 14:34:23 Youenn Fablet sent good summary linking to external implementer discussions 14:34:49 fjh: we're having the discussion on the list 14:34:59 ... there are two conclusions that i'm drawing 14:35:11 ... one is deciding what to do on CORS 14:35:19 ... richt has a proposal that came out just before the call 14:35:26 http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0014.html 14:35:56 ... the second topic is how much requirement do we have to support legacy devices 14:36:05 Zakim, who is making noise? 14:36:15 Josh_Soref, listening for 10 seconds I heard sound from the following: fjh (20%) 14:36:16 jcdufourd: if we don't support legacy devices 14:36:32 ... when NFC comes up in browser 14:36:37 s/NFC/NSD/ 14:36:40 q+ 14:36:44 ... if there are no supported devices 14:36:49 ... no one will be interested in using it 14:37:07 ... we need to design a standard that would be adopted 14:37:17 fjh: that's a question the implementers raised 14:37:25 ... questions about security 14:37:48 ... there's also a question about usefulness 14:38:03 ... i sent a question about 14:38:16 ... what if i have a router which is insecure, it supports Router and Media 14:38:23 ... and you attack the media bit, take over the router 14:38:32 ... and then control DNS and attack other things 14:38:38 ... it seems to be a real case 14:38:51 ... there's a uPNP link pointing to papers identifying insecurities 14:38:55 ... i'm not sure CORS helps 14:39:04 ... i'm not sure it prevents an attack post discovery phase 14:39:13 ... maybe whitelist-blacklist will work 14:39:22 ... i dunno 14:39:24 q- 14:39:30 jcdufourd: the UCs i see that are useful for bootstrapping 14:39:55 scribe: fjh 14:40:07 Zakim, mute me 14:40:07 Josh_Soref should now be muted 14:40:49 jcdufourd: only need to discovery services specific to your need 14:41:11 … permission to discover by user limits what can be discovered 14:41:26 … whitelist should only allow discovery of these two services by one app 14:41:34 s/app/webapp/ 14:41:46 … this could be more of a requirement for more UI 14:42:00 … this could be totally safe 14:43:06 fjh: there's the possibility that a malicious web site could pretend to be friendly 14:43:15 s/Josh_Soref/scribe/ 14:43:27 ... get permission for a reasonable service 14:43:27 s/Josh_Soref/scribe/ 14:43:37 ... attack the buggy part of the reasonable service 14:43:39 s/Josh_Soref/scribe/ 14:43:47 ... and then having taken over the device 14:43:48 s/Josh_Soref/scribe/ 14:43:55 ... abuse the more valuable services (router) 14:43:56 s/Josh_Soref/scribe/ 14:47:30 dom: we should re-use web technologies such as CORS as much as possible and also consider whitelisting to enable legacy to the extent possible 14:47:57 … also we cannot address all security issues ,e.g. regarding the router issue, but we can note in security considerations 14:48:13 fjh: agree we must address the implementer concerns re security in the security considerations section 14:48:37 … even if to only highlight and describe the issue and outline potential mitigations 14:49:32 Josh_Soref: we could propose banning all services from devices which advertise scary services 14:50:31 q? 14:51:07 +q 14:51:15 fjh: a number of issues related to network service discovery are open, we should attempt to resolve on the list 14:51:22 ack igarashi 14:52:00 igarashi: CORS specific to web applications due to HTTP header usage 14:52:09 … so CORS helps 14:52:51 ISSUE-130? 14:52:51 ISSUE-130 -- Enable variety of protocols (e.g. UPnP, Bonour) with protocol independent developer code -- open 14:52:51 http://www.w3.org/2009/dap/track/issues/130 14:52:58 ISSUE-131? 14:52:58 ISSUE-131 -- Support UPnP device discovery by Device Type? -- open 14:52:58 http://www.w3.org/2009/dap/track/issues/131 14:53:05 ISSUE-133? 14:53:05 ISSUE-133 -- Fix UPnP events subscription and unsubscription -- open 14:53:05 http://www.w3.org/2009/dap/track/issues/133 14:53:14 ISSUE-134? 14:53:14 ISSUE-134 -- Rename NetworkServices and NetworkService events -- open 14:53:14 http://www.w3.org/2009/dap/track/issues/134 14:53:29 close ISSUE-134 14:53:29 Closed ISSUE-134. 14:53:36 ISSUE-147? 14:53:36 ISSUE-147 -- Reference 'Requirements for Home Networking Scenarios' in Introduction -- open 14:53:36 http://www.w3.org/2009/dap/track/issues/147 14:53:40 ISSUE-148? 14:53:40 ISSUE-148 -- NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service) -- open 14:53:40 http://www.w3.org/2009/dap/track/issues/148 14:53:48 ISSUE-151? 14:53:48 ISSUE-151 -- USN should not be used as device identifier -- open 14:53:48 http://www.w3.org/2009/dap/track/issues/151 14:53:58 ISSUE-154? 14:53:58 ISSUE-154 -- Security approach -- open 14:53:58 http://www.w3.org/2009/dap/track/issues/154 14:54:18 fjh: web and TV IG is cc'd on security discussion 14:54:47 fjh: waiting on PING and Web & TV formal review given the large number of open issues, potential changes 14:55:09 fjh: can ask PING informally about the Nov slot 14:55:47 fjh: this spec is in WD, eventually LC and CR, not ready to consider given state of change 14:56:21 fjh: can expect this draft will not go into LC until next year 14:56:53 fjh: would like to see LC this year if we can 14:57:59 dom: need to check with Rich but would like to take advantage of current momentum 14:58:13 Topic: Network Information API 14:58:29 q+ 14:58:48 fjh: still discussing with Mounir re Mozilla offline 14:58:52 ack anssik 14:59:02 Phone disconnected me again 14:59:03 zakim, who is here? 14:59:03 On the phone I see fjh, dom, igarashi, Josh_Soref (muted), anssik, LisaDeLuca_(IBM), jcdufourd, Cathy, LisaDeLuca_(IBM).a 14:59:03 Zakim, who is on the call? 14:59:05 On IRC I see Cathy, LisaDeLuca_IBM_, jcdufourd, igarashi, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:59:05 On the phone I see fjh, dom, igarashi, Josh_Soref (muted), anssik, LisaDeLuca_(IBM), jcdufourd, Cathy, LisaDeLuca_(IBM).a 14:59:32 zakim, who is here? 14:59:32 On the phone I see fjh, dom, igarashi, Josh_Soref (muted), anssik, LisaDeLuca_(IBM), jcdufourd, Cathy, LisaDeLuca_(IBM).a 14:59:34 On IRC I see Cathy, LisaDeLuca_IBM_, jcdufourd, igarashi, Josh_Soref, Zakim, RRSAgent, fjh, dom, slightlyoff, anssik, mounir, trackbot 14:59:53 we're looking at this internally and will try come back with feedback 15:00:20 Topic: Roadmap/Charter review 15:00:35 Review plans for progressing work through year-end. 15:00:36 All active non-task-force specifications are in CR (Battery Status, HTML Media Capture, Ambient Light Events, Proximity Events, Vibration API) apart from Network Service Discovery (WD) 15:00:38 http://www.w3.org/2009/dap/#roadmap 15:00:39 Walk through test case status, review plans. 15:00:40 charter: http://www.w3.org/2011/07/DeviceAPICharter 15:00:41 Additional work on permissions API, privacy? 15:01:40 +LisaDeLuca_(IBM).aa 15:06:31 fjh: need to link to test case to HTML Media Capture from DAP home page, not sure of status 15:06:35 https://github.com/w3c/web-platform-tests/pull/306 15:06:44 FYI, here is the Apache Cordova battery events (batterycritical, batterylow, batterystatus) http://cordova.apache.org/docs/en/edge/cordova_events_events.md.html#batterystatus 15:06:58 dom: can anssik check the status of HTML Media Capture test cases and share status on the list 15:08:10 fjh: how do we get the pull request for HTML Media Capture approved, who is reviewing it? 15:08:46 dom: bring attention to the pull request on the DAP list 15:08:56 … seek reviewers 15:09:08 … then we can go from there 15:09:32 … I'll put the link on the home page 15:09:57 Lisa, those events are as per an earlier version of the spec 15:10:04 Topic: Action Review 15:10:10 ACTION-654? 15:10:10 ACTION-654 -- Jean-Claude Dufourd to Propose text for network service discovery to define wildcard api and feature detection -- due 2013-09-11 -- OPEN 15:10:10 http://www.w3.org/2009/dap/track/actions/654 15:10:30 jcdufourd: will have some time to work on it shortly 15:10:37 @anssik, can you email me to see how I can help you with action-523 ... even if it's just testing. ldeluca@us.ibm.com 15:10:48 ACTION-658? 15:10:48 ACTION-658 -- Dominique Hazaël-Massieux to Review issue-149 get input on tradeoff of either failing or offering partial result (not all of request) -- due 2013-10-03 -- OPEN 15:10:48 http://www.w3.org/2009/dap/track/actions/658 15:11:06 ISSUE-149? 15:11:06 ISSUE-149 -- handling of long vibration list - truncate or no vibration at all -- open 15:11:06 http://www.w3.org/2009/dap/track/issues/149 15:11:36 -Josh_Soref 15:11:43 close ACTION-652 15:11:43 Closed ACTION-652. 15:12:01 close ACTION-661 15:12:01 Closed ACTION-661. 15:12:05 -dom 15:12:07 -jcdufourd 15:12:08 close ACTION--662 15:12:10 -LisaDeLuca_(IBM).aa 15:12:14 close ACTION-662 15:12:14 Closed ACTION-662. 15:12:22 s/close ACTION--662// 15:12:24 -igarashi 15:12:31 Topic: Other Business 15:12:32 Lisa, the tests are here: https://github.com/w3c/web-platform-tests/tree/master/battery-status 15:12:45 ... but I assume your impl is not following the latest spec 15:12:53 none 15:12:54 fjh: please review the issues we discussed today (as well as other open issues) so we can resolve on list and close next week if possible 15:13:14 … also any help reviewing or working on test cases or implementation to progress CR drafts would be helpful 15:13:18 … thanks 15:13:21