IRC log of dap on 2015-10-15

Timestamps are in UTC.

13:43:33 [RRSAgent]

RRSAgent has joined #dap

13:43:33 [RRSAgent]

logging to http://www.w3.org/2015/10/15-dap-irc

13:43:35 [trackbot]

RRSAgent, make logs world

13:43:35 [Zakim]

Zakim has joined #dap

13:43:37 [trackbot]

Zakim, this will be DAP

13:43:37 [Zakim]

I do not see a conference matching that name scheduled within the next hour, trackbot

13:43:38 [trackbot]

Meeting: Device APIs Working Group Teleconference

13:43:38 [trackbot]

Date: 15 October 2015

13:47:12 [fjh]

Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0023.html

13:47:25 [fjh]

fjh has changed the topic to: dap agenda https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0023.html webex passwd "dap"

13:47:54 [fjh]

Chair: Frederick_Hirsch

13:47:57 [fjh]

Present+ Frederick_Hirsch

13:48:10 [fjh]

Topic: Welcome, scribe selection, agenda review, announcements

13:59:06 [lukasz]

Good morning.

14:01:49 [lukasz]

yes, sorry (I realized this)

14:01:57 [lukasz]

Present+ Lukasz_Olejnik

14:02:07 [dom]

Present+ Dominique_Hazael-Massieux

14:02:20 [anssik]

anssik has joined #dap

14:02:33 [anssik]

Present+ Anssi_Kostiainen

14:02:40 [anssik]

zakim, who's on the call

14:02:40 [Zakim]

I don't understand 'who's on the call', anssik

14:02:46 [anssik]

zakim, who is on the call?

14:02:46 [Zakim]

Present: Frederick_Hirsch, Lukasz_Olejnik, Dominique_Hazael-Massieux, Anssi_Kostiainen

14:03:48 [anssik]

scribeNick: anssik

14:03:58 [fjh]

Results of Vote on Media Capture and Streams Constraints Registry - https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0021.html

14:03:58 [fjh]

Web Platform WG replaces WebApps WG, http://www.w3.org/2015/10/webplatform-charter.html

14:04:11 [anssik]

fjh: vote on the mediacapture-main went through

14:04:18 [anssik]

... Web Platform WG is the new WebApps WG

14:04:31 [anssik]

Topic: Minutes approval

14:04:33 [fjh]

Approve minutes from 1 Oct 2015

14:04:34 [fjh]

proposed RESOLUTION: Minutes from 1 Oct 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/att-0000/minutes-2015-10-01.html

14:04:48 [anssik]

RESOLUTION: Minutes from 1 Oct 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/att-0000/minutes-2015-10-01.html

14:04:55 [anssik]

Topic: Charter

14:04:59 [fjh]

https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0022.html

14:05:27 [anssik]

dom: integrated changes to the charter drafy

14:05:34 [anssik]

s/drafy/draft/

14:05:58 [anssik]

... going through renewal process, W3C mgmt approval, AC review, before that three week CfC

14:06:09 [anssik]

... some changes may be controversial:

14:06:23 [anssik]

... 1) New Document and Software License enabling forking

14:06:39 [anssik]

... 2) Expedited process for adding new deliverables to the charter

14:07:18 [anssik]

... 3) Streamlining the existing deliverables list, remove inactive work, only exception being NetInfo API which has implementations

14:07:54 [anssik]

... 4) Use of asynchronous decision policy

14:08:04 [anssik]

fjh: does 4 mean we do not need to do CfCs?

14:08:24 [anssik]

dom: formally speaking we could do that, but better do explicit CfCs

14:09:10 [tobie]

Present+ Tobie_Langel

14:10:07 [anssik]

dom: expedited process means we can update the charter with a new deliverable, and the W3C mgmt and AC review only

14:11:38 [fjh]

zakim, slap dom

14:11:38 [Zakim]

I don't understand 'slap dom', fjh

14:11:43 [lukasz]

just continue here.

14:14:00 [lukasz]

(I am not in WebEx)

14:14:32 [fjh]

s/(I am not in WebEx)//

14:15:20 [anssik]

fjh: propose a two week CfC for the new charter

14:15:56 [fjh]

proposed RESOLUTION: proceed with two week CfC for WG to approve proceeding with draft Charter distributed by Dom

14:16:27 [anssik]

RESOLUTION: proceed with two week CfC for WG to approve proceeding with draft Charter distributed by Dom

