W3C

- DRAFT -

Device APIs Working Group Teleconference

11 Dec 2014

Agenda

See also: IRC log

Attendees

Present
fjh, mats, dom, gmandyam, Frederick_Hirsch, Mats_Wichmann, Dominique_Hazael-Massieux, Giri_Mandyam
Regrets
Anssi_Kostiainen
Chair
Frederick_Hirsch
Scribe
fjh

Contents


<trackbot> Date: 11 December 2014

Welcome, agenda review, scribe selection, announcements

<scribe> ScribeNick: fjh

Media Capture Task Force CfC "Adopt new W3C process for Media Capture documents”

http://lists.w3.org/Archives/Public/public-device-apis/2014Dec/0001.html

Battery API

Battery API CR draft published: http://lists.w3.org/Archives/Public/public-device-apis/2014Dec/0004.html

“This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 03 February 2015"

Vibration API

Vibration API PR draft published: http://lists.w3.org/Archives/Public/public-device-apis/2014Dec/0003.html

Comments through 20 January 2015 fjh: will any additional steps be needed to progress to REC if no concerns expressed dom: no, it should be straightforward

Minutes approval

Approve minutes from 13 November 2014 (v2)

http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/att-0016/minutes-2014-11-13.html

RESOLUTION: Minutes from13 November 2014 are approved

Generic Sensor API

follow up - http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/0018.html

fjh: a number of issues on github for follow up

https://github.com/w3c/sensors

fjh: follow up needed re Tim Volodine and Boris Smus joining WG?
... presumably they need to initiate request to join

defer discussion for when we have participants, take to list

Cordova Update

fjh: Lisa not on call. defer.

Charter renewal

fjh: is this just happening

dom: have requested 1 year extension

… we previously discussed rechartering, but with no new work recently, extensibiiltiy mechanism not needed in short term

… simplest to extend current charter

… prefer to avoid full rechartering unless needed

fjh: is extension approved

dom: director reviews and approved, plan for review and approval next week

fjh: we will get a notice

dom: yes

fjh: expectation for new work?

dom: nothing firm but possibilities

Wake lock API

http://w3c.github.io/wake-lock/

see also use cases document http://w3c-webmob.github.io/wake-lock-use-cases/

gmandyam: what is permissions model

… cannot expose across 3rd parties

dom: model is that by default that all can do, but notification to user that screen is being locked

… model is ask for forgiveness model

gmandyam: do not like this model

… web sites can dramatically impact power consumption

dom: any app can do this today, via javascript

… timely for you to disagree, but there has been a discussion

gmandyam: not sure we’ve agreed to bring work into the group

dom: discussed, agreed we do not need to recharter

… if and when we recharter we would add explicitly to charter, but agreed to interpret charter to include this work item

… if you disagree then we need to know so we can got throught the rechartering process

gmandyam: we only have one browser committed to this

dom: two

gmandyam: will check on technical concerns regarding power consumption

dom: levels of disagreement: charter, useful for web, specifics of proposal

… need to be clear on which level of disagreement

gmandyam: are we going to progress the work or not, will got with it being in the charter and having implementer support

… need explicit decision to adopt editors draft

dom: push to FPWD would explicitly resolve decisions about progressing, considering in charter and enable call for exclusion

gmandyam: no decsions yet

dom: we have decision to get proposal in shape to enable FPWD decision

fjh: notes that FPWD triggers IPR obligations hence concern about scope, so want to know what will be in FPWD

gmandyam: would like to see dated version

dom: would want CfC for FPWD noting frozen version

fjh: how long a CfC suffices

gmandyam: a month is enough
... no need to revisit charter concerns, so now only concerned about CfC and FPWD

fjh: will ask editors if draft in github is FPWD material

