# Device APIs Working Group Teleconference ## 19 Sep 2013 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Anssi_Kostiainen, Lisa_DeLuca, Claes_Nilsson, Tatsuya_Igarashi, Dominique_Hazael-Massieux, Cathy_Chan Regrets Josh_Soref, Jean-Claude_Dufourd, Rich_Tibbett Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Welcome, agenda review, scribe selection, announcements][6] 2. [Minutes approval][7] 3. [Proximity and Light][8] 4. [Vibration API][9] 5. [Network Service Discovery][10] 6. [Web Notifications Last Call][11] 7. [Action Review][12] 8. [Issue Review][13] 9. [Network Information API][14] 10. [Other Business][15] 11. [Adjourn][16] * [Summary of Action Items][17] * * * Date: 19 September 2013 trackbot, start telecon Meeting: Device APIs Working Group Teleconference Date: 19 September 2013 ScribeNick: fjh ### Welcome, agenda review, scribe selection, announcements IBM joined group, Lisa Seacat DeLuca, welcome. ldeluca: interested as there is interest in Device APIs and possible relationship to Cordova fjh: possibility of participating in testing, interop ldeluca: maybe later, especially interested in vibration dom: I've been looking into possible convergence with Cordova, so it is great to have you in the group … have been talking with people at adobe on this topic [Apache Cordova (Phonegap opensource face)][18] ### Minutes approval Approve minutes from 4 September 2013 [http://lists.w3.org/Archives/Public/public-device- apis/2013Sep/att-0013/minutes-2013-09-04.html][19] **RESOLUTION: Minutes from 4 September 2013 are approved** ### Proximity and Light CfC concluded, next step is to publish [http://cordova.apache.org/docs/en/3.0.0/][20] that's the url to the cordova APIs fjh: I will send transition requests for CR today anssi: am preparing drafts ready for CR publication, have updated with implementation links, running link checker and pub rules, should have later today … what should crEnd be fjh: doesn't really matter since we know it will take longer to exit CR but 9 weeks is fine dom: used to be needed to set implementer deadline expectations but not really a concern here, 9 weeks should be fine fjh: can we plan to have transition call next week dom: need transition request first, if we wait it will be longer fjh: will send after meeting anssik: will set date for 1 Oct for now dom: exact date not essential for approval ### Vibration API already in CR but getting comments fjh: I believe AnssiK you are still reviewing these items ISSUE-146? ISSUE-146 -- Add vibration strength control -- open [http://www.w3.org/2009/dap/track/issues/146][21] ISSUE-149? ISSUE-149 -- handling of long vibration list - truncate or no vibration at all -- open [http://www.w3.org/2009/dap/track/issues/149][22] ISSUE-150? ISSUE-150 -- Should vibration be additive when multiple instances, e.g. iframes -- open [http://www.w3.org/2009/dap/track/issues/150][23] fjh: I believe we've agreed to defer ISSUE-146 to v.next … but need to formalize that and be clear that is correct anssik: looking at spec to see if ISSUE-149 already allowed fjh: text may need explicit clarification anssi: not sure whether it is better to fail or succeed with clarity fjh: alternative is graceful degradation … I think Daniel has a good point anssi: getting something rather than silence might be better, agreed fjh: think it might be simpler for applications anssik: fairly simple to modify text to say this ... only return false if page hidden , daniel suggests we prune pattern length and entry length fjh: seems partial failure better than absolute failure **ACTION:** dom to review ISSUE-149 get input on tradeoff of either failing or offering partial result (not all of request) [recorded in [http://www.w3.org/2013/09/19-dap-minutes.html#action01][24]] Created ACTION-658 - Review issue-149 get input on tradeoff of either failing or offering partial result (not all of request) [on Dominique Hazaël-Massieux - due 2013-09-26]. ISSUE-150? ISSUE-150 -- Should vibration be additive when multiple instances, e.g. iframes -- open [http://www.w3.org/2009/dap/track/issues/150][23] fjh: I think this was resolved on list to be a union ... I believe next step is to update spec … and share a diff fjh: I don't think we need to go back to LC, only if substantive change that impacts implementions ... we should revisit once changes are in spec, but suspect we don't need another LC anssik: dealing with under specified edge cases are clarifications, no need for LC dom: agree ### Network Service Discovery fjh: we've been working on WD publication, have been doing various publication corrections, expect to publish soon Web & TV IG review, [http://lists.w3.org/Archives/Public/public-device- apis/2013Aug/0063.html][25] fjh: will share once we publish ... expect that we might not meet every of their requirements, would like to see them review and indicate if any significant concerns ISSUE-130? ISSUE-130 -- Enable variety of protocols (e.g. UPnP, Bonour) with protocol independent developer code -- open [http://www.w3.org/2009/dap/track/issues/130][26] discussed earlier need to continue on list ISSUE-131? ISSUE-131 -- Support UPnP device discovery by Device Type? -- open [http://www.w3.org/2009/dap/track/issues/131][27] we have proposal on the list, [http://lists.w3.org/Archives/Public/public- device-apis/2013Sep/0025.html][28] cathy: agree with proposal, still have some additional details fjh: need to check with Rich to see if any other concern cathy: if Igarashi is good with it I think we are ok … we also need jean-claude to look at it fjh: I'll ping them on the list ... is there anything else cathy that we should discuss today cathy: no we are waiting on actions, jean-claude has one, we also need spec update fjh: which spec updates needed cathy: service name with friendly nick needs to be done fjh: if you can share a list of outstanding spec updates on the list that would help issues list [http://www.w3.org/2009/dap/track/issues/open][29] ### Web Notifications Last Call [http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0024.html][30] fjh: would anyone like to volunteer to review this? **ACTION:** fjh to review Web Notifications Last Call specification [recorded in [http://www.w3.org/2013/09/19-dap-minutes.html#action02][31]] Created ACTION-659 - Review web notifications last call specification [on Frederick Hirsch - due 2013-09-26]. fjh: will see if others not on the call are interested as well ### 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][32] anssik: progress is happening, our developers are submitting patches against submitted test cases dom: has marcos responded to suggestions from your team? anssik: have not seen anything dom: using marcos fork … could make pull request against marcos fork … also could merge marcos submission as is and work on top of it … process is not quite entirely clear so we can do what we need to … maybe you should see what your team suggests anssik: started with submitting pull request … need to get marcos involved fjh: i suggest you start by getting marcos involved dom: pull request against my fork... anssik: i instructed qa person to go against dom fork dom: ok but if that doesn't work then I'll help anssik: once we've done this we need to update instructions ACTION-642? ACTION-642 -- Dominique Hazaël-Massieux to Review proximity and ambient light test cases -- due 2013-09-18 -- OPEN [http://www.w3.org/2009/dap/track/actions/642][33] dom: still open anssik: our team is also doing this ACTION-645? ACTION-645 -- Frederick Hirsch to Share Network Service Discovery editors draft with PING -- due 2013-07-31 -- OPEN [http://www.w3.org/2009/dap/track/actions/645][34] fjh: deferring involving PING until I feel the draft is sufficiently stable ... we probably should first clarify the model and boundaries of reveiw ACTION-652? ACTION-652 -- Anssi Kostiainen to Make proposal on list regarding multiple vibration api invocations in frames for vibration -- due 2013-09-11 -- OPEN [http://www.w3.org/2009/dap/track/actions/652][35] ISSUE-150? ISSUE-150 -- Should vibration be additive when multiple instances, e.g. iframes -- open [http://www.w3.org/2009/dap/track/issues/150][23] ACTION-654? ACTION-654 -- Jean-Claude Dufourd to Propose text for network service discovery to define wildcard api and feature detection -- due 2013-09-11 -- OPEN [http://www.w3.org/2009/dap/track/actions/654][36] ACTION-655? ACTION-655 -- Anssi Kostiainen to Update test for light :[https://dvcs.w3.org/hg/dap/rev/916dbd5920d8][37] -- due 2013-09-11 -- OPEN [http://www.w3.org/2009/dap/track/actions/655][38] ACTION-656? ACTION-656 -- Anssi Kostiainen to Update proximity test for [https://dvcs.w3.org/hg/dap/rev/a6ad49819c41][39] -- due 2013-09-11 -- OPEN [http://www.w3.org/2009/dap/track/actions/656][40] anssik: our qa is looking at these both and will have to do pull requests, still open [https://w3c-test.org/web-platform-tests/submissions/126/ambient- light/][41] anssik: do we need to link to submissions in CR draft fjh: we need link to test case and interop document/wiki, can expect changes … does not need to be in CR draft itself but linked document dom: needs to be in interop document, can be mostly empty at this time [http://www.w3.org/2009/dap/wiki/Main_Page][42] ACTION-657? ACTION-657 -- Anssi Kostiainen to Revise battery tests for idlharness, find qa person to help -- due 2013-09-11 -- OPEN [http://www.w3.org/2009/dap/track/actions/657][43] anssik: have qa person working on this ACTION-646 closed Closed ACTION-646. ACTION-653 closed Closed ACTION-653. ACTION-646? ACTION-646 -- Frederick Hirsch to Organize joint call with web and tv group re network service discovery -- due 2013-08-21 -- CLOSED [http://www.w3.org/2009/dap/track/actions/646][44] ACTION-653? ACTION-653 -- Frederick Hirsch to Create issues for vibration questions -- due 2013-09-11 -- CLOSED [http://www.w3.org/2009/dap/track/actions/653][45] ### Issue Review I believe all issues are recorded, if not please add issue or indicate on list ### Network Information API reviewing whether or not to shelve, please indicate if any input anssik: we would like to look at it **ACTION:** anssik to determine interest in progressing Network Information API or not [recorded in [http://www.w3.org/2013/09/19-dap- minutes.html#action03][46]] Created ACTION-660 - Determine interest in progressing network information api or not [on Anssi Kostiainen - due 2013-09-26]. anssik: will get some feedback within a couple of weeks ### Other Business None ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** anssik to determine interest in progressing Network Information API or not [recorded in [http://www.w3.org/2013/09/19-dap- minutes.html#action03][46]] **[NEW]** **ACTION:** dom to review ISSUE-149 get input on tradeoff of either failing or offering partial result (not all of request) [recorded in [http://www.w3.org/2013/09/19-dap-minutes.html#action01][24]] **[NEW]** **ACTION:** fjh to review Web Notifications Last Call specification [recorded in [http://www.w3.org/2013/09/19-dap-minutes.html#action02][31]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][47] version 1.135 ([CVS log][48]) $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/2013Sep/0027.html [4]: http://www.w3.org/2013/09/19-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]: http://cordova.apache.org/ [19]: http://lists.w3.org/Archives/Public/public-device- apis/2013Sep/att-0013/minutes-2013-09-04.html [20]: http://cordova.apache.org/docs/en/3.0.0/ [21]: http://www.w3.org/2009/dap/track/issues/146 [22]: http://www.w3.org/2009/dap/track/issues/149 [23]: http://www.w3.org/2009/dap/track/issues/150 [24]: http://www.w3.org/2013/09/19-dap-minutes.html#action01 [25]: http://lists.w3.org/Archives/Public/public-device- apis/2013Aug/0063.html [26]: http://www.w3.org/2009/dap/track/issues/130 [27]: http://www.w3.org/2009/dap/track/issues/131 [28]: http://lists.w3.org/Archives/Public/public-device- apis/2013Sep/0025.html [29]: http://www.w3.org/2009/dap/track/issues/open [30]: http://lists.w3.org/Archives/Public/public-device- apis/2013Sep/0024.html [31]: http://www.w3.org/2013/09/19-dap-minutes.html#action02 [32]: http://www.w3.org/2009/dap/track/actions/523 [33]: http://www.w3.org/2009/dap/track/actions/642 [34]: http://www.w3.org/2009/dap/track/actions/645 [35]: http://www.w3.org/2009/dap/track/actions/652 [36]: http://www.w3.org/2009/dap/track/actions/654 [37]: https://dvcs.w3.org/hg/dap/rev/916dbd5920d8 [38]: http://www.w3.org/2009/dap/track/actions/655 [39]: https://dvcs.w3.org/hg/dap/rev/a6ad49819c41 [40]: http://www.w3.org/2009/dap/track/actions/656 [41]: https://w3c-test.org/web-platform-tests/submissions/126/ambient- light/ [42]: http://www.w3.org/2009/dap/wiki/Main_Page [43]: http://www.w3.org/2009/dap/track/actions/657 [44]: http://www.w3.org/2009/dap/track/actions/646 [45]: http://www.w3.org/2009/dap/track/actions/653 [46]: http://www.w3.org/2013/09/19-dap-minutes.html#action03 [47]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [48]: http://dev.w3.org/cvsweb/2002/scribe/