14:17:52 [fjh]

two questions I raised privately re charter - 1) should group name change, eg Device APIs and Sensors (DAS)

14:20:16 [fjh]

changing name can reflect change of the scope of the work of the group, a new focus, help others understand where this work is done

14:20:27 [fjh]

makes it easier to market what is done

14:21:12 [fjh]

dom: bluetooth won't move here, question about NFC still

14:23:49 [fjh]

Sensors and media - SAM

14:24:37 [fjh]

it should have the word Sensor in it

14:24:51 [fjh]

suggest CfC is with understanding with group name could change

14:25:19 [fjh]

Device Platform

14:26:24 [fjh]

Device Sensor Platform

14:28:24 [anssik]

Device APIs and Sensors Working Group (DAS WG)

14:28:57 [fjh]

why not "Device and Sensors Working Group"

14:29:57 [fjh]

proposed RESOLUTION: use "Device and Sensors Working Group" in propose charter

14:30:32 [fjh]

s/propose/proposed/

14:30:43 [anssik]

RESOLUTION: use "Device and Sensors Working Group" in proposed charter

14:30:49 [fjh]

will include that in CfC

14:31:48 [anssik]

Topic: Web Intents Task Force

14:31:50 [fjh]

Status and plans for Web Intents Task Force (was joint with WebApps but not mentioned in Web Platform charter)

14:31:58 [dom]

[on the topic of Web Intents like discussion, it's restarting again :) http://www.backalleycoder.com/2015/10/13/app-to-app-interaction-apis/ ]

14:32:00 [anssik]

fjh: suggest we close the TF

14:32:06 [anssik]

... not on the Web Platform WG charter

14:33:27 [anssik]

dom: some blog posts on the topic published recently, regardless should pursue with closing

14:33:37 [fjh]

action: fjh to send CfC for 2 week approval of progressing with charter and name change

14:33:37 [trackbot]

Created ACTION-739 - Send cfc for 2 week approval of progressing with charter and name change [on Frederick Hirsch - due 2015-10-22].

14:33:51 [fjh]

action: fjh to send CfC to close Web Intents TF

14:33:51 [trackbot]

Created ACTION-740 - Send cfc to close web intents tf [on Frederick Hirsch - due 2015-10-22].

14:33:55 [lukasz]

+1

14:34:02 [anssik]

Topic: Generic Sensor API

14:34:13 [anssik]

fjh: FPWD published today, thanks Tobie

14:34:18 [fjh]

WebI2C and WebGPIO https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0015.html

14:34:59 [anssik]

tobie: would like to talk to Rick re the WebI2C and WebGPIO

14:35:41 [anssik]

... Rick seems to be opposing this low-level APIs, and prefers to see Bluetooth and Serial APIs for the Web instead

14:36:55 [anssik]

... a major issue is the security model that is different from the Web's

14:37:13 [anssik]

... nevertheless, an interesting area to explore

14:37:54 [fjh]

breakout session

14:38:35 [fjh]

http://www.w3.org/wiki/TPAC/2015/SessionIdeas#WebGPIO.2C_WebI2C_API

14:39:39 [anssik]

fjh: would be interesting to see the proceedings from the breakout session, please report back

14:40:06 [anssik]

tobie: I was starting to work on the proximity API to see if I can rewrite it on top of Generic Sensor API

14:40:23 [anssik]

... some sensors would like to get data out at regular intervals

14:40:34 [anssik]

... for some sensors, only when the change happens

14:40:46 [anssik]

... e.g. geolocation

14:41:03 [anssik]

... for device location will want to get low latency

14:41:24 [anssik]

... in Android, different API for different type of sensors

14:41:33 [anssik]

... wondering how to handle that in the Generic Sensor API

14:41:58 [anssik]

... should we have two different Generic Sensor APIs to cater for both cases?

14:42:00 [fjh]

q+

14:42:05 [anssik]

q+

14:42:23 [fjh]

ack anssik

14:42:45 [fjh]

anssik: ambient light might be better one to start with for modeling on top of generic sensor API

14:43:09 [fjh]

anssik: we have code

14:43:20 [fjh]

anssik: many platforms use ambient light to implement proximity

14:43:50 [fjh]

q-

14:44:14 [fjh]

q+ to mention that both use cases are important, regular reporting and exception reporting, how to design open

14:44:38 [fjh]

tobie: this is like a higher level sensor then

14:44:55 [fjh]

i/ambient light might/ScribeNick: fjh

14:45:10 [fjh]

ScribeNick: anssik

14:45:20 [anssik]

https://w3c.github.io/ambient-light/

14:46:05 [lukasz]

I'm currently in the process of writing a little doc on possible privacy issues in a bunch of APIs, starting to arrive on possibly interesting constructs/arguments [still I keep it at a far side in order not to interfer with the group's work/jeopardize anything] - hopefully will be of use

