Device APIs Working Group Teleconference -- 09 Jan 2014

<trackbot> Date: 09 January 2014

trackbot, start telecon

<trackbot> Meeting: Device APIs Working Group Teleconference

<trackbot> Date: 09 January 2014

Welcome, agenda review, scribe selection, announcements

<scribe> ScribeNick: fjh

proposed RESOLUTION: Cancel 23 January 2014 teleconference.

proposed RESOLUTION: Cancel 24 April 2014 teleconference.

<dom> +1 on cancelling both

RESOLUTION: Cancel 23 January 2014 teleconference
... Cancel 24 April 2014 teleconference.

fjh: will update minutes page, which has upcoming meetings http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences

Minutes approval

Approve minutes from12 December 2013

http://lists.w3.org/Archives/Public/public-device-apis/2013Dec/att-0027/minutes-2013-12-12.html

RESOLUTION: Minutes from 12 December 2013 are approved

Shelving Notes

fjh: Drafts updated, publication request submitted. Planned publication date 14 January 2014

Links to drafts: http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0009.html

dom: we agreed not to have home page news

fjh: yes

dom: need to contact Comm team

fjh: I can do that

Vibration

Issue status summary: http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0005.html

Issue-149?

<trackbot> Issue-149 -- handling of long vibration list - truncate or no vibration at all -- open

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

proposed change is here: http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0012.html

second change here: http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0112.html

<anssik> http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r1=1.7;r2=1.8;f=h

<anssik> http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html

fjh: believe we need new LC and CR for the normative algorithm change

anssik: ok, can add note then as well, agree for need for publication

<anssik> http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r1=1.6;r2=1.7;f=h

<anssik> allow concurrent invocations in different browsing contexts (ACTION-652)

anssik: this is another change

