[![W3C][1]][2] # Device APIs Working Group Teleconference ## 12 Sep 2012 [Agenda][3] See also: [IRC log][4] ## Attendees Present Alexander_Salas, AnssiK, Anssi_Kostiainen, Bryan_Sullivan, Cathy_Chan, Claes_Nilsson, Colin_Courtney, Dave_Raggett, Diana_Cheng, Dzung_Tran, Frederick_Hirsch, Giri_Mandyam, Josh_Soref, Jungkee_Song, Niklas_Widell Regrets Chair Frederick_Hirsch Scribe Josh_Soref ## Contents * [Topics][5] 1. [Agenda review, Administrative, Announcements][6] 2. [Approval of last minutes][7] 3. [Pick Contacts Intent Draft][8] 4. [WebIntents Addendum - Local Services][9] 5. [Networked Service Discovery and Messaging][10] 6. [Vibration API][11] 7. [Ambient Light][12] 8. [Atmospheric Pressure Sensor][13] 9. [Media Capture][14] 10. [AOB][15] 11. [Action Review][16] * [Summary of Action Items][17] * * * Date: 12 September 2012 ### Agenda review, Administrative, Announcements Scribe: Josh_Soref proposed RESOLUTION: Cancel following 2012 DAP teleconferences: 10 October, 8 Nov (week after TPAC), 20 Nov (US thanksgiving week), 19 December, 26 December. fjh: propose to cancel Oct 10 call, Nov 20, and Dec 19, 26. Any objections? **RESOLUTION: Cancel following 2012 DAP teleconferences: 10 October, 8 Nov (week after TPAC), 20 Nov (US thanksgiving week), 19 December, 26 December.** Please remember to complete the WG questionnaire for the F2F and also the TPAC registration as well as making your travel arrangements. [https://www.w3.org/2002/09/wbs/43696/dapf2ftpac2012/][18] ; [http://www.w3.org/2012/10/TPAC/Overview.html#Registration][19] Please suggest topics for DAP F2F agenda: [http://www.w3.org/2009/dap/wiki/F2F_Agenda_1-2_November_TPAC_Lyon_France][20] dsr: We are looking for topics for the TPAC F2F. There will be a web intents discussion in webapps on the Tuesday. Call for Review of Content Security Policy 1.0, [http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/0020.html][21] dsr: Media TF also on the plan. perhaps for Tuesday too. ### Approval of last minutes Approve minutes from 29 August 2012 [http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/att-0008/minutes-2012-08-29.html][22] proposed RESOLUTION: Minutes from 29 August 2012 are approved. **RESOLUTION: Minutes from 29 August 2012 are approved.** ### Pick Contacts Intent Draft proposed RESOLUTION: Add Jungkee Song as editor of Pick Contacts Intent draft [ No objections ] [http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0003.html][23] **RESOLUTION: Add Jungkee Song as editor of Pick Contacts Intent draft** [http://dvcs.w3.org/hg/dap/raw-file/tip/contacts/Overview.html][24] Not yet fjh: trying to work with Dom to fix script to keep the home page up to date. but I have a few things to start with and as we discussed at the last call alright ### WebIntents Addendum - Local Services [http://w3c-test.org/dap/wi-addendum-local-services/][25] fjh: still a bunch of edits pending based upon email discussions I think my comments on this draft have been addressed Claes: where are we in respect to publication? ... we had comment from Cathy early and we are now waiting for comments on the latest version of the draft. ... the mDNS part is new and needs review. fjh: maybe you should email DAP and Web Intents TF asking for that review? Claes: okay, will send a reminder. fjh: after that we will decide on doing a CfC at the next DAP call. ... any other concerns? Claes: I have an action to work on a hidden disposition fjh: if you have anything else to say on SSL that might be helpful. ### Networked Service Discovery and Messaging [http://w3c-test.org/dap/discovery-api/][26] fjh: we are getting close to being ready to publish updated WD ... will send an informal message to Rich, and then decide if we are ready for a CfC. There are still some comments that have not been addressed. fjh: we need to get those addressed first. ### Vibration API Change to partial interface. Testing offer by Marcos, [http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/0014.html][27] fjh: we are in CR, and may need to revert to LCWD ... shouldn't be a big deal given the implementation experience Anssi: Changing to a partial interface effects the implementation, and this is actually aligned with the implementations given that the change to partial interface is almost editorial, not changing current implementations, but maybe reuse, maybe a LC is not required [http://w3c-test.org/dap/tests/vibration/][28] AnssiK: we're doing test suites Dave: I suspect the decision of reverting to LCWD would depend on whether we feel we still need more feedback from implementers. AnssiK: and we have reports from the browsers ... so you can see their status fjh: do you have a link? [http://www.w3.org/2009/dap/wiki/ImplementationStatus#Vibration_API][29] AnssiK: let me get it fjh: maybe we should add this to the homepage AnssiK: implementation status is linked from the home page ... but there are a bunch of links, so maybe we should clean them up fjh: maybe we should add it to the table AnssiK: that's how dom is doing it for the mobile web report fjh: i'm just interested in making sure we follow the process to REC AnssiK: i think we need to work out some test cases ... i've been working on battery test cases ... and then i can do vibration test cases ... but i'm taking some time off between now and the F2F, so i won't be able to get much done between fjh: will you be at the F2F? AnssiK: yes Quick question about vibration: is there a facility for varying vibration levels in addition to durations? fjh: it might be useful to take Marcos up on his test writing offer AnssiK: yeah ... there's no hardware support for strength Understood, thanks. on implementation status: it would be really handy to have a combined implementation table (specs vs UAs) somewhere linked to the homepage. i get a lot of requests for this and dont mind the research, but others could probably use it as well. I suggest we take Marcus up on his offer ### Ambient Light proposal from Doug analogous to Proximity, support on list "Maybe we should leave DeviceAmbientLight alone and add a new event type for reporting changes in the general range of ambient lighting." fjh: i think that's reasonable [http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0040.html][30] fjh: it's similar to what we've done for Proximity ... i think dougt's going to do that ... if you wish to join that discussion, you should do that change, moving this work forward on the list ### Atmospheric Pressure Sensor **ACTION:** fjh to put Atmospheric Pressure API experimental section of DAP Roadmap due to same reasons as Humidity and Temperature [recorded in [http://www.w3.org/2012/09/12-dap-minutes.html#action01][31]] Created ACTION-575 - Put Atmospheric Pressure API experimental section of DAP Roadmap due to same reasons as Humidity and Temperature [on Frederick Hirsch - due 2012-09-19]. dtran: a lot of phones will have pressure sensors ... the UCs is compelling ... for altitude ... for a hiking app ... you want to know how high you are when you're traveling ... in my Nexus phone, it's there ... this has pressure sensor (for atmospheric reading) support ... we might want to take a look at it fjh: it's good that you did this ... it's experimental stage Josh_Soref: if the main use case is gps altitide couldn't we use the interface from that? it doesn't seem like we need a new interface for this AnssiK: that makes sense fjh: another use case is weather ... if we have all the coordinates from one interface dcheng3: we do have Altitude in the GeoLocation API ... we're not working on a v2 spec ... but that's already there ... we're wrapping up v1 fjh: it sounds like a good idea to minimize APIs ... i'll move this to Experimental ... i think there are UCs different from Altitude ... we can defer til later ### Media Capture [https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-html-media- capture-20120712/doc/][32] fjh: i gave it a week, which was probably a mistake ... AnssiK: i should have pushed back on your comments. but dougt pushed back [http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0050.html][33] AnssiK: thanks for doing the work [http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0051.html][34] AnssiK: there are a couple of replies from shepazu ... i agree his changes make sense ... the only reason i'm hesitant to make the changes right away ... is to make sure we can get implementers' feedback baked in ... i think we should get their feedback before updating the spec fjh: can we take these one at a time? ... the first is message 50 from him ... the multiple arguments for capture ... i think we need to figure that out on the list ... and see if it's consistent with what we have today ... i seem to recall a discussion on the list ... but i couldn't find it ... do you remember it? ... the other one, 51 is more of a bike shed ... shepazu said we can easily change the name ... people expect changes there as part of standardization note we could support two synonyms couldn't we, though not preferable [ fjh didn't call it a bike shed, just something which is more of a preference and less technical ] Josh_Soref: synonyms adds to test case / compliance ... and silly matrix things: capture="camcorder,microphone,videocamera" ... is it first or last? AnssiK: the web page hints it wants to capture a photo ... and it's up to the UA to allow the user to mute the video ... this is a philosophical debate about control for Web Page v. User Agent fjh: shepazu says we have to be concerned about end users, not UAs ... we have to be sure we're addressing UCs that really matter ... i don't think we can just punt everything AnssiK: i understand that side of the story as well ... we're talking about ... historically you just fire up a dialog ... and it could exist anywhere, on your file system, on the network ... this proposal diverges from that fjh: it might not be the right thing to do Josh_Soref: i sent a long thing talking about file pickers I'd also like to note @accept is also just a hint [http://lists.w3.org/Archives/Public/public-device- apis/2011Jun/0083.html][35] is that it? Josh_Soref: thanks bryan fjh: i think we need to address this on the list AnssiK: i feel this discussion may take a while ... please continue this on the list even if i'm not there ... i'm sure you'll land on a consensus before the F2F ... then we can agree on this at the F2F ... i'll try to wade in this week ... i'll try to engage the implementers as well ### AOB Josh_Soref, you wanted to ask if we should consider changing the telco time - specifically asking dougt if he could make a call later in the day Josh_Soref: i'm wondering if moving it forward 1 hour would help Pacific fjh: this is 4/5pm in Europe, if we move it an hour, that may move it an hour, which isn't great but not bad ... not sure about asia Josh_Soref: we should ask dougt if he'd be willing to join calls if we moved the time AnssiK: if this isn't settled by the F2F, we could have a sessions with dougt at the F2F ... between werewolf it gets really late in Asia after 14:00GMT; I am OK with the current time on the west coast fjh: we should talk at the F2F in Seoul, it would be 12 am AnssiK: we'll need to find the middle ground ... i'll try to reply to the open items before i take my leave Jungkee, exactly, I don't want to make it worse for you fjh: i don't think we'll do action review AnssiK: see everyone at the F2F ### Action Review action-548? ACTION-548 -- Dave Raggett to check out why chairs got an email to announce Sony joining group but they're not listed in DBWG -- due 2012-07-17 -- OPEN [http://www.w3.org/2009/dap/track/actions/548][36] ACTION-548? ACTION-548 -- Dave Raggett to check out why chairs got an email to announce Sony joining group but they're not listed in DBWG -- due 2012-07-17 -- OPEN [http://www.w3.org/2009/dap/track/actions/548][36] dsr: i think that was a glitch as they transitioned their organization name ACTION-548: was a glitch due to transition of organization name ACTION-548 Check out why chairs got an email to announce Sony joining group but they're not listed in DBWG notes added close ACTION-548 ACTION-548 Check out why chairs got an email to announce Sony joining group but they're not listed in DBWG closed ACTION-556? ACTION-556 -- Robin Berjon to set up test repository with example, docs, manifest generation for Web Intents -- due 2012-07-18 -- OPEN [http://www.w3.org/2009/dap/track/actions/556][37] fjh: ... i don't know what darobin 's status is. dsr: do you know? I'll follow up directly with Robin ACTION-565? ACTION-565 -- Josh Soref to propose text for HTML Media Capture to allow for alternative capture device if specified device not available -- due 2012-08-22 -- OPEN [http://www.w3.org/2009/dap/track/actions/565][38] Josh_Soref: i might be able to do something on that today, it's definitely related to what i sent If Robin is too busy to handle that, I'll take the action after talking with him ACTION-568? ACTION-568 -- Jungkee Song to work with Robin to move darobin to move API Cookbook to w3c space and prepare for publication as W3C FPWD NOTE -- due 2012-08-29 -- OPEN [http://www.w3.org/2009/dap/track/actions/568][39] I'll talk with Robin and take that action Josh_Soref: my Facebook-Intents action would give us experience w/ WebIntents / Pick-Contact fjh: i should mention that there are discussions on the WebIntents list Josh_Soref: jhawkins has asked about moving discussion to the whatwg list fjh: i can see some concern about IPR ... and general forking discussion risks ... dsr: should i talk with you offline? dsr: let's think about this further fjh: thanks all [ Adjourned ] thanks trackbot, end meeting have a good one ## Summary of Action Items **[NEW]** **ACTION:** fjh to put Atmospheric Pressure API experimental section of DAP Roadmap due to same reasons as Humidity and Temperature [recorded in [http://www.w3.org/2012/09/12-dap-minutes.html#action01][31]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][40] version 1.135 ([CVS log][41]) $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/2012Sep/0049.html [4]: http://www.w3.org/2012/09/12-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #item07 [13]: #item08 [14]: #item09 [15]: #item10 [16]: #item11 [17]: #ActionSummary [18]: https://www.w3.org/2002/09/wbs/43696/dapf2ftpac2012/ [19]: http://www.w3.org/2012/10/TPAC/Overview.html#Registration [20]: http://www.w3.org/2009/dap/wiki/F2F_Agenda_1-2_November_TPAC_Lyon_France [21]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0020.html [22]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/att-0008/minutes-2012-08-29.html [23]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0003.html [24]: http://dvcs.w3.org/hg/dap/raw-file/tip/contacts/Overview.html [25]: http://w3c-test.org/dap/wi-addendum-local-services/ [26]: http://w3c-test.org/dap/discovery-api/ [27]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0014.html [28]: http://w3c-test.org/dap/tests/vibration/ [29]: http://www.w3.org/2009/dap/wiki/ImplementationStatus#Vibration_API [30]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0040.html [31]: http://www.w3.org/2012/09/12-dap-minutes.html#action01 [32]: https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-html-media- capture-20120712/doc/ [33]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0050.html [34]: http://lists.w3.org/Archives/Public/public-device- apis/2012Sep/0051.html [35]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jun/0083.html [36]: http://www.w3.org/2009/dap/track/actions/548 [37]: http://www.w3.org/2009/dap/track/actions/556 [38]: http://www.w3.org/2009/dap/track/actions/565 [39]: http://www.w3.org/2009/dap/track/actions/568 [40]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [41]: http://dev.w3.org/cvsweb/2002/scribe/