14:46:35 [anssik]

https://w3c.github.io/proximity/

14:47:05 [lukasz]

I will try to minimize noise and report only when it has taken shape, then possibly ask for input, CC with PING group as well - perhaps a blueprint for privacy considerations will emerge + other avenues of work

14:47:07 [fjh]

s/code/experimental/

14:47:10 [fjh]

q?

14:47:12 [fjh]

ack fjh

14:47:12 [Zakim]

fjh, you wanted to mention that both use cases are important, regular reporting and exception reporting, how to design open

14:47:25 [anssik]

scribeNick: anssik

14:47:40 [anssik]

fjh: both use cases are important, regular reporting and exception reporting, how to design open

14:48:00 [anssik]

fjh: propose both should be in the same spec

14:48:18 [anssik]

tobie: solved a bunch of issues, some issues still open

14:48:26 [anssik]

... that need to be added to the spec

14:48:38 [anssik]

... want to have issues triaged by TPAC

14:49:03 [anssik]

+1

14:49:09 [anssik]

+1 for echidna

14:49:36 [anssik]

dom: I can help setup echidna at TPAC

14:49:44 [fjh]

support using auto-WD publication for generic sensor API

14:51:11 [anssik]

Topic: Upcoming meetings

14:51:19 [anssik]

fjh: no meeting at TPAC

14:51:23 [fjh]

http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences

14:51:28 [dom]

s/at and during/

14:51:50 [anssik]

Upcoming Teleconferences

14:51:50 [anssik]

15 October 2015, agenda

14:51:50 [anssik]

29 October 2015, cancelled (TPAC)

14:51:50 [anssik]

12 November 2015, agenda

14:51:50 [anssik]

26 November 2015, Cancelled (US Thanksgiving)

14:51:50 [anssik]

10 December 2015, agenda

14:51:50 [anssik]

24 December 2015, Cancelled (Christmas)

14:51:52 [anssik]

7 January 2015, agenda

14:53:20 [fjh]

can we move the 10th Dec to the 3rd Dec

14:53:26 [fjh]

everyone on call ok with it

14:53:32 [fjh]

me lukasz ?

14:53:50 [lukasz]

+1

14:54:33 [fjh]

proposed RESOLUTION: Cancel call on 10th Dec, schedule call 3 De

14:54:44 [fjh]

s/De/Dec/

14:54:53 [anssik]

RESOLUTION: Cancel call on 10th Dec, schedule call 3 Dec

14:55:35 [fjh]

Topic: Other Business

14:55:36 [fjh]

none

14:55:40 [fjh]

Topic: Adjourn

14:55:45 [fjh]

rrsagent, generate minutes

14:55:45 [RRSAgent]

I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh

14:58:32 [fjh]

s/yes, sorry (I realized this)//

14:58:55 [fjh]

s/Good morning.//

14:59:41 [fjh]

s/experimental/experimental code/

15:00:25 [fjh]

s/triaged by TPAC/triaged by TPAC; can we use the auto WD publication mechanism for generic sensor API/

15:00:41 [fjh]

s/support using/I support using/

15:00:58 [fjh]

s/me lukasz ?//

15:01:08 [fjh]

rrsagent, generate minutes

15:01:08 [RRSAgent]

I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh

15:02:44 [fjh]

s/no meeting at TPAC/no DAP meeting at TPAC, but there will be related ad hoc and break out sessions/

15:03:10 [fjh]

rrsagent, generate minutes

15:03:10 [RRSAgent]

I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh

15:04:09 [lukasz]

s/just continue here./

15:04:31 [fjh]

rrsagent, generate minutes

15:04:31 [RRSAgent]

I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh

15:07:53 [fjh]

http://www.w3.org/2008/xmlsec/Group/Scribe-Instructions.html

16:03:56 [mats]

mats has joined #dap

17:01:15 [Zakim]

Zakim has left #dap