# Device APIs Working Group Teleconference ## 06 Feb 2014 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Mats_Wichmann, Anssi_Kostiainen, Lisa_DeLuca, Dominique_Hazael-Massieux, Giri_Mandyam Regrets Cathy_Chan Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Welcome, agenda review, scribe selection, announcements][6] 2. [Minutes approval][7] 3. [Vibration][8] 4. [Standby API Specification proposal][9] 5. [Network Service Discovery][10] 6. [Action Review][11] 7. [Issues][12] 8. [Other Business][13] 9. [Adjourn][14] * [Summary of Action Items][15] * * * Date: 06 February 2014 ### Welcome, agenda review, scribe selection, announcements ScribeNick: fjh ### Minutes approval Approve minutes from 30 January 2014 [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/att-0056/minutes-2014-01-30.html][16] fjh: please note that I annotated the minutes after the call to reflect an update regarding sending a CfC for Vibration and changing the date **RESOLUTION: Minutes from 30 January 2014 are approved** ### Vibration CfC for publishing LC completes today, plan to publish Tuesday, 11 Feb. please respond to CfC on list. CfC: [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0055.html][17] publication draft: [http://dev.w3.org/2009/dap/vibration/LC3.html][18] ACTION-666? ACTION-666 -- Giridhar Mandyam to Check with internal implementers whether vibration api is consistent with chip capabilities -- due 2013-10-17 -- OPEN [http://www.w3.org/2009/dap/track/actions/666][19] gmandyam: some slight spec changes might be useful based on internal feedback, mostly editorial … have shared with Anssi offlist anssik: agrees changes are editorial fjh: should share this on the public list gmandyam: will send email to list outlining feedback and proposed changes anssik: rephrasing of word of spec gmandyam: pattern might not be possible if vibrator busy, driver provides this info, but on android driver does not provide this information … not saying this should be provided to developer … but if not android developer might have this information … instead of saying "or it is disabled" say "or it is disabled or it is busy" "If pattern is an empty list, or if the device does not provide a vibration mechanism (or it is disabled), then return true and terminate these steps." Giri's proposal is to s/(or it is disabled)/(or it is disabled or busy)/ [http://dev.w3.org/2009/dap/vibration/LC3.html][18] step 10 "If pattern is an empty list, or if the device does not provide a vibration mechanism (or it is disabled), then return true and terminate these steps." +1 on fjh's proposal fjh: suggest " , or if device is unable to vibrate, then return true" +1 on fjh's proposal too +1 +1 **RESOLUTION: Adopt proposed change in LC draft** close ACTION-666 Closed ACTION-666. anssik: updating LC draft now "If pattern is an empty list, or if the device is unable to vibrate, then return true and terminate these steps." ### Standby API Specification proposal fjh: please notice that there is a list discussion regarding possible Standby API proposal ... thanks Dom for quick response [http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0001.html][20] fjh: suggest we wait a bit for implementer support for standardizing this ... if we decide to add this can do at any time? dom: yes, rechartering also happens when charter expires fjh: we need to make sure group members are ok with it from IPR perspective dom: can have CfC to agree on re-chartering gmandyam: sent an email, not sure DAP should be doing this given similar sys apps work dom: we need to give some time and thought to whether we do this, based on implementer feedback fjh: lets continue the discussion on the list ### Network Service Discovery Summarized my concern abour rechartering DAP for this deliverable on the mailing list: this should be a two-step process, where the first step would be getting implementer feedback (which can be done in the DAP context) ... fjh: Rich, Jean-Claude, Cathy not on list so need to defer ... need to address issue raised by Jean-Claude [http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0016.html][21] Based on the feedback, the second step should be to decide whether the work actually belongs in DAP WG (versus e.g. SysApps WG) fjh: we need to determine plan for publishing updated WD, schedule for LC … updated WD is appropriate given addition of CORS … wanted to get some issues resolved before publishing dom, you wanted to ask about WebAppSec fjh: would like to publish an update … do we need a CfC, could ask Rich first dom: do not CfC fjh: send request for review to WebAppSec and also Security IG, have not received a response dom: might get better response without formal review request … suggest we start with WebAppSec fjh: I will follow up with Wendy and Brad dom: have Rich present specifics of problem space ... not just about CORS, but exposing network devices without exposing devices … expose general problem space fjh: this came up on PING, the issue and problem of obscuring URLs for local network devices **ACTION:** fjh to follow up on WebAppSec review [recorded in [http://www.w3.org/2014/02/06-dap-minutes.html#action01][22]] Created ACTION-680 - Follow up on webappsec review [on Frederick Hirsch - due 2014-02-13]. ### Action Review ACTION-523? ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN [http://www.w3.org/2009/dap/track/actions/523][23] anssik: still ongoing fjh: Pending close ACTION-674 Closed ACTION-674. close ACTION-678 Closed ACTION-678. ### Issues ISSUE-149? ISSUE-149 -- handling of long vibration list - truncate or no vibration at all -- closed [http://www.w3.org/2009/dap/track/issues/149][24] ### Other Business None ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** fjh to follow up on WebAppSec review [recorded in [http://www.w3.org/2014/02/06-dap-minutes.html#action01][22]] [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/2014Feb/0015.html [4]: http://www.w3.org/2014/02/06-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #item07 [13]: #item08 [14]: #item09 [15]: #ActionSummary [16]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/att-0056/minutes-2014-01-30.html [17]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0055.html [18]: http://dev.w3.org/2009/dap/vibration/LC3.html [19]: http://www.w3.org/2009/dap/track/actions/666 [20]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0001.html [21]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0016.html [22]: http://www.w3.org/2014/02/06-dap-minutes.html#action01 [23]: http://www.w3.org/2009/dap/track/actions/523 [24]: http://www.w3.org/2009/dap/track/issues/149 [25]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [26]: http://dev.w3.org/cvsweb/2002/scribe/