W3C

- DRAFT -

Device APIs Working Group Teleconference

14 Aug 2013

Agenda

See also: IRC log

Attendees

Present
Frederick_Hirsch, Dominique_Hazael-Massieux, Anssi_Kostiainen, Girl_Mandyam, Cathy_Chan, Josh_Soref
Regrets
Chair
Frederick_Hirssch
Scribe
fjh

Contents


<trackbot> Date: 14 August 2013

<scribe> scribenick: fjh

Welcome, agenda review, scribe selection, announcements

welcome Jianliang, Wenmei Huawei ; http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0001.html

No F2F at TPAC - meeting canceled

Publishing moratoria (26 Aug, 11 Nov, 18 Dec) https://lists.w3.org/Archives/Member/chairs/2013JulSep/0029

Minutes approval

Approve minutes from 24 July 2013

http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/att-0002/minutes-2013-07-24.html

RESOLUTION: Minutes from 24 July 2013 are approved

Network Service Discovery

fjh: rich made an update to address issues raised by Adam Barth, need to review changes

ISSUE-135?

<trackbot> ISSUE-135 -- Add security and privacy considerations section -- open

<trackbot> http://www.w3.org/2009/dap/track/issues/135

ISSUE-136?

<trackbot> ISSUE-136 -- Issues related to garbage collection -- open

<trackbot> http://www.w3.org/2009/dap/track/issues/136

fjh: I was looking at implementation for our specs, added these issues related to network service discovery
... looks like chromium implementation is on 'wait and see' versus other browsers and raised issues
... do not believe Mozilla has any plans to implement
... we need a second implementation
... think we need to publish new WD, given promises and others changes
... need to close issues before LC

<Cathy> +1 on publishing updated WD

dom: agree, would be good to publish a draft, blog on it and draw attention to it

fjh: do not need to address all issues to publish another WD

gmandyman: web and TV interest group - suggest we look at implementations other than browser vendor implementations

fjh: need to see who we might specifically include

gmandyam: need to have joint meeting with web and TV interest group to get them involved

<dom> +1 on a joint teleconf with Web & TV IG to draw attention to this; again, a new WD would be a good trigger for that

dom: also need rich on the call for that

<scribe> ACTION: fjh to organize joint call with web and TV group re network service discovery [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action01]

<trackbot> Created ACTION-646 - Organize joint call with web and tv group re network service discovery [on Frederick Hirsch - due 2013-08-21].

<dom> (would work for me)

<dom> +1 on publishing (and not needing a CfC)

RESOLUTION: Publish updated WD of Network Service Discovery

josh_soref: +1 to publishing updated WD of network service disocver

