IRC log of dap on 2016-03-03

Timestamps are in UTC.

14:53:34 [RRSAgent]
RRSAgent has joined #dap
14:53:34 [RRSAgent]
logging to http://www.w3.org/2016/03/03-dap-irc
14:53:36 [trackbot]
RRSAgent, make logs world
14:53:36 [Zakim]
Zakim has joined #dap
14:53:38 [trackbot]
Zakim, this will be DAP
14:53:38 [Zakim]
I do not see a conference matching that name scheduled within the next hour, trackbot
14:53:39 [trackbot]
Meeting: Device APIs Working Group Teleconference
14:53:39 [trackbot]
Date: 03 March 2016
14:53:42 [fjh]
fjh has changed the topic to: dap https://lists.w3.org/Archives/Public/public-device-apis/2016Mar/0001.html
14:53:47 [fjh]
Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2016Mar/0001.html
14:54:05 [fjh]
Chair: Frederick_Hirsch
14:54:16 [fjh]
Present+ Frederick_Hirsch
14:54:29 [fjh]
Topic: Welcome, scribe selection, agenda review, announcements
14:54:58 [fjh]
Present+ Dominique_Hazael-Massieux
15:01:16 [dom]
ScribeNick: dom
15:01:40 [Andrey_Logvinov]
Present+ Andrey_Logvinov
15:04:58 [fjh]
Topic: Minutes Approval
15:05:07 [tobie]
+Tobie_Langel
15:05:09 [fjh]
Approve minutes from 18 Feb 2016
15:05:10 [fjh]
proposed RESOLUTION: Minutes from 18 Feb 2016 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/att-0065/minutes-2016-02-18.html
15:05:28 [anssik]
anssik has joined #dap
15:05:30 [fjh]
rrsagent, generate minutes
15:05:30 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/03/03-dap-minutes.html fjh
15:05:41 [anssik]
Present+ Anssi_Kostiainen
15:05:51 [tobie]
s/+Tobie_Langel//
15:05:56 [dom]
RESOLUTION: Minutes from 18 Feb 2016 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/att-0065/minutes-2016-02-18.html
15:06:03 [tobie]
Present+ Tobie_Langel
15:06:06 [fjh]
Topic: Battery Status API
15:06:17 [fjh]
Steps for transition from CR to PR: https://lists.w3.org/Archives/Public/public-device-apis/2016Mar/0000.html
15:06:17 [fjh]
Review of test case and implementation status, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/0073.html
15:06:29 [dom]
FJH: we plan to go to PR, have been looking at the transition request
15:06:34 [dom]
... we need an implementation report
15:06:38 [dom]
... not sure what we have is suitable
15:06:48 [fjh]
https://www.w3.org/2009/dap/wiki/ImplementationStatus
15:07:14 [dom]
[https://w3c.github.io/test-results/battery-status/20160226.html is our Implementation report]
15:07:29 [fjh]
https://zqzhang.github.io/blog/2016/02/18/testing-battery-status-api.html
15:07:51 [dom]
[https://w3c.github.io/test-results/battery-status/20160226.html
15:08:21 [fjh]
so we will use this as test report
15:08:27 [dom]
Dom: I think we should start with https://w3c.github.io/test-results/battery-status/20160226.html as our implementation report
15:08:51 [dom]
... it's linked from https://www.w3.org/2009/dap/wiki/ImplementationStatus
15:10:08 [fjh]
for PR draft we should like to the results for implementation report, https://w3c.github.io/test-results/battery-status/20160226.html
15:10:09 [dom]
... we'll probably want to link to that specific document in our PR
15:10:23 [fjh]
anssik, please make note that in PR draft we need to change link for implementation report, see above
15:10:38 [anssik]
please open an issue for me
15:11:26 [fjh]
issue: anssik update PR draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html
15:11:26 [trackbot]
Created ISSUE-172 - Anssik update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html. Please complete additional details at <http://www.w3.org/2009/dap/track/issues/172/edit>.
15:12:00 [fjh]
issue: anssik to create PR publication draft, updating status section to note that there were no new issues since CR, that there were no features marked as at risk
15:12:00 [trackbot]
Created ISSUE-173 - Anssik to create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk. Please complete additional details at <http://www.w3.org/2009/dap/track/issues/173/edit>.
15:12:49 [fjh]
issue: anssik to put tentative date of 3 May 2016 in Battery PR draft
15:12:49 [trackbot]
Created ISSUE-174 - Anssik to put tentative date of 3 may 2016 in battery pr draft. Please complete additional details at <http://www.w3.org/2009/dap/track/issues/174/edit>.
15:13:13 [fjh]
anssik, any questions re preparing Battery PR
15:13:32 [fjh]
actioon: anssik to update PR draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html
15:13:44 [fjh]
action: anssik to update PR draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html
15:13:44 [trackbot]
Created ACTION-746 - Update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html [on Anssi Kostiainen - due 2016-03-10].
15:14:13 [fjh]
action: anssik to create PR publication draft, updating status section to note that there were no new issues since CR, that there were no features marked as at risk
15:14:13 [trackbot]
Created ACTION-747 - Create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk [on Anssi Kostiainen - due 2016-03-10].
15:14:45 [fjh]
action: Anssik to put tentative date of 3 may 2016 in battery pr draft
15:14:45 [trackbot]
Created ACTION-748 - Put tentative date of 3 may 2016 in battery pr draft [on Anssi Kostiainen - due 2016-03-10].
15:14:53 [fjh]
close issue-172
15:14:53 [trackbot]
Closed issue-172.
15:14:57 [fjh]
close issue-173
15:14:57 [trackbot]
Closed issue-173.
15:15:03 [fjh]
close issue-174
15:15:03 [trackbot]
Closed issue-174.
15:15:26 [fjh]
action: fjh to send transition request
15:15:26 [trackbot]
Created ACTION-749 - Send transition request [on Frederick Hirsch - due 2016-03-10].
15:16:02 [fjh]
Topic: Generic Sensor API
15:16:02 [dom]
Topic: Generic Sensor API
15:16:53 [dom]
Tobie: I'm progressing towards a complete level 1 version of the spec
15:17:17 [dom]
... I'm on the right track — I've found a model that fits the whole thing very well and lets me solve all but one issues
15:17:25 [dom]
... the one remaining issue is around permissioning
15:17:33 [dom]
... I've started rewriting ambient light based on generic sensor
15:17:41 [dom]
... this I'll complete over the next couple of days
15:17:58 [dom]
... my aim would be to have versions ready by mid next week for publication the week after
15:18:11 [dom]
fjh: we would need a cfc
15:18:23 [dom]
tobie: that makes sense for ambient light; I don't think we need it for generic sensor
15:18:31 [dom]
... since we have agreement for automatic update of that doc
15:18:44 [dom]
fjh: you're right
15:18:53 [dom]
tobie: but yeah, we should do a cfc for ambient light
15:19:30 [dom]
... the other thing I'm going to look at quickly is writing a spec for air pressure, altitude and barometer based on generic
15:19:40 [dom]
fjh: we first have to determine if it's in scope of the charter
15:20:31 [dom]
dom: not sure it would fit the charter as is
15:20:39 [dom]
... could you comment about why that sensor in particular?
15:20:54 [dom]
tobie: I understand Intel would be interested; it comes bundled with existing mobile devices
15:21:02 [dom]
... it should be easy to expose on top of the generic sensor
15:21:10 [dom]
... and would be a good showcase
15:21:58 [dom]
dom: ok; I think you could develop a proposal, but would likely need some more cycles before we can adopt it formally as a wg
15:22:01 [dom]
tobie: sure
15:22:12 [dom]
... it should be fairly easy to get a first draft up
15:22:28 [dom]
... there may be security or privacy issues I haven't thought of yet, but the technical aspects should be simple
15:22:54 [dom]
fjh: first step is to create a draft, and when we get our new charter, we figure the right next process steps
15:23:38 [dom]
tobie: in terms of implementations, riju has been hitting difficulties to a new layering system in chromium
15:25:56 [dom]
tobie: the basic idea is that a given physical sensor will not give guarantees on the actual frequency of data gathering, for a combination of fingerprinting and cross-app usage
15:26:07 [dom]
s/idea/idea of my new approach/
15:26:11 [fjh]
tobie: one physical sensor shared across origins and applications
15:26:16 [dom]
... it also matches how these things are exposed in underlying platforms
15:26:48 [dom]
tobie: the last problem is the permission stuff, linked to the unresolved issue in the permission spec
15:27:10 [dom]
... since I'm not getting traction, I'll keep it as a note in the spec
15:27:31 [dom]
Topic: Vibration API
15:27:37 [fjh]
PING teleconf discussion, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/0072.html
15:27:42 [dom]
FJH: there was a PING call on that API
15:27:58 [dom]
... Lukasz is working on a draft new section
15:28:06 [dom]
... the plan is to work on a Proposed Edited Rec for the API
15:28:22 [dom]
... the changes don't affect conformance, so we can use PER
15:29:02 [dom]
... 3 changes: errata incorporation, addition of Privacy & Sec section, maybe some A11Y change
15:30:47 [dom]
... actually, the A11Y aspect is part of the discussions around privacy & security, so taht's only 2 changes
15:30:49 [fjh]
https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/0081.html
15:31:17 [fjh]
Lukasz is creating draft security and privacy considerations section for Vibration API
15:31:35 [fjh]
action: lukasz to create draft security and privacy considerations section for Vibration API
15:31:35 [trackbot]
Created ACTION-750 - Create draft security and privacy considerations section for vibration api [on Lukasz Olejnik - due 2016-03-10].
15:32:26 [fjh]
process - 1. new editors draft with errata folded in and added security and privacy considerations (2) informal review with PING and others (3) PER process
15:33:29 [fjh]
action: anssik to prepare new Vibration editors draft including errata and security and privacy consideration material from Lukasz and others
15:33:30 [trackbot]
Created ACTION-751 - Prepare new vibration editors draft including errata and security and privacy consideration material from lukasz and others [on Anssi Kostiainen - due 2016-03-10].
15:33:38 [dom]
Topic: Wake Lock API
15:33:42 [fjh]
https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/att-0067/00-part
15:34:03 [dom]
FJH: we have a WD, we want to go to CR
15:34:15 [dom]
... so we should get wide review on our draft before asking transition to CR
15:34:55 [dom]
Dom: https://lists.w3.org/Archives/Public/public-device-apis/2016Mar/0006.html
15:35:18 [dom]
FJH: Andrey walked us through the issues and that the remaining ones are longer term
15:35:39 [dom]
Andrey: yes; addressing these issues would require a significant change to the spec
15:36:01 [dom]
... making these changes would invalidate the existing implementation in chromium
15:38:23 [dom]
Dom: I would say it depends on how likely these changes would affect take up from implementors
15:38:40 [dom]
fjh: I think we have decided to go with that version and get wide review from it
15:40:31 [fjh]
privacy & security questionnaire: https://w3ctag.github.io/security-questionnaire/
15:40:36 [dom]
... Andrey, could look into the seucrity questionnaire?
15:40:59 [dom]
Andrey: yes, I can
15:41:16 [dom]
Dom: since issue 56 is about "book reader use case", we should probably also ask the Digital Publishing IG for review
15:41:19 [fjh]
action: Andrey_Logvinov to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/
15:41:19 [trackbot]
Error finding 'Andrey_Logvinov'. You can review and register nicknames at <http://www.w3.org/2009/dap/track/users>.
15:41:35 [fjh]
action: andrey to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/
15:41:35 [trackbot]
Created ACTION-752 - to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/ [on Andrey Logvinov - due 2016-03-10].
15:41:45 [dom]
https://github.com/w3c/wake-lock/issues
15:43:44 [fjh]
process (1) Andrey to review security privacy questionnaire, (2) any WD updates if needed (3) Dom, Frederick to send request for review
15:44:15 [dom]
Andrey: will try to get that done in the upcoming week
15:44:20 [dom]
Topic: Meeting planning
15:44:25 [fjh]
Upcoming meetings, https://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences
15:44:29 [dom]
FJH: I'll be out for the next 2 calls
15:44:34 [dom]
... Dom will chair March 17
15:44:39 [dom]
... and we will cancel March 31st
15:44:46 [dom]
... we can do most of our work on the list in any case
15:45:41 [fjh]
Let’s cancel 31 March
15:45:49 [dom]
RESOLVED: no call on March 31st
15:45:53 [dom]
Topic: Charter update
15:46:36 [fjh]
dom: current charter expires at end of this month, working on issues with charter
15:46:36 [dom]
Dom: still working on the objection we received; hopefully all will get done before our extension expires at the end of this month
15:47:29 [dom]
RRSAgent, draft minutes
15:47:29 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/03/03-dap-minutes.html dom
15:47:39 [fjh]
Topic: Other Business
15:47:40 [fjh]
none
15:47:44 [fjh]
Topic: Adjourn
15:47:58 [fjh]
s/dom: current charter expires at end of this month, working on issues with charter//
15:48:20 [fjh]
Present+ Anssi_Kostiainen_(IRC)
15:48:23 [fjh]
Present- Anssi_Kostiainen
15:49:31 [fjh]
s/ taht/that/
15:49:41 [fjh]
s/sothat/so that/
15:49:59 [fjh]
rrsagent, generate mninutes
15:49:59 [RRSAgent]
I'm logging. I don't understand 'generate mninutes', fjh. Try /msg RRSAgent help
15:50:05 [fjh]
rrsagent, generate minutes
15:50:05 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/03/03-dap-minutes.html fjh
15:51:08 [fjh]
s/fjh: Let’s cancel 31 March//
15:51:18 [fjh]
rrsagent, generate minutes
15:51:18 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/03/03-dap-minutes.html fjh
15:53:00 [fjh_]
fjh_ has joined #dap
15:53:18 [fjh]
generate http://www.w3.org/2016/03/03-dap-minutes.html
15:59:07 [marcosc]
marcosc has joined #dap
17:47:53 [marcosc]
marcosc has joined #dap
18:10:52 [Zakim]
Zakim has left #dap
19:36:48 [marcosc]
marcosc has joined #dap
21:25:39 [marcosc]
marcosc has joined #dap
22:34:49 [fjh]
fjh has joined #dap
23:14:34 [marcosc]
marcosc has joined #dap