<scribe> ACTION: fjh to check with wake lock editors on stability and suitability for FPWD on wake lock api [recorded in http://www.w3.org/2014/12/11-dap-minutes.html#action01]

<trackbot> Created ACTION-724 - Check with wake lock editors on stability and suitability for fpwd on wake lock api [on Frederick Hirsch - due 2014-12-18].

Other APIs

Network Service Discovery http://www.w3.org/TR/2014/WD-discovery-api-20140220/

fjh: any other APIs to discuss?

Network Service Discovery still under discussion, not clear it will be progressed or not

Issues and Actions

action-712?

<trackbot> action-712 -- Dominique Hazaël-Massieux to Look into chartering extensibility -- due 2014-12-01 -- OPEN

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

dom: extending deadline for when extension expires

<gmandyam> ATSC concluded that they would adopt the HbbTV approach to local network content dist.'n (based on technologies such as DIAL), and the NSD API is not necessary

ACTION-723?

<trackbot> ACTION-723 -- Zhiqiang Zhang to Add test for user denial of captured file leading to no capture -- due 2014-10-09 -- OPEN

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

dom: for HTML Media Capture which is in CR; need to double check

<scribe> ACTION: fjh to follow up with Zhiquiang re ACTION-723 [recorded in http://www.w3.org/2014/12/11-dap-minutes.html#action02]

<trackbot> Created ACTION-725 - Follow up with zhiquiang re action-723 [on Frederick Hirsch - due 2014-12-18].

ACTION-721?

<trackbot> ACTION-721 -- Dominique Hazaël-Massieux to Check on call-in access to tpac plenary day breakout sessions, e.g. web api for health care sensors, next steps for web of things -- due 2014-10-09 -- PENDINGREVIEW

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

close ACTION-721

<trackbot> Closed ACTION-721.

action-722?

<trackbot> action-722 -- Frederick Hirsch to Follow up on inviting bluetooth cg presentation at breakout -- due 2014-10-09 -- OPEN

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

close ACTION-722

<trackbot> Closed ACTION-722.

fjh: only one issue that is not network discovery

ISSUE-170?

<trackbot> ISSUE-170 -- light levels are not retrievable until a change causes the devicelight event to fire. -- open

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

ISSUE-170: under discussion as part of generic sensor API discussion, http://lists.w3.org/Archives/Public/public-device-apis/2014Nov/att-0016/minutes-2014-11-13.html#item05

<trackbot> Notes added to ISSUE-170 light levels are not retrievable until a change causes the devicelight event to fire..

fjh: actually might be better to create new generic sensor api product and associate, will do that

s/will fjh: defer issue//

dom: can expect more involvement in generic sensor api once we have more concrete proposals

Other Business

<dom> +1 on canceling Jan 8

RESOLUTION: cancel 8 Jan teleconference, next teleconference will be 22 January

Adjourn

’s/will defer issue//‘d

a/Topic: Other Business/fjh: cancel 8 Jan?

a/defer discussion/fjh: defer discussion/

Summary of Action Items

[NEW] ACTION: fjh to check with wake lock editors on stability and suitability for FPWD on wake lock api [recorded in http://www.w3.org/2014/12/11-dap-minutes.html#action01]
[NEW] ACTION: fjh to follow up with Zhiquiang re ACTION-723 [recorded in http://www.w3.org/2014/12/11-dap-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2014/12/11 15:49:01 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/NSD/Network Service Discovery/
Succeeded: s/will defer issue//
FAILED: s/will defer issue//
Succeeded: s/Comments through 20 January 2015/Comments through 20 January 2015 fjh: will any additional steps be needed to progress to REC if no concerns expressed dom: no, it should be straightforward/
Succeeded: s/a number of issues on github for follow up/fjh: a number of issues on github for follow up/
Succeeded: s/follow up needed re Tim Volodine and Boris Smus joining WG?/fjh: follow up needed re Tim Volodine and Boris Smus joining WG?/
Succeeded: s/presumably/fjh: presumably/
Succeeded: s/defer/fjh: defer/
Succeeded: s/Lisa/fjh: Lisa/
Succeeded: s/for HTML Media Capture/dom: for HTML Media Capture/
Succeeded: s/extending deadline/dom: extending deadline/
Succeeded: s/only one i/fjh: only one i/
Succeeded: s/actually/fjh: actually/
Found ScribeNick: fjh
Inferring Scribes: fjh
Default Present: fjh, mats, dom, gmandyam
Present: fjh mats dom gmandyam Frederick_Hirsch Mats_Wichmann Dominique_Hazael-Massieux Giri_Mandyam
Regrets: Anssi_Kostiainen
Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2014Dec/0005.html
Found Date: 11 Dec 2014
Guessing minutes URL: http://www.w3.org/2014/12/11-dap-minutes.html
People with action items: fjh

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


[End of scribe.perl diagnostic output]