<dom> [can't you share the editors draft in that case?]

fjh: also can use update WD to share with Ping, but might wait until more issues are resolved

Vibration

Question/Comment on CR draft: http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0050.html

Question Vibration and iframes, http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0055.html

<dom> Intent to implement Vibration API in Chromium

<dom> [Thursday not ideal but workable]

fjh: anssik are you able to answer these questions on the list

anssik: yes, will answer

Light

we've addressed LC comments, not response from Anne, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0015.html

fjh: is there a reason this should not go to CR?

josh_soref: wrote test for page visibility for vibration

fjh: can you please send message on this to the list?

josh_soref: yes, will send today

dom: you will send your test cases as well?

josh_soref: yes

<dom> +1 on sending CfC

<scribe> ACTION: fjh to send CfC to progress Light to CR, two week CfC [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action02]

<trackbot> Created ACTION-647 - Send cfc to progress light to cr, two week cfc [on Frederick Hirsch - due 2013-08-21].

Proximity

fjh: same situation with proximity, LC comments addressed but not closed due to no response

http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0015.html

<scribe> ACTION: fjh to send CfC to progress Proxmity to CR, two week CfC [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action03]

<trackbot> Created ACTION-648 - Send cfc to progress proxmity to cr, two week cfc [on Frederick Hirsch - due 2013-08-21].

HTML Media Capture

<dom> ACTION-523?

<trackbot> ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN

<trackbot> http://www.w3.org/2009/dap/track/actions/523

Test cases and implementation

fjh: thanks Dom for git review and pull for battery and vibration
... both seem to need a bit more work to complete

dom: I marked these as approved because one person produced the test cases, and another reviewed, hope that is ok with group

fjh: I think so

dom: some additional work needed on vibration test case

fjh: todo.txt for battery says: proper {level | chargingtime | dischargingtime}change tests

not sure what that means

https://w3c-test.org/web-platform-tests/master/battery-status/TODO.txt

anssik: need to review whether these todo have been already addressed

<scribe> ACTION: anssik to review todo items associated with battery test cases [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action04]

<trackbot> Created ACTION-649 - Review todo items associated with battery test cases [on Anssi Kostiainen - due 2013-08-21].

anssik: tests were originally done with desktop firefox, need to run test on mobile device

dom: which implementations do we know of

… firefox, is blackberry implementing?

josh_soref: I think so but need to check

anssik: ran on very early firefox device, back then, passed
... first bullet indicates user interaction is required, so about making it easier for human to perform tests

… current test should work, not optimal for tester

fjh: anssik, can you update todo.txt

<dom> (rather than todo.txt, they should be filed as issues in github I think)

fjh: agree with dom, issues should be tracked separately, not in a file

gmandyam: do we have any strategy for comparing actual levels for mobile device for battery api and native api

… or just not worry about it?

dom: we concluded in TPAC, API did not need to provide an exact match

gmandyam: I raised the issue, not sure we agreed, such an issue could cause developers to avoid issue

dom: we are not equipped to do such detailed testing

… in W3C we test at a higher level, could be good to test, but not necessary to test that for interoperability

anssik: conforming implementations can have different quality of implementations, some might match closer, so implementation dependent

josh_soref: privacy consideration, might not want to indicate that other apps are using the battery, so advantage to not having a close match

… not a conformance issue or not a close match

… some might decide this api not needed, since all you can do is make a battery meter, my opinion but we will see

gmandyam: could do it

josh_soref: no point in doing it

gmandyam: not saying we need to do this to exit CR

dom: can continue to submit test cases, suite is not frozen

… please provide test cases if you are able

gmandyam: I will share again on mail list, already did

dom: did you post a test case

gmandyam: showed how I did comparison with native battery readings on windows, requires lots of human

fjh: how do you decide what margin of error is acceptable?

anssik: believe this is quality of implementation issue

josh_soref: +1

fjh: if anyone has any additional test cases please share on list

… we should remove the todo.txt file and raise the issues in git, clarifying that they are enhancements

Action review

ACTION-523?

<trackbot> ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN

<trackbot> http://www.w3.org/2009/dap/track/actions/523

ACTION-621?

<trackbot> ACTION-621 -- Anssi Kostiainen to Create test cases for HTML Media Capture -- due 2013-03-13 -- OPEN

<trackbot> http://www.w3.org/2009/dap/track/actions/621

ACTION-641?

<trackbot> ACTION-641 -- Dominique Hazaël-Massieux to Do a last check on battery and vibration test cases before merging in github master -- due 2013-08-14 -- PENDINGREVIEW

<trackbot> http://www.w3.org/2009/dap/track/actions/641

close ACTION-641

<trackbot> Closed ACTION-641.

ACTION-642?

<trackbot> ACTION-642 -- Dominique Hazaël-Massieux to Review proximity and ambient light test cases -- due 2013-09-18 -- OPEN

<trackbot> http://www.w3.org/2009/dap/track/actions/642

ACTION-643?

<trackbot> ACTION-643 -- Anssi Kostiainen to Review Ambient Light and Proximity test cases by Sept -- due 2013-07-10 -- OPEN

<trackbot> http://www.w3.org/2009/dap/track/actions/643

ACTION-644?

<trackbot> ACTION-644 -- Frederick Hirsch to Ask TAG for feedback on promises with Network Discovery -- due 2013-07-31 -- PENDINGREVIEW

<trackbot> http://www.w3.org/2009/dap/track/actions/644

waiting for spec to stabilize a bit more

<dom> [regrets from me]

Meeting time

Discussion regarding moving regular time for this call, participants on the call are ok with Thur 10 am ET

<scribe> ACTION: fjh to propose changing meeting time to Thur at 10 am ET slot [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action05]

<trackbot> Created ACTION-650 - Propose changing meeting time to thur at 10 am et slot [on Frederick Hirsch - due 2013-08-21].

josh_soref: 5 Sept might be a problem

Other business

None

Adjourn

<scribe> Chair: Frederick_Hirsch

Summary of Action Items

[NEW] ACTION: anssik to review todo items associated with battery test cases [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action04]
[NEW] ACTION: fjh to organize joint call with web and TV group re network service discovery [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action01]
[NEW] ACTION: fjh to propose changing meeting time to Thur at 10 am ET slot [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action05]
[NEW] ACTION: fjh to send CfC to progress Light to CR, two week CfC [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action02]
[NEW] ACTION: fjh to send CfC to progress Proxmity to CR, two week CfC [recorded in http://www.w3.org/2013/08/14-dap-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2013-08-14 15:02:18 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/publish LC/publish a/
Succeeded: s/tit/it/
Succeeded: s/concludeer/concluded/
Succeeded: s/not/no/
Succeeded: s/ISSUE=136?//
Succeeded: s/+q//
Succeeded: s/+q//g
Succeeded: s/ACTIOBN-621?//
Found ScribeNick: fjh
Inferring Scribes: fjh
Present: Frederick_Hirsch Dominique_Hazael-Massieux Anssi_Kostiainen Girl_Mandyam Cathy_Chan Josh_Soref
Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0021.html
Found Date: 14 Aug 2013
Guessing minutes URL: http://www.w3.org/2013/08/14-dap-minutes.html
People with action items: anssik fjh

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]