# Device APIs and Policy Working Group Teleconference ## 13 Jul 2011 [Agenda][3] See also: [IRC log][4] ## Attendees Present Robin_Berjon, Frederick_Hirsch, Cecile_Marc, Dominique_Hazael-Massieux, SungOk_You, Wonsuk_Lee, Dzung_Tran, Cathy_Chan, Kihong_Kwon, Dong-Young_Lee, Josh_Soref, Kangchan_Lee, Bryan_Sullivan, Rich_Tibbett Regrets Ernesto_Jimenez Chair Robin_Berjon, Frederick_Hirsch Scribe Bryan_Sullivan ## Contents * [Topics][5] 1. [Administrative][6] 2. [Minutes from July 6 approval][7] 3. [F2F][8] 4. [battery][9] 5. [contacts][10] 6. [network information][11] * [Summary of Action Items][12] * * * Date: 13 July 2011 Scribe: Bryan_Sullivan ScribeNick: bryan SungOk_You ### Administrative discontinuing UK, FR dial-in zakim numbers [http://lists.w3.org/Archives/Member/member-device- apis/2011Jul/0000.html][13] Media Annotations group is going to last call with Media Annotation Resources and Webapps with WebIDL also bryan: I will look for internal reviewers on media annotation [http://www.w3.org/mid/4E1C8BD6.8020607@w3.org][14] -> MAWG Media Annotation API LC [http://www.w3.org/mid/4E1C72C8.9030402@nokia.com][15] -> Web IDL LC ### Minutes from July 6 approval [http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/att-0062/minutes-2011-07-06.html][16] proposed RESOLUTION: Minutes from 6 July 2011 are approved **RESOLUTION: Minutes from 6 July 2011 are approved** ### F2F if you plan to use a car please indicate to Cecile [http://www.w3.org/2009/dap/wiki/F2F_Agenda_19%2c_20%2c_21_July_2011%2c_ Paris][17] fjh: Any comments or concerns to the agenda? ... Web and TV - plan to introduce by Francois is TBD ... dial-in will be provided ... APIs not progressing will be moved to Day 3 ### battery (we have one open issue ISSUE-112) ISSUE-112? ISSUE-112 -- Do we need to give an estimated time remaining indication with battery events? -- open [http://www.w3.org/2009/dap/track/issues/112][18] darobin: need to review it before last call diiscovery proposal -> [http://lists.w3.org/Archives/Public/public- device-apis/2011Jul/0073.html][19] event firing issue -> [http://lists.w3.org/Archives/Public/public- device-apis/2011Jul/0070.html][20] dom: device orientation API that inspired the battery API has a discussion re event firing, the battery API may need to change as a result darobin: had we removed mention of immediate (firing) [http://dev.w3.org/2009/dap/system-info/battery-status.html#the- batterystatus---------event][21] "When an event listener is registered with the event type batterystatus, then the user agent must retrieve the relevant information and dispatch a BatteryStatusEvent event asynchronously as defined in [DOM- LEVEL-3-EVENTS]. " darobin: confirms immediate was removed concern with potential side effects dom: invoking add event listener should not have side effects ISSUE: addEventListener in Battery Status has side effects Created ISSUE-113 - AddEventListener in Battery Status has side effects ; please complete additional details at [http://www.w3.org/2009/dap/track/issues/113/edit][22] . ISSUE-113: see [http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/0070.html][20] ISSUE-113 AddEventListener in Battery Status has side effects notes added darobin: to continue discussing at the F2F and make decision on last call then ### contacts fjh: where are we darobin: at the F2F will review last call comments ... we can go to CR when we have addressed all comments fjh: should consider vacations darobin: getting close to end of july with one-week review, effectively Sept before transition richt: need more implementations and test suites, may need to go back to WD? fjh: yes, that happens [we already have the start of a test suite, fwiw [http://w3c- test.org/dap/contacts/tests/][23] ] darobin: testing is also planned to discussion at F2F forpic: other APIs (Robin is an editor!) ### network information fjh: can we resolve the ethernet/usb issue I think Josh's feedback is close to the feedback we got from Jo, to which our response is still pending (cf ACTION-411) ACTION-411? ACTION-411 -- Robin Berjon to reply to Jo about NetInfo -- due 2011-06-15 -- OPEN [http://www.w3.org/2009/dap/track/actions/411][24] timeless: knowing the wire interface is not useful dom: we should document the discussion and resolution about the level of information that can be given in the network info API timeless: agree richt: have an implementation of the API, for Android browser. changes cost to implementations and need to be factored into the decision timeless: would be good to know if 4G is ever returned dom: suggest timeless reach out to google for their input as I mentioned last week if we can mark up emails with [contacts] [netinfo] etc then it would be easier for other (busy) people to participate. Parsing all the emails received takes time. ...or setup sub-groups. timeless: will make an effort to reach out [richt: make a proposal to the list] dom: re proposal to markup subject line on emails, the new charter will enable task forces (with separate mailing lists), and we can also improve email usage in the way suggested - new email lists have a management overhead bryan: I support use of tags over additional lists timeless, you wanted to note that having to subscribe to lots of mailing lists or unsubscribe is painful '500 emails a day' was conservative. But I was assuming you read them all ;) timeless: having to subscribe/unsubscribe is painful - tags are better fjh: tags are probably easier dom: open to many options but we need people to express themselves Should be simple enough to add tags to new email threads. Really helps to focus in on particular subjects at a time. It's an informal proposal. dom: webapps uses tags and also has distinct lists let's maybe start with tagging subjects; could the chairs suggest this to the list? dom, that's what I mean at [contacts] in the subject line. darobin: should continue on the list It shouldn't need to much discussion. People either do it or we don't. +1 for tag, even though it will not be perfect +1 +1 someone suggest the tags to use fjh: AOB? yes fjh: no call the week after the F2F ## Summary of Action Items [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][25] version 1.135 ([CVS log][26]) $Date: 2009-03-02 03:52:20 $ [1]: http://www.w3.org/Icons/w3c_home [2]: http://www.w3.org/ [3]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/0069.html [4]: http://www.w3.org/2011/07/13-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #ActionSummary [13]: http://lists.w3.org/Archives/Member/member-device- apis/2011Jul/0000.html [14]: http://www.w3.org/mid/4E1C8BD6.8020607@w3.org [15]: http://www.w3.org/mid/4E1C72C8.9030402@nokia.com [16]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/att-0062/minutes-2011-07-06.html [17]: http://www.w3.org/2009/dap/wiki/F2F_Agenda_19%2c_20%2c_21_July_2011%2c_Paris [18]: http://www.w3.org/2009/dap/track/issues/112 [19]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/0073.html [20]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jul/0070.html [21]: http://dev.w3.org/2009/dap/system-info/battery-status.html#the- batterystatus---------event [22]: http://www.w3.org/2009/dap/track/issues/113/edit [23]: http://w3c-test.org/dap/contacts/tests/ [24]: http://www.w3.org/2009/dap/track/actions/411 [25]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [26]: http://dev.w3.org/cvsweb/2002/scribe/