<scribe> ACTION: anssik to update Vibration spec with note related o ISSUE-149 and update status section to list changes since last CR publication [recorded in http://www.w3.org/2014/01/09-dap-minutes.html#action01]

<trackbot> Created ACTION-673 - Update vibration spec with note related o issue-149 and update status section to list changes since last cr publication [on Anssi Kostiainen - due 2014-01-16].

<scribe> ACTION: fjh to open CfC for LC publication of Vibration [recorded in http://www.w3.org/2014/01/09-dap-minutes.html#action02]

<trackbot> Created ACTION-674 - Open cfc for lc publication of vibration [on Frederick Hirsch - due 2014-01-16].

Ambient Light

fjh: Do we have a resolution of question whether to merge light level event into LightEvent and rename, http://lists.w3.org/Archives/Public/public-device-apis/2013Apr/0043.html ?
... is this resolved?

anssik: working on implementation and then can send in feedback in next few months

fjh: can we publish update now or wait for implementation

anssik: should wait for implementation feedback

fjh: ok, this will impact the schedule, makes sense, but does move the schedule out

anssik: yes, will double check on implementation plans

Network Information API

Marcos has proposal, http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0013.html

fjh: I suggest we should have further list discussion on this, but wanted to bring to your attention

anssi: having connection type is useful

… this proposal could accommodate different levels of abstraction, so this might work

fjh: we have a detailed issue yet are discussing higher level concerns, thus suggest closing the issue

ISSUE-128?

<trackbot> ISSUE-128 -- Need more description on how bandwidth should be estimated -- open

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

fjh: once we have a detailed proposal we could raise new issues

dom: maybe wait until we decide to move to Marcos proposal, if we do. If we do change to that proposal then this can be closed

Testing

fjh: any updates?

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

anssik: test suites have been updated

fjh: if there are any significant changes please send a summary to the DAP list

anssik: Pull request for HTML Media Capture test is waiting for review

<scribe> ACTION: anssik to send update on test status, pull requests on the DAP public list [recorded in http://www.w3.org/2014/01/09-dap-minutes.html#action03]

<trackbot> Created ACTION-675 - Send update on test status, pull requests on the dap public list [on Anssi Kostiainen - due 2014-01-16].

fjh: it would be very helpful to summarize the status, what is missing, and which pull requests need review

Roadmap planning

fjh: good to understand what we are trying to do and when

Review of plans for DAP WG and specifications on home page

roadmap on home page: http://www.w3.org/2009/dap/#roadmap

we have six specs not in TF: battery, html media capture, network information, light, proximity, vibration, network service discovery

stable CR with test work: battery, html media capture, proximity

revisions requiring LC/CR: light, vibration

<scribe> new: network information

<scribe> new: network service discovery

anssik: battery implementation has work in chromium so this is helpful

fjh: not sure of timing but perhaps we can move Battery to REC by summer?

<dom> anssik, re battery in Chromium, could you add a ref in http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API ?

fjh: html media capture, proximity need test cases and implementation
... Note - Network Service Discovery overview (with Rich) for Privacy Interest Group (PING) scheduled at next PING teleconference, 30 January 2014 9 am PT/noon ET, see http://lists.w3.org/Archives/Public/public-privacy/2013OctDec/0036.html

WebAppSec call to be scheduled for Network Service Discovery http://www.w3.org/2011/webappsec/

<anssik> Intent to Implement: Battery Status API in Chromium -> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/fzoG6Phr09k

fjh: for network service discovery PING call will be to give an overview, then we can expect privacy feedback subsequently
... expect we need to publish an updated WD of Network Service discovery once RIch is available, maybe end Jan//Feb
... network information has active discussion on list, new proposal from Marcos, please review and join in
... plan is to persistently work to drive this work forward, but we have limited control over implementations so cannot accurately predict a schedule

dom: we need to think ahead about implementation reports and test reports and to get test results from implementations
... we also need to make sure we review implementation results to determine if problems are bugs in implementations or spec problems

<anssik> updated http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API

fjh: we don't have completed test cases for most, but for battery we do so we should focus on battery first to see have this right

Issue Review

fjh: trying to get focus and reduce number of open issues

anssik: once we have implementations we can get more tests and feedback

fjh: most issues are Network Service Discovery, will defer discussion
... Postponed issues are deferred until a subsequent v.next publication (e.g. after the upcoming REC)

<dom> dom: "postponed" can mean whatever we want (since that's not a w3c process defined term)

<dom> ... but I agree this is how I would interpret it

fjh: yes, I want to be clear how i am using it - to defer to next release.

please review postponed issues and note on list if any concern/disagreement: http://www.w3.org/2009/dap/track/issues/postponed

fjh: most are contacts or messaging, so no longer relevant. A number of vibration issues however

Agenda

ACTION-671?

<trackbot> ACTION-671 -- Anssi Kostiainen to Prepare shelved note publications after tpac http://lists.w3.org/Archives/Public/public-device-apis/2013Nov/0010.html -- due 2013-11-14 -- PENDINGREVIEW

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

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-666?

<trackbot> ACTION-666 -- Giridhar Mandyam to Check with internal implementers whether vibration api is consistent with chip capabilities -- due 2013-10-17 -- OPEN

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

fjh: actions from today:

ACTION-673?

<trackbot> ACTION-673 -- Anssi Kostiainen to Update vibration spec with note related o issue-149 and update status section to list changes since last cr publication -- due 2014-01-16 -- OPEN

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

ACTION-674?

<trackbot> ACTION-674 -- Frederick Hirsch to Open cfc for lc publication of vibration -- due 2014-01-16 -- OPEN

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

ACTION-675?

<trackbot> ACTION-675 -- Anssi Kostiainen to Send update on test status, pull requests on the dap public list -- due 2014-01-16 -- OPEN

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

<scribe> ACTION: fjh to contact W3C Comm team regarding sharing status of shelved documents without news item [recorded in http://www.w3.org/2014/01/09-dap-minutes.html#action04]

<trackbot> Created ACTION-676 - Contact w3c comm team regarding sharing status of shelved documents without news item [on Frederick Hirsch - due 2014-01-16].

Other Business

none

- DRAFT -

Device APIs Working Group Teleconference

09 Jan 2014

Attendees

Contents