W3C

Device APIs Working Group Teleconference

16 Jan 2014

Agenda

See also: IRC log

Attendees

Present
Frederick_Hirsch, Mats_Wichmann, Anssi_Kostiainen, Cathy_Chan, Lisa_DeLuca, JeanClaude_Dufourd, Rich_Tibbett, Dominique_Hazael-Massieux, Giri_Mandyam
Regrets
Chair
Frederick_Hirsch
Scribe
fjh

Contents


<trackbot> Date: 16 January 2014

<scribe> ScribeNick: fjh

Welcome, agenda review, announcements

Shelving notes published, see http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0025.html

Minutes approval

Approve minutes from 9 January 2014

http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/att-0015/minutes-2014-01-09.html

RESOLUTION: Minutes from 9 January 2014 are approved

Network Information API

Marcos proposal and Fernando proposal, http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0020.html

fjh: marcos note on next step. http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0027.html

anssik: mozilla and google waiting for each other

… no consensus yet whether feature will land, discussion last Nov/Dec

fjh: anything we can do

anssik: not much, keep on table

fjh: there appears to be momentum on the list
... Fingerprinting issue discussion, general use of "events only fired at top level browsing context Window object" language?

Testing

anssik: just sent an update to close action

<anssik> http://lists.w3.org/Archives/Public/public-device-apis/2014Jan/0028.html

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

anssik: details are in the message, might have some new QA support as well

close ACTION-675

<trackbot> Closed ACTION-675.

Network Service Discovery

fjh: Scheduled review with Privacy Interest Group (PING) (with Rich) 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/

richt: published last 24 Sept, some changes in spec since then, around security, privacy considerations, adopted CORS model

… there are open issues listed in agenda, need to review those

… hasn't been much recent discussion

fjh: do we need to publish an updated WD

richt: lets clarify on call next week, probably

cathy: we need Rich's view on the issues listed in the agenda so that we can discuss

richt: decisions on issues should be based on implementation experience

… might need some clarification of some of them

… discussions going on elsewhere

… we could tweak, but need to make sure of security and privacy, came up in chromium review and elsewhere

<dom> +1 on figuring out the security model as being primordial right now

… in current state it is implementable, would like to document what is going on

fjh: I think Jean Claude had feedback that has not been addressed

jdufourd: yes, we had agreement with Cathy and some items

… completely agree that making sure it is acceptable from security perspective, that is a priority

… some changes proposed have little impact on this aspect

… so should still consider

… question, when you talk about implementation, what does this mean, Opera implementation of 1 1/2 year ago

… my java proxy implementation

… this is up to date with draft I believe

… what other implementation should we know about

richt: chrome extension

… missing UI side

… opt-in

… switched engines on our work, so need to rework code, but need more focus on UI

jcdufourd: UI not part of standard

richt: yes but important

… believe we have discussed most of issues in agenda, I've presented view, not clear what to do, wait for implementations

fjh: can we work through some of the issues without waiting, if we can
... can we invite someone from Chromium to join PING call to share issues with PING

richt: cannot say if they can join

fjh: we had review of CORS

richt: we had review of Promises

fjh: will follow up on various reviews

richt: if you are interested in this it would be helpful if you would lobby your favorite browser vendor

<scribe> ACTION: fjh to follow up with WebAppSec and CORs review of Network Service Discovery [recorded in http://www.w3.org/2014/01/16-dap-minutes.html#action01]

<trackbot> Created ACTION-677 - Follow up with webappsec and cors review of network service discovery [on Frederick Hirsch - due 2014-01-23].

Vibration API

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

gmandyam: did not get answer still looking into it

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

<dom> [I didn't send this to public-device-apis, but people in the group might find interesting/entertaining my review of API permissions: http://lists.w3.org/Archives/Public/public-web-mobile/2014Jan/0001.html ]

dom: sent report to look at consistency across permissions

fjh: can you please share this with PING

dom: I think you can

fjh: ok

anssik: can you please share with sysapps

Other Business

fjh: Reminder, no call next week. Next call in two weeks, 30 January. Lets discuss on list, goal to be able to decide to publish update of Network Security Discovery.

Adjourn

Summary of Action Items

[NEW] ACTION: fjh to follow up with WebAppSec and CORs review of Network Service Discovery [recorded in http://www.w3.org/2014/01/16-dap-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009-03-02 03:52:20 $